Myntra Orders vs Settlement Reconciliation: A Complete Guide for Finance Teams

Myntra orders vs settlement reconciliation is the process of comparing internal order records with the settlement report received from Myntra.

For brands selling on Myntra, internal order records show the sales that were booked, invoiced, shipped, cancelled, returned, or expected to be collected. Myntra settlement records show what Myntra has paid after adjusting commissions, fixed fees, logistics charges, returns, refunds, penalties, TDS, TCS, GST on fees, and other marketplace deductions.

This reconciliation helps finance teams answer:

• Are all Myntra orders recorded internally present in the settlement report?
• Are all settlement entries supported by valid internal orders?
• Are returns, cancellations, and refunds adjusted correctly?
• Do gross order values, deductions, taxes, and net settlements match?
• Are commissions, fixed fees, logistics deductions, and recoveries properly explained?
• Which orders are missing, mismatched, duplicated, short-settled, or pending review?

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

What Is Myntra Orders vs Settlement Reconciliation?

Myntra orders vs settlement reconciliation compares the order-side view with the marketplace settlement-side view.

Side A: Internal Orders Report
This represents the company’s internal view of Myntra sales. It may include order IDs, invoices, SKUs, quantities, sale values, tax amounts, order status, shipment details, cancellations, returns, and expected receivables.

Side B: Myntra Settlement Report
This represents Myntra’s payment-side view. It may include order references, settlement references, gross sale value, return adjustments, refund adjustments, commission, fixed fee, logistics charge, GST on fees, TDS, TCS, penalties, recoveries, and final payable amount.

The goal is to confirm whether every valid Myntra order has been settled correctly after considering returns, refunds, fees, taxes, and deductions.

Matching is usually based on:

• Myntra order ID
• Internal order ID
• Invoice number
• SKU or item code
• Shipment ID
• Return reference
• Settlement reference
• Payment reference
• Gross order value
• Return amount
• Refund amount
• Commission amount
• Fixed fee amount
• Tax amount
• Net settlement amount
• Order date
• Settlement date

If the order reference, sale amount, deduction logic, and net settlement value match across both reports, the transaction can be treated as reconciled. If the order exists but amounts differ, it becomes a mismatch. If a record appears only on one side, it becomes an exception.

Why This Reconciliation Matters

Myntra settlements do not usually equal gross sales. The final amount received may be lower because Myntra deducts marketplace fees, commissions, logistics charges, payment-related charges, taxes on fees, penalties, claims, recoveries, and return adjustments before settlement.

Without reconciliation, finance teams may face issues such as:

• Orders recorded internally but not settled by Myntra
• Settlement entries without matching internal orders
• Returns or refunds adjusted incorrectly
• Commission or fixed fee overcharged
• Logistics charges not validated
• TDS, TCS, or GST differences
• Duplicate order or settlement entries
• Unsupported deductions accepted without review
• Incorrect marketplace receivable balance
• Month-end close delays and audit queries

A structured reconciliation process helps finance teams validate order-level settlement accuracy instead of only checking final payout totals.

Reports Involved

Side A: Orders Report

The orders report represents the internal order-side view of Myntra sales.

Common fields may include:

• Myntra order ID
• Internal order ID
• Invoice number
• Invoice date
• Order date
• SKU or item code
• Product description
• Quantity
• Gross order value
• Discount amount
• Taxable value
• GST amount
• Net order value
• Shipment ID
• Order status
• Return or cancellation status
• Expected receivable

This report shows what the business has recorded as sales, returns, cancellations, and expected collections.

Side B: Settlement Report

The settlement report represents Myntra’s payment and deduction-side view.

Common fields may include:

• Settlement reference
• Settlement date
• Payment reference
• Myntra order ID
• Shipment ID
• Gross sale value
• Return adjustment
• Refund adjustment
• Commission amount
• Fixed fee amount
• Logistics charge
• GST on fees
• TDS amount
• TCS amount
• Penalty or recovery
• Net settlement amount
• Settlement status

This report shows what Myntra has paid, deducted, adjusted, recovered, or kept pending.

