Digiway Payment
All articles
Reconciliation 8 min read

Building a Daily Reconciliation Process

Reconciliation is not a month-end exercise. Done daily it takes minutes and catches problems while they are still small enough to fix.

Digiway Payment editorial team

Reconcile four records, not two

Businesses often compare their order list to their bank statement and stop there. That hides where discrepancies actually originate. There are four records, and each boundary can break independently.

  • Your order or invoice record: what you expected to collect.
  • The payment record: what the provider reports as authorised or captured.
  • The settlement record: what the provider says it paid out, net of fees.
  • The bank statement: what actually credited your account.

Match in that order

Compare orders to payments first to find collection gaps. Then compare payments to settlements to find amounts held, deducted or delayed. Finally compare settlements to your bank credits to confirm the money arrived.

Working in this sequence tells you which boundary failed, which is the difference between a five-minute fix and a day of searching.

Know your exception categories

Most days produce a small number of recurring exception types. Naming them makes the queue manageable.

  • Paid but no order: often a duplicate customer attempt, or a payment against a cancelled order.
  • Order but no payment: an abandoned or failed attempt.
  • Stuck pending: needs a status query rather than a retry.
  • Amount mismatch: usually fees, a partial refund or a partial payment.
  • Settled but not credited: a bank timing difference, or a payout on hold.
  • Refund not reflected: netted against a later settlement rather than paid separately.

Make it a routine, not a project

Run it at the same time each day against the previous settlement day. Pull provider reports by API or scheduled export rather than manual download so the input is consistent. Auto-match on the payment reference, then work only the unmatched rows.

Assign an owner and keep a short written note against each exception. An unexplained difference that stays open for weeks becomes an audit problem.

What good looks like

A mature process closes each day with every row either matched or carrying a documented reason. The exception queue should be small and ageing should be visible, so a growing category signals a real operational issue early.

Keep references, reports and notes for the retention period your agreements and statutory obligations require. Reconciliation evidence is what resolves disputes months later.

Key takeaways

  • Reconcile orders, payments, settlements and bank credits as four separate records.
  • Match in sequence so you can see which boundary failed.
  • Name your exception categories and track their ageing.
  • Automate report collection and reconcile daily, not monthly.

This article is general information and not financial, legal or tax advice. DIGIWAY PAYMENT PRIVATE LIMITED provides financial-technology, onboarding and integration support. Payment, banking and other regulated services are delivered by the relevant authorised service partner, subject to eligibility, KYC, risk review and applicable terms.

Have a payment requirement to discuss?

Share your business requirement and our team will explain the available next steps.