Myntra Sales vs Payments Fixed Fee Reconciliation: A Complete Guide for Finance Teams

Myntra sales vs payments fixed fee reconciliation is the process of comparing internal sales records with payment or settlement records received from Myntra to validate whether fixed fees, deductions, returns, and net payments have been applied correctly.

For brands selling on Myntra, the sales report may show order-level sales, invoice values, SKUs, quantities, taxes, discounts, returns, and expected receivables. The payment report may show settled amounts after marketplace deductions such as fixed fees, commissions, logistics charges, penalties, tax deductions, return adjustments, and other marketplace recoveries.

This reconciliation helps finance teams answer:

• Are all Myntra sales available in the payment report?
• Are all payment entries supported by valid sales records?
• Has the fixed fee been charged correctly?
• Are returns, cancellations, and refunds adjusted properly?
• Are deductions, fees, taxes, and settlements mapped correctly?
• Which orders are missing, mismatched, short-settled, duplicated, or pending review?

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

What Is Myntra Fixed Fee Reconciliation?

Myntra fixed fee reconciliation compares sales-side records with payment-side records to verify whether the fixed fee and other settlement deductions have been applied as expected.

Side A: Sales Report
This represents the internal sales-side view. It may include order ID, invoice number, SKU, quantity, gross sale value, discount, tax, return status, credit note value, and expected receivable.

Side B: Payment Report
This represents the marketplace payment or settlement-side view. It may include payment reference, order reference, settled amount, fixed fee, commission, deductions, tax deductions, return adjustment, refund adjustment, and net payable amount.

The goal is to confirm whether every sale has a valid payment entry and whether the fixed fee deducted in the payment report is correct.

Matching is usually based on:

• Myntra order ID
• ERP order number
• Invoice number
• SKU or item code
• Payment reference
• Settlement reference
• Sale amount
• Return amount
• Fixed fee amount
• Deduction amount
• Net payment amount
• Order date
• Invoice date
• Settlement date

If the sales reference and payment reference match, and the fee and settlement logic is correct, the record can be treated as reconciled. If the reference matches but the fixed fee or payment amount differs, it becomes an exception.

Why This Reconciliation Matters

Marketplace payments do not usually equal gross sales. Myntra may deduct fixed fees, commissions, logistics charges, return charges, penalties, tax deductions, and other adjustments before making the final payment.

Without reconciliation, finance teams may face issues such as:

• Sales recorded internally but not paid by Myntra
• Payment entries without matching sales records
• Fixed fee charged incorrectly
• Duplicate fee deductions
• Returns adjusted against the wrong orders
• Net payment not matching expected receivable
• Marketplace deductions not recorded correctly
• Incorrect receivable balance
• Month-end close delays
• Audit queries due to missing order-level support

A structured reconciliation process helps finance teams validate whether sales, fees, deductions, returns, and payments are properly aligned.

Reports Involved

Side A: Sales Report

The sales report represents the internal order or invoice-level view of Myntra sales.

Common fields may include:

• Order ID
• Invoice number
• SKU or product code
• Product description
• Quantity
• Order date
• Invoice date
• Gross sale value
• Discount amount
• Tax amount
• Net sale value
• Return amount
• Credit note amount
• Expected receivable

This report shows what the business has recorded as sales and receivables.

Side B: Payment Report

The payment report represents the settlement-side view received from Myntra.

Common fields may include:

• Myntra order ID
• Payment reference
• Settlement reference
• Settlement date
• Gross payable amount
• Fixed fee amount
• Commission amount
• Logistics or shipping deduction
• Return adjustment
• Refund adjustment
• Tax deduction
• Other deduction amount
• Net payment amount
• Payment status

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

How Matching Typically Works

Myntra sales vs payments fixed fee reconciliation usually works by comparing order-level sales with payment-level deductions and settlement values.

A typical process looks like this:

1. The sales report is uploaded.
2. The payment report is uploaded.
3. Order IDs, invoice numbers, SKUs, and payment references are mapped.
4. Sales values are compared with gross payment values.
5. Fixed fee deductions are validated against expected fee logic.
6. Returns, refunds, credit notes, and cancellations are reviewed separately.
7. Net payment values are compared with expected receivables.
8. Records are categorized as matched, partially matched, unmatched, or skipped.

For example:

