Myntra Marketplace Reconciliation Using OMS

Myntra marketplace reconciliation becomes much easier when finance teams compare OMS records with marketplace reports in a structured workflow. Cointab helps teams match internal order data with external Myntra reports, identify settlement differences, review open items, and export audit-ready reconciliation reports.

For ecommerce and fashion businesses, this is usually not a single report check. It is a recurring process that may involve sales, settlements, payments, returns, reversals, deductions, and GST-related reports. Cointab organizes that work into a reusable reconciliation setup so teams do not have to rebuild the same Excel logic every month.

Why Myntra reconciliation becomes complex

Myntra data often arrives across multiple reports, and each report answers a different finance question. A team may need to reconcile:

• internal OMS sales data against Myntra order or sales reports
• settlement data against expected receivables
• payment or disbursement data against internal records
• reversal and cancellation entries against order status changes
• GST or tax-related reports against sales and settlement summaries
• non-order settlement items against the correct transaction group

When these files are checked manually in spreadsheets, the work becomes repetitive and difficult to audit. Different team members may use different formulas, files, and filtering logic. As transaction volumes grow, it becomes harder to identify missing orders, short settlements, duplicate entries, or partial matches.

How Cointab structures Myntra marketplace reconciliation

Cointab uses a Side A and Side B model.

Supporting data can also be added when needed. For example, teams may upload product master files, fee rate files, return reports, order metadata, or mapping files to enrich the primary data before reconciliation.

This structure makes the workflow clearer than a spreadsheet-based process because every file has a defined role. Finance teams can see what is being compared, what is being used only for lookup or enrichment, and what results were matched, partially matched, unmatched, or skipped.

Typical Myntra reports used in the workflow

A Myntra reconciliation workflow may use one or more of the following files:

• Myntra seller order detail report
• Myntra sales revenue report
• Myntra forward settlement report
• Myntra reversal settlement report
• Myntra GST return report
• Myntra non-order settlement report
• Internal OMS export or sales working file

The exact setup depends on how the business records orders internally and which Myntra reports are required for review.

Common reconciliation scenarios

Cointab can help finance teams review several types of mismatches in the same workflow.

Sales vs OMS

Teams can compare Myntra sales or order reports against OMS data to verify that internal order records and marketplace records are aligned.

Settlement vs expected receivables

Settlement reports can be checked against OMS or internal working files to identify short payments, missing settlements, or unexplained differences.

Reversal and cancellation analysis

When orders are canceled, exchanged, or reversed, the related entries can be compared against the OMS order status and value movement.

GST and tax-related review

If a team uses GST-related reports as part of its reconciliation process, Cointab can compare the relevant figures with internal order and settlement records for follow-up and reporting.

Missing or extra records

Cointab highlights records that appear on one side but not the other, helping teams identify:

• orders present in OMS but not in Myntra reports
• orders present in Myntra reports but missing in OMS
• settlements that do not map cleanly to internal records
• records with incomplete identifiers or invalid amounts

How the reconciliation workflow works

A typical workflow follows these steps:

1. The user starts a new reconciliation in the team workspace.
2. The user selects a popular reconciliation or creates a custom one.
3. Files are uploaded for Side A and Side B.
4. Required columns such as date, amount, and identifiers are mapped.
5. Supporting files are added if lookup or enrichment is needed.
6. Optional derived columns can be created using AI-assisted formula generation.
7. The reconciliation is run manually or on a schedule.
8. Cointab applies structured matching logic across the files.
9. Remaining open transactions are analyzed further with AI.
10. The user reviews the report dashboard and filters the results.
11. The Excel report can be downloaded for internal review, audit, or partner follow-up.

If a file was missed, the user can upload it under the same reconciliation and refresh the report. That is useful for real finance operations, where partner files often arrive late.

What the report shows

After the run completes, the report separates transactions into clear categories.

Fully matched

These are transactions where the relevant identifiers and amounts match according to the reconciliation rules.

Partially matched

These are transactions where the identifiers suggest a relationship, but the amounts do not fully match. This is useful for spotting deductions, fee differences, rounding issues, or other settlement variances.

Unmatched

These are records present on one side but not found on the other side. They often point to missing files, incomplete mappings, timing differences, or data quality issues.

Skipped

These are rows that were not included in the reconciliation because of missing data, invalid amounts, duplicates, or other file issues. Visibility into skipped rows helps finance teams understand exactly what was excluded.

Why this matters for finance teams

A Myntra reconciliation workflow is usually part of month-end close, settlement review, or ongoing marketplace control. Cointab helps teams make that work more consistent by providing:

• a reusable setup for repeated reconciliation runs
• structured matching logic instead of fragile spreadsheet formulas
• clearer exception handling for open items
• manual match support when business context is needed
• audit-friendly Excel exports for internal review
• a shared team workspace with roles, permissions, and history
• automation options through email, SFTP, or API for recurring workflows

This is especially useful for ecommerce teams managing multiple reports, multiple settlement cycles, or multiple partner files across the same month.

Reuse for recurring periods

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

That reuse matters because the underlying reconciliation logic, mapped fields, and supporting data often stay the same while only the period and files change.

Built for review, not blind matching

Cointab applies structured rules first and then uses AI to help analyze remaining open transactions. The goal is not to force weak matches. It is to help finance teams focus on transactions that genuinely need review.

That approach is important in marketplace reconciliation, where a sales order, settlement line, return, fee deduction, or GST-related record may need business context before it can be closed.

The final result is a clear reconciliation report that shows what matched, what did not match, and what needs attention next.