Myntra Marketplace Reconciliation Using ERP

Overview

Myntra marketplace reconciliation helps finance teams compare Myntra-side reports with ERP records to identify matched orders, settlement differences, missing entries, and unresolved exceptions. For brands selling through Myntra, this process is often part of sales reconciliation, settlement reconciliation, and month-end close.

With Cointab, the reconciliation can be set up as a reusable workflow where Myntra reports are loaded on one side and ERP exports are loaded on the other. The platform then applies structured matching logic to separate fully matched, partially matched, unmatched, and skipped transactions.

What gets reconciled

In this use case, Side A and Side B typically represent:

• Side A: Myntra marketplace records
• Side B: ERP records from the business system

Depending on the workflow, teams may reconcile one or more of the following data sets:

The exact files used depend on how the business records Myntra sales, settlements, deductions, reversals, and tax entries in its ERP.

Why Myntra reconciliation with ERP matters

Marketplace data and ERP data rarely line up perfectly without review. Common differences include:

• orders recorded in one system but missing in the other
• settlement amounts that do not match invoice values
• deductions such as fees, reversals, returns, or adjustments
• tax-related differences across reports
• duplicate or incomplete entries
• timing differences between marketplace reporting and ERP posting

Without a structured workflow, teams often handle these checks in Excel using VLOOKUPs, filters, and manual comparisons. That can make the process slow, repetitive, and difficult to audit.

Cointab helps finance teams standardize the reconciliation process so the same setup can be reused for each period.

How the reconciliation works

A typical Myntra marketplace reconciliation follows a simple workflow:

1. Upload Myntra reports and ERP exports.
2. Map required fields such as date, amount, and identifiers.
3. Add supporting files if needed for enrichment or lookups.
4. Create derived columns where a clean identifier or adjusted amount is needed.
5. Run reconciliation manually or on a schedule.
6. Review matched, partially matched, unmatched, and skipped records.
7. Export the reconciliation report for review, follow-up, or audit.

Cointab supports CSV, XLS, and XLSX files. If a file does not match the configured format, the system can reject it with a clear error so the team can correct the input before running the report.

Typical matching logic

Myntra reconciliation is not always a simple one-to-one match. A single marketplace settlement may relate to multiple order-level records, and one ERP posting may represent a grouped or netted value.

Cointab's reconciliation engine supports structured logic such as:

• one-to-one matching
• one-to-many matching
• many-to-one matching
• many-to-many matching
• net-to-net comparison
• partial matching
• contra matching

This is useful when comparing order IDs, invoice numbers, settlement IDs, UTRs, or other identifiers that may appear in different formats across reports.

What the report shows

After reconciliation, finance teams can review the output in a dashboard with clear status buckets.

Fully matched

These are records where the amount and matching logic align between Myntra data and ERP data.

Partially matched

These are records where the identifier matches, but the amount does not. This is useful for identifying deductions, rounding differences, returns, or posting issues.

Unmatched

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

• a Myntra order not recorded in ERP
• an ERP posting that cannot be found in Myntra reports
• a settlement line that has no corresponding entry in the business system

Skipped

These are rows excluded from reconciliation because of missing fields, invalid values, duplicates, or other file issues. Skipped records remain visible so the team understands what was not included and why.

Example reconciliation outcomes

A Myntra marketplace reconciliation using ERP data may help teams identify situations such as:

• a sales order recorded in Myntra but not posted in ERP
• settlement recorded in ERP at a lower amount than the Myntra report
• a reversal or deduction that explains a mismatch
• an invoice or ledger entry that appears in ERP but not in the marketplace report
• a file missing from the monthly workflow

These outcomes give finance teams a clear starting point for investigation instead of forcing them to manually review every transaction.

Using supporting data and derived columns

Some marketplace reconciliations need extra preparation before matching can begin. Cointab supports supporting data for enrichment and derived columns for calculated fields.

Supporting data can help teams:

• combine reports before reconciliation
• look up missing identifiers
• map marketplace codes to internal codes
• add fee, return, or tax-related context
• normalize references across systems

Derived columns can help with:

• cleaning order IDs
• calculating net amount
• creating normalized transaction references
• deriving payment or settlement values
• building match-ready fields from raw columns

Users can create derived columns using AI assistance by describing the logic in simple terms.

Reusable setup for recurring periods

This use case is usually repeated every month or settlement period. Cointab lets teams configure the reconciliation once and reuse it later.

That means future runs usually require only:

• selecting the saved reconciliation
• choosing the period
• uploading or receiving the required files
• running the reconciliation
• reviewing the output

The same setup can also be automated through email, SFTP, or API integrations, which is useful for recurring finance operations.

Manual review and exception handling

Not every exception should be auto-matched. Cointab keeps open items visible so finance teams can decide how to handle them.

Users can:

• inspect unmatched records
• analyze partially matched records
• review AI-assisted explanations for open items
• manually match transactions when the business context is clear
• refresh the report if a missed file is uploaded later

This keeps the process practical for finance teams while still maintaining control and auditability.

Why this matters for finance teams

Myntra marketplace reconciliation is not just a reporting exercise. It supports day-to-day finance operations such as:

• sales and settlement tracking
• period-end close
• receivables review
• fee and deduction analysis
• exception follow-up
• audit preparation
• internal reporting accuracy

By moving the workflow into a structured reconciliation platform, teams reduce spreadsheet dependency and create a clearer audit trail for each run.

Common questions finance teams ask

What if the ERP report and Myntra report use different identifiers?

Cointab allows users to map different reference fields, create derived columns, and use structured matching logic to reconcile across inconsistent formats.

Can multiple files be used in one reconciliation?

Yes. Users can upload multiple files on each side and add supporting datasets where needed.

Can the reconciliation be reused every month?

Yes. Once configured, the same reconciliation can be reused for future periods without rebuilding the setup from scratch.

Can the output be shared with other systems?

Cointab can optionally deliver reconciliation output through email, SFTP, or API so downstream teams can use the results in their own systems.

FAQ

Is this only for settlement reconciliation?

No. The workflow can cover sales, settlements, reversals, deductions, tax-related entries, and ERP postings depending on how the business records Myntra data.

Can this be used if the team still relies on Excel today?

Yes. Teams often begin with Excel-style reconciliation logic and then move it into Cointab for repeatable, structured matching and reporting.

What if a file is received late?

A missed file can be uploaded under the same reconciliation and the report can be refreshed so the latest data is included.

Does the platform show which rows were ignored?

Yes. Skipped records are shown separately so finance teams can see what was excluded and why.