Sales Order vs MTR Reconciliation: A Complete Guide for Finance Teams

Sales Order vs MTR reconciliation is the process of comparing internal order and return records with marketplace MTR reports.

For businesses selling on marketplaces such as Amazon, the order report shows what the business recorded as sales, while the MTR report shows marketplace-side invoice and tax-related transaction data. When these reports do not match, finance teams may face issues with revenue reporting, return accounting, tax validation, and audit preparation.

This reconciliation helps answer questions such as:

• Are all sales orders reflected in the MTR reports?
• Are all marketplace invoice records present in the internal order report?
• Do order amounts match invoice amounts?
• Are returns correctly adjusted as negative values?
• Are B2B and B2C transactions captured correctly?
• Which orders are missing, mismatched, or duplicated?

For finance teams handling marketplace sales, Sales Order vs MTR reconciliation is a key control for validating sales, returns, invoice values, and tax reporting accuracy.

What Is Sales Order vs MTR Reconciliation?

Sales Order vs MTR reconciliation compares internal sales and return records with external MTR reports.

In this workflow, the internal side includes:

• Order Report
• Order Return

The external side includes:

• MTR B2B
• MTR B2C

The internal order report contains sales transactions with fields such as order ID, purchase date, and item total including tax. The order return report contains return transactions, where the order amount is treated as negative.

The MTR side contains invoice-level records with order ID, invoice date, and invoice amount.

The goal is to confirm whether every internal sale or return has a corresponding MTR record and whether the amounts match.

Why This Reconciliation Matters

Marketplace sales data often flows through multiple reports. The order report may show customer orders, while MTR reports may show invoice and tax records. Returns may be available separately and need to be adjusted against the original sale.

If these reports are not reconciled, finance teams may face issues such as:

• Sales recorded internally but missing in MTR
• MTR invoices not found in order reports
• Return amounts not adjusted correctly
• Invoice amount mismatch
• B2B and B2C classification differences
• Duplicate orders
• Incorrect net sales reporting
• Tax reporting gaps
• Delayed month-end close

Sales Order vs MTR reconciliation helps ensure that marketplace revenue and tax-related records are complete and accurate.

Reports Involved

Side A: Internal Sales and Return Records

The internal side contains two reports.

Order Report

The order report represents sales recorded by the business. Important fields include:

• Order ID
• Purchase date
• Item total including tax

This report shows the expected sale value for each order.

Order Return

The order return report represents returned orders. Important fields include:

• Order ID
• Order date
• Negative order amount

Returns are treated as negative values because they reduce the net sales amount.

Together, the order and return reports represent the business’s internal view of gross sales, returns, and net order value.

Side B: MTR B2B and B2C Reports

The MTR side contains marketplace invoice records.

The configuration includes both:

• MTR B2B
• MTR B2C

Important fields include:

• Order ID
• Invoice date
• Invoice amount

B2B and B2C reports may need to be reconciled together because marketplace orders can be classified differently depending on customer type, invoice treatment, or tax reporting requirements.

How Matching Typically Works

Sales Order vs MTR reconciliation usually depends on three key fields:

1. Order ID
2. Amount
3. Date

A typical matching flow looks like this:

1. Internal order and return records are prepared.
2. Return values are treated as negative amounts.
3. MTR B2B and B2C invoice records are combined for comparison.
4. Internal order IDs are matched with MTR order IDs.
5. Internal item totals including tax are compared with MTR invoice amounts.
6. Purchase dates or order dates are compared with invoice dates.
7. Records are categorized as matched, partially matched, unmatched, or skipped.

For example:

• Order report shows order 123-456 with item total including tax of ₹2,000.
• MTR B2C shows the same order ID with invoice amount of ₹2,000.
• The transaction is treated as matched.

If the order ID matches but the amount differs, it becomes an amount mismatch.

If an order is present internally but not in MTR, it becomes an internal-only exception.

If an MTR invoice exists but no internal order is found, it becomes an MTR-only exception.

Why Returns Need Separate Handling

Returns are a major reason why Sales Order vs MTR reconciliation becomes complex.

In this workflow, the order return report uses a negative order amount. This means return values reduce the total value of sales.

If returns are not handled correctly, finance teams may see false mismatches between internal sales and MTR invoice values.

Common return-related issues include:

• Return exists internally but not in MTR
• Return appears in MTR but not in internal records
• Return amount differs from original order value
• Return posted in a different period
• Partial return not adjusted correctly
• Same order has both sale and return entries

A good reconciliation process should clearly separate sales matches, return matches, and net differences.

Common Exceptions

1. Sales Order Missing in MTR

This happens when an order is present in the internal order report but not found in MTR B2B or B2C.

Possible reasons include:

• Marketplace MTR report is incomplete
• Wrong reporting period was used
• Order was cancelled before invoicing
• Order ID format differs between reports
• Invoice was generated later
• Order was classified under another report

This exception should be reviewed because internal sales may not be supported by marketplace invoice records.