• The sales report shows a Myntra order of ₹2,000.
• The payment report shows the same order with a fixed fee deduction of ₹100 and net payment of ₹1,900.
• If the fixed fee is expected and the net payment calculation is correct, the transaction is treated as matched.

Another example:

• The sales report shows a Myntra order of ₹2,000.
• The payment report shows a fixed fee deduction of ₹150 instead of the expected ₹100.
• The ₹50 difference becomes a fixed fee mismatch and should be reviewed.

If a sale exists but no payment entry is found, it becomes a sales-only exception.

If a payment entry exists but no sale is found, it becomes a payment-only exception.

Why Myntra Fixed Fee Reconciliation Is Complex

Fixed fee reconciliation can be difficult because the final payment amount may include multiple deductions and adjustments beyond the fixed fee.

Common complexity drivers include:

• One payment cycle covering multiple orders
• Fixed fees charged per order, item, shipment, or return
• Returns adjusted in later payment cycles
• Partial returns affecting fee logic
• Commission and fixed fee reported separately
• Tax deductions shown in different columns
• Discounts and promotions affecting receivable value
• Previous-period adjustments included in the current payment report
• Multiple SKUs linked to one order
• Different reference formats across sales and payment files

A good reconciliation process should validate the order-level sale first and then explain the bridge from gross sale value to net payment.

Common Exceptions in Myntra Sales vs Payments Fixed Fee Reconciliation

1. Sale Missing in Payment Report

This happens when the sales report shows a Myntra sale, but no matching payment entry is found.

Possible reasons include:

• Payment cycle is pending
• Sale was not yet settled by Myntra
• Order was cancelled or returned
• Payment report period is incomplete
• Order reference is missing or formatted differently
• Wrong payment report was uploaded

This exception should be tracked until the payment is received, adjusted, or explained.

2. Payment Entry Missing in Sales Report

This happens when the payment report contains an entry, but no matching sale is found.

Possible reasons include:

• Sales report is incomplete
• Payment belongs to another period
• Entry is an adjustment, refund, or recovery
• Order reference is stored differently internally
• Sale was not posted in the ERP
• Manual classification is required

This exception should be reviewed so every payment-side entry has valid sales or adjustment support.

3. Fixed Fee Mismatch

This happens when the fixed fee deducted in the payment report does not match the expected fee amount.

Possible reasons include:

• Wrong fixed fee rate applied
• Fee charged at item level instead of order level
• Fee charged on returned order
• Fee charged twice
• Fee not reversed after cancellation
• Fee logic changed for a category or period
• Wrong fee column selected

Fixed fee mismatches directly affect marketplace profitability and receivable accuracy.

4. Duplicate Fixed Fee Deduction

Duplicate fee deductions occur when the same order, item, or shipment appears to have been charged more than once.

Possible causes include:

• Duplicate payment entry
• Duplicate fee line
• Order split into multiple shipments
• Return fee and sales fee both applied incorrectly
• Same file uploaded twice
• Payment report contains repeated lines

Duplicate fee deductions should be reviewed carefully because they can reduce net settlement incorrectly.

5. Amount Mismatch

Amount mismatches occur when the order reference matches, but the sales amount and payment amount do not reconcile.

Possible causes include:

• Fixed fee difference
• Commission deduction
• Logistics deduction
• Tax deduction
• Return adjustment
• Refund adjustment
• Promotional adjustment
• Rounding difference
• Wrong amount field selected

Amount mismatches affect receivable tracking and marketplace settlement reporting.

6. Return or Refund Difference

Returns and refunds reduce the expected payment amount.

Common issues include:

• Return shown in payment report but missing in sales records
• Credit note posted internally but not reflected in payment report
• Partial return creating amount difference
• Refund adjusted in a later payment cycle
• Return fee deducted but not expected
• Return linked to the wrong order

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

7. Tax or TDS Difference

Marketplace payments may include tax deductions, TCS, TDS, or GST-related adjustments.

Possible issues include:

• Tax deduction not recorded internally
• TDS amount differs from expectation
• GST on fee not mapped correctly
• Tax value differs due to return or credit note
• Wrong tax column selected
• Tax posted in a different period

Tax differences are important because they affect statutory reporting and audit support.

8. Settlement Timing Difference

Sales and payments may appear in different periods.

Possible reasons include:

• Sale happened in one month but payment settled in the next month
• Return adjusted in a later cycle
• Fixed fee deducted in a later settlement
• Payment file covers a different date range
• Prior-period adjustment included in current payment