How Matching Typically Works

Myntra orders vs settlement reconciliation usually works by comparing internal order records with Myntra settlement entries at order level.

A typical process looks like this:

1. The internal orders report is uploaded.
2. The Myntra settlement report is uploaded.
3. Order IDs, invoice numbers, shipment IDs, settlement references, and amount fields are mapped.
4. Valid orders are matched with settlement entries.
5. Returns, cancellations, and refunds are reviewed against settlement adjustments.
6. Commission, fixed fees, logistics charges, taxes, and recoveries are validated.
7. Net settlement is compared with expected receivable after valid deductions.
8. Records are categorized as matched, partially matched, unmatched, or skipped.

For example:

• The orders report shows a Myntra order of ₹3,000.
• The settlement report shows the same order with gross sale value of ₹3,000.
• Myntra deducts commission, fixed fee, logistics charge, and tax on fees.
• If the deductions are valid and the net settlement is correct, the transaction is reconciled.

Another example:

• The orders report shows a completed order of ₹2,000.
• The settlement report shows only ₹1,650 after deductions.
• The ₹350 difference should be explained through commission, fees, taxes, refund, return, penalty, or other valid adjustment.
• If the difference is unsupported, it becomes an exception.

If an order exists internally but no settlement entry is found, it becomes an order-only exception.

If a settlement entry exists but no internal order is found, it becomes a settlement-only exception.

Common Exceptions in Myntra Orders vs Settlement Reconciliation

1. Order Missing in Settlement Report

This happens when the internal orders report shows a valid Myntra order, but the settlement report does not show a matching settlement entry.

Possible reasons include:

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

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

2. Settlement Entry Missing in Orders Report

This happens when the Myntra settlement report contains an entry, but no matching internal order is found.

Possible reasons include:

• Orders report is incomplete
• Settlement belongs to a prior-period order
• Entry is a recovery, reimbursement, or correction
• Order reference is stored differently internally
• Wrong date range was selected
• Settlement entry relates to a return or claim adjustment

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

3. Amount Mismatch

Amount mismatches occur when the order exists on both sides, but the values do not reconcile.

Possible causes include:

• Sale value difference
• Tax amount difference
• Discount treatment difference
• Commission deduction
• Fixed fee deduction
• Logistics charge
• Return or refund adjustment
• Rounding difference
• Wrong amount column selected

Amount mismatches affect receivable accuracy, settlement reporting, and audit documentation.

4. Return or Refund Difference

Returns and refunds reduce the expected settlement amount.

Common issues include:

• Return shown in settlement but missing internally
• Refund adjustment not mapped to original order
• Internal return recorded but settlement adjustment missing
• Partial refund creating amount difference
• Return charge deducted separately
• Refund adjusted in a later settlement cycle

Return and refund differences should be reviewed separately from normal order settlement differences.

5. Commission or Fixed Fee Difference

Myntra may deduct commission, fixed fees, and other marketplace charges before settlement.

Possible issues include:

• Commission charged at a different rate
• Fixed fee charged more than expected
• Fee charged on cancelled or returned order
• Fee reversal missing after return
• GST on fee not mapped correctly
• Multiple fee lines grouped together

These differences should be supported by Myntra settlement details before being accepted in the books.

6. Logistics Charge Difference

Marketplace settlements may include logistics-related deductions.

Possible issues include:

• Logistics charge applied to the wrong order
• Higher charge than expected
• Return logistics charge not reviewed separately
• Shipping fee deducted even after cancellation
• Weight or category mismatch
• Multiple logistics deductions grouped together

Logistics deductions should be reviewed carefully because they directly affect marketplace profitability.

7. Tax, TDS, or TCS Difference

Myntra settlement reports may include statutory deductions and tax-related values.

Possible issues include:

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

Tax differences are important for statutory reporting and audit readiness.

8. Settlement Timing Difference

Orders and settlements may appear in different periods.

Possible reasons include:

• Order happened in one month but settled in the next
• Return adjusted in a later settlement cycle
• Refund processed after the original payout
• Previous-period recovery included in current settlement
• Bank credit received after settlement date
• Cutoff dates differ between internal and Myntra reports

Timing differences should be tracked separately from true mismatches.

9. Duplicate Order or Settlement Entry

Duplicates may appear in either report.

Examples include:

• Same order repeated internally
• Same invoice repeated
• Same settlement line repeated
• Same settlement reference repeated
• Duplicate refund or return entry
• Duplicate file upload

Duplicates can overstate sales, deductions, settlements, or receivables if not identified.

10. Unsupported Deduction or Recovery

This happens when Myntra applies a deduction that cannot be explained through expected commission, fee, tax, return, refund, or adjustment logic.

Possible causes include:

• Marketplace penalty
• Claim recovery
• Promotional recovery
• Return charge
• Logistics dispute
• Packaging charge recovery
• Previous-period correction

Unsupported deductions should be reviewed before being posted or accepted.

Why Manual Excel Reconciliation Is Difficult

Many finance teams reconcile Myntra order and settlement reports manually in Excel.

The usual process includes:

1. Exporting the internal orders report.
2. Downloading the Myntra settlement report.
3. Cleaning order IDs, invoice numbers, shipment IDs, and settlement references.
4. Matching orders using lookup formulas.
5. Comparing sale values, deductions, taxes, refunds, and settlement amounts.
6. Reviewing unmatched records and amount mismatches.
7. Preparing exception reports for finance and marketplace teams.

This becomes difficult as order volumes increase.

Common Excel challenges include:

• Different order ID formats
• Multiple deduction columns
• Returns adjusted in later settlement cycles
• One settlement covering many orders
• Fees, taxes, and recoveries mixed together
• Duplicate records missed
• Broken formulas
• Manual copy-paste errors
• Wrong amount column selected
• No clear audit trail

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

What a Good Myntra Orders vs Settlement Reconciliation Process Should Include

A reliable process should include:

• Complete orders report
• Complete settlement report
• Order-level matching
• Invoice-level matching
• SKU-level visibility where required
• Return and refund matching
• Commission and fixed fee review
• Logistics charge review
• TDS, TCS, and GST comparison
• Net settlement validation
• Order-only exception reporting
• Settlement-only exception reporting
• Amount mismatch reporting
• Duplicate detection
• Audit-ready output

The output should clearly show which orders matched, which settlements were correct, which deductions were valid, and which records need follow-up.

How Cointab Helps

Cointab can help finance teams automate Myntra orders vs settlement reconciliation by comparing internal order data with Myntra settlement data in a structured workflow.

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

Cointab helps teams:

• Upload internal order and Myntra settlement reports
• Match Myntra orders with settlement entries
• Compare sales, returns, refunds, deductions, taxes, and net settlement values
• Identify fully matched transactions
• Highlight amount mismatches and deduction differences
• Show order-only and settlement-only exceptions
• Review unsupported deductions and recoveries
• Detect duplicate orders, invoices, refunds, 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 Myntra settlements and receivable differences.

Business Value

Myntra orders vs settlement reconciliation helps finance teams:

• Validate Myntra marketplace receivables
• Track orders pending settlement
• 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 order-level settlement issues faster.

Best Practices

Finance teams should follow these best practices:

• Reconcile Myntra orders and settlements for every settlement cycle
• Use Myntra order ID, invoice number, shipment ID, and settlement reference wherever available
• Match returns and refunds before validating net settlement
• Validate commission, fixed fees, and logistics deductions separately
• Track timing differences separately from true mismatches
• Check duplicate orders, invoices, refunds, and settlement references
• Maintain period-wise reconciliation history
• Document manual corrections clearly

Conclusion

Myntra orders vs settlement reconciliation helps finance teams confirm whether marketplace orders, returns, refunds, deductions, taxes, settlements, and receivables are properly aligned.

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

With Cointab, finance teams can automate Myntra orders vs settlement 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 Myntra orders vs settlement reconciliation without relying on manual Excel work. No credit card required.

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