2. MTR Invoice Missing in Order Report

This happens when the MTR report contains an invoice, but the internal order report has no matching order.

Possible reasons include:

• Internal order report is incomplete
• Marketplace invoice belongs to another period
• Order was missed during internal export
• Order ID is stored differently
• B2B or B2C report was mapped incorrectly
• Duplicate or historical invoice is included

This can affect revenue completeness and audit support.

3. Amount Mismatch

Amount mismatches occur when the order ID matches but the amount does not.

Possible causes include:

• Tax-inclusive and tax-exclusive amount differences
• Shipping or additional charges treated differently
• Discount adjustment
• Partial return
• Rounding difference
• Incorrect return treatment
• Invoice correction or adjustment

Amount mismatches should be reviewed carefully because they directly affect sales and tax reporting.

4. Return Mismatch

Return mismatches occur when return records do not align with MTR invoice or credit records.

Possible reasons include:

• Return recorded internally but missing from MTR
• Return appears in MTR but not in internal records
• Return amount is different
• Return posted in a later period
• Partial return not identified correctly
• Negative amount handling is incorrect

Returns should be reconciled separately so that net sales are accurate.

5. Date Difference

The internal order report uses purchase date, the return report uses order date, and the MTR reports use invoice date.

These dates may differ due to:

• Invoice generation delay
• Return processing delay
• Marketplace reporting cutoff
• Month-end period differences
• Order placed late in the day
• Tax invoice generated after purchase

Date differences are not always errors, but they should be visible during reconciliation.

6. Duplicate Orders

Duplicates may appear in either internal or MTR reports.

Examples include:

• Same order appearing twice in the order report
• Duplicate invoice entries in MTR
• Same return uploaded twice
• Overlapping report periods
• Sale and return not clearly separated

Duplicate transactions can distort sales, returns, and tax reporting.

Excel-Based Reconciliation Challenges

Many finance teams reconcile Sales Order vs MTR manually using Excel.

The usual process includes:

1. Export order report.
2. Export order return report.
3. Download MTR B2B and B2C reports.
4. Convert returns into negative amounts.
5. Match order IDs across reports.
6. Compare item totals with invoice amounts.
7. Review missing and mismatched records.
8. Prepare exception reports.

This process becomes difficult when order volumes are high.

Common Excel challenges include:

• Wrong amount field selected
• Return amounts not negated correctly
• B2B and B2C reports handled separately
• Broken lookup formulas
• Date format issues
• Duplicate records missed
• Manual copy-paste errors
• No clear audit trail

A structured workflow reduces these risks and improves repeatability.

What a Good Sales Order vs MTR Reconciliation Process Should Include

A reliable process should include:

• Correct order report selection
• Correct return report selection
• MTR B2B and B2C report mapping
• Standardized order ID matching
• Proper negative treatment for returns
• Amount comparison including tax
• Date comparison across reports
• Matched and unmatched categorization
• Return mismatch reporting
• Duplicate detection
• Audit-ready output

The output should clearly show which orders matched, which did not, and why a transaction needs review.

How Cointab Helps

Cointab can help finance teams automate Sales Order vs MTR reconciliation by comparing internal order and return records with MTR B2B and B2C reports.

Finance teams can map order IDs, dates, and amount fields once and reuse the same reconciliation setup for future periods.

Cointab helps teams:

• Upload order, return, MTR B2B, and MTR B2C reports
• Match records using order IDs
• Compare item totals and invoice amounts
• Treat return values as negative amounts
• Identify fully matched transactions
• Highlight amount mismatches
• Show internal-only and MTR-only records
• Review skipped or invalid records
• Download audit-ready Excel reports

This reduces manual Excel effort and improves visibility into marketplace sales and return exceptions.

Business Value

Sales Order vs MTR reconciliation helps finance teams:

• Validate marketplace sales
• Confirm invoice-level accuracy
• Track return impact correctly
• Improve tax reporting support
• Reduce month-end close delays
• Identify missing or duplicate orders
• Improve audit readiness
• Reduce manual reconciliation work

It also helps finance and marketplace operations teams quickly identify recurring reporting gaps.

Best Practices

Finance teams should follow these best practices:

• Reconcile sales and returns regularly
• Use order ID as the primary matching reference
• Combine B2B and B2C MTR reports carefully
• Treat returns as negative values
• Review amount mismatches separately
• Track date differences across periods
• Check for duplicate order IDs
• Maintain period-wise reconciliation history
• Document manual adjustments clearly

Conclusion

Sales Order vs MTR reconciliation helps finance teams confirm whether internal sales and return records match marketplace MTR invoice data.

Because the reconciliation involves order reports, return reports, MTR B2B, MTR B2C, invoice amounts, tax-inclusive sales values, and negative return amounts, a structured process is essential.

With Cointab, finance teams can automate Sales Order vs MTR reconciliation, reduce manual effort, identify exceptions faster, and generate audit-ready outputs for review.

To learn more or get started with automated reconciliation, visit: https://www.cointab.net/