Your Amazon payout is not revenue. Here’s how to break it down correctly in QuickBooks Online, which integration tool fits your setup, and the clearing account method that keeps your GL clean.
Every two weeks, Amazon deposits a single number into your bank account. No breakdown. No line items. Just a lump sum that quietly bundles gross sales, FBA fees, storage charges, advertising spend, refunds, and a rolling reserve into one figure.
If your bookkeeper—or your client—is categorizing that deposit as “Revenue” straight from the bank feed, the income statement is wrong. Margins are wrong. And tax liability is almost certainly wrong, too.
This isn’t a QuickBooks problem. It’s an architecture problem.
The way you connect Amazon to QuickBooks determines whether your books tell the truth or merely balance on paper.
Here’s a breakdown of how the integration actually works, which tools are worth your time, and the one workflow change that makes reconciliation genuinely straightforward.
Why the Native Intuit Connector Falls Short
QuickBooks does offer a native Amazon connector, and in January 2026, Amazon embedded a QuickBooks dashboard directly inside Seller Central.
It gives sellers a P&L snapshot and fee visibility without leaving Amazon—useful for a seller checking margins, but not useful for a bookkeeper building accurate financials.
The native connector has the same structural problems it has always had: inconsistent data pulls, limited chart-of-accounts configuration, and poor handling of marketplace facilitator tax.
For any client doing meaningful volume, it creates more cleanup work than it saves.
The fix is a dedicated third-party integration layer.
But before you pick one, you need to make a decision about architecture.
The Core Decision: Summary vs. Order-Level
Every Amazon integration tool falls into one of two camps.
Settlement-summary tools ingest the 14-day settlement report and post a single aggregated journal entry to QuickBooks. That entry breaks out gross revenue, refunds, FBA fees, referral fees, and storage charges into separate chart-of-accounts lines. Transaction volume stays low. The entry matches the bank deposit exactly. Reconciliation takes minutes.
Order-level tools push individual invoices or sales receipts for every transaction, with SKU-level COGS tracking inside QuickBooks. For a client doing 5,000 orders a month, this means 5,000 transaction records hitting the GL every cycle. QuickBooks slows down, report generation lags, and the configuration required to map every SKU correctly becomes a maintenance burden of its own.
For most ecommerce bookkeeping clients, settlement-summary is the right default.
Order-level sync only makes sense when a client genuinely needs SKU-level inventory managed inside QuickBooks itself—which is less common than tool vendors would suggest.
4 Integration Tools Worth Knowing
1. A2X — Best for Clean Accrual Accounting on a Single Channel
A2X has been the default choice for accountants focused on settlement-period accrual accounting for years, and it holds that position for good reason.
It pulls the 14-day Amazon settlement, converts it into a clean summary journal entry, and posts it to QuickBooks with revenue, fees, and refunds mapped to separate accounts.
It handles multi-currency adjustments, marketplace facilitator tax splits, and rolling reserves reliably.
The setup is straightforward, and the reconciliation workflow is predictable.
Where it gets expensive: A2X pricing scales by transaction volume, which makes it a tough call for low-margin clients.
It also does one thing—Amazon settlement accounting. If a client adds Shopify or processes payments through Stripe, you need a separate connector for each channel, and the app costs stack up.
Configuration depth is also limited compared to newer tools. You get reliable output, but not much flexibility in how data is mapped or how line items are handled.
Best fit: Single-channel Amazon sellers, accountants who want a proven settlement tool with minimal configuration, and firms already standardized on the A2X workflow.
2. PayTraQer — Best for Customization, Cost Efficiency, and Multi-Platform Coverage
Most Amazon integration tools make one decision for you: either you get summary-level journal entries or per-transaction sync.
PayTraQer gives you both, by channel, with the flexibility to switch between them depending on what a client actually needs.
That configurability is where it separates itself from A2X and other summary tools in practice.
A2X locks you into settlement-summary accounting with limited mapping control. PayTraQer lets you get granular at the field level. You control exactly how each transaction type maps to your chart of accounts, which items get consolidated under Common Item Mode, and how taxes and fees are routed.
For accountants managing multiple clients with different reporting requirements, that per-client configurability matters.
Platform coverage extends beyond the usual list. Beyond Amazon, Shopify, eBay, and Walmart, PayTraQer connects to a wider range of payment gateways and ecommerce platforms—including Stripe, PayPal, Square, WooCommerce, Etsy, and more.
For clients running non-standard stacks or expanding to newer platforms, that breadth reduces the chance of needing a second connector later.
The review tab and rollback feature are genuinely useful guardrails.
Transactions are staged in a review tab before anything posts live. You can audit exactly how Amazon sales, fees, refunds, and marketplace facilitator taxes will land in the chart of accounts before committing.
If a mapping goes wrong after posting, the rollback function unwinds the entries cleanly—a level of control that A2X doesn’t match.
On cost, PayTraQer is more cost-efficient than A2X at comparable transaction volumes.
A2X pricing scales aggressively by tier, which becomes a real issue for high-volume clients or firms managing many accounts. PayTraQer’s pricing model provides more room for growth without forcing a tier upgrade simply because order counts increase.
Where it draws a line: It handles financial data only. It maps transactions for accurate P&L and COGS reporting but does not sync live FBA inventory counts into QuickBooks.
Best fit: Accountants who want per-transaction control without sacrificing summary-mode efficiency for high-volume channels, clients using non-standard platform combinations, and firms that need one tool to cover a broad range of marketplace and gateway connections without paying for separate connectors.
3. Webgility — Best for QuickBooks Desktop and Operational Inventory Management
Webgility operates at the order-level end of the spectrum.
It pushes individual transaction details into QuickBooks with deep SKU mapping and automated COGS tracking across channels.
If a client uses QuickBooks Desktop or Enterprise as both the financial ledger and the operational inventory master, Webgility is built for that setup.
Where it creates friction: Pushing individual orders into QuickBooks introduces significant configuration complexity.
Users consistently run into tax-calculation conflicts when Webgility’s sync logic operates alongside QuickBooks’ built-in automated sales tax engine.
That combination requires careful, ongoing configuration to avoid errors.
Best fit: QuickBooks Desktop or Enterprise environments where inventory management inside QuickBooks is a genuine operational requirement, not merely a reporting preference.
4. Synder — Worth Knowing for Hybrid Reporting Needs
Synder offers both per-transaction sync and summary-sync modes, covering Amazon, Shopify, Stripe, PayPal, and Square.
For clients who need granular transaction-level data for audit purposes but want the option to run summary mode during high-volume periods, the dual-mode setup is useful.
It connects to QuickBooks Online, QuickBooks Desktop, and Xero.
That said, PayTraQer covers a similar range of use cases with greater customization depth and broader platform support.
Synder is worth evaluating if a client specifically uses Xero rather than QuickBooks or if a firm already has established Synder workflows in place.
Best fit: Xero-based setups or clients who need transaction-level detail for audit trails and aren’t running high-volume, multi-channel operations.
The Clearing Account Method — The Workflow Change That Actually Matters
Regardless of which tool you use, the single most important workflow decision is where the integration posts its entries.
Never configure an Amazon integration to post directly into the client’s primary bank account feed.
Here’s the setup that works:
Step 1
Create an Amazon Clearing Account in the chart of accounts.
Set it up as a Bank-type account. This allows it to function as a dummy bank register inside QuickBooks.
Step 2
Point the integration tool to the clearing account, not the operating bank.
The tool posts gross revenue, FBA fees, refunds, advertising costs, and marketplace facilitator tax into this clearing ledger.
Every line item lives here, separated and correctly categorized.
Step 3
When the actual deposit hits the real bank feed, record it as a Bank Transfer from the clearing account to the operating account.
Do not categorize it as income.
Do not add it directly.
Step 4
Match the bank transfer in one click inside the Banking Center.
The result: Revenue is recorded once at the gross level, with fees broken out properly.
The actual deposit is simply the settlement of a transfer.
There is no double-counted income, no distorted margins, and the clearing account balance should return to zero after every settlement cycle—creating a built-in reconciliation check.
On tax mapping, route marketplace facilitator tax lines directly to a sales tax liability account.
QuickBooks will attempt to apply its own tax logic to automated transactions if you allow it to do so.
That creates duplicate tax entries that are time-consuming to unwind at month-end.
Choosing Based on Your Client’s Actual Setup
| Client Profile | Recommended Tool | Why |
| Single Amazon channel, clean accrual focus | A2X | Proven settlement-summary workflow and reliable marketplace facilitator tax handling |
| Multi-channel or mixed payment stack | PayTraQer | Broad connector coverage, flexible mapping, and better value at scale |
| High-volume clients needing per-transaction control | PayTraQer | Configurable per-transaction or summary mode by channel |
| QuickBooks Desktop, inventory managed in QuickBooks | Webgility | Built for Desktop/Enterprise order-level sync |
| Xero users or audit-focused transaction detail | Synder | Dual-mode sync and Xero compatibility |
| Low volume, just starting out | Manual journal entry | Settlement-report-based bookkeeping without connector costs |
If you want a more complete breakdown beyond the tool comparison, see our detailed guide to navigating Amazon with QuickBooks Online.
The tool matters less than the architecture.
Any of the summary-based options above, paired with a properly configured clearing account and correct marketplace facilitator tax mapping, will produce accurate financials.
The differences between tools come down to channel coverage, configurability, pricing at scale, and how much setup your team is willing to maintain for each client.
