Automate marketplace payouts into QuickBooks Online or Xero
Updated · By Ecomsellertool editorial team
To automate marketplace payouts into QuickBooks Online or Xero, pull each Amazon settlement report, Shopify Payments payout and Walmart reconciliation report as it posts, map every line type to an account your accountant approves, and post one balanced summary entry per payout. Rules check that the lines add up to the bank deposit, and anything that does not, such as a reserve or a new fee, goes to a person.
- Amazon schedules settlement reports itself and they cannot be requested; the Flat File V2 version lists every charge in amount-type, amount-description and amount columns (checked October 2, 2026).
- Shopify Payments payout details break each payout into charges, refunds, adjustments, fees and reserves, and export to CSV with the amount, fee and net of each transaction.
- Walmart's Recon Report API returns settlements, order transactions, commissions, shipping fees, taxes, adjustments and refunds for reconciliation.
- QuickBooks Online requires a journal entry's debits to equal its credits, and Intuit tells users who are unsure which accounts to use to consult their accountant.
- Xero's own Shopify integration is free on all Xero plans; A2X, a connector app, lists plans from US$29 a month for a channel such as Amazon or Shopify (checked October 2, 2026).
The step map: who runs each step
Trigger: A marketplace payout posts: an Amazon settlement report, a Shopify Payments payout or a Walmart reconciliation report.
| Step | What happens | Who runs it |
|---|---|---|
| 1 | When a settlement or payout posts, the workflow pulls the report with every line item and stores it under its settlement or payout ID. | Rule |
| 2 | The lines are checked to add up to the report's own total, and the payout ID is checked so the same payout is never posted twice. | Rule |
| 3 | Each line type (sales, shipping, refunds, each fee, tax collected by the marketplace, reimbursements, reserves) is mapped to an account through a mapping table your accountant approves. | Rule |
| 4 | An AI model suggests an account for any line type the table has never seen, with its reasoning, and the entry waits until a person accepts or changes it. | AI model |
| 5 | One balanced summary entry is built per payout and currency, with the net amount sent to a clearing account and the source report attached. | Rule |
| 6 | Mismatches are flagged: totals that do not tie out, reserves held or released, refunds without a matching order, and deposits that have not reached the bank. | Rule |
| 7 | A person reviews flagged payouts and approves the entry; payouts that tie out with every line mapped can post on their own once your accountant agrees. | Person |
| 8 | The entry is posted to QuickBooks Online or Xero, matched to the bank deposit when it arrives, and logged with the report it came from. | Rule |
6 rule steps · 1 AI model step · 1 person step. A rule follows fixed logic you approve; an AI model handles messy input and its output is checked by rules; a person makes the calls listed below.
What stays with a person
- The account mapping, and any new line type the model suggests an account for
- Payouts that do not tie out to their own total or to the bank deposit
- Reserves, chargebacks and disputes, and any reimbursement you choose to chase
- Month-end cut-off and tax treatment, decided with your accountant
Which tools can run it
- Your accounting system's own channel integration, such as Xero's Shopify integration
- A connector app built for marketplace payouts, such as A2X
- Custom code on your accounts, when channels, entities or rules outgrow the apps
Systems it connects
- Amazon Seller Central
- Shopify Payments
- Walmart Marketplace
- QuickBooks Online
- Xero
- Your bank feed
Build size: Medium
Reading the reports is routine; the work is the account map for each channel and the checks that catch a payout that does not tie out.
A marketplace payout is not a sale. It is sales, minus fees, minus refunds, plus or minus a dozen smaller lines, netted into one bank deposit days or weeks later. Bookkeepers who enter that deposit as revenue get the books wrong, and bookkeepers who rebuild it from reports every week lose a day to it. This recipe posts each payout as one balanced summary entry, splits fees and refunds by account, and stops the moment something does not add up. It is one page of our automation library.
What does the workflow do, step by step?
The step map above runs once per payout. It starts from the marketplace's own report, never from the bank deposit, because only the report says what the deposit is made of. Xero's e-commerce accounting guide makes the same point: a payout arrives bundled, so you separate gross sales from platform fees and refunds, and the net left over should match the deposit (checked October 2, 2026). Each channel publishes that breakdown in its own format.
| Channel | Where the payout data comes from | What it lists |
|---|---|---|
| Amazon | The settlement report, Flat File V2, retrieved through the Selling Partner API. Amazon schedules these reports itself; they cannot be requested or scheduled, and the older flat-file and XML versions are deprecated (checked October 2, 2026) | Settlement start and end dates, deposit date and total amount, then one row per charge, with amount-type, amount-description, amount and SKU |
| Shopify Payments | Payout details in the Shopify admin, exportable to CSV (checked October 2, 2026) | Charges, refunds, adjustments, fees and reserves; per transaction, the amount, fee and net |
| Walmart | The Recon Report API, which Walmart says can be parsed into accounting and ERP systems (checked October 2, 2026) | Settlements, order transactions, commissions, shipping fees, taxes, adjustments and refunds |
Between settlements, Amazon's Finances API returns financial events without waiting for a statement period to close (checked October 2, 2026). The workflow can use it to warn early about a large refund or a new charge, but it posts from the settlement report, so the entry matches the money that actually moved.
The heart of the build is the account map: one row per line type, agreed with your accountant before anything posts. The table below is an example of its shape, not a recommendation for your books.
| Line type in the payout | Example account | Note |
|---|---|---|
| Product sales | Sales, one account per channel | Lets you see revenue by channel |
| Shipping and gift wrap charged to buyers | Shipping income | Kept apart from product sales |
| Refunds to buyers | Sales refunds | Refund fees go with the other fees |
| Referral, commission and fulfillment fees | Selling fees and fulfillment costs | One account per fee family keeps contribution margin readable |
| Advertising charged against the payout, if your ad account bills that way | Advertising | Otherwise ads arrive as a card charge |
| Sales tax the marketplace collected and remits | A tax clearing account, not income | Under marketplace facilitator rules, the marketplace collects; your accountant decides the treatment |
| Reimbursements for lost or damaged units | Other income or an inventory adjustment | Your accountant decides |
| Reserve held back or released | A marketplace reserve balance | Explains why the deposit differs from sales minus fees |
| The net payout | A clearing account for the channel | Cleared when the bank deposit is matched |
Payout check: sales + other income − refunds − fees − other charges − reserve held + reserve released = the bank deposit
Which tool should run it?
Pick the simplest option that covers your channels, and be honest about when that is an app rather than a build. If you sell on Shopify and use Xero, start with Xero's own Shopify integration: Xero lists it as free on all Xero plans, syncing sales, payouts, fees and taxes, with a daily summary option for high-volume stores (checked October 2, 2026). If you sell on several standard channels, a connector app is usually the better choice than custom code.
| Option | Fits when | What to know |
|---|---|---|
| Your accounting system's own channel integration | One Shopify store into Xero | Free on all Xero plans; daily summary or per-sale sync; Shopify Payments payouts matched to the bank |
| A connector app such as A2X | Standard channels into one accounting file | A2X says it posts payout summaries to QuickBooks Online, Xero, Sage or NetSuite for channels including Amazon, Shopify, eBay, Etsy, Walmart, TikTok Shop and PayPal. Its pricing page lists plans from US$29 a month for channels such as Amazon or Shopify, and from US$79 a month for Walmart (checked October 2, 2026) |
| Custom code on your accounts | Channels or charges the apps miss, several legal entities, your own mapping rules, or payout data that also feeds reporting | QuickBooks Online journal entries must balance, debits equal to credits, and Xero's Accounting API has a Manual Journals endpoint for posting them (checked October 2, 2026). It can run on Ecomsellertool Growth OS |
Custom code earns its cost when the payout is one input among several: 3PL invoices, landed costs, a profit report per SKU and a finance team that wants the mapping rules in code it can test. If all you need is clean books for two channels, the app is cheaper and you should use it.
What should stay with a person?
The account map, first of all. The model step exists for the day a marketplace adds a fee type nobody has seen: it suggests an account and explains why, but the entry waits until a person accepts or changes the mapping. After that, a person handles the payouts the rules flag, decides what to do about reserves, chargebacks and disputes, and closes the month with your accountant. Recovering lost inventory is a separate job, covered on our FBA reimbursements page; this workflow only books the reimbursement lines Amazon has already paid.
What can go wrong, and how do you catch it?
Most errors in marketplace bookkeeping are timing and classification errors, not arithmetic. Each one needs a check that stops the entry instead of posting a wrong number.
| What goes wrong | How it shows up | The check that catches it |
|---|---|---|
| Amazon holds a reserve | The deposit is less than sales minus fees | Reserve lines map to a reserve balance; Amazon's guide to account level reserves describes them as temporary holds, set per seller, with a standard release about 7 days after delivery (checked October 2, 2026) |
| The deposit is late or missing | The clearing account does not clear | An alert when no matching bank line arrives in the expected window; Shopify says a bank can take 1 to 3 business days to deposit a payout |
| A new fee type appears | An unmapped line | The model suggests an account and the entry waits for a person |
| A settlement spans two months | Revenue lands in the wrong month | Your accountant chooses the cut-off rule, and the workflow applies it the same way every time |
| The same payout is posted twice | Doubled sales and fees | Payout and settlement IDs are stored and a repeat is refused |
| 3PL charges never appear | Fulfillment costs look too low | 3PL invoices are a separate input, checked as on our 3PL reconciliation page |
Who builds this for ecommerce brands?
Ecomsellertool builds finance workflows like this one on your own accounts. We have built software on Amazon's seller APIs since 2017, including fee and finance data pipelines for profit reporting, and shipped 50+ tools for 100+ teams. We map your channels and your accountant's chart of accounts first, then build the pulls, checks and postings. Send a project brief below, or read how our workflow automation service works.
The data side of this recipe is work we have shipped:
- Fees Amazon does not report as a line. For Seller-Drive we built a profit and loss statement that pulls Amazon's financial data through its Finances API and a fee calculation engine that computes the fees Amazon does not provide.
- An accounting firm's Amazon pipeline. For Zonkeepers, an accounting firm, we built an AWS pipeline that ingests Amazon order and finance reports into P&L analytics, with Amazon fees, tax, shipping, refunds, promotions and reimbursements broken out.
Get this workflow built
Send us your version of this workflow
Describe the workflow you want automated. We reply with a written plan: scope, timeline and a fixed price.
Frequently asked questions
Should I post every marketplace order to QuickBooks or Xero?
Usually not. Most brands post one summarized entry per payout, split by account, and keep order-level detail in the marketplace reports or their own reporting. Summaries keep the ledger readable and still match the bank deposit. Your accountant decides how much detail your books need.
Why doesn't my Amazon deposit match my sales?
Because a payout is net. Amazon deducts fees, refunds and other charges before it pays, and it can hold part of the balance as a reserve that is released in a later period. The settlement report lists each of those lines, which is why the workflow posts from the report rather than from the bank deposit.
Is A2X or a custom build better for marketplace accounting?
For standard channels going into one accounting file, a connector app such as A2X is usually the better choice, since it is built for exactly this job. A custom build earns its cost when you have channels or charges the app does not cover, several legal entities, mapping rules of your own, or payout data that also feeds other systems.
Can the workflow post entries without anyone checking them?
It can, for payouts that tie out to the deposit and contain only line types already mapped, if your accountant agrees. Anything else, such as a new fee, a reserve change or a missing deposit, waits for a person. Many teams review every entry for the first few months, then switch to exceptions only.
Is this page accounting or tax advice?
No. It shows how the workflow moves and checks the numbers. Which accounts to use, how to treat sales tax a marketplace collected, reserves and reimbursements, and how to handle a payout that spans two months are decisions for your accountant or tax advisor.
Which marketplaces can this workflow handle?
Any channel that publishes payout data you can download or read through an API. This page covers Amazon settlement reports, Shopify Payments payouts and Walmart's reconciliation report. For any other channel we check its payout data first, before we put it in a plan.
