--- title: "How to Sync Amazon Seller Central With QuickBooks" description: "Book Amazon payouts properly in QuickBooks: split settlements into sales, refunds, and every fee, then reconcile to the bank deposit automatically." canonical: https://www.stacksync.com/blog/sync-amazon-seller-central-with-quickbooks last_modified: 2026-07-22 --- # One Deposit, Forty Line Items: Amazon Payouts in QuickBooks > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md A practical guide to syncing Amazon Seller Central with QuickBooks. It explains why an Amazon payout is never the same number as your sales, which parts of a settlement belong on which QuickBooks account, how to set up a sync that splits the payout automatically, and how to reconcile the resulting entry to the bank deposit. Covers the item and price data that has to travel back the other way, the approaches sellers usually try first, and where each one breaks. Author Ruben Burdin · Founder & CEO Published July 22, 2026 Read time 9 min read ARTICLE Every couple of weeks Amazon sends money to your bank account. One number, one deposit line. Behind that number sit thousands of orders, a dozen categories of fee, refunds from a period that already closed, an advertising bill, and a slice of your own money that Amazon is holding in reserve. The deposit is what is left after all of it. Booking that deposit in QuickBooks as a single line called Amazon sales is the most common accounting mistake sellers make, and it is a quiet one. The bank reconciles, the file looks clean, and the accounts are wrong in a specific way: revenue is understated by exactly the amount Amazon charged you, and the cost of selling on the channel does not exist anywhere in the books. You cannot work out your Amazon margin from accounts that never recorded the fees. ![Three steps from one Amazon payout to books that balance: connect both sides, split the settlement, reconcile to the deposit](https://www.stacksync.com/images/blog-highlights/asc-quickbooks-summary.webp) This guide covers how to fix that: what a settlement is actually made of, which QuickBooks account each part belongs on, how to set up a sync that splits it automatically, and how to keep the resulting entry reconciled to the bank deposit every cycle. ## Why the payout never matches your sales A settlement is a statement, not a receipt. It lists everything that happened to your account during the period, in both directions, and the payout is the arithmetic result. Amazon reports it in enough detail to book properly, which is the good news. The bad news is that the detail arrives as a flat file with dozens of transaction types and no opinion about your chart of accounts. Roughly, a settlement contains four families of line. Money in: product sales, shipping and gift wrap credits, and reimbursements when Amazon loses or damages your stock. Money back out to buyers: refunds, and the portion of the original fees that Amazon returns with them. Money out to Amazon: referral fees on every sale, fulfillment fees if you use FBA, storage, advertising, and the seller subscription. And money that moves without leaving: reserve amounts held against future returns, released in a later period. Each of those wants a different treatment. A referral fee is a cost of sale. A storage fee is closer to warehousing. Advertising belongs with marketing, not with the cost of the product. A reserve is not an expense at all, it is your money sitting somewhere else, and treating it as one will misstate the period. That is the whole reason a mapping exists. ## What actually has to move Before configuring anything, decide where each kind of line lands. This is the table to agree with whoever owns the chart of accounts, because it is the part a tool cannot decide for you. | What Amazon reports | Where it belongs in QuickBooks | | --- | --- | | Product sales | Income, split by SKU group or channel | | Shipping and gift wrap credits | Their own income accounts, not merged into sales | | Promotional rebates | Contra-revenue, not a selling expense | | Refunds and returns | Contra-revenue, with the returned fee credited back | | Referral fees | Cost of sale | | FBA fulfillment fees | Cost of fulfillment | | Storage and long-term storage | Warehousing expense | | Advertising costs | Marketing expense | | Seller subscription | Fixed selling expense | | Reserve and unavailable balance | A balance sheet holding account, never an expense | | The net payout | The bank deposit, matched against the feed | Agree this mapping once. Everything downstream is mechanical after that. ![Pipeline from an Amazon settlement to a QuickBooks entry: settled, captured, mapped, posted, reconciled](https://www.stacksync.com/images/blog-diagrams/asc-quickbooks-concept.webp) *The settlement arrives as one file and leaves as one entry with every line on its own account.* Note what is not in that table: individual orders. Most sellers should not push thousands of Amazon orders into QuickBooks one at a time. It bloats the file, it slows the interface down, and it tells you nothing the summary does not. Keep order-level detail where it is useful, in the ERP or the warehouse, and send accounting the summary it actually needs. ## Setting the sync up With the mapping agreed, the configuration itself is short. Four steps, and none of them involve writing against the Selling Partner API yourself. - **Authorize both systems.** Connect Amazon Seller Central and QuickBooks over OAuth. No Selling Partner API credentials to store or rotate, and no scheduled export sitting on somebody's laptop. - **Choose what syncs.** Settlements and financial events out of Amazon, and, if QuickBooks holds your item list, items and prices back the other way. - **Apply the mapping.** Point each settlement line type at the account you agreed, and decide how sales are grouped: one income line, or split by SKU family or marketplace. - **Set the conflict policy.** Decide which side wins when the same item price changes in both, and turn it on. From there each closed settlement posts on its own. ![Sequence diagram: Amazon settlement closes, Stacksync splits the lines and posts to QuickBooks, then a QuickBooks item change is written back to the Amazon listing](https://www.stacksync.com/images/blog-diagrams-mermaid/asc-quickbooks-sequence.webp) *The round trip, including the half that goes back to Amazon.* That return leg is worth dwelling on. If your item list lives in QuickBooks, a price change made there should reach the listing, not wait for someone to remember. The risk with any two-way setup is an echo: the engine writes a price to Amazon, reads it back as a change, and writes it to QuickBooks again. Origin tracking is what stops that, and it is the difference between a sync you can leave running and one you have to watch. ## Reconciling to the bank deposit The test of the whole exercise is simple: when the deposit appears in the bank feed, does it match a QuickBooks entry exactly, with nothing left over. If it does, the split was right. If it does not, the difference tells you which line type was mishandled, and it is almost always the reserve or a refunded fee. Two timing details cause most of the confusion. First, a settlement period closes before the money moves, so the entry and the deposit can land on different days. Post the entry when the settlement closes and let it clear against the deposit rather than trying to date them together. Second, the reserve means money earned this period may be paid in the next one. If it sits in a holding account rather than being netted into sales, the two periods still reconcile cleanly. ## The three approaches, and where each breaks Most sellers try these in order, usually because each one stops working at a particular volume. | | Manual CSV export | Point connector | Real-time two-way sync | | --- | --- | --- | --- | | Cadence | When someone remembers | On a fixed schedule | When the settlement closes | | Fee detail | Whatever the spreadsheet keeps | Usually a fixed mapping | Every line type, mapped by you | | Direction | One way | One way | Both, on one connection | | Item and price changes | Retyped by hand | Not covered | Written back to the listing | | When Amazon throttles | The download fails | The run fails partway | Work queues and drains | | Reconciliation | Manual, every cycle | Manual when it drifts | Entry matches the deposit | The CSV works until the fee categories multiply. The point connector works until you need the other direction. ## Get the split right once Amazon gives you the detail you need to account for the channel properly. The work is deciding, once, where each line belongs, and then never doing it by hand again. Do that and the monthly question stops being what this deposit was and becomes what the channel actually earned, which is the question worth asking. Stacksync connects Amazon Seller Central and QuickBooks on one engine, in real time and both ways, over OAuth and without storing a copy of your data. To see it against your own settlements, [book a demo](https://www.stacksync.com/book-a-demo), or read more about the [Amazon Seller Central and QuickBooks integration](https://www.stacksync.com/integrations/amazon-seller-central-and-quickbooks), the [QuickBooks connector](https://www.stacksync.com/connectors/quickbooks), and what to look for in an [enterprise iPaaS for Amazon Seller Central](https://www.stacksync.com/blog/enterprise-ipaas-amazon-seller-central). If stock rather than the books is the pressing problem, start with [two-way sync between Amazon Seller Central and NetSuite](https://www.stacksync.com/blog/two-way-sync-amazon-seller-central-netsuite). FAQ ## Frequently asked questions How do I sync Amazon Seller Central with QuickBooks? Authorize both systems over OAuth, choose which Amazon records you want in QuickBooks, map each settlement line type to the account it belongs on, then turn the sync on. With Stacksync that is a short configuration rather than a project: no Selling Partner API keys to rotate, no CSV downloads, and no scripts to maintain. Once it is running, each settlement posts to QuickBooks with its fees split out and the net payout recorded as the deposit. Why does my Amazon payout not match my sales in QuickBooks? Because the payout is a net figure. Amazon takes referral fees, FBA fulfillment fees, storage, advertising, and the subscription charge out of gross sales, adds shipping and gift wrap credits, subtracts refunds, and holds part of the balance in reserve. What lands in your bank is what is left. If you book that deposit as a single sales line, your revenue is understated, every fee is invisible, and the cost of selling on Amazon never appears in the accounts. Should Amazon orders go into QuickBooks individually or summarized? For most sellers, summarized. Posting thousands of individual orders into QuickBooks Online inflates the file, slows it down, and gives you no information the settlement summary does not already carry. The usual pattern is a summary entry per settlement period with sales, refunds, and each fee type on its own line. Sellers who need per-order detail, usually for tax or channel-margin reasons, keep the detail in the ERP or the warehouse and send the summary to QuickBooks. Can data flow from QuickBooks back to Amazon? Yes, and that is often the half people forget. If QuickBooks holds your item list, a price change or a quantity-on-hand adjustment there should reach the Amazon listing rather than waiting for someone to retype it. Stacksync runs both directions on one connection and tracks the origin of every write, so a price pushed to Amazon is not read back a minute later as a fresh change and applied again. How often does Amazon settle? Amazon closes settlement periods on its own schedule, commonly every two weeks, and generates the report when the period closes. You cannot request one on demand. That is why a sync built around settlements has to watch for the report becoming available rather than poll on a fixed calendar, and why the reserve balance matters: money earned in the current period may not appear in a payout until the next one. Does this work with QuickBooks Online and QuickBooks Desktop? The pattern is the same either way, and the mapping work is identical. The difference is the connection: QuickBooks Online exposes a hosted API that a sync engine can authorize over OAuth, so it is the simpler of the two to keep in real time. Which edition you are on is worth confirming before you scope the project, because it changes how the connection is set up rather than what the entries look like. About the author Ruben Burdin Founder & CEO Ruben Burdin is the Founder and CEO of Stacksync, the first real-time and two-way sync for enterprise data at scale. Ruben is a Y Combinator alumni with a strong background in software engineering and business. [All posts by Ruben Burdin](https://www.stacksync.com/blog/author/ruben-burdin) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [connector Amazon Seller Central integrations](https://www.stacksync.com/connectors/amazon-seller-central) - [connector QuickBooks integrations](https://www.stacksync.com/connectors/quickbooks) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [Data engineering Amazon–NetSuite Sync for Beauty Brands: Match Variation Families to ERP Products 5 min read read](https://www.stacksync.com/blog/amazon-netsuite-sync-for-beauty-brands-match-variation-families-to-erp-products) [Data engineering Amazon–NetSuite Sync for Household Consumables: Reconcile Marketplace Order Quantities 5 min read read](https://www.stacksync.com/blog/amazon-netsuite-sync-for-household-consumables-reconcile-marketplace-order-quantities) [Data engineering Amazon–NetSuite Sync for Packaged Food Brands: Separate FBA and Merchant-Fulfilled Orders 5 min read read](https://www.stacksync.com/blog/amazon-netsuite-sync-for-packaged-food-brands-separate-fba-and-merchant-fulfilled-orders) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)