Home Amazon Reconciliation

Amazon Reconciliation

Automate Amazon reconciliation with Cointab. Match orders, settlements, fees, refunds, and payments to detect discrepancies, reduce manual work, and improve financial accuracy.
By Vishwesh Sarkar
• 12 articles

How do I create and run a new reconciliation for Amazon MTR Report vs Disbursement?

Short Answer: Open the New reconciliation page, choose or create a Reconciliation name, set Period, upload the Amazon MTR and Amazon Disbursement files, verify mappings with 'View format', then click 'Run reconciliation'. PreRequisites 1. Signed in to Cointab 2. CSV, XLS or XLSX files for Amazon MTR Report and Amazon Disbursement ready 3. Access to the reconciliation page Steps 1. Open the New reconciliation page for the Amazon MTR vs Disbursement flow. You see 'Reconciliation name', 'Period' and tiles for 'Amazon MTR Report' and 'Amazon Disbursement'. 2. Select an existing Reconciliation name or click '+ New' to create one. The Reconciliation name field is populated. 3. Click 'Select month/year' and pick the Period you want to reconcile. Period is selected and visible in the Period field. 4. Under each tile for example 'Amazon MTR Report' and 'Amazon Disbursement' click 'Upload files' and add your CSV/XLS/XLSX files. Files appear attached in the respective tile. 5. Click 'View format' for each dataset to confirm field mappings Date, Amount, Reference / Identifier and 'Records to include' rules. 'Expected data format' modal opens allowing you to verify mappings and filters. 6. Click 'Run reconciliation' top-right to run the matching process. Reconciliation runs and opens the results report page with summary cards. 7. Review results on the report page and use 'Download report' or 'Add files & update report' if you need to export or update. Summary cards and the tabbed results list are visible. Troubleshooting 1. Upload fails or files do not appear in the tile. LikelyCause: Unsupported file type, corrupt file, or temporary network error. Action: Confirm files are CSV/XLS/XLSX, try re-saving the file or upload a smaller sample. Retry upload and check your network. 2. Many records are missing from results or show as 'Skipped'. LikelyCause: 'Records to include' filters exclude those rows. Action: Open 'View format' for that dataset and either toggle on 'Include all records' or adjust the filter values to include your rows. 3. Reconciliation totals look wrong after the run. LikelyCause: Fields Date/Amount/Reference are mis-mapped or the Header row is incorrect. Action: Open 'View format' and verify 'Header row', 'Date', 'Amount' and 'Reference / Identifier' mappings; correct and re-run. Note: If you need to change files after a run, use 'Add files & update report' to attach new files and re-run.

Last updated on Sep 01, 2026

How do I view and adjust the expected data format and required fields?

Short Answer: Click 'View format' under the dataset tile to open the 'Expected data format' modal, then confirm or change Sheet, Header row, Date, Amount, Reference / Identifier and 'Records to include'. PreRequisites 1. Files uploaded or previewable in the tile 2. New reconciliation or report page open Steps 1. Click 'View format' under the dataset you want to inspect e.g., Amazon B2C MTR Report or Amazon Disbursement. The 'Expected data format' modal opens. 2. For Amazon B2C MTR Report confirm 'Sheet' is CSV, 'Header row' is 1, 'Date' = Invoice Date, 'Amount' = Invoice Amount and 'Reference / Identifier' = Order Id. Preview shows sample rows with those columns and mappings. 3. For Amazon Disbursement confirm 'Date' = posted-date, 'Amount' = amount and 'Reference / Identifier' = order-id, then review the left data preview. Disbursement preview shows settlement-id and sample rows with the selected columns. 4. Adjust 'Records to include' by toggling 'Include all records' or adding filters e.g., transaction-type in list Order, Refund or amount-description in list. Only records that match conditions will be included in reconciliation. 5. Click 'Download format' to get a template if you need to modify your file to match required columns. A template file is downloaded for editing. Troubleshooting 1. Mapped columns don't match your file or preview shows blank headers. LikelyCause: Header row is set to the wrong row or file lacks headers. Action: Change the 'Header row' value to the correct row number or add a header row to your file and re-open the preview. 2. Rows you expect to include are shown as Skipped. LikelyCause: 'Records to include' filters exclude those rows. Action: Turn on 'Include all records' or update the filter values to include your rows, then re-run reconciliation. Note: Field names Invoice Date, Invoice Amount, Order Id, posted-date, amount, order-id are shown in the UI as example mappings; adjust to your file's column names as needed.

Last updated on Sep 01, 2026

How do I view matched transaction details when one MTR invoice matches multiple disbursement lines?

Short Answer: On the report page expand the matched row e.g., 'Multiple transactions (1)' to open 'Matched transaction details' which shows 'Match basis' and the MTR and Disbursement rows that were matched and their totals. PreRequisites 1. Reconciliation has been run 2. Report page Amazon MTR Report vs Disbursement Report is open Steps 1. Open the reconciliation report Amazon MTR Report vs Disbursement Report. You see summary cards and the detailed list of matched rows. 2. Click the grouped link in the Reference / Identifier column, for example 'Multiple transactions (1)' or use the expand arrow on the row. 'Matched transaction details' modal opens. 3. In the modal review the 'Match basis' shows 'Reference ID' + 'Amount' and compare the 'Amazon MTR Report transactions' table with the 'Amazon Disbursement transactions' table. You can see each matched row, settlement or transaction IDs, and the subtotal/difference. 4. If needed, click 'Unmatch' to separate the matched records see next steps to re-match manually. Matched rows are unlinked and will appear in the appropriate status unmatched or partially matched. Troubleshooting 1. Modal does not show expected disbursement lines. LikelyCause: Some disbursement rows were excluded by 'Records to include' filters or the file used a different identifier. Action: Open 'View format' for the Disbursement dataset, ensure filters include the expected transaction types and the Reference / Identifier is mapped correctly, then re-run reconciliation. 2. Difference is not 0.00 even though rows appear present. LikelyCause: Rounding, currency or missing tax/fee rows. Action: Check individual amounts, settlement IDs and descriptions in the modal, update/upload missing rows and re-run.

Last updated on Sep 01, 2026

Why does a single Amazon MTR invoice match multiple Amazon Disbursement lines and how is the difference calculated?

Short Answer: The reconciliation can match one MTR row to multiple disbursement transactions by using the Reference/Identifier and adding disbursement 'Amount' values; the modal shows 'Match basis: Reference ID + Amount' and the Difference subtotal mismatch if any. PreRequisites 1. Reconciliation run completed and matched groups exist Steps 1. Open the reconciliation report and find the row that indicates 'Multiple transactions (n)'. Grouped row appears in the list showing the combined amount. 2. Expand the group to open 'Matched transaction details'. Modal shows 'Match basis' and tables for both sides. 3. Read the 'Match basis' card. It will list 'Reference ID' and 'Amount'. Review the disbursement lines and their amounts for example 521.19 Principal + 93.81 Product Tax = 615.00. Subtotal matches the MTR invoice and Difference shows 0.00 if sums align. 4. If the sums do not match, check for excluded lines, mapping errors, or rounding differences and correct source files or filters before re-running. After adjusting, re-run reconciliation to update matches. Troubleshooting 1. Combined disbursement amount doesn't equal the invoice amount. LikelyCause: A disbursement row is missing, excluded by filters, or there is a rounding/currency difference. Action: Verify the disbursement file contains all necessary tax/fee/principal lines and that filters in 'Records to include' are not excluding them. Fix data and re-run.

Last updated on Sep 01, 2026