For exporters in India, payment reconciliation stops being simple the moment money starts arriving from different countries, currencies, and payment channels.
A buyer may pay two invoices in one transfer. Another payment may arrive after FX conversion and fees. The money is there; the challenge is proving which payment belongs to which invoice and why the amount changed.
A buyer may pay two invoices in one transfer. Another payment may arrive after FX conversion and fees. The money is there; the challenge is proving which payment belongs to which invoice and why the amount changed.
TL;DR
- Payment reconciliation matches money received against invoices, payment records, settlements, and accounting entries.
- Cross-border reconciliation is harder because FX conversion, fees, settlement timing, refunds, chargebacks, and remitter names can all create mismatches.
- Matching on transaction identifiers and invoice references is more reliable than matching only on amounts.
- Automation does not remove reconciliation work; it automatically matches routine transactions so finance teams can focus on exceptions.
What is payment reconciliation?
Payment reconciliation is the process of comparing payment records with invoices, settlements, bank credits, and accounting entries to confirm that each transaction is correctly accounted for.
It answers: Did the payment arrive? → Does it match the expected transaction? → Is it recorded correctly?
Settlement vs reconciliation
These terms are related but different.
| Settlement | Reconciliation |
|---|---|
| Movement of funds to the merchant | Matching those funds to business records |
| Answers “Did money reach us?” | Answers “What was this money for?” |
| Driven by the payment provider or bank | Driven by transaction, invoice, and accounting data |
A payment can settle successfully and still remain unreconciled.
How does payment reconciliation work?
A practical reconciliation flow has four stages:
Collect records → match transactions → investigate exceptions → close and document
Step 1: Gather the records
Bring together invoices, bank statements, gateway and settlement reports, refunds, chargebacks, and accounting entries.
Step 2: Match the transactions
Compare identifiers, invoice numbers, dates, amounts, currency, payment status, and settlement information.
Step 3: Investigate differences
A mismatch may come from fees, FX conversion, timing, partial payments, combined invoices, refunds, chargebacks, or incorrect references.
Step 4: Close and document
Once the difference is understood, update the appropriate records and retain a clear audit trail of how the exception was resolved.
What are the main types of reconciliation?
| Type | What is being matched |
|---|---|
| Accounts receivable reconciliation | Customer payments against invoices |
| Bank reconciliation | Internal ledger against bank statement |
| Payment gateway reconciliation | Gateway transactions against orders, settlements, and bank credits |
| Accounts payable reconciliation | Payments made against supplier invoices |
| Card reconciliation | Card transactions against expense or sales records |
| General ledger reconciliation | Ledger balances against supporting records |
Why is cross-border payment reconciliation harder?
A cross-border payment can change between checkout and bank credit.
Consider this example:
| Stage | Amount |
|---|---|
| Invoice | US$1,000 |
| Customer payment | US$1,000 |
| INR conversion | ₹83,200 |
| Processing/other deductions | ₹2,000 |
| Bank credit | ₹81,200 |
Nothing necessarily went wrong. The customer paid the full invoice, but US$1,000, ₹83,200, and ₹81,200 are three different values linked to the same transaction.
Other complications include combined invoices, partial payments, different transaction and settlement dates, mismatched remitter names, refunds, and chargebacks. That is why cross-border reconciliation should not rely only on amount and date.
What is payment gateway reconciliation?
Payment gateway reconciliation matches transactions recorded by the payment gateway against internal orders, settlements, refunds, chargebacks, and bank credits.
Four common gateway reconciliation gaps
Fee gap: gross transaction amount differs from net settlement.
Timing gap: payment date and settlement date differ.
Status gap: authorised, captured, settled, refunded, and charged-back transactions are not equivalent.
Aggregation gap: one bank credit can represent many individual customer payments.
Why are transaction identifiers better than amount matching?
Amounts are useful, but they are not always stable.
Invoice amount → FX conversion → fees/deductions → settlement amount
PayGlocal documents two identifiers for this purpose:
- GID (PayGlocal ID): created by PayGlocal when a transaction is initiated and used for tracking and reconciliation.
- MUID (Merchant Unique ID): a merchant-generated identifier that can be used to connect the PayGlocal transaction back to the merchant's own order or record.
Manual vs automated reconciliation
| Manual reconciliation | Automated reconciliation |
|---|---|
| Finance team downloads and compares files | Systems pull and match transaction data |
| Amount/date matching is common | Identifier-based rules can be used |
| Every transaction may need review | Only exceptions need manual attention |
| More re-keying and spreadsheet work | Less repetitive data handling |
| Month-end process can become heavy | Matching can happen more frequently |
Automation means routine transactions are matched automatically and the exceptions queue becomes the work.
What are good payment reconciliation practices?
- Reconcile frequently: Daily or weekly checks make discrepancies easier to investigate.
- Use unique references: Carry invoice, order, and transaction IDs through the payment flow.
- Separate gross and net values: Record fees, FX, refunds, and deductions explicitly.
- Define exception rules: Decide what can auto-match and what needs review.
- Standardise data: Keep date, currency, and reference formats consistent.
- Keep an audit trail: Record how exceptions were resolved.
How does reconciliation connect to export documentation?
For Indian exporters, reconciliation can also support the records used to demonstrate that export proceeds were received and matched correctly.
Depending on the flow, this can include FIRA, purpose codes, shipment/payment matching, EDPMS closure for applicable goods exports, and e-BRC records where applicable.
How PayGlocal supports international payment reconciliation
PayGlocal provides transaction tracking and reconciliation data for Indian businesses collecting internationally.
Current capabilities include GID and MUID identifiers, real-time payment and settlement visibility, Multi-Currency Accounts, collections across 130+ global currencies from 180+ countries, INR settlement, automated FIRA, and EDPMS/e-BRC support for applicable exporter flows.
