Ops & Supply

How to reconcile amazon seller settlements as CPG Founders

Ops & SupplyFor CPG Founders3 apps12 steps~24 min to set up

Every two weeks Amazon deposits a number in your bank account, and it rarely matches what you expected. You pull the settlement report from Seller Central — a flat file with 40+ columns — and try to reconcile it against your COGS in QuickBooks, your FBA fee estimates in a spreadsheet, and your ad spend in Amazon Ads. Somewhere in the gap are reimbursements Amazon owes you for lost or damaged inventory, shortfalls from Reserve holds, and chargebacks you never disputed. Most CPG founders spend 3-5 hours per settlement period on this and still aren't confident the number is right. If you're running multiple ASINs across grocery and DTC, it gets worse fast.

Build this on Starch → See the apps used

Ops & SupplyFor CPG Founders3 apps12 steps~24 min to set up

Outcome

What you'll set up

A live settlement reconciliation dashboard that maps every Amazon disbursement line — FBA fees, referral fees, reserve holds, reimbursements, ad spend — against your actual COGS so you see true per-SKU margin on every settlement, not just gross revenue

Automated flagging of discrepancies: reimbursements Amazon owes you for lost/damaged units, unexpected fee increases, and settlement amounts that don't match your revenue recognition in QuickBooks

A running log of disputes worth filing, pre-populated with the data Amazon needs, so nothing falls through the cracks between settlement cycles

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Transaction Insights Investor Reporting

Data sources & config

Starch connects directly to Amazon Seller Central via the Amazon Seller Dashboard app (currently in beta — request access) for settlement report data and FBA fee detail. Starch syncs your Plaid bank account data on a schedule to match cash deposits against expected settlement amounts. Starch syncs your QuickBooks data on a schedule — pulling invoices, payments, and journal entries — to reconcile revenue recognition against actual disbursements. Amazon Ads spend data is pulled live from Starch's integration catalog when your reconciliation app runs.

Prompts to copy

Pull my last three Amazon settlement reports and break down each disbursement by fee type — FBA fulfillment fees, referral fees, storage fees, reimbursements, reserve holds, and ad spend. Show me the net per-SKU margin for each ASIN after all fees, and flag any line item that differs by more than 10% from the prior settlement.

Cross-reference my Amazon settlement total against my Plaid bank deposits for the same period and tell me if the numbers match. If there's a gap, show me what's sitting in reserve or pending reimbursement.

Build me a monthly reconciliation view that shows Amazon revenue recognized in QuickBooks versus actual cash received via settlement, broken out by ASIN, and highlight any SKUs where the gap is growing over time.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect your Amazon Seller Central account through the Amazon Seller Dashboard (currently in beta). This gives Starch access to your settlement reports, FBA fee detail, reserve balance, and reimbursement history.

2 Connect your Plaid bank account so Starch syncs your actual cash deposits on a schedule. This is the ground truth — what Amazon actually wired you — and it's what you reconcile everything else against.

3 Connect QuickBooks through Starch's scheduled sync. Starch pulls your invoices, payments, and journal entries so you can compare revenue recognized in your books against what Amazon disbursed.

4 Connect Amazon Ads from Starch's integration catalog so the agent can pull your ad spend per ASIN live when your reconciliation app runs. This is the cost most founders forget to subtract before calling a number 'profit.'

5 Ask Starch to build a settlement breakdown app: 'For each settlement period, show me gross Amazon revenue, then subtract FBA fulfillment fees, referral fees, storage fees, and ad spend by ASIN, and give me net margin per unit.' Starch builds the surface; you describe it in plain language.

6 Run the first reconciliation pass. Starch maps every line item in the settlement flat file to a category — fees, reimbursements, reserves, adjustments — and surfaces a total that should match your Plaid deposit. Any gap gets flagged immediately.

7 Review the reimbursement queue. FBA lost-and-damaged claims are the most common source of money Amazon owes CPG brands and never proactively pays out. Starch identifies units Amazon confirmed as lost or damaged that haven't generated a reimbursement line in the settlement.

8 Check reserve holds. If you're a newer seller or had a spike in refund rate, Amazon holds a percentage of your settlement. Starch tracks your reserve balance over time so you know when it releases and can plan cash accordingly.

9 Compare net settlement margin against your QuickBooks COGS for the same SKUs. If your gross margin looks fine but net settlement margin is shrinking, the culprit is almost always rising storage fees, a fee category reclassification, or ad spend creep.

10 Set up a recurring automation: 'Every time a new Amazon settlement posts, pull the report, compare it to my Plaid deposit, flag any discrepancy over $200, and Slack me a summary with the top three fee categories driving the gap.' Starch runs this on schedule so you don't have to remember.

11 For any reimbursement or fee dispute identified, use Starch's browser automation to pull the relevant Seller Central case history — no API needed — and attach it to your dispute log so you have backup documentation in one place.

12 At the end of each quarter, generate a reconciliation summary for your bookkeeper or CFO: Amazon gross revenue, total fees by category, net disbursed, reimbursements received, and any open disputes — pulled from Plaid, QuickBooks, and Amazon in a single report.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

March 2026 Settlement Reconciliation — Grain-Free Granola Brand, 6 ASINs

Sample numbers from a real run

