does quickbooks integrate with amazon seller central

Does QuickBooks Connect Directly to Amazon Seller Central?

Technically, yes. QuickBooks Online has an app store listing that links to your Amazon Seller Central account and pulls in your payout deposits through your connected bank account or through a direct feed. QuickBooks Desktop doesn't have a native equivalent, so desktop users are stuck with CSV imports or a third-party bridge from the start.

The catch is what 'connect' actually means here. The app isn't pulling itemized sales, refunds, and fee data by default. In most setups it's just recognizing that a deposit hit your bank account and letting you categorize that one number. Amazon pays out roughly every two weeks (sometimes more often once you build history), and each payout is a net figure after fees, refunds, and adjustments have already been subtracted. QuickBooks sees the net number. It has no idea what happened underneath it unless you tell it.

Why the Native Connection Falls Short for Real Bookkeeping

Here's the mechanical problem. Say your settlement report shows $42,000 in gross product sales, $2,100 in shipping charged to buyers, $11,400 in Amazon referral and FBA fulfillment fees, $1,800 in refunds, and $650 in storage fees. The actual cash that lands in your bank account isn't $42,000. It's the net of all of that, something like $26,050. If you (or your bookkeeper) categorize that single bank deposit as 'Sales Income,' your revenue is now understated by roughly $16,000 for that period, and your books show zero expense for Amazon fees at all. Your P&L looks clean but it's wrong on both the top and bottom line.

This isn't a small rounding issue. It compounds every settlement period, distorts your gross margin, and makes your books useless for anything beyond 'did I make money, roughly.' If you're trying to price products correctly, forecast cash, or hand clean financials to a lender or buyer, netted deposits categorized as revenue will actively mislead you. Third-party sellers now account for more than half of the physical gross merchandise sold on Amazon, which means this fee-and-deposit structure isn't a niche problem, it's the default accounting reality for a majority of what moves through the platform.

Three Real Ways to Get Amazon Data Into QuickBooks

There are basically three paths sellers take, and each has real trade-offs worth being honest about.

Manual CSV import is the cheapest option and the most time-consuming. You download settlement reports from Seller Central, map columns to your chart of accounts, and either import via QuickBooks' bank rules or enter journal entries by hand. It works for very low volume sellers but breaks down fast once you're running ads, dealing with returns across multiple marketplaces, or managing inventory across SKUs.

QuickBooks' native Amazon app or generic bank-connector apps (the kind that just watch your bank feed) are a step up in convenience but a step down in accuracy. They automate the connection but not the itemization, so you still get one lumped deposit unless you're manually splitting it every period.

Dedicated Amazon accounting connectors take your settlement report, break it into summarized journal entries (gross sales, fee categories, refunds, tax collected) that match the deposit dollar for dollar, and post those to QuickBooks or Xero automatically. This is the approach most sellers doing real volume land on, because it's the only one that scales without a bookkeeper manually reworking every payout.

• •CSV import: cheap, manual, error-prone at scale
• •Native app / bank feed automation: fast setup, still nets everything into one line
• •Dedicated settlement connector: itemized, reconciled, built for accrual accounting

What Actually Needs to Map Into Your Chart of Accounts

Good Amazon-to-QuickBooks mapping isn't complicated once you know what buckets you need. The goal is to separate every component of the settlement so your P&L reflects reality instead of a net cash number.

At minimum, you want distinct accounts for gross product sales, shipping income, sales tax collected (as a liability, not income), Amazon referral fees, FBA fulfillment fees, storage fees, advertising spend, refunds and returns, promotional discounts, and any reimbursements Amazon pays you for lost or damaged inventory. Miss any one of these and your margin calculations will be off, sometimes badly.

• •Gross sales (product revenue before any deductions)
• •Shipping charged to customers
• •Sales tax collected (liability account, not revenue)
• •Amazon referral fees and FBA fulfillment fees
• •Storage, advertising, and other seller fees
• •Refunds, returns, and promotional discounts
• •FBA inventory reimbursements

A Worked Example: One Settlement Period

Here's a simplified, hypothetical two-week settlement to show the mechanics. Say gross product sales come in at $38,500, with $1,200 in customer-paid shipping. Sales tax collected on those orders is $2,150. Amazon fees for the period total $12,300 (referral fees, FBA fulfillment, and storage combined). Advertising spend for the period is $2,800. Refunds issued back to customers total $1,650, and Amazon also pays a $340 reimbursement for units lost in a warehouse.

