Next-generation Payment Reconciliation with AI

AI can help payment reconciliation by classifying descriptions, ranking candidate matches and summarising exceptions. It should not turn a non-zero difference into an apparently balanced journal. Ecommerce money moves through several records: order, invoice, payment authorisation, capture, processor balance, fee, refund, dispute, payout and bank statement. The workflow must preserve those events and explain how they combine.

Use the ecommerce integrations service for controlled matching and exception routing, the ecommerce service for order and gateway integration, and the ecommerce resource hub for connected operating guidance. Finance and tax advisers should approve the accounting design for the actual entity.

1. Draw the money and data flow

Keep external IDs exactly as supplied. Do not replace a gateway transaction ID with a shortened display number. Store currency, amount, event time, effective date, order link, customer reference where permitted, source file or API and ingestion time. The reconciliation engine needs immutable evidence even when an order status later changes.

2. Use a clearing-account model where appropriate

Xero’s guidance for bulk online-sales receipts describes using a clearing account: individual invoice payments are recorded to the clearing account, and the bulk bank receipt is allocated to the same account. The items should cancel when timing and fees are handled correctly. A remaining balance points to missing payments, missing payouts or another difference that requires explanation. A qualified adviser should configure the chart and posting rules.

3. Build a match hierarchy

1. Exact processor event ID to imported transaction
2. Exact payout ID to bank description or bank-feed reference
3. Expected payout total from included balance transactions
4. Order payment to invoice using controlled commerce references
5. Refund to original capture and order line allocation
6. Amount-and-date candidate only after stronger references fail
7. AI-ranked suggestion with evidence, confidence and human review

Run deterministic rules first because they are easier to test and explain. A model may help when bank descriptions are inconsistent or remittance text is unstructured, but confidence should never be the only control. Require compatible currency, direction, date window, unused status and source reliability before presenting a candidate.

4. Reconcile at event level before payout level

A payout of R9,420 might contain R10,000 of captured orders, R300 of fees, a R200 refund and an R80 reserve adjustment. Matching the payout to one sales total loses the composition. Confirm each component, then roll it into the payout. Preserve delayed captures, refunds paid in a later settlement, withheld reserves, chargebacks and processor corrections as separate timing or exception items.

5. Keep refund status precise

WooCommerce explains that automatic refunds rely on supported gateway integration, while a manual refund requires the merchant to send the money through the payment method separately. Therefore record requested, approved, submitted, processor-accepted, failed and bank-settled states. Do not mark the financial event complete because the order quantity was restocked or an internal status became refunded.

6. Govern AI recommendations

For every suggestion, store candidate records, features used, exclusions, confidence, model or rule version, reviewer and final decision. Prevent the assistant from posting journals or writing off differences above approved limits. Use a separate permission for retrieving records, proposing a match, creating a draft and approving a posting. Rejected suggestions become test cases; they should not silently retrain or change behaviour without review.

7. Close with control totals

Confirm order payments, processor gross movements, fees, refunds, disputes, payouts, bank receipts and clearing balances for the same scope and cut-off. Show unmatched items by age and value, not only count. Reconcile currencies separately. Preserve the source extracts and completion evidence so another reviewer can reproduce the close.

Worked payout

An SME receives a bulk bank deposit covering twelve orders. The processor report also includes one fee per charge, one partial refund from a prior order and a reserve release. Exact IDs link eleven orders automatically. The twelfth has a truncated bank description, so the assistant proposes one candidate based on amount, currency, payout membership and unused transaction state. Finance verifies the evidence, approves the match and records the fee and timing items separately. The clearing account reaches the expected balance without writing off an unexplained difference.

Sources checked

• Xero Central: Reconcile payments received from online sales
• WooCommerce: Refunding orders
• WooCommerce Analytics: Orders report
• WooCommerce: Managing orders

This resource provides general implementation guidance. Verify platform settings, tax, legal, payment and operational requirements against the current business context before making a live change.