Ecommerce accounting integrations: shift to platform-managed apps

April 2026

For online merchants, the link between your ecommerce platform and your accounting system is often where day-to-day accuracy is won or lost. Over the past couple of years, one practical change has become hard to ignore: more integration work is being shaped by platform marketplaces and platform-managed connection methods, rather than by one-off custom links or “set-and-forget” plugins. Even if you don’t follow product announcements closely, the effects show up in familiar places—how apps are approved, what data they can access, and how reliably they stay connected.

This post summarises the trend in plain terms and focuses on what it means for merchants and their accountants: review routines, control points, and the questions worth asking before you choose or renew an integration.

1) More control (and more rules) from platforms

A common direction across ecommerce and accounting ecosystems is stronger platform governance over integrations. That typically includes:

App marketplaces as the default route. Integrations are increasingly installed and authorised through official app stores/marketplaces rather than manual file uploads or custom scripts. For merchants, this can simplify discovery and installation, but it also means the platform’s rules play a larger role in what an integration can do and how quickly changes must be adopted.

Stricter permissioning and re-authorisation. Many connections now rely on token-based access and explicit permissions. In practice, this can mean integrations occasionally require re-connecting after password changes, security upgrades, or policy updates. It is not always predictable from the merchant side, so having a simple “connection health” check in your monthly close becomes more important than it used to be.

Faster change cycles. Platforms regularly update APIs, tax features, checkout behaviour, and reporting fields. Even when these changes are incremental, they can affect accounting outcomes: a renamed field, a new discount type, or a change in how refunds are represented can alter what flows into QuickBooks Online or Xero. Merchants don’t need to track every release note, but they do benefit from knowing which parts of the flow are most sensitive (tax, shipping, discounts, refunds, gift cards, and payment fees).

What’s uncertain: the pace and scope of governance changes vary by platform and region. Some merchants will see very little disruption; others may notice more frequent authorisation prompts or adjustments to mapping options after platform updates.

2) A stronger focus on payouts, fees, and reconciliation (not just orders)

Historically, many merchants judged an integration by whether orders appeared in the accounting system. That still matters, but a noticeable shift is the growing emphasis on reconciling to payment processor payouts (for example, card processors, PayPal-type wallets, and “buy now, pay later” providers). This reflects how many finance teams work in practice: bank deposits are the hard anchor, and everything else should tie back to them.

In practical terms, integrations are increasingly expected to help with:

Separating gross sales from fees. Payment processing fees, currency conversion fees, and chargeback fees can be material. If they are not captured distinctly, your profit reporting can be misleading. A common approach is to record gross sales to income and fees to an expense account, with the net amount matching the payout.

Handling timing differences. Orders may be created today, but payouts arrive days later (and may bundle multiple days). Refunds and disputes may also post in a different period than the original sale. A good workflow acknowledges those timing differences rather than trying to force everything into a single date field.

Reducing “mystery clearing balances.” Many merchants end up with a growing balance in a clearing or undeposited funds account because a few edge cases never quite match: partial refunds, mixed-tax orders, split shipments, or manual adjustments in the ecommerce admin. The recent trend is less about eliminating clearing accounts and more about managing them intentionally—using them as a reconciliation tool with defined rules and regular review.

What merchants can do now: ask your accountant which number they want to reconcile to each month (bank deposits, processor statements, or both), and confirm the integration supports that approach. This is often more important than “does it sync orders?” because it directly affects close time and confidence in the numbers.

3) Data mapping decisions are becoming more consequential

As platforms introduce more selling features—subscriptions, bundles, multiple tax behaviours, multiple warehouses, international pricing, and more payment methods—integrations have to make more choices about how data maps into the chart of accounts. The trend is not necessarily “more complexity for everyone,” but rather that more merchants reach a point where default mappings are no longer enough.

Three areas come up repeatedly in reviews and cleanup work:

Taxes (especially mixed rates and inclusive pricing). Tax behaviour varies by country and sometimes by product type. If the ecommerce platform calculates tax in a way that doesn’t line up with how the accounting system expects it, you can end up with small discrepancies that add up. It’s worth confirming how tax is posted (tax codes, tax liability accounts, and rounding behaviour) and whether the integration posts tax as summaries or line-level detail.

Discounts, gift cards, and store credit. Discounts might be a reduction of revenue, a marketing expense, or something you want tracked separately. Gift cards and store credit can be liabilities until redeemed. Integrations differ in how they represent these, and some only support certain treatments. The key is consistency: choose a method you and your accountant agree on and stick to it unless business needs change.

Refunds and returns. Refunds may be full, partial, or tied to returns. Some systems represent them as negative invoices, credit notes, or separate refund transactions. The accounting outcome matters: revenue reversal, tax adjustment, and (if tracked) inventory effects. If returns are frequent, clarify how the integration records them and how you will reconcile them to the processor’s dispute/refund reports.

Practical implication: integration setup is increasingly a finance configuration exercise, not just an app installation. Merchants benefit from treating the first month as a pilot period with a controlled review, rather than assuming everything is correct because the sync “ran.”

Further reading: details on ecommerce-to-accounting connections are available at https://www.carrytheone.co.uk.

Checklist for merchants and accountants

• Confirm what you will reconcile to each month (bank deposits, processor payouts, or both) and ensure the integration supports that workflow.
• Review how the integration handles fees, chargebacks, and currency conversion—separately from sales.
• Agree on treatments for discounts, gift cards/store credit, and refunds before going live.
• Check tax mapping: tax codes, rounding behaviour, and whether transactions post as summaries or line details.
• Set a recurring “connection health” step (e.g., monthly) to catch expired permissions or failed syncs early.
• Run a short pilot close: pick a week, reconcile payouts, and compare ecommerce reports to accounting totals to spot edge cases.
• Document any manual adjustments (and why) so they don’t become ongoing, unexplained differences.