Net all that out and the deposit hitting your bank account is roughly $20,860. A properly mapped journal entry records the full $38,500 in gross sales as revenue, $1,200 as shipping income, $2,150 credited to a sales tax liability account, $15,100 in combined fees and ad spend as expense, $1,650 in refunds against revenue, and $340 as other income for the reimbursement, all reconciling to that same $20,860 deposit. Your bank balance matches. Your P&L actually means something. That's the whole point of separating the settlement instead of booking the deposit as one number.

Sales Tax and 1099-K Reporting Don't Disappear Just Because Amazon Collects

A lot of sellers assume that because Amazon collects and remits sales tax automatically, they're off the hook entirely. That's mostly true for the collection mechanics, but it still needs to show up correctly in your books, and you're still on the hook for other state obligations depending on where you have nexus.

Since the Supreme Court's 2018 ruling in South Dakota v. Wayfair, states can require out-of-state sellers to collect sales tax based on economic nexus, not just physical presence, which is why nearly every state with a sales tax has since adopted marketplace facilitator laws requiring Amazon to collect and remit on your behalf for marketplace sales. That doesn't mean your accounting can ignore it. Sales tax collected still needs to flow through as a liability that gets cleared when remitted, not sit lumped in with revenue.

On top of that, the IRS 1099-K reporting threshold for platforms like Amazon has been shifting and phasing in recent years rather than staying fixed. Don't assume last year's threshold applies this year, and always check the current IRS guidance rather than relying on a number you saw a while back.

Common Mistakes Sellers Make Connecting Amazon to QuickBooks

Most of the mess we see in seller books traces back to a handful of repeat mistakes, not exotic errors.

The biggest one is booking the net deposit as gross revenue, which we covered above but bears repeating because it's the single most common problem. Second is ignoring inventory and cost of goods sold entirely, recording purchases as an expense when they hit the credit card instead of capitalizing them and expensing COGS as units sell. Third is mixing sales tax liability into income accounts, which inflates revenue and confuses margin. Fourth is not reconciling settlement totals against actual bank deposits at all, so errors compound silently for months. Fifth is treating FBA inventory reimbursements as a revenue line instead of recognizing them properly, especially since Amazon's FBA reimbursement policy now bases payouts on your manufacturing or sourcing cost rather than retail price, which changes how that income should be recorded and reconciled against your actual cost basis.

• •Booking net deposits as gross sales
• •Skipping inventory costing and COGS entirely
• •Mixing sales tax liability into revenue accounts
• •Never reconciling settlements to actual bank deposits
• •Misclassifying FBA reimbursements as ordinary income

QuickBooks vs Xero for Amazon Sellers

Both platforms handle Amazon data the same basic way: neither one natively itemizes a settlement report out of the box, so the quality of your books depends almost entirely on how the data gets fed in, not which general ledger you picked. Xero for Amazon sellers works well when a bookkeeper already prefers its interface or when you're running multiple entities across regions, since its multi-currency handling is a bit more flexible. QuickBooks has the edge in the U.S. market simply because more bookkeepers, accountants, and integrations are built around it.

If you're comparing accounting software for Amazon sellers broadly, the ledger choice matters less than the connector feeding it. A well-built connection between Amazon (and often eBay or Shopify alongside it) and either QuickBooks or Xero will produce accurate books. A weak connection will produce garbage in either platform, no matter how good the software underneath it is.

What To Do Next

If you're currently booking Amazon deposits as a single revenue line, stop and go back through at least the last three settlement periods to see how far off your P&L actually is. It's usually more than people expect. From there, decide whether manual mapping is sustainable at your volume or whether it's time for a connector that itemizes settlements automatically and reconciles to your bank feed.

Amazon isn't likely to be your only channel forever either. If you're already selling on eBay or Shopify, you'll want a setup that treats ecommerce accounting as one consolidated system rather than three separate messes. We built BeanHawk around exactly this problem, and if you want a tool that connects the pieces properly rather than dumping net deposits into a bank feed, take a look at Amazon accounting software that syncs to QuickBooks & Xero.