Amazon MTR B2B and B2C vs Disbursement Reconciliation: A Complete Guide for Finance Teams

Amazon MTR B2B and B2C vs disbursement reconciliation is the process of comparing Amazon sales and transaction records from MTR reports with Amazon disbursement records to validate whether marketplace payments have been settled correctly.

For brands selling on Amazon, MTR reports may include B2B and B2C order-level sales, invoices, SKUs, taxes, returns, refunds, and transaction values. Amazon disbursement reports show the amount paid by Amazon after applying marketplace fees, commissions, shipping charges, refunds, claims, tax deductions, storage charges, penalties, and other adjustments.

This reconciliation helps finance teams answer:

• Are all Amazon B2B and B2C sales available in the disbursement report?
• Are all Amazon disbursement entries supported by valid MTR records?
• Are returns, refunds, credit notes, and cancellations adjusted correctly?
• Do gross sales, tax values, deductions, fees, and net disbursements match?
• Are Amazon commission, shipping fees, FBA fees, TCS, TDS, and other charges mapped correctly?
• Which orders are missing, mismatched, duplicated, short-settled, or pending review?

For finance teams, this reconciliation supports Amazon receivable accuracy, marketplace settlement validation, GST review, month-end close, and audit readiness.

What Is Amazon MTR vs Disbursement Reconciliation?

Amazon MTR vs disbursement reconciliation compares the sales-side records from Amazon MTR reports with the settlement-side records from Amazon disbursement reports.

Side A: Amazon MTR B2B and B2C Reports
This represents the Amazon transaction-side view. It may include B2B orders, B2C orders, invoice numbers, order IDs, SKUs, quantities, taxable values, GST amounts, returns, refunds, and expected receivables.

Side B: Amazon Disbursement Report
This represents the payment and settlement-side view. It may include settlement references, disbursement dates, order-level payments, Amazon fees, commission, shipping charges, refund adjustments, tax deductions, storage charges, and net payment amounts.

The goal is to confirm whether every Amazon sale, return, and refund recorded in the MTR reports is correctly reflected in the Amazon disbursement report.

Matching is usually based on:

• Amazon order ID
• Shipment ID
• Invoice number
• SKU or item code
• B2B or B2C transaction type
• Settlement reference
• Disbursement reference
• Sale amount
• Taxable value
• GST amount
• Return amount
• Refund amount
• Marketplace fee
• Commission amount
• Net disbursement amount
• Order date
• Invoice date
• Settlement date

If the order reference, sales value, tax value, refund impact, deduction logic, and disbursement amount align across reports, the transaction can be treated as reconciled. If the order appears but the amount differs, it becomes an exception. If a record appears only on one side, it becomes unmatched.

Why This Reconciliation Matters

Amazon marketplace payments rarely equal gross sales. Amazon may deduct commission, referral fees, closing fees, shipping charges, FBA charges, storage fees, returns, refunds, reimbursements, claim adjustments, TCS, TDS, and other recoveries before making a disbursement.

At the same time, Amazon MTR reports may contain both B2B and B2C transactions. These transactions may have different invoice treatment, tax treatment, customer types, and reporting requirements. If finance teams reconcile only the final disbursement amount, they may miss order-level issues, tax differences, return adjustments, and unsupported deductions.

Without reconciliation, finance teams may face issues such as:

• Amazon sales recorded but not settled
• Disbursement entries without matching MTR records
• Returns adjusted in disbursement but missing in sales records
• Refunds not mapped to the original order
• GST or tax amount differences
• Excess marketplace fee deductions
• Short disbursements not identified
• Duplicate orders or settlement entries
• Incorrect Amazon receivable balance
• Month-end close delays and audit queries

A structured reconciliation process helps finance teams validate Amazon sales, returns, deductions, and disbursements at transaction level.

Reports Involved

Side A: Amazon MTR B2B Report

The Amazon MTR B2B report represents Amazon business-to-business transactions.

Common fields may include:

• Amazon order ID
• Invoice number
• Invoice date
• Buyer type
• GSTIN or business buyer details
• SKU or item code
• Product description
• Quantity
• Taxable value
• CGST amount
• SGST amount
• IGST amount
• Total invoice value
• Return or refund status
• Expected receivable amount

