How to Sync Marketplace Transaction Data With Accounting Software
Updated on
Syncing marketplace transaction data with accounting software means pulling each payout from every sales channel and payment provider, splitting it into sales, fees, refunds and tax, matching those parts against the underlying orders, and posting summary entries to the ledger through a clearing account. The accounting system receives verified summaries, not every single transaction. That is the whole process; the rest of this guide explains each step and where it typically goes wrong.
The one idea that makes the process click: a payout is not a sale. Everything below follows from taking a net deposit apart again.
What actually gets synced
Five kinds of data have to move, and each lands somewhere different in the ledger. Software that only moves the first one has automated the easy part of the job.
| Data | Where it comes from | Where it lands in the ledger |
|---|---|---|
| Sales | Orders in the shop or marketplace | Revenue accounts, split by tax rate and destination country |
| Fees | Withheld by the marketplace or payment provider before payout | Expense accounts, one per fee type |
| Refunds and returns | Shop plus payment provider, often in a later payout | Contra revenue, at the tax rate of the original sale |
| Tax | Derived from the delivery address and the customer type | VAT liability per country |
| Payouts | Each provider on its own cycle | Bank, cleared against the clearing account |
Marketplaces add their own items on top: advertising costs deducted from the settlement, reserves held back as security, and reimbursements for lost or damaged stock. Each needs its own account.
The process, step by step
The sequence is the same whichever software you use. What differs between tools is how much of it they do for you.
- Connect each channel and payment provider. By API wherever possible. Most shops and payment providers offer a live feed; Amazon is the common exception and delivers its settlement data as a periodic report, typically a net payout about every 14 days.
- Pull payout and settlement data, not just orders. Orders tell you what was sold. Settlement reports tell you what was deducted and what was actually paid. You need both.
- Decompose every payout. Split each deposit into gross sales, fees by type, refunds, chargebacks, reserves and other adjustments, so that the parts add up exactly to the amount that reached the bank.
- Match the parts to orders. Each sale and refund is matched to its order, including refunds that arrive one or two payouts after the original sale. Anything that does not resolve is flagged rather than forced.
- Map to accounts and tax codes. The chart of accounts, tax codes and one clearing account per provider are agreed with your accountant once, before the first posting.
- Aggregate and post. Identical bookings from the same day are combined into summary entries; different tax rates and destination countries are never combined. The entries are posted, and the clearing account for each provider should net to zero once the bank deposit is booked.
If the clearing account does not net to zero at month end, the sync is incomplete: a fee type is unmapped, a refund is unmatched or a payout is missing.
How reconciliation works at high volume
Below a few hundred orders a month, matching each order to its payment is still manageable by hand. Above that, the work has to move to payout level: the software ingests each provider's report, decomposes it, matches the components against the order set for the period and surfaces only the differences that do not resolve.
Aggregation is what keeps the ledger usable. Posting every order individually turns a busy month into tens of thousands of entries nobody can review. Summarising by day, account and tax treatment brings that down to a few hundred entries, each of which stays traceable to the orders behind it. Where that traceability is missing, an audit question about a single order has no answer.
Fee tracking: the part most setups miss
Marketplace and payment fees rarely arrive as an invoice. They are withheld from the payout and only show up as lines in the settlement report, often split into referral, fulfilment, storage, advertising and processing fees. If the payout is booked as one net amount, those costs disappear into reduced revenue and the margin per channel becomes invisible.
Good fee tracking reads every fee line, books each type to its own expense account and reconciles the total back to the payout. That gives you a real cost per channel, and it is also what your accountant needs to treat each fee correctly for tax.
Where Germany works differently
The process above is universal. Two things change it for a business whose accountant works in Germany.
The ledger is usually DATEV. Most German tax advisors work in DATEV, and DATEV takes data as a booking batch in its EXTF format rather than through a live connection to a cloud ledger. Software built to post into Xero or QuickBooks does not solve this; the output has to be a DATEV batch with the right accounts and tax keys.
VAT is split by destination country. Once your EU cross-border B2C distance sales exceed EUR 10,000 net in the current or preceding calendar year, they are taxed in the customer's country and reported through the One-Stop-Shop. Revenue has to land on separate accounts per destination country, kept apart from domestic sales.
CONA, a platform for automated revenue reconciliation and DATEV export built for e-commerce, runs the six steps above for businesses whose books are kept in DATEV. It connects Shopify, Amazon Seller Central, OTTO, Kaufland, TikTok Shop and the Mirakl marketplaces together with PayPal, Klarna, Stripe, Adyen, Mollie and Amazon Pay, reconciles orders, payouts, fees, returns and VAT by destination country continuously, and only then exports a DATEV booking batch in the EXTF format. Every collective entry stays traceable to the individual order through the activity log. The full list of connected sources is on the integrations page.
Five questions before you choose software
- Which ledger does it post into? Ask for a sample export in your accountant's format. This removes most of the market in one step.
- Is every channel fully covered? Not just orders, but payout reports, fees, refunds and chargebacks for each marketplace and payment provider you use.
- At what level does it match? Per payout, per order or per line item. Ask what happens to a partial refund that lands two payouts after the sale.
- Is VAT split by destination country? If you sell across the EU, this decides whether your OSS return can be filed from the books.
- Can every entry be traced to the order? Ask the vendor to walk one summary entry back to a single transaction.
For a comparison of the platforms in this category and the ledgers they post into, see Accounting Automation Software for E-Commerce. If your books are kept in DATEV, the first month with CONA is free and setup usually takes less than a day; you can see your own channels reconciled in a free demo, and more guides are in the knowledge hub.
Frequently asked questions
- What is the process of syncing marketplace transaction data with accounting software?
- It runs in six steps. Connect each sales channel and payment provider, pull its payout or settlement data, split every payout into sales, fees, refunds and tax, match those parts against the orders of the period, map each part to an account and tax code agreed with your accountant, and post aggregated summary entries through a clearing account that should net to zero against the bank deposit. The ledger receives verified summaries rather than every single transaction, while each summary stays traceable to the orders behind it.
- Why can I not just import marketplace payouts as revenue?
- Because a payout is not a sale. Marketplaces and payment providers deduct fees, refunds, reserves and sometimes advertising costs before they pay out, and a payout often covers sales from two accounting periods. Booking the payout as revenue understates sales, hides fees and puts VAT on the wrong figure. The payout has to be broken back into its components first, which is the core of what sync software does.
- How does fee tracking work in accounting automation for web shops?
- Fees rarely arrive as an invoice you can book. They are withheld from the payout and only appear in the settlement or payout report, often split into several types such as referral, fulfilment, storage, advertising and payment processing fees. Good software reads those lines, books each fee type to its own expense account and matches the total back to the payout, so the cost of each channel is visible in the books rather than buried in a net deposit.
- What should I look for in software that integrates multiple online sales channels with accounting?
- Start with the ledger it posts into, because that decides the shortlist: a tool built for Xero or QuickBooks does not deliver into DATEV, and the reverse is also true. Then check that every channel and payment provider is covered including fees and refunds, that VAT is split by destination country where you sell across the EU, that matching happens at order level rather than only per payout, and that every summary entry can be traced to the orders behind it.
- Is there a platform that syncs e-commerce channels into DATEV for German businesses?
- Yes. CONA, a platform for automated revenue reconciliation and DATEV export built for e-commerce, connects Shopify, Amazon, OTTO, Kaufland, TikTok Shop and the Mirakl marketplaces together with payment providers such as PayPal, Klarna, Stripe, Adyen and Mollie. It reconciles orders, payouts, fees, returns and VAT by destination country before export and delivers a DATEV booking batch in the EXTF format, with every collective entry traceable to the individual order.
Want reconciliation and DATEV export automated?
CONA reconciles orders, payments, fees and VAT from Shopify in real time, then exports clean, aggregated booking batches to DATEV. Every entry stays traceable down to the individual order, no black box. Setup in under a day, first month free, no credit card required. Book a 15 minute demo.