Amazon FBA Accounting with Wave: The Complete Setup Guide (2026)
March 4, 2026
·
MerchantLedger Team
·
15 min read
Key Takeaways
- Wave is genuinely free accounting software — not a free trial — making it the best option for Amazon sellers under ~$500K annual revenue who want double-entry bookkeeping without a monthly fee.
- Wave has no native Amazon Seller Central integration, and no third-party tool (A2X, Link My Books, Bookkeep) supports Wave — MerchantLedger is the only solution that posts Amazon FBA settlements directly to Wave via API.
- Use the chart of accounts template in this guide to create Amazon-specific accounts in Wave before posting your first settlement. Wave does not support sub-accounts, so the naming convention matters.
- Every settlement journal entry must be balanced: total debits equal total credits. The debit to Amazon Settlements Receivable clears when the bank deposit arrives.
- Never record the net bank deposit as revenue. Your actual gross sales for a typical two-week period are thousands of dollars higher than what hits your account — fees and refunds are deducted before the deposit.
- Without COGS entries, your gross margin in Wave is overstated. MerchantLedger calculates and posts COGS automatically using the Average Cost method.
Why Wave Is a Legitimate Choice for Amazon FBA Accounting
Wave is genuinely free — not a freemium tier with the useful features locked behind a subscription. The accounting module (double-entry books, unlimited accounts, journal entries, financial reporting), invoicing, and receipt scanning are all free with no usage limits and no expiration. Wave makes money on payment processing and payroll, not on accounting software.
For Amazon FBA sellers doing under roughly $500K in annual revenue, Wave offers everything you actually need: a complete chart of accounts, journal entry screens, a profit and loss statement, and a balance sheet. It handles multi-currency. It supports the clearing account structure that Amazon's settlement cycle requires. And because it's cloud-based with an API, it can accept programmatic journal entry posts from tools like MerchantLedger.
The gap is integration. Wave has no native connection to Amazon Seller Central. There is no official Wave app on Amazon's integration marketplace. And unlike QuickBooks Online and Xero, Wave has not built a broad third-party app ecosystem, so most Amazon accounting tools simply do not support it. A2X, Link My Books, Bookkeep, and ConnectBooks all require QuickBooks or Xero. Not Wave.
MerchantLedger is the only tool that connects Amazon SP-API to Wave's API directly, pulling your settlement data and posting balanced journal entries to Wave automatically — the same workflow it uses for QuickBooks and Xero, built specifically to support Wave's API format.
If you are a small Amazon seller who does not want to pay $30–50/month for QuickBooks Online or Xero, Wave is a defensible choice. This guide will show you how to set it up correctly for Amazon FBA Wave accounting from scratch.
The Manual Approach — And Why It Breaks Down
Before getting to the setup, it helps to understand what manual settlement accounting in Wave actually involves. Because many sellers try to do this, discover how painful it is, and conclude (incorrectly) that Wave just cannot work for Amazon accounting.
The process starts with downloading your settlement flat file V2 from Seller Central. Go to Reports → Payments → Settlement tab, find a completed period, and download the V2 tab-delimited file. What you get is a text file with hundreds or thousands of rows — one per transaction — across dozens of column headers. Open it in Excel or Google Sheets and you will see order IDs, transaction types like Principal, FBAPerUnitFulfillmentFee, Commission, FBAMonthlyInventoryStorageFee, and amounts that can be positive or negative depending on the direction of the transaction.
To turn that into Wave journal entries, you need to:
- Sum all
Principalrows to get gross product sales. - Sum all
Shippingrows to get shipping income. - Sum all
Refundtransactions separately. - Sum each fee type individually:
FBAPerUnitFulfillmentFee,Commission,FBAMonthlyInventoryStorageFee,FBALongTermStorageFee,Advertising, and others. - Open Wave, navigate to Accounting → Transactions → More → Add Journal Transaction.
- Enter each account, the description, and the debit or credit amount — one line at a time.
- Verify total debits equal total credits before saving.
This takes 30 to 45 minutes per settlement period. Amazon runs settlements every 14 days, which means roughly 26 times a year. At 40 minutes each, that's over 17 hours annually — and that's assuming you make no errors. One transposed digit or wrong account means your P&L is wrong until you find it.
At any meaningful scale — multiple SKUs, multiple marketplaces, or a high order volume where settlements have 1,000+ rows — this process is untenable. The settlement report is designed for Amazon's systems, not for manual bookkeeping.
What Every Settlement Contains — and How to Account for It in Wave
Before setting up your accounts, it helps to map every transaction type that appears in an Amazon FBA settlement to its correct accounting treatment. This table is the reference you should keep open while building your chart of accounts.
| Transaction Type | Wave Account | Direction | Example Amount |
|---|---|---|---|
| Product sales (Principal) | Amazon - Product Sales | Credit (Income) | $7,612.06 |
| Shipping income | Amazon - Shipping Income | Credit (Income) | $318.50 |
| Customer refunds | Amazon - Refunds | Debit (reduces income) | $215.60 |
| FBA fulfillment fees | Amazon - FBA Fulfillment Fees | Debit (Expense) | $892.41 |
| Referral fees (commission) | Amazon - Referral Fees | Debit (Expense) | $1,156.22 |
| Monthly storage fees | Amazon - Storage Fees | Debit (Expense) | $78.50 |
| Long-term storage fees | Amazon - Storage Fees | Debit (Expense) | $44.00 |
| Advertising (PPC) | Amazon - Advertising | Debit (Expense) | $340.00 |
| Professional seller subscription | Amazon - Other Fees | Debit (Expense) | $39.99 |
| Reimbursements (lost/damaged) | Amazon - Reimbursements | Credit (Other Income) | $112.00 |
| Promotional rebates | Amazon - Refunds | Debit (reduces income) | $31.20 |
| Net settlement amount | Amazon - Settlements Receivable | Debit (Asset) | $5,247.83 |
Every fee type needs its own account. The most common mistake after recording the net deposit as revenue is lumping all Amazon fees into a single "Amazon Fees" expense line. That tells you nothing useful. You cannot tell whether your FBA costs are rising because of a product-mix shift, whether your storage fees are climbing because you overstocked Q4, or whether referral fee rate changes affected your margins. Separate accounts give you that visibility.
Note that reimbursements are Other Income, not sales. They represent Amazon compensating you for inventory it lost or damaged in its fulfillment centers — not a customer buying your product. Recording reimbursements as product revenue inflates your unit revenue metrics and distorts your average selling price calculations.
For a deeper look at how these same fee types map to QuickBooks, see How to Post Amazon FBA Fees to QuickBooks — the logic is identical, only the platform differs.
Chart of Accounts Template for Wave + Amazon FBA
This is the section to bookmark. Copy this structure directly into Wave to get a complete, analysis-ready chart of accounts for Amazon FBA Wave accounting.
One important Wave-specific note before the tables: Wave does not support sub-accounts. QuickBooks and Xero let you create parent accounts with children (e.g., "Cost of Sales → FBA Fulfillment Fees"). Wave has a flat account list. The workaround is a consistent naming prefix — "Amazon -" for all Amazon-related accounts — so they sort together alphabetically and are immediately identifiable in reports.
Revenue Accounts
| Account Name | Wave Category | Account Type | Purpose |
|---|---|---|---|
| Amazon - Product Sales | Income | Sales | Gross revenue from FBA product orders |
| Amazon - Shipping Income | Income | Sales | Shipping charges collected from buyers |
| Amazon - Refunds | Income | Sales | Customer refunds — entered as a negative debit to reduce revenue |
Amazon Refunds is an income account because refunds are a reduction of revenue, not an increase in expenses. Recording them this way keeps your gross-to-net revenue reconciliation clean: gross sales minus refunds equals net product revenue.
Expense Accounts
| Account Name | Wave Category | Account Type | Purpose |
|---|---|---|---|
| Amazon - FBA Fulfillment Fees | Expense | Operating Expenses | Per-unit pick, pack, and ship costs |
| Amazon - Referral Fees | Expense | Operating Expenses | Amazon's sales commission (typically 8–15%) |
| Amazon - Storage Fees | Expense | Operating Expenses | Monthly and long-term warehouse storage |
| Amazon - Advertising | Expense | Advertising & Promotion | Sponsored Products, Brands, Display spend |
| Amazon - Other Fees | Expense | Operating Expenses | Seller subscription, label service, misc. charges |
Keeping Amazon - Advertising separate from operating expenses is worth the extra account. Advertising is a growth lever you control actively — separating it lets you calculate an advertising-adjusted margin and run TACOS (total advertising cost of sale) analysis directly from your P&L.
Balance Sheet Accounts
| Account Name | Wave Category | Account Type | Purpose |
|---|---|---|---|
| Amazon - Settlements Receivable | Asset | Other Current Asset | Clearing account — Amazon owes you this until the deposit arrives |
| Amazon - Reimbursements | Income | Other Income | Compensation for lost/damaged FBA inventory |
| Inventory Asset | Asset | Other Current Asset | Value of inventory currently held in FBA or at home |
The Settlements Receivable account is essential and frequently omitted by sellers who are new to double-entry bookkeeping. Amazon closes your settlement on one date and deposits the funds 1–3 business days later. Without a clearing account, your books show revenue recognized but no corresponding asset — the accounting does not balance. Settlements Receivable bridges that gap: you debit it when posting the settlement, and credit it when the deposit arrives.
COGS Accounts
| Account Name | Wave Category | Account Type | Purpose |
|---|---|---|---|
| Cost of Goods Sold - Amazon | Cost of Goods Sold | COGS | Product cost for units sold during the settlement period |
Wave supports COGS accounts natively — you will find "Cost of Goods Sold" as a category when creating a new account. Create one account here and use it consistently for every settlement's COGS entry.
Journal Entry Format for Wave
With your accounts created, here is what a complete settlement journal entry looks like in Wave. These are real numbers — not rounded, not simplified — because a simplified example will mislead you about how the math actually works.
Settlement Period: Feb 1–14, 2026
| Account | Debit | Credit |
|---|---|---|
| Amazon - Settlements Receivable | $5,247.83 | |
| Amazon - FBA Fulfillment Fees | $892.41 | |
| Amazon - Referral Fees | $1,156.22 | |
| Amazon - Storage Fees | $78.50 | |
| Amazon - Advertising | $340.00 | |
| Amazon - Refunds | $215.60 | |
| Amazon - Product Sales | $7,612.06 | |
| Amazon - Shipping Income | $318.50 |
Total debits: $7,930.56 — Total credits: $7,930.56 — the entry balances.
The $5,247.83 debit to Settlements Receivable is the net deposit Amazon will send to your bank. It equals gross revenue ($7,612.06 + $318.50) minus fees and refunds ($892.41 + $1,156.22 + $78.50 + $340.00 + $215.60). To verify: $7,930.56 − $2,682.73 = $5,247.83. That number should match your bank statement exactly.
When the bank deposit arrives 1–3 days later, post this clearing entry:
Bank Deposit Clearing Entry
| Account | Debit | Credit |
|---|---|---|
| Checking Account | $5,247.83 | |
| Amazon - Settlements Receivable | $5,247.83 |
After this, Settlements Receivable returns to zero and your bank balance reflects the deposit.
How to enter this in Wave: Go to Accounting → Transactions → click the More button in the top right → select Add Journal Transaction. Wave requires at least two lines per journal entry and will not let you save until debits equal credits — this is the platform enforcing double-entry rules. Enter each account from the tables above, add a description (e.g., "Amazon Settlement FEB-01-14-2026"), and enter the amount in either the Debit or Credit column. The running balance at the bottom of the screen shows your current debit/credit difference — it should reach zero before you save.
Automating Amazon FBA Settlement Posting with MerchantLedger
Manually executing those journal entries every two weeks is manageable for one settlement, but it does not stay manageable for long. Thirty to 45 minutes per settlement, 26 settlements per year, multiplied by any growth in SKU count or marketplaces — it compounds into a significant operational burden.
MerchantLedger was built specifically to eliminate this. Here is exactly what the automation does:
1. Automatic settlement import via Amazon SP-API. MerchantLedger authenticates with your Seller Central account using Amazon's OAuth flow and pulls every completed settlement automatically — no CSV downloads, no flat file parsing, no copy-paste. When Amazon closes a settlement, MerchantLedger picks it up.
2. Fee mapping to Wave accounts. Every transaction type in your settlement — FBAPerUnitFulfillmentFee, Commission, FBAMonthlyInventoryStorageFee, and two dozen others — is mapped to the correct Wave account in your chart of accounts. The mapping table is customizable from the MerchantLedger dashboard, so if your account names differ from the template above, you can remap any category in a few clicks.
3. Balanced journal entries posted to Wave. MerchantLedger builds the journal entry programmatically — gross revenue, every fee, refunds, reimbursements — and posts it to Wave via Wave's API. Debits always equal credits. No manual math.
4. Idempotent posting. If you re-run a posting (because of an error, a test, or a configuration change), MerchantLedger detects the existing entry and skips it. You will never get duplicate journal entries in Wave from running MerchantLedger twice.
5. Edge case handling. Multi-currency settlements, prior-period adjustments, reimbursements, and promotional rebates are all handled automatically. These are the line items that trip sellers up most often in manual entry.
The before/after comparison is straightforward: a 30–45 minute manual process every two weeks becomes automatic, same-day posting with no manual intervention.
COGS with the Average Cost Method in Wave
Revenue without cost of goods sold gives you a revenue figure, not a profit figure. If you posted $7,612.06 in Amazon product sales but never recorded what those products cost you, your gross margin in Wave is 100% — which is obviously wrong.
Every settlement journal entry needs a corresponding COGS entry. The most practical method for Amazon FBA sellers is Average Cost (also called weighted average cost), for two reasons specific to the Amazon model. First, you likely restock the same SKU at different prices over time — your first order of a product might cost $8.00/unit, your next reorder $9.20/unit because raw material costs shifted. Average Cost blends those purchase prices into a single per-unit cost. Second, Amazon uses commingled inventory, meaning your units may be fulfilled from any warehouse — you cannot track specific unit costs the way FIFO would require.
The calculation is straightforward:
- You buy 100 units at $8.00 = $800 total cost
- You buy 50 more units at $10.00 = $500 total cost
- Total inventory: 150 units, total cost: $1,300
- Average cost per unit: $1,300 ÷ 150 = $8.67
- You sell 30 units in the settlement period → COGS = 30 × $8.67 = $260.10
The COGS journal entry for that settlement would add one line to your existing entry:
| Account | Debit | Credit |
|---|---|---|
| Cost of Goods Sold - Amazon | $260.10 | |
| Inventory Asset | $260.10 |
Wave's COGS account category is designed for exactly this. MerchantLedger tracks your inventory purchase costs and automatically calculates and posts COGS entries to Wave for each settlement period using the Average Cost method, so your gross margin figures are accurate without any additional spreadsheet work. We'll cover the Average Cost method in depth for Amazon FBA in an upcoming guide.
Common Mistakes in Amazon FBA Wave Accounting
Mistake 1: Recording the Net Deposit as Revenue
If $5,247.83 hits your bank account and you record it as "Amazon Sales," you have hidden $2,682.73 in fees and refunds. Your revenue is understated, your expenses are understated, and your P&L is useless for any meaningful analysis. This is the most common mistake and the most consequential. Always post the full settlement breakdown.
Mistake 2: Using Wave's "Income" Recording Instead of Journal Entries
Wave gives you multiple ways to record transactions. If you use the simplified income recording (Accounting → Transactions → Add Income), you will capture revenue but miss fees entirely. The only correct method for Amazon settlements is a journal entry that records gross revenue and all deductions simultaneously. This is what keeps your books balanced.
Mistake 3: Skipping the Settlements Receivable Clearing Account
Some sellers post Amazon settlements directly to their checking account with the full gross revenue credit on the settlement date. The problem: the deposit arrives 1–3 days later. If your books show the cash in your checking account before it arrives, your bank reconciliation will not work. The Settlements Receivable clearing account is the correct way to handle this timing difference — debit it on settlement date, credit it when the deposit arrives.
Mistake 4: Omitting COGS Entries
This one affects every seller who tracks product profitability. If you are not posting COGS, your Wave P&L overstates gross profit. Tax deductions get miscalculated. And the unit economics analysis that tells you which SKUs are actually worth reordering is impossible without accurate COGS.
Frequently Asked Questions
Is Wave really free for Amazon sellers?
Yes. Wave's accounting software is 100% free — no monthly fee, no transaction limits, no feature tiers. Wave's business model monetizes payment processing (for sellers who use Wave Payments to accept credit cards) and payroll (a paid add-on). The core accounting features — double-entry books, chart of accounts, journal entries, financial reports, bank connections — are free permanently with no asterisks.
Can Wave handle multiple Amazon marketplaces?
Yes. Since Wave does not support sub-accounts, the cleanest approach for multi-marketplace sellers is to add marketplace-specific prefixes to your account names. For example: "Amazon US - Product Sales", "Amazon CA - Product Sales", "Amazon UK - Product Sales". This keeps accounts separate for reporting while maintaining the flat account structure Wave requires. Wave also supports tags, which you can use to slice reports by marketplace without creating separate accounts for every line item. MerchantLedger handles multi-marketplace settlements and maps each to the correct Wave accounts automatically.
Should I switch from Wave to QuickBooks as I grow?
It depends on your revenue and operational complexity, not just size. Wave handles the core Amazon accounting workflow well up to roughly $500K in annual revenue. Above that threshold, QuickBooks Online's more powerful reporting, class and location tracking, accountant collaboration tools, and broader integration ecosystem may justify the $30–50/month cost. The transition is straightforward because MerchantLedger supports both platforms — you can switch your accounting provider in the MerchantLedger settings without changing your Amazon connection or losing settlement history.
Does MerchantLedger work with Wave's free plan?
Yes. MerchantLedger connects to Wave via Wave's API, which is available on Wave's free tier. There is no paid Wave plan required. You connect your Wave account to MerchantLedger using OAuth, authorize access, and MerchantLedger posts journal entries to Wave using the same API that Wave's own mobile app uses.
Getting Started with Amazon FBA Wave Accounting
- Create your Amazon accounts in Wave using the chart of accounts template above. Pay attention to the naming convention ("Amazon -" prefix) and Wave account categories — Income for revenue, Expense for fees, Other Current Asset for receivables and inventory.
- Download one settlement from Seller Central and walk through the transaction types manually. Understanding what
FBAPerUnitFulfillmentFeeversusCommissionlooks like in the raw data makes your account mapping decisions more confident. - Post your first journal entry manually in Wave using the format in this guide. This exercise teaches you how Wave's journal entry screen works and confirms your chart of accounts is correct before you automate.
- Sign up for MerchantLedger and connect your Amazon Seller Central account using the Amazon SP-API OAuth flow.
- Connect your Wave account in the MerchantLedger dashboard, map your accounts to the Wave accounts you created, and post your next settlement automatically.
Start your free MerchantLedger account — connect Amazon and Wave in under 5 minutes.