This report helps finance teams validate B2B Amazon sales, tax treatment, invoice values, and receivables.

Side A: Amazon MTR B2C Report

The Amazon MTR B2C report represents Amazon business-to-consumer transactions.

Common fields may include:

• Amazon order ID
• Invoice number
• Order date
• Invoice date
• SKU or item code
• Product description
• Quantity
• Gross sale value
• Discount amount
• Taxable value
• GST amount
• Total order value
• Return status
• Refund status
• Expected receivable amount

This report helps finance teams validate B2C Amazon sales, returns, tax values, and expected settlement amounts.

Side B: Amazon Disbursement Report

The Amazon disbursement report represents Amazon’s payment and settlement-side view.

Common fields may include:

• Settlement ID
• Disbursement date
• Order ID
• Shipment ID
• Transaction type
• Principal amount
• Product tax amount
• Shipping amount
• Shipping tax
• Commission or referral fee
• Closing fee
• FBA fee
• Storage fee
• Refund amount
• Reimbursement amount
• TCS amount
• TDS amount
• Other adjustment amount
• Net disbursement amount

This report shows what Amazon has paid, deducted, refunded, recovered, reimbursed, or kept pending.

How Matching Typically Works

Amazon MTR B2B and B2C vs disbursement reconciliation usually works by comparing Amazon order-level sales records with disbursement-side settlement records.

A typical process looks like this:

1. The Amazon MTR B2B report is uploaded.
2. The Amazon MTR B2C report is uploaded.
3. The Amazon disbursement report is uploaded.
4. Amazon order IDs, invoice numbers, SKUs, shipment IDs, and settlement references are mapped.
5. B2B and B2C sales are matched with disbursement entries.
6. Returns and refunds are matched with disbursement-side adjustments.
7. Amazon fees, commission, shipping charges, taxes, reimbursements, and recoveries are reviewed.
8. Net disbursement is compared with expected receivable after valid deductions.
9. Records are categorized as matched, partially matched, unmatched, or skipped.

For example:

• The MTR report shows an Amazon B2C sale of ₹2,500.
• The disbursement report shows the same order with principal amount of ₹2,500.
• Amazon deducts referral fee, closing fee, shipping fee, and applicable taxes before settlement.
• If the deductions are valid and the net disbursement calculation is correct, the transaction is reconciled.

Another example:

• The MTR report shows an Amazon B2B invoice of ₹10,000.
• The disbursement report shows the same order with payment of ₹9,200 after deductions.
• The ₹800 difference should be explained through Amazon fees, tax deductions, returns, refunds, or other valid adjustments.
• If the difference is not supported, it becomes an exception.

If an MTR sale exists but no disbursement entry is found, it becomes an MTR-only exception.

If a disbursement entry exists but no MTR sale, return, or refund record is found, it becomes a disbursement-only exception.

Common Exceptions in Amazon MTR vs Disbursement Reconciliation

1. MTR Sale Missing in Disbursement Report

This happens when the MTR B2B or B2C report shows a valid Amazon sale, but the disbursement report does not show a matching settlement entry.

Possible reasons include:

• Settlement cycle is pending
• Order was cancelled before settlement
• Order was returned or refunded
• Disbursement report period is incomplete
• Order ID format differs across reports
• Order is under Amazon dispute or hold

This exception should be tracked until the order is settled, returned, refunded, or explained.

2. Disbursement Entry Missing in MTR Report

This happens when the Amazon disbursement report contains an entry, but no matching MTR transaction is found.

Possible reasons include:

• MTR report export is incomplete
• Entry belongs to a prior-period order
• Entry is a reimbursement, recovery, or adjustment
• Order reference is stored differently
• Wrong marketplace account or period was selected
• Disbursement entry relates to a refund or claim instead of a fresh sale

This exception should be reviewed before accepting the payment-side entry.

3. B2B and B2C Classification Difference

Amazon MTR may split transactions into B2B and B2C categories. Classification issues can occur when the transaction appears in one report but is expected in another.

