Amazon Marketplace Reconciliation Calculator
Amazon pricing decisions are only as strong as the data behind them. For marketplace sellers, the real question is not just what price to set, but what remains after Amazon fees, settlements, refunds, and deductions are reconciled against internal records.
Cointab helps finance teams compare internal sales and SKU data with Amazon-side reports so they can understand net margin at the transaction and product level. Instead of working through repeated Excel checks, teams can upload files once, map fields, run reconciliation, and review matched and unmatched items in a structured report.
Why Amazon marketplace pricing needs reconciliation
A product may look profitable on the surface and still deliver a weaker margin after marketplace deductions are applied. Referral fees, shipping charges, fulfillment costs, closing fees, and other deductions can materially change the net outcome for a SKU.
Reconciliation gives finance teams a clearer view of:
- the selling price recorded internally
- the amount Amazon settled
- fees and deductions applied by the marketplace
- refunds, returns, and reversals
- differences that affect the final margin
This makes reconciliation useful not only for month-end review, but also for pricing analysis, product profitability checks, and settlement review.
What data can be compared
Cointab uses a Side A / Side B reconciliation model.
| Side | Typical data used in Amazon workflows |
|---|---|
| Side A | Internal sales report, SKU master, product cost file, pricing sheet, order report |
| Side B | Amazon settlement report, fee report, payout report, refund or reversal data |
Supporting data can also be uploaded where needed. For example, teams may add SKU mapping files, product cost files, or fee rate cards to enrich the primary reports before reconciliation.
How the reconciliation workflow works
A typical Amazon marketplace workflow in Cointab follows a simple structure:
- Upload the required files for Side A and Side B.
- Map fields such as date, amount, and identifiers like order ID, SKU, settlement ID, or payment reference.
- Add supporting data if a lookup or merge is needed.
- Create derived columns when a formula is needed for net amount, clean references, or margin calculations.
- Run reconciliation manually or on a schedule.
- Review fully matched, partially matched, unmatched, and skipped records.
- Download the Excel report for internal review, follow-up, or audit support.
If a file is missing, the user can upload it later under the same reconciliation and refresh the report.
What the report helps finance teams see
Amazon reconciliation is not only about confirming whether a payment landed. It also helps answer questions that affect pricing and profitability:
- Which orders were fully settled as expected?
- Which orders were partially paid because of deductions or fee differences?
- Which SKUs are showing consistent margin pressure?
- Which transactions are still open because data is missing?
- Which differences are caused by returns, refunds, or timing gaps?
The report separates:
- Fully matched records where the expected and received values align
- Partially matched records where identifiers match but amounts differ
- Unmatched records that appear on one side only
- Skipped records that were not included because of missing or invalid data
That structure helps teams focus on exceptions instead of manually reviewing every row.
Common Amazon fee and settlement exceptions
Amazon marketplace data often contains differences that need structured review. Common examples include:
- referral fee differences
- shipping or fulfillment fee deductions
- closing fees or service charges
- refunds not yet reflected on both sides
- returns that affect the final settlement amount
- order references that do not cleanly match across reports
- delayed settlements or missing payout rows
- SKU-level mismatches caused by inconsistent product mapping
Cointab helps finance teams isolate these exceptions so they can determine whether the issue is a real discrepancy, a timing difference, or a missing file.
Using reconciliation for pricing analysis
A pricing calculator is most useful when it reflects actual net economics. For Amazon sellers, that means reviewing the final amount received after deductions rather than relying on gross selling price alone.
With reconciled data, teams can analyze:
- net revenue by SKU
- fee impact by price point
- margin differences across products or periods
- deductions that reduce the expected return from a sale
- whether a price change improves or weakens true profitability
This is especially helpful when a business sells multiple SKUs or tests different price points across the marketplace.
Why structured reconciliation is better than Excel-only review
Excel can work for small files, but marketplace data becomes harder to manage as volume, exceptions, and report formats grow. Cointab provides a reusable workflow designed for finance operations.
Benefits include:
- structured matching logic instead of ad hoc formulas
- reusable reconciliation setup for future periods
- clear handling of matched, partially matched, unmatched, and skipped records
- manual match options for cases that need business review
- audit-ready Excel exports
- recurring automation through email, SFTP, or API where needed
This helps teams reduce repetitive spreadsheet work while keeping the process transparent.
When to use this workflow
An Amazon marketplace reconciliation workflow is useful when a team needs to:
- understand fee impact on pricing and margin
- reconcile sales against settlement data
- review deductions and refunds
- support month-end or period-end close
- prepare audit-ready reports
- reduce manual follow-up on open items
- reuse the same reconciliation for future periods
For teams managing Amazon data regularly, the value is not just in one report. It is in having a repeatable process that can be used again for future settlements, periods, and SKU reviews.