Timing differences should be tracked separately from true mismatches.

9. Duplicate Sales or Payment Records

Duplicates may appear in either report.

Examples include:

• Same order repeated in sales report
• Same invoice repeated
• Same payment reference repeated
• Same fixed fee line repeated
• Duplicate return entry
• Duplicate file upload

Duplicates can overstate sales, deductions, or payment values if not identified.

10. Unsupported Deduction

This happens when the payment report contains a deduction that cannot be explained through expected fee, commission, tax, return, or adjustment logic.

Possible causes include:

• Marketplace penalty
• Claim adjustment
• Previous-period recovery
• Return charge
• Logistics dispute
• Promotional recovery
• Manual adjustment

Unsupported deductions should be reviewed before being accepted in the books.

Why Manual Excel Reconciliation Is Difficult

Many finance teams reconcile Myntra sales and payments manually in Excel.

The usual process includes:

1. Exporting the sales report.
2. Downloading the Myntra payment report.
3. Cleaning order IDs, invoice numbers, SKUs, and payment references.
4. Matching sales with payment entries using lookup formulas.
5. Calculating expected fixed fee manually.
6. Comparing fixed fee with actual deduction.
7. Reviewing returns, refunds, taxes, and unmatched records.
8. Preparing an exception report.

This becomes difficult as transaction volumes increase.

Common Excel challenges include:

• Different reference formats
• Multiple fee and deduction columns
• Fixed fee charged at different levels
• Returns adjusted in later cycles
• One payment cycle covering many orders
• Duplicate fee lines missed
• Broken lookup 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 each payment cycle.

What a Good Myntra Fixed Fee Reconciliation Process Should Include

A reliable process should include:

• Complete sales report
• Complete payment report
• Order-level and invoice-level matching
• SKU-level visibility where required
• Fixed fee validation
• Commission and deduction review
• Return and refund visibility
• Tax and TDS comparison
• Net payment comparison
• Sales-only exception reporting
• Payment-only exception reporting
• Fixed fee mismatch reporting
• Duplicate detection
• Audit-ready output

The output should clearly show which orders matched, which fees were correct, which fee differences need review, and which payments are pending.

How Cointab Helps

Cointab can help finance teams automate Myntra sales vs payments fixed fee reconciliation by comparing sales data with payment data in a structured workflow.

Finance teams can map order references, invoice references, SKU fields, payment references, fixed fee fields, deduction fields, amount fields, and date fields once and reuse the setup for future periods.

Cointab helps teams:

• Upload sales and payment reports
• Match sales records with payment records
• Validate fixed fee deductions
• Compare sales, returns, refunds, deductions, taxes, and net payments
• Identify fully matched transactions
• Highlight fixed fee mismatches
• Show sales-only and payment-only exceptions
• Review unsupported deductions
• Detect duplicate orders, invoices, payments, and fee lines
• Download audit-ready Excel reports
• Reuse the workflow for recurring reconciliation

This reduces manual Excel work and gives finance teams better visibility into Myntra fee and payment differences.

Business Value

Myntra sales vs payments fixed fee reconciliation helps finance teams:

• Validate marketplace receivables
• Confirm fixed fee accuracy
• Identify missing payments
• Detect duplicate or excess fee deductions
• Review returns and refunds accurately
• Improve settlement accuracy
• Reduce marketplace disputes
• Support tax and audit review
• Speed up month-end close
• Reduce manual reconciliation work

It also helps marketplace operations, finance, and accounting teams resolve fee-related issues faster.

Best Practices

Finance teams should follow these best practices:

• Reconcile sales and payment reports for every settlement cycle
• Use order ID, invoice number, SKU, and payment reference wherever available
• Validate fixed fee separately from other deductions
• Review returns and refunds separately from normal sales
• Track timing differences separately from true mismatches
• Check duplicate order IDs, invoices, payment references, and fee lines
• Maintain period-wise reconciliation history
• Document manual corrections clearly
• Review fixed fee logic periodically

Conclusion

Myntra sales vs payments fixed fee reconciliation helps finance teams confirm whether sales, fixed fees, returns, refunds, deductions, taxes, payments, and receivables are properly aligned.

Because this reconciliation depends on sales records, payment records, order references, invoice references, SKU details, fixed fee logic, deductions, returns, and timing differences, manual Excel reconciliation can become slow and error-prone as transaction volumes grow.

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

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