Possible causes include:

• Business buyer transaction classified incorrectly
• B2B order included in B2C review
• GSTIN or buyer details missing
• Wrong MTR report selected
• Invoice classification mismatch
• Internal ERP mapping not aligned with Amazon classification

This is important because B2B and B2C transactions may have different tax, reporting, and reconciliation treatment.

4. Amount Mismatch

Amount mismatches occur when the order reference matches, but the MTR value and disbursement value do not reconcile.

Possible causes include:

• Amazon fee deduction
• Commission or referral fee
• Shipping fee or closing fee
• Refund adjustment
• Return impact
• TCS or TDS deduction
• Reimbursement or claim adjustment
• Rounding difference
• Wrong amount column selected

Amount mismatches affect receivable accuracy and settlement reporting.

5. Return or Refund Difference

Returns and refunds reduce the expected disbursement amount.

Common issues include:

• Return shown in MTR but not adjusted in disbursement
• Refund shown in disbursement but missing from MTR
• Partial refund creating amount difference
• Refund adjusted in a later settlement cycle
• Refund linked to the wrong order
• Return charges deducted separately
• Credit note not mapped correctly

Return and refund differences should be reviewed separately from normal sales differences.

6. Amazon Fee or Commission Difference

Amazon may deduct multiple marketplace fees before disbursement.

Possible issues include:

• Referral fee charged at a different rate
• Closing fee not expected
• FBA fee or shipping fee mismatch
• GST on fee not mapped correctly
• Fee charged on returned order
• Fee reversal missing
• Multiple fee lines grouped together

These differences should be supported by Amazon disbursement details before being accepted in the books.

7. TCS, TDS, or GST Difference

Amazon disbursement reports may include tax-related deductions and adjustments.

Possible issues include:

• TCS amount not recorded internally
• TDS amount differs from expectation
• GST on fees not mapped correctly
• Product tax amount differs from MTR
• Tax reversal missing for returned order
• Tax posted in another period

Tax differences are important because they affect statutory reporting, GST reconciliation, and audit documentation.

8. Reimbursement or Claim Difference

Amazon may issue reimbursements or recoveries for claims, lost inventory, damaged items, incorrect deductions, or previous-period adjustments.

Common issues include:

• Reimbursement appears in disbursement but not in MTR
• Claim recovery deducted without internal support
• Reimbursement linked to older order
• Adjustment posted in a different period
• Recovery treated incorrectly as fee
• Manual accounting entry missing

These entries should be reviewed separately from order-level sales.

9. Settlement Timing Difference

Amazon sales and disbursements may appear in different periods.

Possible reasons include:

• Sale happened in one period but disbursed in the next
• Refund adjusted in a later settlement cycle
• Return confirmed after the original settlement
• Disbursement cycle differs from accounting period
• Previous-period adjustment included in current disbursement
• Bank credit received after settlement date

Timing differences should be tracked separately from true mismatches.

10. Duplicate Order or Disbursement Entry

Duplicates may appear in either MTR reports or disbursement reports.

Examples include:

• Same Amazon order repeated in MTR
• Same invoice repeated
• Same SKU line duplicated
• Same disbursement line repeated
• Same settlement reference repeated
• Duplicate report uploaded

Duplicates can overstate sales, refunds, fees, disbursements, or receivables if not identified.

Why Manual Excel Reconciliation Is Difficult

Many finance teams reconcile Amazon MTR and disbursement reports manually in Excel.

The usual process includes:

1. Downloading Amazon MTR B2B and B2C reports.
2. Downloading the Amazon disbursement report.
3. Cleaning order IDs, invoice numbers, SKUs, shipment IDs, and settlement references.
4. Combining B2B and B2C reports into a single reconciliation view.
5. Matching MTR records with disbursement entries.
6. Comparing sale values, tax values, refunds, fees, deductions, and net disbursements.
7. Reviewing unmatched transactions and preparing exception reports.

This becomes difficult as transaction volumes increase.

Common Excel challenges include:

