Sales Revenue and Return Reports vs Myntra Payment Reconciliation: A Complete Guide for Finance Teams

Sales revenue and return reports vs Myntra payment reconciliation is the process of comparing internal sales, return, and RTO records with the payment report received from Myntra.

For brands selling on Myntra, internal reports may show sales revenue, return transactions, RTO transactions, invoices, credit notes, GST values, and expected receivables. Myntra’s payment report shows what has been settled after applying marketplace deductions, commissions, fixed fees, logistics charges, return adjustments, refund adjustments, TDS, TCS, GST on fees, penalties, and other recoveries.

This reconciliation helps finance teams answer:

• Are all Myntra sales recorded internally available in the Myntra payment report?
• Are all Myntra payment entries supported by valid sales, return, or RTO records?
• Are returns and RTOs adjusted correctly against sales and payments?
• Do sales value, tax value, deduction value, and net payment value match?
• Are commissions, fixed fees, logistics charges, tax 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, return validation, GST review, payment control, month-end close, and audit readiness.

What Is Sales vs Myntra Payment Reconciliation?

Sales vs Myntra payment reconciliation compares internal sales and return-side records with Myntra’s payment-side records.

Side A: Sales Revenue, Return, and RTO Reports
This represents the internal business view. It may include sales revenue, invoices, order IDs, SKUs, taxable value, GST, returns, RTO entries, credit notes, refund values, and expected receivables.

Side B: Myntra Payment Report
This represents the marketplace settlement view. It may include order references, settlement references, gross sale value, return adjustments, refund adjustments, commission, fixed fee, logistics charges, GST on fees, TDS, TCS, penalties, recoveries, and net payable amount.

The goal is to confirm whether every valid sale, return, and RTO recorded internally is correctly reflected in Myntra’s payment report.

Matching is usually based on:

• Myntra order ID
• Internal order ID
• Invoice number
• SKU or item code
• Return reference
• RTO reference
• Credit note number
• Settlement reference
• Payment reference
• Gross sale amount
• Return amount
• RTO amount
• GST amount
• Deduction amount
• Net payment amount
• Order date
• Return date
• Settlement date

If the order reference, sale value, return value, RTO status, deduction logic, and payment amount match across both sides, the transaction can be treated as reconciled. If the reference matches but the amount differs, it becomes an exception. If a record appears only on one side, it becomes unmatched.

Why This Reconciliation Matters

Marketplace payments rarely equal gross sales. Myntra may deduct commissions, fixed fees, logistics charges, taxes on fees, TDS, TCS, return charges, penalties, claims, promotional recoveries, or previous-period adjustments before settlement.

At the same time, internal sales reports may record the original sale, while return and RTO reports may record reductions separately. If finance teams reconcile only sales against payments, they may miss return-related adjustments or incorrectly treat valid deductions as mismatches.

Without reconciliation, finance teams may face issues such as:

• Sales recorded internally but not paid by Myntra
• Payment entries without matching sales records
• Returns adjusted by Myntra but missing internally
• RTO entries recorded internally but not adjusted in payment
• Credit notes not mapped correctly
• Excess or unsupported deductions
• Net payment not matching expected receivable
• Duplicate orders, returns, or payment entries
• GST and tax reporting differences
• Month-end close delays and audit queries

A structured reconciliation process helps finance teams validate sales, returns, RTOs, deductions, and payments before closing marketplace receivables.

Reports Involved

Side A: Sales Revenue Report

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

Common fields may include:

• Myntra order ID
• Internal order ID
• Invoice number
• Invoice date
• SKU or item code
• Product description
• Quantity
• Gross sale value
• Discount amount
• Taxable value
• GST amount
• Net sale value
• Customer or marketplace name
• Expected receivable

This report shows what the business has recorded as valid marketplace sales.

Side A: GSTR Return Report

The GSTR return report represents sales returns or customer return transactions recorded internally.

Common fields may include:

• Original order ID
• Original invoice number
• Return reference
• Credit note number
• Return date
• Returned SKU
• Return quantity
• Return taxable value
• GST reversal amount
• Return value
• Return reason
• Return status

This report helps finance teams validate whether Myntra has adjusted returns correctly in the payment report.

Side A: GSTR RTO Report

The GSTR RTO report represents return-to-origin transactions or failed delivery returns recorded internally.

Common fields may include:

• Original order ID
• Invoice number
• RTO reference
• AWB or shipment reference
• RTO date
• SKU or item code
• RTO quantity
• RTO value
• GST reversal amount
• Delivery or return status
• Expected adjustment amount

