Myntra Marketplace Reconciliation for Finance Teams

Myntra marketplace reconciliation helps finance teams compare internal sales records with Myntra reports, settlement files, and bank receipts. Instead of checking every order manually in Excel, teams can map fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped transactions in a structured report.

Why Myntra marketplace reconciliation matters

For marketplace sellers, the main challenge is not just confirming that an order was placed. Finance teams also need to verify what was invoiced, what was settled, what was deducted, and what actually reached the bank.

A Myntra reconciliation workflow typically helps teams track:

• Orders that were paid, canceled, returned, or exchanged
• Settlement amounts after fees, commissions, and adjustments
• Pending or short-paid transactions
• Settlement differences between the marketplace report and the bank statement
• Missing files or late reports that keep items open during close

This is where manual spreadsheet checks become difficult. Large report files, repeated monthly setup, and changing exception patterns can slow down close and make audit review harder.

Common Myntra reports used in reconciliation

Cointab can be set up with a popular reconciliation workflow for standard Myntra seller reports or a custom workflow if your finance process needs additional internal files.

How Cointab handles Myntra reconciliation

Cointab follows a structured workflow so finance teams can move from file upload to review without rebuilding the process every month.

1. Upload files and map fields

Users upload CSV, XLS, or XLSX files and map the required fields such as:

• Header row
• Date column
• Amount column
• Reference or identifier column

For Myntra workflows, identifiers may include order ID, invoice number, transaction reference, settlement ID, UTR, or other business keys.

2. Use a popular setup or build a custom one

If your reports follow a standard structure, Cointab can use a reusable popular reconciliation setup. If your process depends on internal logic, extra files, or custom matching rules, users can create a custom reconciliation.

In both cases, the goal is the same: upload your files, map fields once, and run reconciliation anytime.

3. Add supporting data when needed

Supporting data is useful when the core report needs enrichment before matching.

For example, a finance team may use supporting files to:

• Pull in missing order details
• Combine sales and returns data
• Add fee or tax lookups
• Normalize partner-specific identifiers into internal IDs
• Prepare the source data before matching

4. Create derived columns with AI assistance

If a reconciliation needs calculated fields, Cointab can help users build derived columns using AI-generated Excel-style formulas.

This is useful for fields such as:

• Clean order ID
• Net amount
• Delivered payment amount
• Refund amount as a negative value
• Combined reference key
• Normalized transaction ID

5. Run reconciliation and review progress

When the reconciliation starts, Cointab applies structured matching logic across the uploaded files. Users can see live progress while the run is in process.

The matching engine can support cases such as:

• One-to-one matching
• One-to-many or many-to-one matching
• Net-to-net comparison
• Partial matching
• Contra and cross-side matching

6. Review open items with AI assistance

After structured matching is complete, AI helps analyze remaining open transactions where simple rules are not enough.

This can help finance teams investigate:

• Slightly different descriptions
• Missing or partial identifiers
• Complex grouping situations
• Refunds, deductions, or settlement differences
• Possible reasons a file may be missing

If evidence is not strong enough, the item stays unmatched so the output remains audit-friendly.

7. Manually match exceptions when needed

Cointab also supports manual matching for cases where the user knows the business context but the system cannot confidently match the records.

This is useful when:

• A partner report is incomplete
• A one-off exception needs review
• Identifiers are missing
• The totals still tally, but the system needs human confirmation

8. Reuse the same setup for future periods

Once the Myntra reconciliation is configured, the same setup can be reused for future periods such as monthly, quarterly, yearly, or custom settlement periods.

That means finance teams do not need to rebuild the workflow every month. They can simply select the reconciliation, choose the period, upload the files, and run it again.

What the reconciliation report shows

Once the run is complete, users get a report dashboard that separates results clearly so finance teams can focus on exceptions instead of reviewing every row manually.

The report can show:

• Total summary
• Fully matched transactions
• Partially matched transactions
• Unmatched transactions
• Skipped transactions
• Transaction-level detail tables
• Filters for deeper review
• Downloadable Excel output

Fully matched

These are transactions where the identifiers and amounts match according to the configured logic.

Example: an internal order record matches a Myntra settlement entry by order ID and amount.

Partially matched

These are transactions where the records are related, but the amounts do not fully align.

Example: the order ID matches, but the invoice amount and settlement amount differ because of fees, deductions, returns, or other adjustments.

Unmatched

These are transactions that appear on one side but not the other.

For Myntra workflows, this may include:

• Orders in the internal file but missing in the settlement report
• Settlement records in the Myntra report but missing in internal books
• Bank receipts that do not map cleanly to the settlement file

Skipped

These are records that were not included in reconciliation because they were invalid, incomplete, excluded by rule, or otherwise unusable.

Showing skipped items is important because finance teams need to know what was ignored and why.

How this supports month-end close and audit readiness

Myntra reconciliation is not just about matching files. It is also about making the finance process easier to review, explain, and reuse.

Cointab helps teams by supporting:

• Audit-ready Excel reports
• Team workspaces with shared history
• Reconciliation history on the dashboard
• Reusable workflows for recurring monthly close
• Scheduled runs when files are received automatically
• Output delivery through email, SFTP, or API where automation is configured

For many finance teams, this means less spreadsheet dependency and a clearer view of what was matched, what was open, and what needs attention.

Practical outcomes for Myntra sellers

A well-structured Myntra reconciliation workflow helps finance teams:

• Verify sales, settlements, and bank receipts in one process
• Identify deductions, refunds, returns, and short payments faster
• Reduce repeated Excel work across monthly close cycles
• Keep a visible record of matched, unmatched, and skipped items
• Reuse the same reconciliation logic for future periods
• Maintain a cleaner audit trail for internal review

When to use a custom reconciliation setup

A custom setup is useful when your Myntra process includes additional internal files or business-specific matching logic.

Examples include:

• Internal sales report vs Myntra settlement plus bank statement
• Sales report vs settlement report with supporting return and fee files
• Marketplace settlement reconciliation with custom lookup data
• Finance workflows that combine Myntra with other marketplaces in a broader close process

In these cases, users can define the Side A and Side B files, map the required fields, add supporting data, and reuse the setup for future runs.

Reconciliation without rebuilding the same process every month

The main advantage of Cointab is reuse. Once the Myntra workflow is configured, finance teams can keep using the same setup for recurring periods instead of starting from scratch.

That makes it easier to manage marketplace reconciliation as part of daily finance operations, not just as a one-time spreadsheet exercise.