Match a bank transaction using its UTR or payment reference together with account, amount, direction, date and counterparty evidence. Retain the exact reference and identify which payment system or provider issued it. A reference is powerful matching evidence, but it does not automatically identify the invoice or prove that every related accounting entry is correct.
Distinguish the reference for a bank settlement from the references for individual customer payments inside that settlement. A provider can combine many transactions into one bank credit. Matching only the payout reference will not, by itself, allocate every customer invoice.
Understand which identifier you have
Consider an illustrative Hyderabad laboratory-supplies distributor receiving NEFT, RTGS and provider settlements. It keeps separate fields for bank reference, customer remittance reference, provider payment identifier and settlement identifier where those are relevant.
RBI describes the RTGS UTR as a 22-character code identifying a transaction in that system. Do not apply that length rule to every other payment rail or internal reference. RBI's NEFT guidance also recommends transaction references alongside dates, amounts and party information when tracing funds.
A customer's typed invoice number is a different kind of reference from a bank-issued transfer identifier. Both can help, but the business should know whether the field comes from an external transaction record or from a payer's description.
Preserve the source value
Copy the full bank reference from the source statement or advice. Avoid manually shortening it to the final four digits in the working records. A masked display can be used in a summary, while the controlled source record retains the complete value needed for investigation.
Import reference columns as text where necessary. Microsoft documents how spreadsheet conversion can remove leading zeros or alter long numeric identifiers. Once information is lost, changing the display format may not reconstruct the original reference.
Keep a raw field even if a separate cleaned field removes spaces for comparison. Normalisation should not destroy the source value or make two different strings appear identical without review.
Use references to distinguish identical amounts
The distributor receives two illustrative ₹20,250 credits on the same day. The final digits below are masked display labels, not complete bank references.
| Bank movement | Amount | Reference display | Supported allocation |
|---|---|---|---|
| Receipt 1 | ₹20,250 | …8102 | Customer A invoice A-74 |
| Receipt 2 | ₹20,250 | …8103 | Customer B invoice B-19 |
Customer remittance advices connect each full reference with the correct invoice. Amount and date alone would not distinguish them. Matching the first bank row to the first open invoice could leave both bank totals correct while assigning customer balances incorrectly.
After matching, retain the link among statement row, book receipt and invoice allocation. The customer ledger and bank reconciliation should agree on the same transaction evidence.
Recognise one-to-many settlement references
A separate bank credit of ₹39,780 carries settlement reference P-01. The provider's supported report shows two customer collections of ₹20,000 each and ₹220 of identified deductions, giving ₹40,000 less ₹220, or ₹39,780.
The bank reference identifies the payout. Individual payment identifiers connect the ₹20,000 collections to sales or customer balances. Use the settlement report as the bridge rather than inventing a ₹39,780 sale equal to the net credit.
Razorpay's official report descriptions distinguish payment reports, settlement reports and settlement reconciliation detail. The exact reports and fields vary by provider, but the evidence requirement remains: connect the bank payout with its underlying movements and actual deductions.
Check the status as well as the reference
A reference attached to a prepared or pending instruction does not necessarily establish completed payment. Review the bank or provider status and the receiving account evidence appropriate to the transaction. Keep a failed payment and its reversal linked instead of treating the repeated reference as an automatic duplicate.
A debit and a later credit can share related identifiers because one reverses the other. Direction and amount therefore belong in the matching check. Do not delete a reversal merely because the reference resembles a payment already imported.
If the statement omits a useful reference, obtain the bank advice or additional detail. Do not fabricate a bank identifier to satisfy a blank field. An internal tracking number can be added, clearly labelled as internal.
Resolve imperfect matches explicitly
Differences can arise from partial payment, combined invoices, fees, withholding, refunds or a mistaken reference. Obtain the relevant remittance and supporting treatment before allocating the difference. A reference match is not permission to write off any amount that remains.
Where two candidates share a reference field, examine whether the provider uses it at batch level. Add party, amount and detailed report identifiers to the comparison. Record the reason for any manual match so another reviewer can follow it.
Avoid broad automatic rules such as matching every same-day same-amount item to the oldest invoice. That can work only under a documented, appropriate allocation process with checks for exceptions.
Search before manually changing a reference
A typo in an internal remittance field can be corrected with evidence, but retain the original source reference. Changing a bank-issued value merely to agree with an invoice description can destroy the strongest link available for a later bank trace.
Keep matching useful for later questions
Retain the bank source, remittance evidence, match link and any split allocation. When a customer queries an unpaid balance, the business should be able to identify the actual transfer rather than only an accounting receipt number.
A good reference-based match explains which movement occurred, through which system and against which obligation. Using the identifier's proper scope, preserving its exact value and checking the surrounding facts makes matching faster without sacrificing the accuracy of customer, supplier or settlement records.