Myntra Marketplace Reconciliation Using OMS

Myntra marketplace reconciliation often involves matching internal OMS records with multiple marketplace reports, settlement files, reversals, and tax-related exports. For finance teams, the challenge is not just finding whether numbers differ, but understanding why they differ and what needs review.

Cointab helps teams structure this work as a reusable reconciliation workflow. You can compare Side A records from your OMS or internal system with Side B records from Myntra, map the required fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped transactions in an audit-friendly report.

Why Myntra reconciliation is difficult to manage manually

Myntra-related reconciliations usually involve more than one report and more than one business question. Finance teams may need to compare sales, settlements, reversals, deductions, refunds, and tax-related data across different periods.

Common challenges include:

• Order and settlement files do not always follow the same structure as OMS exports.
• Fees, reversals, and deductions can change the final amount that appears in settlement files.
• Returns, cancellations, and exchanges create partial or netted transactions.
• Reference fields may appear in different formats across reports.
• Late or missed files can leave open items unresolved at month end.
• Manual Excel checks become repetitive and difficult to audit.

How Cointab structures Myntra reconciliation

Cointab uses a Side A and Side B model so finance teams can clearly define what they expect to match.

Side A: Your OMS or internal records

Side A is typically the business source of truth, such as:

• OMS exports
• Internal sales reports
• Order working files
• Ledger or receivables data
• Supporting enrichment files such as SKU or store mappings

Side B: Myntra marketplace records

Side B contains the external records received from Myntra, such as:

• Sales reports
• Settlement reports
• Reversal or refund reports
• GST or tax-related exports
• Non-order settlement files

What you can reconcile

A Myntra reconciliation setup can be used for several related workflows, depending on how your finance team works.

• OMS sales vs Myntra sales reports
• OMS orders vs Myntra settlement reports
• OMS data vs Myntra reversal or refund files
• Internal sales working vs Myntra tax or GST-related exports
• Net sales vs payout or settlement amounts
• Deductions, commissions, and fees vs internal working files

For standard partner formats, a reusable reconciliation template can reduce setup effort. For business-specific OMS layouts, a custom reconciliation gives you more flexibility in mapping fields and defining rules.

Typical fields used in the setup

To compare OMS and Myntra data reliably, teams usually map the key fields needed for matching.

Common identifiers

• Order ID
• Transaction ID
• Reference number
• Settlement ID
• Invoice number
• Return or reversal reference
• SKU or item reference

Common amount and date fields

• Transaction date
• Settlement date
• Gross amount
• Net amount
• Fee or deduction amount
• Refund amount

If a report contains inconsistent references, Cointab can also support derived columns and supporting data to clean, enrich, or standardize values before reconciliation.

Common mismatch scenarios in Myntra reconciliation

Once the files are mapped, the reconciliation engine can identify the transactions that need review.

Fully matched

These are records where the OMS and Myntra values align according to the selected rules.

Partially matched

These are records where the reference matches, but the amount differs. For example, an order may be present in both files, but the settlement amount is lower because of fees, deductions, or reversals.

Unmatched

These are records found on one side but not on the other. For example:

• An order appears in the OMS but not in the Myntra report.
• A settlement entry appears in Myntra but is missing from the OMS.
• A reversal or refund appears in one file but not the other.

Skipped

Skipped rows are records that were not included in the reconciliation because of missing required data, invalid values, duplicates, or file issues. Visible skipped rows help finance teams understand what was excluded and why.

How the reconciliation workflow works

A typical Myntra reconciliation in Cointab follows a simple finance workflow.

1. Upload the OMS file and the relevant Myntra reports.
2. Map the required fields such as date, amount, and identifiers.
3. Add supporting data if you need lookups, merging, or enrichment.
4. Create derived columns if the report needs cleaned identifiers or calculated amounts.
5. Run reconciliation manually or on a schedule.
6. Review the results in matched, partially matched, unmatched, and skipped sections.
7. Filter open items for deeper analysis.
8. Download the Excel reconciliation report for internal review or audit support.

If a file is received late, it can be uploaded under the same reconciliation and the report can be refreshed without rebuilding the setup.

AI support for open-item analysis

After structured matching is complete, remaining open transactions can be reviewed with AI assistance when deterministic rules are not enough.

This is useful for:

• Slightly different order references
• Inconsistent descriptions
• Missing identifiers
• Complex grouping scenarios
• Exceptions that need a business explanation

AI is used conservatively. If the match is not strong enough, the item remains open rather than being forced into a weak match.

Why finance teams use this approach

A structured Myntra reconciliation helps teams move away from repeated spreadsheet work and toward a controlled finance workflow.

Key advantages include:

• Less manual comparison across OMS and marketplace files
• Reusable setup for future periods
• Clear separation of matched, partially matched, unmatched, and skipped records
• Better visibility into fees, deductions, reversals, and settlement differences
• Audit-ready Excel reports for review and follow-up
• Shared workspace access for finance and marketplace operations teams

Reuse for recurring periods

Once the Myntra reconciliation is configured, the same setup can be reused for future periods. Teams can run monthly, quarterly, or custom-period reconciliations without rebuilding the workflow each time.

This is especially useful when your team handles recurring reports and wants a consistent process for review, exceptions, and reporting.

FAQ

What data can be used for Myntra reconciliation?

You can use OMS exports, Myntra sales files, settlement reports, reversal or refund files, and optional supporting data such as SKU, store, or mapping files.

Can Cointab reconcile different file formats from Myntra and OMS?

Yes. You can upload CSV, XLS, or XLSX files and map the required fields for each report. If a file does not match the configured structure, the system can reject it with a clear error.

How are differences handled?

Cointab separates fully matched, partially matched, unmatched, and skipped records so finance teams can focus on exceptions rather than reviewing every row manually.

Can the same reconciliation be reused for future periods?

Yes. Once configured, the reconciliation setup can be reused for future months or other reporting periods, which helps reduce repetitive setup work.

What if a report arrives late?

You can upload the missed file under the same reconciliation and refresh the report, which is useful when marketplace or settlement files arrive after the initial run.