How to reconcile amazon seller settlements on Starch
Every time Amazon settles a payment to your bank account, it bundles dozens of line items into a single deposit: product sales, FBA fees, referral fees, advertising charges, storage fees, returns, reimbursements, and adjustments from previous periods. That lump sum hits your bank and tells you almost nothing on its own. Reconciling Amazon seller settlements means matching each component of that deposit against your own records — your orders, your fees, your ad spend — so you know whether Amazon paid you correctly, where your margin actually went, and what to book in your accounting system. It sounds like a one-time cleanup job. In practice, it's a recurring workflow that compounds quickly when settlements arrive every two weeks and every SKU has its own fee profile. What this looks like in practice depends on whether you're managing the work yourself, running it through a bookkeeper, or operating at a volume where exceptions and disputes are their own workload. The core problem is the same: the raw settlement file is not an answer, it's raw material. On Starch, the end state is a reconciled view you can actually act on — a dashboard that shows per-SKU net payout after every Amazon fee category, flags discrepancies between what you expected and what was deposited, and rolls up into your broader P&L without a manual export in sight. Your settlement numbers are always current, always broken down, and already in the format your bookkeeper or finance review needs.
Why it matters
Amazon underpays sellers more often than most operators expect — through miscalculated FBA fees, reimbursements that never arrive for lost or damaged inventory, and promotional adjustments applied incorrectly. If you're not reconciling at the line-item level, you're leaving money on the table and you have no idea how much. On the flip side, clean reconciliation data is the only way to know your true margin per SKU — which is the number that actually tells you whether a product is worth running.
Common pitfalls
The most common mistakes: treating the deposit amount as revenue instead of reconciling each component separately, which makes your P&L look cleaner than it is; reconciling on a monthly cadence when settlements land every two weeks and disputes have a filing deadline; ignoring the 'other' and 'adjustment' line items because they're small individually — they're often where errors accumulate; and failing to track open reimbursement claims, so Amazon's 60-day window closes before you've filed.
Starch apps used
See this running on Starch
Connect your tools, describe what you want, and the agent builds it. Closed beta is free.
Choose your operator
A version of this guide tailored to your role — same recipe, different starting context.
Related workflows in Ops & Supply
Inventory shrinkage is the gap between what your records say you have and what's actually on the shelf, in the warehouse, or at your co-packer.
Read guide →Closing out the POS at end of night means verifying that what the register says happened actually matches what the cash drawer holds, what the card processor settled, and what the day's receipts show.
Read guide →Contractor job costing is the practice of tracking what a job actually costs — labor, materials, subcontractors, equipment — against what you estimated, and updating that number as work progresses and change orders land.
Read guide →Retailer deductions and distributor chargebacks are line items that show up on your remittance as money already taken — a short-pay for a late delivery, a promotional allowance you never agreed to, a compliance fee for a label that met spec.
Read guide →