ACCOUNTING & OPERATIONS

Ecommerce bookkeeping software: reconcile orders, fees and payouts

An online shop can have healthy sales and a bank deposit that looks nothing like its order total. The missing link is often the settlement: the group of payments, fees and adjustments that reaches the bank together. Your software should make that link easy to explain.

Retailer checking order receipts against a ledger beside parcels, a calculator and a laptop.
The useful bookkeeping trail connects the order, payment activity and eventual bank deposit.
In this guide
  1. Start with the journey from checkout to bank
  2. Why the payout is not the sales total
  3. Choose a level of detail you can maintain
  4. Make exceptions part of the demonstration
  5. Keep the connector and accounting plan in the same budget
  6. Give the month-end handover a named owner

Start with the journey from checkout to bank

Ecommerce bookkeeping software needs to account for several events that happen at different times. A customer places an order, a payment is captured, the shop fulfils it, and a provider later sends a settlement. A return or dispute can arrive after the original sale. Treating every event as the same record makes the numbers harder to follow.

Before comparing integrations, sketch that journey for your own store. Identify the storefront, every payment provider, the bank account receiving funds and the accounting system. Add marketplaces and separate currencies if you use them. The important question is which system explains the difference between the customer payment and the bank deposit.

Why the payout is not the sales total

Shopify’s payout documentation describes the transactions and adjustments behind each payment to the bank. Its export includes amount, fee and net fields. Refunds, fees, reserves and other adjustments can change what is eventually paid out. The deposit is therefore a settlement result, rather than a complete description of sales.

Consider a deliberately simplified example. A settlement contains £1,200 of captured customer payments, £80 of refunds and £24 of fees. With no other adjustments or timing differences, the expected deposit is £1,096. Seeing only that deposit tells you very little about the £1,200 customers originally paid. These figures illustrate a reconciliation bridge; they do not prescribe tax treatment or ledger entries.

Illustrative settlement bridge; not a merchant statement
ComponentAmountQuestion to answer
Captured payments£1,200Which orders and captures are included?
Refunds−£80Which returned payments affected this settlement?
Processing fees−£24Can the provider statement explain each fee?
Expected deposit£1,096Does the bank amount and reference match?

Choose a level of detail you can maintain

An integration might send each order individually or prepare summarised records for a period or settlement. Neither description, on its own, establishes that the books will reconcile. The retained detail must support the accountant’s reporting needs and leave an understandable path back to the source transactions.

Ask the vendor to demonstrate the same small sample in the storefront, settlement report and accounting system. Can someone move from the deposit to the underlying activity without manually opening hundreds of orders? If a summary is used, where are the supporting details kept, and what happens when the connector subscription ends? Agree the accounting treatment with the person responsible for the books.

Make exceptions part of the demonstration

A successful sale is the easiest example a supplier can show. A more useful evaluation includes a partial refund, a payout containing several days of activity and a refund that falls into a later payout. Shopify’s refund guidance explains that a refund can be deducted from a subsequent available payout. Your reconciliation process needs to retain that connection.

Use synthetic records in an authorised test environment. Decide how a missing settlement, duplicate import or unmatched order is surfaced and who investigates it. A connector that silently stops can be more troublesome than one that clearly reports an incomplete period. Record the last successful import and the owner of unresolved differences.

Keep the connector and accounting plan in the same budget

The complete service can involve the store subscription, payment processing, accounting software, a connector and bookkeeping support. Some connectors charge according to orders, channels or entities; others use a different unit. Ask for the actual charging basis and the handling of refunds or cancelled orders. A store with many inexpensive orders may have a different integration bill from a store with the same revenue and fewer orders.

Build a normal-month and busy-month estimate. Include historical imports, additional currencies and any setup work needed to map the data. Use our accounting first-year cost guide to keep introductory prices separate from the operating budget. Avoid counting the same bookkeeping work in both a managed service and an internal-time estimate.

Give the month-end handover a named owner

A good purchase ends with a repeatable routine. Decide when the store period is ready to review, which reports are retained, who matches bank deposits and who resolves exceptions. Keep the settlement identifier with the supporting file so the trail survives a staff handover. Restrict access according to the work each person actually needs to perform.

Start your shortlist with the Xero and QuickBooks profiles, then check the exact connector for your Shopify or WooCommerce setup. Choose the arrangement that makes a difficult settlement explainable, rather than the one with the largest list of integration logos.

Frequently asked questions

Why does an ecommerce payout differ from sales?

A payout can combine captured payments with refunds, processing fees, reserves and other adjustments, and the activity may cross dates. Use the provider’s settlement details to explain the deposit.

Should every ecommerce order be imported into the accounting software?

That depends on the reporting and accounting requirements. Individual transactions and supported summaries need different checks, but both should leave a traceable connection to the source activity.

What should I test before buying an ecommerce bookkeeping connector?

Use a small authorised sample containing a normal sale, partial refund, later-period adjustment and grouped payout. Check the supporting detail, duplicate prevention, exception handling and bank match.

Put the guide into practice

Explore accounting tools, then compare your shortlist.

Explore the category →