# EDI 835 Health Care Claim Payment/Advice (ERA)

> EDI 835 ERA explained: BPR, TRN, CLP, CAS, SVC and PLB segments, CO/PR/OA/PI group codes, CARC and RARC, balancing, and matching CLP01 to the 837.

<QuickAnswer>
The EDI 835 Health Care Claim Payment/Advice, or electronic remittance advice (ERA), is the HIPAA X12 transaction a health plan sends a provider to explain a payment. For each claim and service line it shows the billed, paid and adjusted amounts, with group codes (CO, PR, OA, PI), claim adjustment reason codes and remark codes explaining every difference.
</QuickAnswer>

**The EDI 835 is the explanation behind every health care payment.** A deposit lands in the practice's account for $4,812.37. The 835 says which claims that money covers, why each one paid less than billed, what the patient owes, and what the payer took back from earlier overpayments. Billing teams post payments from it, work denials from it and bill patients from it, so reading CAS segments correctly is a core billing skill.

This guide covers the 835's structure, every segment billing and health IT teams read, the claim adjustment group codes and reason codes, how the file balances, how to match an 835 claim back to the 837 that billed it, and a live example with a payment, a denial and a takeback. It explains the file format only. It is not billing, coding or legal advice; the payer's companion guide and your contracts govern how amounts are calculated.

<EDIGuideCTA
  transactionType="835"
  headline="Read an 835 claim by claim"
  body="Paste an 835 into the free EDI inspector to see each claim, service line and CAS adjustment broken out segment by segment, with envelope and control-number problems flagged."
/>

## What Is an EDI 835?