• Separate B2B and B2C MTR files
• Different order and shipment reference formats
• Multiple fee and tax columns
• Returns adjusted in later settlement cycles
• One disbursement covering many orders
• Reimbursements and recoveries mixed with order payments
• Duplicate order lines missed
• Broken lookup formulas
• Manual copy-paste errors
• No clear audit trail

A structured reconciliation workflow reduces these risks and creates a repeatable process for every settlement cycle.

What a Good Amazon MTR vs Disbursement Reconciliation Process Should Include

A reliable process should include:

• Complete Amazon MTR B2B report
• Complete Amazon MTR B2C report
• Complete Amazon disbursement report
• Order-level matching
• Invoice-level matching
• SKU-level visibility where required
• B2B and B2C classification review
• Return and refund matching
• Fee and commission review
• TCS, TDS, and GST comparison
• Reimbursement and recovery review
• Net disbursement validation
• MTR-only exception reporting
• Disbursement-only exception reporting
• Amount mismatch reporting
• Duplicate detection
• Audit-ready output

The output should clearly show which orders matched, which refunds were adjusted, which fees were valid, which disbursements were correct, and which records need follow-up.

How Cointab Helps

Cointab can help finance teams automate Amazon MTR B2B and B2C vs disbursement reconciliation by comparing Amazon MTR data with Amazon disbursement data in a structured workflow.

Finance teams can map order references, invoice numbers, SKU fields, shipment IDs, settlement references, fee fields, tax fields, refund fields, amount fields, and date fields once and reuse the setup for future periods.

Cointab helps teams:

• Upload Amazon MTR B2B, MTR B2C, and disbursement reports
• Match Amazon MTR transactions with disbursement entries
• Compare sales, returns, refunds, fees, taxes, reimbursements, and net disbursements
• Identify fully matched transactions
• Highlight amount mismatches and fee differences
• Show MTR-only and disbursement-only exceptions
• Review B2B and B2C transaction classification
• Detect duplicate orders, invoices, SKUs, and settlement entries
• Download audit-ready Excel reports
• Reuse the workflow for recurring reconciliation

This reduces manual Excel work and gives finance teams better visibility into Amazon settlements and receivables.

Business Value

Amazon MTR B2B and B2C vs disbursement reconciliation helps finance teams:

• Validate Amazon marketplace receivables
• Track sales pending disbursement
• Confirm return and refund adjustments
• Identify unsupported deductions
• Detect duplicate order or settlement entries
• Improve settlement accuracy
• Reduce marketplace disputes
• Support GST and audit review
• Speed up month-end close
• Reduce manual reconciliation work

It also helps finance, marketplace operations, eCommerce, and accounting teams resolve transaction-level settlement issues faster.

Best Practices

Finance teams should follow these best practices:

• Reconcile Amazon MTR and disbursement reports for every settlement cycle
• Combine B2B and B2C MTR records carefully before reconciliation
• Use Amazon order ID, invoice number, SKU, shipment ID, and settlement reference wherever available
• Review B2B and B2C transactions separately where tax treatment differs
• Match returns and refunds before validating net disbursement
• Validate Amazon fees separately from tax deductions and reimbursements
• Track timing differences separately from true mismatches
• Check duplicate orders, invoices, SKUs, and disbursement references
• Maintain period-wise reconciliation history
• Document manual corrections clearly

Conclusion

Amazon MTR B2B and B2C vs disbursement reconciliation helps finance teams confirm whether Amazon sales, returns, refunds, marketplace fees, taxes, reimbursements, disbursements, and receivables are properly aligned.

Because this reconciliation depends on MTR B2B records, MTR B2C records, disbursement records, order IDs, invoice numbers, SKU details, tax values, fee deductions, refunds, and settlement timing, manual Excel reconciliation can become slow and error-prone as transaction volumes grow.

With Cointab, finance teams can automate Amazon MTR vs disbursement reconciliation, reduce manual Excel work, identify missing or mismatched records faster, and generate audit-ready reports for review.

Start your 14-day free trial with Cointab and automate Amazon MTR B2B and B2C vs disbursement reconciliation without relying on manual Excel work. No credit card required.

Visit: https://www.cointab.net/