Guides

What a Bank Statement Tells You About an Export, and What It Hides

The statement is the only proof that money arrived, and it is written for accounting rather than for compliance. Here is what each field means for an export, which one is the UTR, and why the same credit looks different at every bank.

By Anirudh Pratap Singh · · 8 min read

What is actually in a bank statement?

A statement line is built to answer one question: how did the balance change. Everything an exporter needs, which is who paid, for what, and against which shipment, has been compressed into a narration field that was never designed to carry it.

FieldWhat it reliably tells youWhat it does not
Value dateWhen the credit hit the accountWhen the buyer paid, or when the goods shipped
AmountWhat arrived in INR after conversionThe foreign currency amount or the rate applied
NarrationA remitter name and often a reference stringAnything in a fixed position or format
Reference numberThe bank internal transaction idWhether it is the same id your AD desk will quote back

That last column is why statement reading is harder than it sounds. The fields you need for closure exist, but they are not where the format promises they will be.

Which number is the UTR, and why does it keep moving?

For an inward remittance, the reference that matters is the one your bank uses when it registers the credit against your export. In practice you will meet several candidates in the same line: a bank transaction id, a SWIFT reference from the correspondent, a gateway payout id, and sometimes an IRM reference generated when the remittance is registered.

They are not interchangeable. The one to carry forward is whatever your AD bank quotes on the FIRA or advice for that credit, because that is the reference the bank will look up when you ask for an entry to be closed.

What is the purpose code doing in this?

Every inward remittance is reported under a purpose code that says what the money was for. It decides whether the credit is treated as export proceeds for goods, a service receipt, or something else entirely, and therefore whether it can ever close a shipping bill.

A goods export credited under a services code will not match anything in EDPMS, and the fix is a correction with your bank rather than more matching. The purpose code reference lists what applies, and purpose codes on marketplace receipts covers the aggregator case, where the code is set by whoever pushed the payout rather than by you.

Why does every bank produce a different file?

There is no single statement format, and the differences are not cosmetic. Across the banks Indian exporters use, all of the following vary:

  • Whether debits and credits are two columns or one signed column.
  • Whether the date is the value date, the posting date, or both.
  • How much of the remitter name survives truncation in the narration.
  • Whether the foreign currency amount and rate appear at all, or only the INR figure.
  • How a reversal is represented, which decides whether a refund cancels a credit or adds a new line.

Anything that reads statements has to be told about each format rather than inferring it, and a format that changes silently after a portal upgrade is the most common cause of a reconciliation that worked last month and does not this month.

What breaks a machine reading this?

The failure modes are boringly consistent, which is the good news, because it means they can be checked for:

  1. Two credits with the same amount on the same day, distinguishable only by a reference the parser dropped.
  2. A narration long enough to be truncated exactly where the reference was.
  3. A reversal posted as a fresh debit with no link to the credit it cancels.
  4. A rounded INR figure that cannot be reconciled to the foreign amount because no rate was published on the line.
  5. A statement exported for a date range that silently excludes the value date you were looking for.

What should I ask my bank for?

Three things make closure materially easier, and all of them are ordinary requests:

  • A statement export that carries the foreign currency amount and the rate applied, not only the INR credit.
  • The advice or FIRA for each inward remittance, which is where the reference and the purpose code are stated plainly. How to download a FIRA covers the usual routes.
  • Your pending EDPMS list, so you are working from the entries the bank actually holds open rather than from your own guess about which are outstanding.

With those three, most of a month reconciles mechanically. Without them, you are reading a ledger and inferring an export, which is exactly the step where errors enter and where EDPMS rejections come from.

Sources & citations

  • RBI purpose code framework for inward remittances. Determines how a credit is classified when the AD bank reports it, and therefore whether it can close an export entry.
  • FIRA and inward remittance advice, issued by AD banks. The per remittance document carrying the reference and purpose code that a statement line compresses or omits.

Update history

  • First published.