This report helps finance teams identify orders that should not be treated as collectible sales because they were returned to origin.

Side B: Myntra Payment Report

The Myntra payment report represents the marketplace payment and settlement-side view.

Common fields may include:

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

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

How Matching Typically Works

Sales revenue and return reports vs Myntra payment reconciliation usually works by comparing internal order-level sales, return, and RTO records with Myntra payment-side settlement values.

A typical process looks like this:

1. The sales revenue report is uploaded.
2. The GSTR return report is uploaded.
3. The GSTR RTO report is uploaded.
4. The Myntra payment report is uploaded.
5. Order IDs, invoice numbers, SKUs, return references, RTO references, and payment references are mapped.
6. Valid sales are matched against Myntra payment entries.
7. Returns and RTOs are matched against payment-side return or refund adjustments.
8. Commissions, fixed fees, logistics charges, taxes, penalties, and recoveries are reviewed.
9. Net payment is compared with expected receivable after valid adjustments.
10. Records are categorized as matched, partially matched, unmatched, or skipped.

For example:

• The sales revenue report shows a Myntra order of ₹3,500.
• Myntra payment report shows the same order with gross sale value of ₹3,500.
• Myntra deducts commission, fixed fee, and taxes on fees before settlement.
• If the deductions are valid and the net payment calculation is correct, the transaction is reconciled.

Another example:

• The GSTR return report shows a return against an order worth ₹1,200.
• Myntra payment report shows a return adjustment of ₹1,200 against the same order.
• The return adjustment is treated as matched.

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

If a Myntra payment entry exists but no sales, return, or RTO record is found internally, it becomes a payment-only exception.

Common Exceptions in Sales vs Myntra Payment Reconciliation

1. Sale Missing in Myntra Payment Report

This happens when the sales revenue report contains a valid Myntra sale, but the Myntra payment report does not show a matching payment or settlement entry.

Possible reasons include:

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

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

2. Myntra Payment Entry Missing in Sales Report

This happens when the Myntra payment report contains an entry, but no matching sale is found in the internal sales revenue report.

Possible reasons include:

• Sales report is incomplete
• Payment belongs to a prior-period order
• Entry is an adjustment, recovery, or correction
• Order reference is stored differently internally
• Wrong marketplace account was selected
• Payment entry relates to return or RTO adjustment instead of fresh sale

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

3. Return Adjustment Missing in Myntra Payment Report

This happens when the internal return report shows a completed return, but the Myntra payment report does not show a matching return or refund adjustment.

Possible reasons include:

• Return adjustment is pending
• Return was recorded after the payment cutoff
• Return reference is not available in the payment report
• Credit note was not linked correctly
• Return was adjusted in another settlement cycle
• Return status differs between internal records and Myntra

This exception affects receivable accuracy because returns reduce the expected payment.

4. Myntra Return Adjustment Missing Internally

This happens when Myntra applies a return or refund adjustment, but the internal return report does not show a matching return.

Possible reasons include:

• Return was not updated internally
• Return report is incomplete
• Return belongs to a previous period
• Myntra adjustment relates to an older order
• Return was handled manually
• Wrong return report was uploaded

These cases should be reviewed before accepting the deduction.

5. RTO Difference

RTO differences occur when return-to-origin status is not aligned between internal records and Myntra payment records.

Common issues include:

• Internal report shows RTO but Myntra does not adjust payment
• Myntra adjusts payment for RTO but internal report does not show RTO
• RTO posted in a later period
• Shipment status differs across systems
• RTO value does not match the original order value
• GST reversal for RTO is missing

RTO differences should be reviewed separately from normal customer returns because they may impact sales recognition and receivable closure.

6. Amount Mismatch

Amount mismatches occur when the order reference matches, but values differ across reports.

Possible causes include:

• Sale value difference
• Tax amount difference
• SKU quantity difference
• Partial return
• RTO adjustment
• Commission or fixed fee difference
• Logistics deduction
• Rounding difference
• Wrong amount field selected

Amount mismatches affect settlement accuracy and marketplace receivable reporting.

7. Commission or Fixed Fee Difference

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

Possible issues include:

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

These differences should be supported by Myntra’s payment logic before being accepted in the books.

8. Tax, TDS, or TCS Difference

Marketplace payment reports often include statutory or tax-related deductions.

Possible issues include:

• TDS not recorded internally
• TCS mismatch
• GST on commission or fee not mapped correctly
• Tax reversal missing for return or RTO
• Tax amount differs due to discount or return logic
• Tax posted in another period

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