**An EDI 835 is the Health Care Claim Payment/Advice transaction set defined by [ASC X12](https://x12.org/products/transaction-sets), used by a health plan to send payment information and an explanation of each claim's adjudication to a provider or its billing agent.** It is the HIPAA standard for health care remittance advice. [45 CFR 162.1602](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-162/subpart-P/section-162.1602) names the X12 technical report `005010X221`, and files carry the errata version `005010X221A1` in `GS08` and `ST03`. The same section names the NACHA CCD+ format for the health care EFT that moves the money, with the 835's TRN reassociation trace number in the addenda record.

Authoritative references for 835 work:

- [45 CFR Part 162](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-162), administered by CMS, lists the HIPAA transaction standards, including the 835 and the EFT standard
- [X12's claim adjustment group codes](https://x12.org/codes/claim-adjustment-group-codes), [claim adjustment reason codes (CARC)](https://x12.org/codes/claim-adjustment-reason-codes) and [remittance advice remark codes (RARC)](https://x12.org/codes/remittance-advice-remark-codes) are the external code lists every CAS and LQ segment draws from. X12 publishes all three; its code list index shows the RARC list as maintained by CMS
- The [CMS Medicare 835 companion guide](https://www.cms.gov/medicare/billing/electronicbillingeditrans/downloads/5010a1835cg.pdf) shows how one large payer fills each element, including which codes Medicare does not use

**Who sends it?** The health plan, or a clearinghouse or payment vendor acting for it.

**Who receives it?** The payee named in loop 1000B: the provider, or a billing service or clearinghouse acting for it. Providers usually enroll for ERA with each payer before 835s start flowing.

**When is it sent?** With each payment cycle, alongside the EFT or check. One 835 covers one payment (or one notification) to one payee.

**Why does it matter?** The 835 is what posts payments, sets patient balances and starts denial follow-up. Misreading a CAS group code means billing a patient for an amount the provider was supposed to write off, or writing off an amount the patient actually owes.

## How Claim Payment and Remittance Works

1. **Provider bills.** The provider sends an [837 claim](/guides/edi/837-health-care-claim). `CLM01` carries its patient control number.
2. **Payer acknowledges.** A [999](/guides/edi/999-implementation-acknowledgment) confirms the file passed validation, and a 277CA claim acknowledgment says which claims were accepted into adjudication.
3. **Payer adjudicates.** Each line is priced against the contract or fee schedule, benefits are applied (deductible, coinsurance, copay), and edits run.
4. **Payer pays and explains.** The money moves by EFT (or check), and the 835 explains it. `TRN02` in the 835 matches the trace number in the EFT addenda so the two can be reassociated.
5. **Provider posts.** The billing system matches each `CLP01` back to the claim, posts payments and adjustments, moves patient responsibility to the patient's account, and queues denials.
6. **Follow-up.** Denied or underpaid claims are corrected and resent as replacement 837s, or appealed. Status questions in between go out as [276 claim status requests](/guides/edi/276-claim-status-request) and come back as [277 responses](/guides/edi/277-claim-status-response).

## Interactive Example: Payment, Denial and Takeback

A fictional health plan pays a fictional family practice for two claims and recovers an earlier overpayment:

- Claim `EFP26110301` (office visit plus rapid strep test, billed $160.00) is processed as primary. Each line is reduced to the contracted rate (`CO-45`) and the patient owes a $25.00 copay (`PR-3`). The plan pays $85.00.
- Claim `EFP26110288` (billed $95.00) is denied with `CO-204` (service not covered under the patient's current benefit plan) and remark `N130`.
- A `PLB` segment recovers a $40.00 overpayment on an earlier claim (`WO`).
- The check is for $85.00 minus $40.00 = **$45.00**.

The first claim's `CLP01` matches `CLM01` on the [837P sample in our 837 guide](/guides/edi/837-health-care-claim). All people, providers and IDs are fictional; NPI `1999999992` is a check-digit-valid test value.

<EDISample id="835-claim-payment-era" />

## 835 Structure at a Glance

| Loop | Segment | Name | Usage | Notes |
|---|---|---|---|---|
| Header | **ST** | Transaction Set Header | Required | `ST01` = `835`, `ST03` = `005010X221A1` |
| Header | **BPR** | Financial Information | Required | Total payment, method, bank details, payment date |
| Header | **TRN** | Reassociation Trace Number | Required | Check or EFT trace number, payer identifier |
| Header | **REF** | Receiver / Version Identification | Situational | Receiver ID, payer's local version |
| Header | **DTM** | Production Date | Required | When the payer produced the remittance |
| 1000A | **N1, N3, N4** | Payer Identification and Address | Required | `N101` = `PR` |
| 1000A | **PER** | Payer Contact | Required / Situational | Technical contact (`BL`) is required; business contact optional |
| 1000B | **N1, N3, N4** | Payee Identification and Address | Required | `N101` = `PE`, usually with NPI (`XX`) |
| 1000B | **REF** | Payee Additional Identification | Situational | Tax ID (`TJ`) and others |
| 2000 | **LX** | Header Number | Situational | Groups claims (for example by bill type) |
| 2100 | **CLP** | Claim Payment Information | Required, repeats | One per claim |
| 2100 | **CAS** | Claim Adjustment | Situational | Claim-level adjustments |
| 2100 | **NM1** | Patient Name | Required | `NM101` = `QC` |
| 2100 | **NM1** | Insured, Corrected, Service Provider | Situational | When different from or in addition to the patient |
| 2100 | **MIA / MOA** | Inpatient / Outpatient Adjudication | Situational | Remark codes and amounts at claim level |
| 2100 | **REF, DTM, AMT** | Claim references, dates, amounts | Situational | Statement dates, claim received date, coverage amounts |
| 2110 | **SVC** | Service Payment Information | Situational, repeats | One per service line |
| 2110 | **DTM** | Service Date | Situational | `472` service date |
| 2110 | **CAS** | Service Adjustment | Situational | Line-level adjustments |
| 2110 | **REF** | Line Item Control Number | Situational | `6R`, echoes the 837 line control number |
| 2110 | **AMT** | Service Supplemental Amount | Situational | `B6` allowed amount |
| 2110 | **LQ** | Health Care Remark Codes | Situational | `HE` RARC |
| Trailer | **PLB** | Provider Adjustment | Situational | Adjustments not tied to one claim |
| Trailer | **SE** | Transaction Set Trailer | Required | Segment count and control number |

## Key Segments Explained

### BPR: Financial Information

```
BPR*I*45*C*CHK************20261120~
```

| Element | Name | Example | What it means |
|---|---|---|---|
| **BPR01** | Transaction Handling Code | `I` | `I` remittance with payment. `H` notification only, no money moves |
| **BPR02** | Total Payment Amount | `45` | The payment total. Must equal the claim payments minus PLB adjustments |
| **BPR03** | Credit/Debit Flag | `C` | `C` credit to the payee |
| **BPR04** | Payment Method Code | `CHK` | `ACH`, `CHK`, `NON` (no payment), and others |
| **BPR05 to BPR15** | Bank details | | Payer and payee bank routing and account details, used when `BPR04` = `ACH` |
| **BPR16** | Payment Effective Date | `20261120` | The check issue date or EFT effective date |

### TRN: Reassociation Trace Number

```
TRN*1*CHK00412877*1990000001~
```

`TRN02` is the check number or EFT trace number. It is the key that joins the 835 to the deposit on your bank statement. `TRN03` identifies the payer; the TR3 has it as a `1` followed by the payer's tax ID. When an EFT arrives without its 835 (or the other way round), matching `TRN02` to the trace number in the bank's CCD+ addenda is how the two are reassociated.

### N1: Payer (1000A) and Payee (1000B)

```
N1*PR*SAMPLEVILLE HEALTH PLAN~
N1*PE*EXAMPLE FAMILY PRACTICE*XX*1999999992~
```

`PR` is the payer and `PE` the payee. The payee is normally identified by NPI (`XX`), with the tax ID in a following `REF*TJ`. The payer also sends a `PER` segment with its technical (`BL`) contact for EDI questions.

### CLP: Claim Payment Information

```
CLP*EFP26110301*1*160*85*25*12*SHP2611190001*11*1~
```

| Element | Name | Example | What it means |
|---|---|---|---|
| **CLP01** | Patient Control Number | `EFP26110301` | The provider's claim ID, echoed from `CLM01` on the 837 |
| **CLP02** | Claim Status Code | `1` | `1` processed as primary, `2` secondary, `3` tertiary, `4` denied, `19` to `21` processed and forwarded to another payer, `22` reversal of previous payment, `23` not our claim, forwarded |
| **CLP03** | Total Claim Charge | `160` | What the provider billed |
| **CLP04** | Claim Payment Amount | `85` | What the payer paid on this claim |
| **CLP05** | Patient Responsibility | `25` | What the patient owes, the total of PR adjustments |
| **CLP06** | Claim Filing Indicator | `12` | The type of coverage, for example `12` PPO, `HM` HMO, `MB` Medicare Part B, `MC` Medicaid |
| **CLP07** | Payer Claim Control Number | `SHP2611190001` | The payer's own ID for the claim. Quote it on corrections and appeals |
| **CLP08** | Facility Type Code | `11` | Place of service (professional) or facility type (institutional) from the claim |
| **CLP09** | Claim Frequency Code | `1` | `1` original, `7` replacement, `8` void, from the claim |

### CAS: Claim Adjustment

`CAS` explains every difference between what was billed and what was paid. It appears at claim level (loop 2100) and service line level (loop 2110).

```
CAS*CO*45*33~
CAS*PR*3*25~
```

| Element | Name | Example | What it means |
|---|---|---|---|
| **CAS01** | Claim Adjustment Group Code | `CO` | Who carries the adjustment: `CO`, `PR`, `OA` or `PI` |
| **CAS02** | Adjustment Reason Code | `45` | The CARC: why the amount was adjusted |
| **CAS03** | Adjustment Amount | `33` | The amount adjusted. Positive reduces payment; negative increases it |
| **CAS04** | Adjustment Quantity | | Units adjusted, when units differ |
| **CAS05 to CAS19** | More reason, amount, quantity sets | | Up to six adjustments under one group code |

One CAS segment holds up to six reason/amount/quantity sets that share a group code. A second group code needs a second CAS segment.

### SVC: Service Payment Information

```
SVC*HC:99213*125*67~
DTM*472*20261103~
CAS*CO*45*33~
CAS*PR*3*25~
AMT*B6*92~
```

| Element | Name | Example | What it means |
|---|---|---|---|
| **SVC01** | Composite Procedure Code | `HC:99213` | Qualifier (`HC` for HCPCS/CPT, others for revenue codes, NDC, dental) and the procedure, plus any modifiers |
| **SVC02** | Line Item Charge | `125` | Billed for the line |
| **SVC03** | Line Item Payment | `67` | Paid for the line |
| **SVC04** | Revenue Code | | Institutional revenue code, where used |
| **SVC05** | Units of Service Paid | | Units paid, when not 1 |
| **SVC06** | Original Procedure Code | | The billed procedure, when the payer paid a different one |

`AMT*B6` gives the allowed amount for the line. If the payer adjudicated a different procedure or units than you billed, `SVC06` and `SVC07` show what you originally sent, which is how you spot recoding.

### LQ: Remark Codes

```
LQ*HE*N130~
```

`LQ01` = `HE` marks a remittance advice remark code (RARC) in `LQ02`. RARCs add detail to a CARC, or carry an informational alert. Some CARCs, such as `16` and `96`, carry a usage note in the X12 list saying a remark code must accompany them. Claim-level remark codes go in `MIA` (inpatient) or `MOA` (outpatient) instead.

### PLB: Provider Level Adjustment

```
PLB*1999999992*20261231*WO:EFP26100917*40~
```

| Element | Name | Example | What it means |
|---|---|---|---|
| **PLB01** | Provider Identifier | `1999999992` | The provider the adjustment applies to, usually its NPI |
| **PLB02** | Fiscal Period Date | `20261231` | The last day of the provider's fiscal year, as the TR3 defines it |
| **PLB03** | Adjustment Reason and Reference | `WO:EFP26100917` | Reason code and a reference, often the claim the adjustment relates to |
| **PLB04** | Adjustment Amount | `40` | Positive reduces the payment; negative increases it |
| **PLB05 to PLB14** | More reason and amount pairs | | Up to six adjustments per PLB |

Common PLB reason codes include `WO` (overpayment recovery), `L6` (interest owed), `FB` (forwarding balance), `72` (authorized return) and `J1` (nonreimbursable). PLB adjustments are not tied to any claim in the same 835, so they are easy to miss during posting and are a common reason a deposit "does not match" the claims.

## Claim Adjustment Group Codes: CO, PR, OA, PI

The group code is the first thing to read on any CAS segment, because it says who carries the amount. X12 publishes four group codes.

| Code | X12 name | What it generally means | Who usually carries it |
|---|---|---|---|
| **CO** | Contractual Obligation | An amount adjusted under the provider's contract or a regulation, such as the difference between billed charges and the contracted rate | The provider. It is generally written off, not billed to the patient |
| **PR** | Patient Responsibility | Deductible, coinsurance, copay and other amounts the patient owes under the plan | The patient (or a secondary payer) |
| **OA** | Other Adjustment | An adjustment that fits neither CO nor PR, such as an exact duplicate claim or an amount already paid by another payer | Depends on the reason code |
| **PI** | Payor Initiated Reduction | A reduction the payer initiates where, in the payer's view, the patient is not responsible and no contract between payer and provider covers it | Disputed between provider and payer |

Not every payer uses all four. The CMS Medicare companion guide limits Medicare contractors to `CO`, `OA` and `PR`. Whether a provider may bill a patient for any adjusted amount is set by its contracts and applicable law, not by the 835 format.

## Claim Adjustment Reason Codes (CARC) and Remark Codes (RARC)

CARCs explain why an amount was adjusted; RARCs add detail. Both lists are updated on a regular cycle, and codes are added, revised and deactivated with start and stop dates, so your billing system should load them from the published lists rather than hard-coding descriptions. A few CARCs you will see constantly:

| CARC | X12 description (short) | Typical group |
|---|---|---|
| **1** | Deductible amount | PR |
| **2** | Coinsurance amount | PR |
| **3** | Co-payment amount | PR |
| **45** | Charge exceeds fee schedule/maximum allowable or contracted/legislated fee arrangement | CO |
| **97** | The benefit for this service is included in the payment/allowance for another service/procedure that has already been adjudicated | CO |
| **16** | Claim/service lacks information or has submission/billing error(s) | CO, with a remark code |
| **18** | Exact duplicate claim/service | OA |
| **29** | The time limit for filing has expired | CO |
| **50** | Non-covered services because this is not deemed a "medical necessity" by the payer | CO |
| **96** | Non-covered charge(s) | CO, with a remark code |
| **204** | This service/equipment/drug is not covered under the patient's current benefit plan | CO or PR, per the payer |

A few RARCs that often travel with them:

| RARC | Description (short) |
|---|---|
| **N130** | Consult plan benefit documents/guidelines for information about restrictions for this service |
| **M15** | Separately billed services/tests have been bundled as they are considered components of the same procedure |
| **MA130** | Your claim contains incomplete and/or invalid information, and no appeal rights are afforded because the claim is unprocessable |
| **N381** | Alert: Consult our contractual agreement for restrictions/billing/payment information related to these charges |

The "typical group" column reflects common usage, not a rule. The group code on the actual CAS segment is what counts, and the X12 list itself restricts some pairings (for example, its note on CARC `18`).

## How an 835 Balances

The 835 is built to balance at three levels. A file that does not balance is a payer error worth raising, and a posting that does not balance is usually a missed PLB or CAS.

| Level | Rule | Example from the sample |
|---|---|---|
| **Service line** | `SVC02` minus the line's CAS amounts = `SVC03` | 125 minus 33 minus 25 = 67 |
| **Claim** | `CLP03` minus all claim and line CAS amounts = `CLP04` | 160 minus 33, 25 and 17 = 85 |
| **Transaction** | Sum of `CLP04` minus sum of PLB amounts = `BPR02` | 85 plus 0 minus 40 = 45 |

The transaction rule comes straight from the TR3, which X12 quotes in its published interpretation on [PLB amounts](https://x12.org/resources/requests-for-interpretation/rfi-1961-plb-adjustment-field-lengh): the sum of all claim payments minus the sum of all provider-level adjustments equals the total payment amount.

## Matching the 835 Back to the 837

Posting depends on finding the claim each CLP refers to. The identifiers that tie the two together:

| 835 element | 837 element | What to use it for |
|---|---|---|
| **`CLP01`** Patient Control Number | **`CLM01`** Patient Control Number | Primary match. Keep `CLM01` unique per claim so this is never ambiguous |
| **`CLP07`** Payer Claim Control Number | **`REF*F8`** in loop 2300 of a later claim | Quote it when you send a replacement (`7`) or void (`8`) claim |
| **`REF*6R`** in loop 2110 | **`REF*6R`** Line Item Control Number in loop 2400 | Line-level match, when you send line control numbers |
| **`SVC01`**, **`DTM*472`** | **`SV1`/`SV2`/`SV3`** and **`DTP*472`** | Fallback line match by procedure and date |
| **`NM1*QC`** patient | Subscriber or patient loop | Sanity check, not a key |

A few cases break naive matching:

- **Reversals and corrections.** A payer that reprocesses a claim may send a reversal (`CLP02` = `22`, amounts negated) and the corrected claim in the same or a later 835. Post both.
- **Split claims.** A payer may split one 837 claim into several CLPs with the same `CLP01`. Match on `CLP01` plus `CLP07`.
- **Forwarded claims.** `CLP02` values `19` to `21` and `23` mean the payer forwarded the claim to another payer; expect a second 835 from that payer.

## Where the 835 Sits in the Claim Cycle

| Transaction | Sent by | Purpose |
|---|---|---|
| **[270](/guides/edi/270-eligibility-benefit-inquiry) / [271](/guides/edi/271-eligibility-benefit-response)** | Provider / Payer | Check coverage and benefits before or at the visit |
| **[837 Health Care Claim](/guides/edi/837-health-care-claim)** | Provider | Bill the payer |
| **[999 Implementation Acknowledgment](/guides/edi/999-implementation-acknowledgment)** | Receiver | Confirm the claim file passed validation |
| **277CA Claim Acknowledgment** | Payer | Accept or reject each claim into adjudication |
| **[276](/guides/edi/276-claim-status-request) / [277](/guides/edi/277-claim-status-response)** | Provider / Payer | Ask about and report claim status before payment |
| **835 Claim Payment/Advice** | Payer | Explain the payment and every adjustment |
| **[834](/guides/edi/834-benefit-enrollment-and-maintenance) / [820](/guides/edi/820-payment-order)** | Plan sponsor | Enrollment and premium payment on the plan side; "patient not eligible" denials often trace back to enrollment |

## Common 835 Problems and How to Handle Them

| Problem | What happens | What to do |
|---|---|---|
| **PLB not posted** | Deposit does not match the posted claims | Post PLB adjustments as their own entries, by reason code |
| **CO amounts moved to the patient** | Patients billed for amounts the provider should write off | Drive patient balances from PR adjustments only |
| **`CLP01` not unique** | Payments posted to the wrong claim | Generate unique patient control numbers per claim on the 837 |
| **Reversal posted without its correction** | Account shows a takeback with no repayment | Post `CLP02` = `22` reversals together with the corrected claim |
| **Hard-coded CARC/RARC descriptions** | Outdated or wrong denial text | Load the current X12 code lists on each update |
| **835 arrives without EFT, or EFT without 835** | Cash cannot be applied | Reassociate on `TRN02` and the EFT trace number |
| **Payer sends a different procedure in `SVC01`** | Line does not match the claim | Read `SVC06` for the original code, and review recoding |
| **Unbalanced 835** | Posting cannot reconcile | Raise it with the payer's EDI contact in `PER*BL` |

## 835 Implementation Checklist

- Enroll for ERA (and EFT) with each payer, and note which clearinghouse or payee ID will receive the 835
- Get each payer's 835 companion guide and confirm `005010X221A1`
- Confirm your billing system loads current CARC and RARC lists
- Map group codes to posting actions: CO write-off, PR patient balance, OA and PI by reason
- Post PLB adjustments separately, with their reason codes and references
- Set up reassociation between 835s and deposits on `TRN02`
- Keep `CLM01` unique on outbound 837s so `CLP01` always finds one claim
- Send line item control numbers (`REF*6R`) on 837 lines if you want line-level matching
- Build a denial work queue keyed on CARC, RARC and payer
- Monitor for 835s that do not balance and raise them with the payer

## Reading 835 Files With OrderSync's Free Inspector

When a remittance does not match the deposit or a denial makes no sense, start with the raw file. Paste any X12 file into the [free EDI inspector](/edi-inspector) to see the payment, each claim, every service line and CAS adjustment broken out segment by segment, with control-number and segment-count problems flagged. It runs in your browser and needs no signup. Use sample files, or files with patient data removed, when you are trying it out. The same files can be converted with the [EDI to JSON converter](/edi-to-json), and our [EDI document types reference](/edi-document-types) covers how the 835 fits among other X12 transactions.

## Frequently Asked Questions

<div className="not-prose">

### What is an 835 file?

An 835 file is the X12 Health Care Claim Payment/Advice transaction, also called an electronic remittance advice (ERA). A health plan sends it to a provider to explain a payment: which claims it covers, what was paid on each claim and service line, and why any amount differs from what was billed.

### What is the difference between an 835 and an 837?

The provider sends the 837 to bill a health plan for care. The health plan sends the 835 back to explain how it paid or denied those claims. CLP01 on the 835 echoes CLM01 on the 837, which is how the two are matched.

### What do CO, PR, OA and PI mean on an 835?

They are claim adjustment group codes in CAS01. CO is contractual obligation, generally written off by the provider. PR is patient responsibility, such as deductible, coinsurance and copay. OA is other adjustment. PI is a payer initiated reduction. Medicare uses only CO, OA and PR.

### What are CARC and RARC codes?

Claim adjustment reason codes (CARCs) explain why an amount was adjusted, for example 45 (charge exceeds the fee schedule or contracted rate) or 1 (deductible). Remittance advice remark codes (RARCs) add detail or alerts. X12 publishes both lists and updates them regularly, so load the current versions rather than relying on old descriptions.

### What is the PLB segment in an 835?

PLB is the provider level adjustment. It carries adjustments that are not tied to one claim in the 835, such as overpayment recoveries (WO), interest (L6) and forwarding balances (FB). A positive PLB amount reduces the payment, and the total payment equals claim payments minus PLB amounts.

### How do I match an 835 payment to the bank deposit?

Use the TRN segment. TRN02 is the check number or EFT trace number, and for EFT payments the same trace number travels in the CCD+ addenda record. Matching the two reassociates the remittance with the money.

### What does CLP02 = 22 mean?

CLP02 = 22 is a reversal of previous payment. The payer is taking back an earlier payment on that claim, with the amounts shown as negatives. It is usually followed by the claim reprocessed with a new CLP, and both need to be posted.

### Why doesn't my 835 match the deposit?

The most common reasons are a PLB adjustment that was not posted, a reversal posted without its corrected claim, or the 835 and EFT belonging to different payments. Check that claim payments minus PLB amounts equal BPR02, and that TRN02 matches the EFT trace number.

</div>