Myntra Marketplace Reconciliation Using ERP

For marketplace teams, Myntra reconciliation is more than matching sales to settlements. Finance teams often need to compare order data, payouts, deductions, returns, refunds, fees, and tax-related entries from Myntra against ERP records and internal working files. Cointab provides a structured reconciliation workflow that helps teams upload both sides, map fields once, run reconciliation, and review audit-ready results.

Why Myntra reconciliation becomes complex

Myntra data usually arrives in multiple reports, and each report may serve a different purpose. Finance teams may need to match:

• order-level sales data
• settlement and payout data
• reversal or return data
• fee and deduction lines
• tax-related summaries
• internal ERP or ledger entries

When these records are reconciled manually in spreadsheets, the process can become slow and repetitive. Teams may spend time cleaning files, adjusting formulas, tracing missing references, and checking why a settlement does not match the books. Small differences can also remain open for too long if the review process is not structured.

How Cointab handles Myntra and ERP data

Cointab uses a Side A and Side B model for reconciliation.

• Side A contains your internal records, such as ERP exports, sales working files, ledger data, or internal order reports.
• Side B contains external records from Myntra, such as order reports, sales revenue reports, settlement reports, reversal reports, or tax-related files.

The workflow is designed to be reusable. Once the reconciliation is configured, finance teams can use the same setup for future periods instead of rebuilding the logic every month.

File upload and field mapping

Users can upload CSV, XLS, or XLSX files and map key fields such as:

• transaction date
• amount
• order ID
• settlement ID
• invoice number
• reference or identifier columns

If needed, users can upload multiple files under the same reconciliation and add supporting data for lookup, merging, enrichment, or calculation. Supporting data is especially useful when internal and external reports use different reference formats.

Derived columns for cleaner matching

If a field needs to be normalized before reconciliation, users can create derived columns using AI-assisted formulas. This is useful for tasks such as:

• cleaning order references
• normalizing identifiers
• calculating net amounts
• creating adjusted settlement values
• combining multiple reference fields

Derived columns are recalculated each time reconciliation runs, which helps keep the workflow repeatable.

Typical Myntra reports used in reconciliation

A Myntra reconciliation workflow may include one or more of the following report types:

• Myntra order detail reports
• Myntra sales revenue reports
• Myntra settlement reports
• Myntra reversal or return reports
• Myntra TCS-related reports
• Myntra non-order settlement reports
• ERP sales, ledger, or booking exports

The exact combination depends on how the finance team manages sales recognition, settlement tracking, deductions, and tax review.

What teams usually reconcile

Myntra reconciliation is often used to answer practical finance questions such as:

• Which orders were sold, settled, refunded, or reversed?
• Are settlement amounts matching the ERP records?
• Are there deductions, fees, or reversals that need review?
• Are any transactions present in ERP but missing in Myntra reports?
• Are any Myntra entries not reflected in the books?
• Do partial differences point to a fee, return, tax, or timing issue?

Cointab helps separate these cases clearly so finance teams can focus on exceptions instead of reviewing every row manually.

How the reconciliation workflow runs

A typical Myntra reconciliation setup follows these steps:

1. Create a new reconciliation in the workspace.
2. Choose a popular reconciliation where applicable, or create a custom workflow for your ERP-based process.
3. Upload the required files for Side A and Side B.
4. Map key fields such as date, amount, and identifiers.
5. Add supporting files if lookup or enrichment is required.
6. Create derived columns if a value needs to be cleaned or calculated.
7. Run reconciliation manually or on a schedule.
8. Review the report once processing is complete.
9. Drill into matched, partially matched, unmatched, and skipped records.
10. Download the Excel report for review, audit, or follow-up.

The system shows live progress while reconciliation is running, which helps users know the job is in progress rather than stuck.

How Cointab classifies transaction results

Cointab separates results into clear reconciliation categories.

Fully matched

These are records where the identifiers and amounts align according to the configured matching logic.

Partially matched

These are records where the identifiers match, but the amounts differ. Partial matches are useful for spotting deductions, adjustments, returns, or settlement differences that need review.

Unmatched

These are records found on one side but not the other. For example, a sales entry may exist in the ERP but not appear in the Myntra report, or a Myntra settlement entry may not yet be reflected in the books.

Skipped

Skipped records are rows that were not included in reconciliation because of missing data, invalid values, exclusions, or file issues. Keeping skipped rows visible helps finance teams understand what was left out and why.

AI-assisted analysis for open items

After structured matching is complete, Cointab can use AI to analyze remaining open items where rules alone are not enough. This can help finance teams review:

• slightly different descriptions
• incomplete references
• unstructured partner data
• complex grouping scenarios
• exceptions that need human review

AI support is conservative and audit-friendly. If evidence is not strong enough, the item remains unmatched rather than being forced into a weak match.

Manual match and missed files

Some transactions need manual review because the business context is clear even when the data is incomplete. Cointab supports manual matching for those cases, and users can undo manual matches if needed.

If a file was missed during the first run, it can be uploaded under the same reconciliation and the report can be refreshed. This is useful in real finance operations, where marketplace or bank files may arrive later than expected.

Automation for recurring Myntra workflows

Once the reconciliation is set up, teams can automate recurring runs using email, SFTP, or API-based data flow where configured. That means the workflow does not need to rely on manual uploads every time.

Automated runs are useful for:

• daily or weekly settlement checks
• month-end close support
• ongoing exception monitoring
• multi-source marketplace finance operations
• output delivery to internal systems after reconciliation is complete

Cointab can also push reconciliation output back to downstream systems through email, SFTP, or API so finance teams can keep accounting, reporting, or analytics workflows updated.

Why finance teams use this workflow

A Myntra marketplace reconciliation workflow is valuable because it helps teams:

• reduce manual spreadsheet work
• standardize how settlements and exceptions are reviewed
• reuse the same setup for future periods
• keep matched, partial, unmatched, and skipped records visible
• support audit review with downloadable Excel reports
• maintain a shared workspace with roles and visibility into who ran each reconciliation
• automate recurring data collection and reconciliation runs where required

Common reporting outcomes

A clear Myntra reconciliation report helps finance users answer the questions that matter most during review:

• What matched fully?
• What matched only partially?
• What is still open?
• Which records were skipped?
• Which differences are likely caused by timing, deductions, returns, or missing files?
• What needs manual review before close or audit?

By keeping the workflow structured and reusable, Cointab helps teams manage Myntra reconciliation with more control and less spreadsheet dependency.

Frequently asked questions

Can Myntra reconciliation be reused for future periods?

Yes. Once the workflow is configured, the same reconciliation setup can be reused for future runs by selecting the period, uploading the relevant files, and running reconciliation again.

What if the Myntra and ERP files use different column names?

Users can map the required fields during setup. If needed, supporting files and derived columns can help normalize data before reconciliation.

Does the report show partial differences and skipped rows?

Yes. Cointab separates fully matched, partially matched, unmatched, and skipped records so finance teams can review exceptions clearly.

Can the workflow be automated for recurring runs?

Yes. Where configured, Cointab supports automated data input and scheduled reconciliation runs through email, SFTP, or API-based workflows.

Is the reconciliation limited to sales only?

No. Myntra workflows can be used for sales, settlements, reversals, deductions, returns, tax-related data, and other finance review processes where two sides of data need to be compared.