Amazon Settlement Review: Spreadsheet vs Software
A spreadsheet can be enough to review a small, stable set of Amazon settlement reports. Software becomes worth evaluating when repeated imports, multiple accounts, late refunds, and unresolved items make the review hard to repeat. The choice depends on your records and controls, not a universal order-count threshold.
Start with the same source records
Download the closed-period settlement report from Seller Central, preserve the original file, and note the account, currency, period, and download date. Amazon's India guidance distinguishes the settlement report from transaction and date-range summary reports. Use the report that answers the question you are checking; a sales summary alone cannot prove the amount transferred to a bank.
In a working spreadsheet, keep source identifiers and amounts on separate rows. Add review columns rather than editing the imported values. For example, use source row, settlement period, transaction reference, order reference where present, type, signed amount, match status, and reviewer note. These are suggested working columns, not a claim about the exact headings in every Amazon export.
| Source event | Signed amount | What to check |
|---|---|---|
| Order A sale | +₹1,000 | Match the order reference and transaction date. |
| Order A marketplace charge | −₹150 | Keep the charge type and source row visible. |
| Earlier Order B refund | −₹300 | Look back to the original order; it need not belong to this settlement period. |
| Other adjustment | +₹50 | Read the statement description before classifying it. |
| Illustrative transfer | ₹600 | Compare with the statement total and bank receipt, allowing for transfer timing. |
The calculation is ₹1,000 − ₹150 − ₹300 + ₹50 = ₹600. It is intentionally simplified: a real statement may include an opening balance, reserves, taxes, more fee types, and transactions outside the order dates you first selected. If your bank receipt differs, investigate the statement and transfer references instead of adding a balancing row with no explanation.
Where each approach helps—and where it needs a check
| Question | Controlled spreadsheet | Software to evaluate |
|---|---|---|
| Can you repeat the review next period? | Use a locked template, documented formulas, and a separate copy of each original report. Check that new report columns do not shift formulas. | Ask how imports are mapped, changed report layouts are detected, and rules are versioned. |
| What remains unmatched? | Maintain an exception tab with owner, reason, source reference, and resolution date. | Ask to see an exception queue, manual override history, and whether an item can carry into the next period. |
| Can a reviewer trace a number? | Keep source rows and formulas visible; avoid replacing raw data with a pasted total. | Ask for drill-down to the source transaction and an export the accountant can retain. |
| Who can access seller data? | Restrict file sharing and protect copies containing buyer or account details. | Confirm permissions, data transfer, retention, deletion, and any integration authorisation in writing. |
| What does it cost? | Count template maintenance and review time as well as spreadsheet licences. | Compare the full subscription, setup, account limits, extra services, and review effort. |
A spreadsheet is often the clearest starting point when one person reviews a manageable number of statements and can explain every adjustment. Software may help when the same review must be performed consistently across periods or people, but an attractive dashboard is not evidence of correct matching. Test both approaches on the same sanitized statement and compare their unresolved items, audit trail, and total with the source file.
Five questions for a QarBexOS demonstration
- Which Amazon India report versions can this workflow import today, and how are errors shown?
- Can you trace one transfer total to individual source lines, including a refund from an earlier period?
- How does the system label and carry forward an unmatched transaction?
- What can a reviewer change, and is that change recorded?
- What are the export, access, retention, and full-price terms for my account?
These are evaluation questions, not assertions that QarBexOS currently supports every listed feature. Ask for a demonstration using sample data and a written description of limitations before connecting a live seller account.
Sources and review
Reviewed 23 September 2026 for Amazon India. Amazon's India payment-report overview describes settlement, transaction, and summary reports; its report download instructions explain available statement files. The comparison table and numbers above are QarBex educational examples, not an Amazon report, a customer result, or accounting advice.