9. Settlement Timing Difference

Sales, returns, RTOs, and payments may appear in different periods.

Possible reasons include:

• Order invoiced in one month but settled in the next
• Return recorded in one period but adjusted later
• RTO recorded internally before marketplace adjustment
• Myntra payment cycle differs from internal reporting period
• Previous-period adjustment included in current payment
• Bank credit received after settlement date

Timing differences should be tracked separately from true mismatches.

10. Unsupported Deduction or Recovery

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

Possible causes include:

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

Unsupported deductions should be reviewed before being posted or accepted.

Why Manual Excel Reconciliation Is Difficult

Many finance teams reconcile sales, returns, RTOs, and Myntra payment reports manually in Excel.

The usual process includes:

1. Exporting the sales revenue report.
2. Exporting return and RTO reports.
3. Downloading the Myntra payment report.
4. Cleaning order IDs, invoice numbers, SKUs, return references, and settlement references.
5. Matching sales with payment entries.
6. Matching returns and RTOs with payment-side adjustments.
7. Comparing sale values, return values, RTO values, deductions, taxes, and net payments.
8. Preparing exception reports.

This becomes difficult as order, return, and payment volumes increase.

Common Excel challenges include:

• Different order ID formats
• Separate sales, return, and RTO files
• Returns adjusted in later payment cycles
• RTO status changes after shipment updates
• Multiple deductions under one order
• One settlement covering many transactions
• SKU-level and invoice-level differences
• Duplicate records 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 payment cycle.

What a Good Sales vs Myntra Payment Reconciliation Process Should Include

A reliable process should include:

• Complete sales revenue report
• Complete return report
• Complete RTO report
• Complete Myntra payment report
• Order-level matching
• Invoice-level matching
• SKU-level visibility where required
• Return and credit note matching
• RTO adjustment matching
• Commission and fixed fee review
• Tax, TDS, and TCS comparison
• Net payment validation
• Sales-only exception reporting
• Return-only exception reporting
• RTO-only exception reporting
• Payment-only exception reporting
• Amount mismatch reporting
• Duplicate detection
• Audit-ready output

The output should clearly show which sales matched, which returns were adjusted, which RTO cases were settled correctly, and which records need follow-up.

How Cointab Helps

Cointab can help finance teams automate sales revenue and return reports vs Myntra payment reconciliation by comparing internal sales, return, and RTO data with Myntra payment data in a structured workflow.

Finance teams can map order references, invoice numbers, SKU fields, return references, RTO references, credit note references, payment references, deduction fields, tax fields, amount fields, and date fields once and reuse the setup for future periods.

Cointab helps teams:

• Upload sales revenue, return, RTO, and Myntra payment reports
• Match sales with Myntra payment entries
• Match returns and RTOs with marketplace adjustments
• Compare sale values, return values, RTO values, deductions, taxes, and net payments
• Identify fully matched transactions
• Highlight amount mismatches and deduction differences
• Show sales-only, return-only, RTO-only, and payment-only exceptions
• Review unsupported deductions and recoveries
• Detect duplicate orders, returns, invoices, and payment 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 marketplace receivables.

Business Value

Sales revenue and return reports vs Myntra payment reconciliation helps finance teams:

• Validate Myntra marketplace receivables
• Track orders pending payment
• Confirm return and RTO adjustments
• Identify unsupported deductions
• Detect duplicate payment or return 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 sales, returns, RTOs, and payments for every settlement cycle
• Use Myntra order ID, invoice number, SKU, return reference, RTO reference, and payment reference wherever available
• Review sales, returns, and RTOs separately before validating net settlement
• Track return and RTO adjustments against payment-side deductions
• Validate commission and fixed fees separately from other deductions
• Track timing differences separately from true mismatches
• Check duplicate orders, invoices, returns, RTOs, and payment references
• Maintain period-wise reconciliation history
• Document manual corrections clearly

Conclusion

Sales revenue and return reports vs Myntra payment reconciliation helps finance teams confirm whether marketplace sales, returns, RTOs, credit notes, deductions, taxes, payments, and receivables are properly aligned.

Because this reconciliation depends on sales records, return records, RTO records, payment records, invoice references, SKU details, deductions, tax fields, and settlement timing, manual Excel reconciliation can become slow and error-prone as transaction volumes grow.

With Cointab, finance teams can automate sales revenue and return reports vs Myntra payment 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 sales vs Myntra payment reconciliation without relying on manual Excel work. No credit card required.

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