Amazon gross sales (3 settlement periods)	84,200
FBA fulfillment fees	-18,900
Referral fees (8% grocery category)	-6,736
Storage fees (Q1 long-term storage spike)	-3,100
Amazon Ads spend (auto + branded campaigns)	-11,400
Reserve hold (new ASIN launched Feb)	-4,200
Reimbursements — lost FBA units (flagged by Starch)	1,840
Net cash deposited (Plaid verified)	41,704

In March, this brand ran $84,200 in gross Amazon sales across six granola SKUs. Their QuickBooks showed $79,000 in revenue recognized — a $5,200 gap the founder assumed was timing. Starch's reconciliation showed it was a combination of a $4,200 reserve hold on a new ASIN launched in February (normal, releases in 90 days) and $1,000 in settlement adjustments from a January return dispute Amazon resolved late. More importantly, Starch flagged $1,840 in reimbursements for 47 units Amazon confirmed as lost in transit during a peak restock in February — units the brand had shipped and never received credit for. The founder had no idea. After subtracting all fees and ad spend, net margin on these six SKUs came in at 49.5% of gross — down from 54% in Q4. The culprit: long-term storage fees tripled because a slower-moving SKU had been sitting in FBA since October. Starch identified the SKU, calculated the storage cost per unit, and suggested a removal order. Total time to run the reconciliation: 20 minutes, versus the 4+ hours the founder previously spent manually parsing settlement flat files in Excel.

Measurement

How you'll know it's working

Net settlement margin by ASIN (gross revenue minus all Amazon fees, storage, and ad spend, divided by units sold)

Reimbursement recovery rate (dollars recovered from Amazon lost/damaged claims as a percentage of total eligible claims)

Reserve hold balance and expected release date (cash flow impact of Amazon withholding)

Settlement-to-deposit variance (difference between what Starch calculates you're owed and what Plaid confirms was deposited)

Storage fee per unit by ASIN (leading indicator of margin erosion on slow-moving SKUs)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Sellerboard or Fetcher

Good at Amazon-only P&L, but neither connects to your QuickBooks, Plaid bank deposits, or distributor deductions — so you still end up reconciling across multiple tabs to get a full picture.

Manual settlement reconciliation in Excel

Free and familiar, but the settlement flat file has 40+ columns, you have to re-do it every two weeks, and you will miss reimbursement claims Amazon never proactively flags — most brands leave hundreds to thousands of dollars on the table per quarter.

A3 Reimbursements or GETIDA (reimbursement services)

These services are good at recovering lost/damaged reimbursements on a commission basis, but they don't reconcile your full settlement against your books, track storage fee trends, or connect to anything outside Amazon.

QuickBooks alone

QuickBooks tracks what you recognize, not what Amazon actually disbursed — the gap between those two numbers is exactly what you're trying to understand, and QuickBooks can't bridge it without a tool that also reads the settlement report.

On Starch RECOMMENDED

One platform — amazon seller dashboard, transaction insights, investor reporting all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Does Starch connect directly to Amazon Seller Central?

The Amazon Seller Dashboard is currently in beta development. Request beta access to get notified when it launches. In the meantime, Starch can automate Amazon Seller Central through your browser — no API required — to pull settlement reports, reimbursement history, and FBA case data. It's not a formal sync, but it's functional for getting a reconciliation built before the full integration ships.

Will Starch store my historical settlement data or just query it live?

Starch's Plaid and QuickBooks integrations sync data on a schedule and store it in Starch's database, which is what makes historical trend views (storage fees over time, margin by quarter) possible. Amazon settlement data, once the integration is live, will follow the same pattern. Starch is designed for live data surfaces and rolling history, not a long-term data warehouse — if you need archived analytics going back years, you'd want a separate BI tool.

Can Starch actually file reimbursement claims with Amazon, or does it just identify them?

Starch identifies the claims worth filing and surfaces the backup data you need. For the actual submission, Starch can automate the Seller Central case filing workflow through your browser — navigating to the right case form, pre-filling it with unit counts and shipment IDs, and submitting it — since Amazon's case management interface is web-based and doesn't require a separate API.

What if my QuickBooks P&L report views aren't working?

QuickBooks report views (P&L, Transaction List, Vendor Expenses) are temporarily disabled in Starch pending an upstream connector fix. Entity-level data — invoices, bills, payments, vendors, and journal entries — syncs normally. For settlement reconciliation, the entity-level data is actually what you need (payment and invoice records), so this limitation shouldn't block your workflow.

I sell on Amazon, Shopify, and through a distributor. Can Starch reconcile all three?

Yes. Plaid sees all cash deposits regardless of source, so your Shopify payouts, Amazon settlements, and distributor payments all show up in the same bank feed. You can connect Shopify from Starch's integration catalog — the agent queries it live — and build a reconciliation view that compares revenue by channel against deposits. Distributor deductions are a separate problem (the Deduction Manager app is in development for that), but at the cash-in-bank level, Plaid gives you a unified view.

Is Starch SOC 2 certified? I'm connecting bank and financial data.

Starch is not currently SOC 2 Type II certified. If that's a hard requirement for your business — some retailers and investors ask — it's worth knowing upfront. Plaid handles the bank connection using its own security infrastructure, which is SOC 2 certified, so the bank credential itself never touches Starch directly.