When an order, payment, refund and payout do not agree, teams can lose hours searching across the shop, payment service and accounts. A clear reconciliation process connects the available records, reveals differences and shows who should take the next step.
An order can be complete in the shop while the related payout shows a different amount. Fees, refunds or disputes often explain the difference, but the information is not always held in one place. Shop operators therefore need more than an account balance: they need a traceable route from order to accounting entry.
Which records do you need for a complete reconciliation?
Start with a closed period and connect every order ID to its payment ID. Add refunds, disputes, fees, payouts and the accounting status. This creates a review chain that makes missing or duplicate connections easier to spot.
WooCommerce documentation describes WooPayments Reconciliation Reports for balance movements involving fees, refunds, disputes and payouts. The published update says the feature is in beta rollout. Check which reports are available in your account and whether their fields support your accounting process before relying on them.
How can you isolate a difference without getting stuck on one case?
Begin with the order ID and follow the amount through payment, any refund or dispute, and the final payout. Compare the gross amount, fees, deductions and amount paid using the same sequence each time. Record every difference with its cause, status and next review step.
Set both an amount threshold and an age threshold for open differences. A small rounding difference may only need a label, while an older or larger amount should trigger direct review. A shared framework prevents the team from making a new judgement for every case.
Who takes the next step across shop, payments and finance?
Assign each type of issue to a named role. The shop team checks order status and refund handling, the payments side checks payment events and payouts, and finance confirms the accounting entry and closure. Cases involving more than one area need a defined escalation route with a deadline.
Every handover should include the same references: order ID, payment ID, payout, amount, date and checks already completed. The next person can then continue without rebuilding the case. The record also shows where the case is waiting and which information is still missing.
How do you know your payment reconciliation is dependable?
Recreate the process for a closed period and include a standard payment, partial refund, full refund and dispute. Check whether every difference can be assigned a cause and status within the agreed time. Give unresolved cases a next review date instead of leaving them on an unclear remainder list.
A dependable reconciliation gives finance an explainable total and gives the shop team specific cases to resolve. It also reveals whether an integration or handover regularly loses data. Recurring gaps can then become a process improvement instead of a monthly search exercise.
DKSIGN can review the handovers between WooCommerce, WooPayments, ERP and finance using real operating workflows. Together, we define references, control points, roles and escalation routes. The result is a reconciliation process that shop and finance teams can use reliably in daily work.
Checklist
- Choose a closed period and representative payment cases.
- Connect the order ID, payment ID, refund, dispute, fee, payout and accounting status.
- Set amount thresholds, age thresholds and statuses for open differences.
- Document roles and the escalation route across shop, payments and finance.
- Review recurring data gaps at integrations and handovers.
Do differences between WooCommerce, WooPayments and finance stay open for too long? DKSIGN reviews the reconciliation process with your real workflows and develops clear control points for your team.