A practical guide to automated payment reconciliation

Reconciliation becomes reliable when every order, transaction, fee and settlement can be traced with shared references—and exceptions reach the right person.

ORDERTRANSACTIONSETTLEMENTLEDGER

Automation should remove repetitive matching while preserving visibility. The aim is not to hide differences; it is to identify them earlier and route them with evidence.

01 / Model

Match more than two numbers

A useful model connects the commerce order, payment transaction and settlement line. Depending on the operation, it may also include refunds, fees, tips, taxes, currencies and outlet identifiers. This makes it possible to explain both the gross sale and the net amount received.

02 / References

Preserve identifiers from the point of sale

The order reference should travel into the payment request where the payment workflow allows it. Gateway or acquirer references should then return to the commerce system or integration layer. These identifiers form the trace between platforms.

Design principle:

Never depend only on amount and date when a stable transaction or order identifier is available.

03 / Timing

Treat authorisation and settlement as different events

A successful customer payment does not mean funds have already settled. The workflow should represent authorisation, capture, refund, reversal and settlement as separate states, then apply the correct timing window to each payment method.

04 / Exceptions

Make exceptions a managed queue

When a match cannot be completed, create an exception with a reason, status, owner and supporting references. Common categories include missing orders, duplicate postings, partial settlements, refund timing and fee differences.

  • Prioritise exceptions by age and value.
  • Keep resolution notes with the record.
  • Allow corrected data to be reprocessed safely.
  • Measure recurring causes so the upstream workflow can improve.
05 / Controls

Keep finance in control of the outcome

Dashboards and alerts should summarise matched value, unmatched value, ageing and the last successful data receipt. Export or posting rules must be agreed with finance so automation produces the right accounting outcome—not simply a technical success.

EISOL scopes payment integrations around the systems and payment capabilities available to each customer, including connected RewardlyPAY workflows and suitable Adyen or Airwallex components.

Related solution

Design an omnichannel payment workflow that remains reconcilable.

Explore payment integration