Payments reconciliation for ecommerce brands: matching payouts, refunds and orders
How a payments reconciliation build matches card, bank and marketplace payments to orders and refunds for ecommerce brands.
Updated 2026-03-17
Why Ecommerce brands need a payments reconciliation
Ecommerce brands collect money from several sources at once. A storefront payment processor settles card sales in batches, a marketplace pays out net of its own fees, and a wholesale buyer may still pay by bank transfer. Each source describes the same sale differently, so one order can show up as a gross amount, a fee, a refund and a later adjustment. Linking those lines back to the right orders is the step that most often slips during a busy sales period. A payments reconciliation build reads settlement reports as they arrive, pairs each line with an order and its return history, and places anything with a difference in a review queue. For an owner or team lead, the payout figure then reflects what customers actually paid after returns, and a double refund appears as a single line to check.
Payments reconciliation: Ecommerce brands in plain language
Money reaches an online store in more than one shape. A customer's card payment may be recorded on the day of the sale, but the funds usually arrive later, in a single deposit that combines many sales, fees and refunds. A marketplace may hold funds and deduct its commission before a payout leaves its account. Because the deposit and the sale are separate events, the figure in the bank account rarely matches any single order.
Reconciliation is the discipline of tracing that deposit back to its parts. It asks which sales a payout covers, which fees were taken, which refunds reduced it, and whether anything was paid twice or not at all. A brand selling abroad may see one rate on the sale and another when the money settles, and that difference needs explaining before the books close.
An owner who knows the true value of a month's sales can price products, judge the cost of returns and decide where to spend on advertising. Without that trace, the store sees its revenue in the storefront dashboard and its cash in the bank, and the gap between the two stays unexplained.
Features for this industry
- Card processor settlement lines matched to the orders they pay for, with fees recorded before payout
- Marketplace payouts split back into individual orders, showing commission and refunds against each one
- Refunds and returns linked to the original payment, so a repeated refund is flagged for review
- A review queue for split baskets, partial shipments and payments in more than one currency
- Posting of confirmed matches into the ledger, with each entry traceable to its source report
At a glance
| Build | Payments reconciliation |
|---|---|
| Industry | Ecommerce brands |
| Complexity | moderate |
| Tools | Xero, Make, n8n |
| First release |
|
Examples
Marketplace payout matching
A brand sells through its own website and a marketplace. The marketplace pays out in batches, net of its commission and any refunds. The build breaks each payout into its component orders, lists the commission and refunds against each, and places any order with no matching sale in the review queue for the team to check.
Card settlement review
One brand takes card payments through a hosted checkout, and its processor deposits daily settlement reports. Some days include sales from the previous day, refunds and chargeback fees. The build pairs each settlement line with an order, flags any amount that does not agree, and places it in a queue for the bookkeeper.
Refund and return tracking
An online store issues refunds for returns, partial orders and cancelled shipments. Each refund should appear once in the payments record and once in the ledger, against the order it relates to. The build compares refunds with returns and payment records, and flags any refund that has no matching return or that appears twice.
Payments reconciliation: Ecommerce brands in practice
Inside a store that uses this build, the work is a quiet background process with one short human task. Statements from the processor, the marketplace and any wholesale bank account arrive on a schedule the team agrees, and an automation in Make or n8n can handle the pulling and first-pass matching. The review queue is where a person steps in.
As the rules improve, more lines clear without a person. A bookkeeper might first clear a run of lines that share a pattern, such as a fee worded slightly differently each time. Each correction is a cue to update the matching logic, so the same line is not fixed twice. Some items stay in the queue for good, such as a refund issued as store credit rather than to the original card, and a standing note serves those better than a fresh decision each period.
Where the ledger is Xero, confirmed matches land there as posted entries. The bookkeeper can then answer an accountant's question from the ledger itself. A new sales channel needs its import and rules in place before its first payout arrives, so unmatched money does not build up unseen.
The local angle
MILabs is based in Sydney and works remotely, so for a store outside Sydney the sessions run by video call in the same way. For an Australian brand that sells overseas, the local question is mostly about the ledger. Xero records the books in one base currency, which for an Australian business is normally the Australian dollar, so each foreign payout needs a written rule for which exchange rate applies. Shipping to New Zealand or the United States, for example, brings payouts in other currencies into the same ledger. Goods and services tax on each order is a separate question from the matching itself, and it belongs with the accountant who prepares the business activity statement. Keeping those two questions apart makes the review easier for an Australian bookkeeper to follow at closing.
Frequently asked questions
- Which tools does a payments reconciliation build for ecommerce brands use?
- A build of this kind usually connects the payment sources a brand already uses to its accounting ledger. Xero is one option for the ledger, where confirmed matches are posted. Make and n8n are automation platforms that can run scheduled imports from payment reports, apply matching rules and send unmatched lines to a review queue. The right mix depends on the storefront, processor and marketplaces, so MILabs confirms those first.
- How do I measure a payments reconciliation build in an ecommerce brand?
- Measure it by counting the lines left in the review queue at the end of each closing period. A falling count suggests the matching rules now cover more of the payments the brand receives. Some teams also track how many refunds were flagged as repeats, since that number points to where the returns process needs attention. Keep the same definitions each period so the figures can be compared.
- Day to day, what does an ecommerce brand team do with a payments reconciliation build?
- Day to day, most of the work runs in the background. Imports arrive from the storefront, processor and marketplace, and the matching rules pair each payment with its order or refund. The team's task is the review queue, where a person decides on each line the rules could not resolve, such as a payout that combines several orders. Confirmed matches flow into the ledger, leaving the bookkeeper a short list of decisions.
- Is a payments reconciliation build right for a small ecommerce brand?
- Yes, if the brand takes payments through more than one route, such as a storefront and a marketplace, or if refunds are frequent enough that checking them by hand takes real time. A brand with one processor and few refunds may find a monthly check in its ledger is enough. Discuss the build once the review work becomes a step the team keeps postponing. Describe your sales channels through the enquiry form.
- Can I build a payments reconciliation myself in an ecommerce brand?
- Yes, for a single payment source. Some brands start with a spreadsheet or the matching features in some accounting software, a reasonable first step. A custom build becomes harder to maintain when statement formats change or several marketplaces pay out in different ways. MILabs can design the integration so the team keeps the final decision on every unclear entry, and document the rules in plain language so they can be adjusted later.
Related
read these nextUp a level
Payments reconciliation for other industries
Other builds for Ecommerce brands
- Abandoned cart automation for ecommerce brands
- Customer support assistant for ecommerce brands
- Delivery notification automation for ecommerce brands
- Ecommerce and ERP sync for ecommerce brands
- Email to ticket integration for ecommerce brands
- Inventory forecast report for ecommerce brands
- Inventory tracker for ecommerce brands
- Order tracking portal for ecommerce brands
- Ordering app for ecommerce brands: stock, orders and customer questions
- Pet owner app for ecommerce brands: features, scope and examples
- Price list update automation for ecommerce brands
- Product description writer for ecommerce brands
