Every settlement, matched to the last paisa.
This is the actual page you open every morning. No spreadsheet, no Seller Central export, no manual VLOOKUP. Amazon disbursements, line-matched to the orders, fees, refunds and reserves behind them — live.
- →5 status buckets — Settled, Pending, Not settled, Overdue, Cancelled — clickable as filters
- →Drill any order to see fees, refunds and reserve releases line-by-line
- →Date range picker, pagination, CSV/XLSX export — already built in
01Who opens this page
Whose Monday morning this fixes.
Reconciliation lands on different desks in different teams — ops chasing claims, finance closing the books, founders watching cash flow. Same page, three jobs.
Operations lead
Spots short-pays before they compound. Opens the discrepancy row, takes the evidence pack to Seller Central, and gets on with the day.
Finance / CA
Pulls a settlement-level CSV for the GSTR-1 cycle. Every disbursement maps to invoice + HSN + tax split — no manual joining.
Founder
Glances at the 5 status cards, sees ₹14L stuck in Pending or Not-settled, and knows when to escalate.
02How a match happens
Every disbursement, traced to its orders.
Every disbursement on the page above is broken down into its constituent transactions and rebuilt from first principles. If the rebuilt total matches the wired amount to the paisa, the row stays Settled. If not, the delta lands in your discrepancy queue.
₹18.4L
Each disbursement row in the Orders table above starts here — the amount Amazon wired to your bank.
1,284 orders
Every Order ID in that window joins back to its disbursement — that's how the Settled bucket gets to 1,847.
Referral · FBA · Storage
Click into any order from the table — the fee breakdown shows up per line, referral %, FBA pick-pack, storage.
47 refunds
Refund chains net out against gross sales on the order — that's the Settlement column you saw.
Hold released
Amazon's transfer-hold buffer releases on its own clock; releases roll into the Settled bucket the day they hit.
03Discrepancy queue
Every gap, queued with evidence. Evidence pre-assembled
When the match engine finds a gap — a fee that shouldn't exist, a reimbursement that never showed up, a short-pay — it lands here with the supporting documents pre-assembled, ready for your team to raise the case in Seller Central.
Open discrepancies · last 30 days · amazon.in
Live| Issue | SKU | Marketplace | Amount | Filed on | Status |
|---|---|---|---|---|---|
| FBA fee overcharge | XYZ-KURTI-RED-M | amazon.in | ₹1,240 | 18 Apr | Claim filed |
| Missing reimbursement | ABC-MUG-50 | amazon.in | ₹3,400 | 21 Apr | Approved ✓ |
| Short-pay on settlement | DEF-OIL-500ML | amazon.in | ₹6,820 | 24 Apr | In review |
| Lost inventory — warehouse | GHI-TSHIRT-L | amazon.in | ₹14,500 | 02 May | Approved ✓ |
| Reversed customer charge | JKL-CANDLE-200G | amazon.in | −₹18,400 | 08 May | Reversed |
| Removal-order shortage | MNO-BAG-BLACK | amazon.in | ₹2,180 | 12 May | Pending |
Each row carries the shipment IDs, FNSKU history and settlement reference your team needs when raising a case in Seller Central.
- →Filter by issue type, SKU, marketplace, age, amount
- →Each row carries the supporting documents Seller Central typically asks for
- →Log the case ID + outcome you record against each gap — full audit trail in one place
04Same data, exported
Same data. CSV or XLSX. Order-level or product-level.
Schedule monthly to an inbox, drop to S3, or wire straight into Tally — same row data either way.
Preview · apr-2026-reconciliation.csv
Render the exact file month-end opens — no surprises when the books close.
| order_id | order_date | payment_status | revenue | fees | refunds | reserve | settlement | payout_pct | marketplace |
|---|---|---|---|---|---|---|---|---|---|
| 405-2387661-9821304 | 2026-04-28 | settled | 1820.00 | 248.00 | 0.00 | 48.00 | 1524.00 | 83.7 | amazon.in |
| 403-4458882-1182937 | 2026-04-28 | settled | 3240.00 | 452.00 | 0.00 | 69.00 | 2719.00 | 83.9 | amazon.in |
| 406-1102994-7783326 | 2026-04-27 | pending | 2180.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.0 | amazon.in |
| 405-9923118-2284557 | 2026-04-27 | not_settled | 4820.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.0 | amazon.in |
| 402-7782334-8814429 | 2026-04-27 | overdue | 6140.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.0 | amazon.in |
| 405-8821443-2210077 | 2026-04-26 | settled | 1440.00 | 192.00 | 0.00 | 42.00 | 1206.00 | 83.8 | amazon.in |
| sku | asin | units_sold | gross_revenue | fees | refunds | net_payout | marketplace | period |
|---|---|---|---|---|---|---|---|---|
| KURTI-RED-M | B0CJ8H4XYZ | 184 | 334880.00 | 46180.00 | 12420.00 | 276280.00 | amazon.in | 2026-04 |
| OIL-NEEM-500ML | B09KLM2N4P | 412 | 201880.00 | 28260.00 | 4020.00 | 169600.00 | amazon.in | 2026-04 |
| DIYA-BRASS-SET | B07XJ8C8F5 | 96 | 115200.00 | 16128.00 | 2880.00 | 96192.00 | amazon.in | 2026-04 |
| AGARBATTI-SANDAL | B08QR3T7XY | 634 | 126800.00 | 17752.00 | 1268.00 | 107780.00 | amazon.in | 2026-04 |
| SAREE-GREEN-SILK | B0BPYV6L9R | 42 | 189000.00 | 26460.00 | 9000.00 | 153540.00 | amazon.in | 2026-04 |
| KURTI-BLUE-L | B0CW1VHF2K | 127 | 228600.00 | 32004.00 | 5400.00 | 191196.00 | amazon.in | 2026-04 |
05Hand-off to your books
Reports in the formats month-end already uses.
Settlement-level CSV and XLSX exports shaped to fit the books your team already runs — line-level fees, GST splits, marketplace tags. Schedule the file to an inbox, to S3 or to SFTP. No reshaping at month-end.
Export layout shaped to the voucher format Tally imports — no reshaping at month-end.
GST-aware columns line up with the journal CSV your team already drops into Zoho Books.
Class-tagged columns per marketplace, ready for the journal entry import your bookkeeper runs.
Column layout matches the manual journal CSV template; tracking categories map to SKU groups.
Multi-subsidiary segment columns ready for NetSuite's CSV journal import — no schema work.
06Proof
Operators who run on it.
We were leaving ₹6-8L on the table every quarter in un-claimed reimbursements. Sellerbud's queue now files them automatically — recovered ₹4.2L in the first month, and finance stopped chasing me for settlement CSVs.
Recovered reimbursements · 6-month trend
+₹4.2L mo 107Objections
Things operators ask before they buy.
How accurate is the auto-match?
The engine matches the vast majority of lines out of the box. Anything it can't confidently match lands in the discrepancy queue with the gap pre-quantified — you decide whether to raise a claim or write it off, but you always know which it is.
Does this work for FBA + FBM mixed accounts?
Yes. The match engine handles FBA fees, MFN-Prime fees, EasyShip charges and self-ship adjustments in the same settlement. SKU-level attribution stays consistent whether Amazon or you fulfilled the order.
Does Sellerbud file the claim for me?
The queue assembles the evidence — shipment ID, reimbursement window, FNSKU history, settlement reference — so your team can raise the case in Seller Central with everything in hand. We make the paperwork instant; you stay in control of what gets submitted.
Can I get the data into Tally, Zoho or QuickBooks?
Yes — exports are shaped to fit the import formats those tools accept: Tally vouchers, Zoho Books journal CSVs, QuickBooks / Xero / NetSuite journal templates. Schedule the file straight to an inbox, S3 or SFTP — no manual reshaping.
What if a claim gets disputed?
Log the case ID and outcome — credit, partial credit, denial — against the original gap in the queue. The settlement that owns it carries the full audit trail, so you can see at any point what was raised, what landed, and what's still open.
Can I share the report with finance without giving them Sellerbud access?
Yes — schedule the CSV/XLSX to an inbox or to an S3/SFTP destination. Nobody downstream needs to log in.
What's the difference between order-level and product-level reports?
Order-level gives you one row per Amazon order — best for cash reconciliation. Product-level pivots that onto SKU/ASIN, so you can see which products are short-paying after fees and refunds — best for margin analysis.