Myntra Commission Fee Reconciliation Automation
Myntra commission fee reconciliation helps marketplace finance teams verify whether commission charges in settlement reports match the amount they expect from sales data, category rules, and brand-based fee logic. For sellers operating at scale, even small fee differences can create recurring exceptions across forward settlements and refund orders.
Cointab provides a structured reconciliation workflow for this use case. Finance teams can upload the relevant reports, map the fields once, calculate expected commission fees, and compare them against Myntra's reported values. The result is a clear view of correctly charged, overcharged, undercharged, and refund-related commission entries.
What this reconciliation checks
Myntra commission fee verification is usually about comparing two sides of the same financial event:
- Side A: the seller's internal records, such as sales data, order data, or expected fee logic
- Side B: Myntra's settlement and reversal reports, which show the commission actually charged or refunded
This helps teams review whether the marketplace has applied the right commission amount for each order and whether refund entries have been handled correctly.
In practice, this reconciliation can help finance teams review:
- commission charged on forward sales
- commission refunded on cancelled or returned orders
- category-based or brand-based fee differences
- exceptions where the reported fee does not match the expected fee
- missing or incomplete rows that need follow-up
How the workflow is set up in Cointab
Cointab is built to make repeat reconciliation work reusable. For a Myntra commission fee verification workflow, the setup usually follows these steps:
- Upload the seller's internal sales or order data on Side A.
- Upload Myntra settlement and reversal reports on Side B.
- Map key fields such as order ID, transaction date, amount, and commission fields.
- Add supporting data where needed, such as category mapping, brand mapping, product master data, or return reports.
- Create derived columns if expected commission needs to be calculated from business rules.
- Run the reconciliation manually or on a schedule.
- Review the report for matched, mismatched, and exception items.
- Download the audit-ready Excel output for finance review or follow-up.
This setup reduces the need to rebuild formulas or compare reports in spreadsheets every month.
Commission fee logic for forward settlements
For forward settlement reconciliation, Cointab compares the commission fee expected from the configured rules with the commission fee reported by Myntra.
A typical review includes:
- Total commission fee reported in Myntra settlement data
- Correctly charged commission fee where the expected and reported values match
- Overcharged commission fee where Myntra's reported fee is higher than expected
- Undercharged commission fee where the reported fee is lower than expected
This is especially useful when commission rates are not stored as a single fixed rate card and instead depend on product category, brand, or other business logic.
Commission fee logic for refund orders
Refund and reversal reports need separate treatment because the original commission may be refunded back to the seller when the order is returned or cancelled.
Cointab can reconcile these refund-side entries by comparing the expected commission reversal with the amount shown in Myntra's refund or reversal settlement data.
The output helps teams identify:
- commission refunded correctly
- commission over-refunded
- commission under-refunded
- orders that appear in one report but not in the other
For finance teams, this distinction matters because a refund-side mismatch can affect settlement accuracy, open items, and month-end review.
What the report shows
Once the reconciliation run is complete, Cointab presents the results in a structured dashboard and downloadable report. Teams can review totals and drill into transaction-level details.
Typical output categories include:
| Output category | What it means |
|---|---|
| Correctly charged | The expected commission and reported commission align |
| Overcharged | The reported commission is higher than expected |
| Undercharged | The reported commission is lower than expected |
| Refund correctly paid | The commission refund matches the expected reversal |
| Refund overpaid | Myntra refunded more commission than expected |
| Refund underpaid | Myntra refunded less commission than expected |
The same reconciliation view can also help teams identify partially matched, unmatched, or skipped records when a row cannot be processed cleanly or needs further review.
Why marketplace teams use this workflow
Commission fee verification is not just about finding differences. It also helps teams create a repeatable control process for marketplace accounting.
Common benefits include:
- fewer manual spreadsheet checks
- a consistent method for expected fee calculation
- faster review of commission exceptions
- clearer tracking of forward and refund-side differences
- reusable setup for monthly or periodic reconciliations
- audit-friendly output that finance teams can review internally
For businesses selling on Myntra alongside other marketplaces, the same reconciliation approach can also be extended to broader marketplace settlement reconciliation workflows.
Data that often supports the reconciliation
A commission fee workflow often uses more than one file. Supporting data can help the reconciliation engine calculate the expected fee more accurately and explain differences more clearly.
Useful supporting inputs may include:
- product master data
- category mapping files
- brand mapping files
- return or reversal reports
- order metadata
- fee rate files
- internal sales export files
These files are not always reconciled directly. In many cases, they are used to enrich the main dataset before reconciliation runs.
Derived columns and fee calculation
If the expected commission fee must be calculated from business logic, Cointab can create derived columns from uploaded data.
For example, the reconciliation can use calculated fields to:
- derive the expected commission amount
- normalize an order identifier
- clean reference fields
- isolate refund-specific amounts
- convert category or brand rules into a usable calculation field
This is helpful when finance users understand the logic but do not want to build complex formulas manually every time the reconciliation is run.
Reusable and automation-friendly by design
Once the Myntra commission fee workflow is configured, the same setup can be reused for future periods. Finance teams do not need to start from scratch each month.
Cointab also supports recurring reconciliation flows, so teams can automate data input and scheduled reconciliation runs where needed. That makes the workflow useful for daily, weekly, or monthly finance operations rather than a one-time file check.
FAQ
How does Cointab verify Myntra commission fees?
Cointab compares the expected commission fee from Side A records and supporting business rules with the commission fee shown in Myntra settlement or reversal reports on Side B. It then flags matching and non-matching entries.
Can the workflow handle refund orders?
Yes. Refund and reversal records can be reconciled separately so finance teams can review whether commission has been refunded correctly, over-refunded, or under-refunded.
What if Myntra report columns do not match the setup?
The file mapping step lets users map the required fields such as date, amount, and identifier columns. If a file does not match the configured format, the system can reject it with a clear error.
Can the same setup be reused for future periods?
Yes. Once configured, the reconciliation can be reused for future runs, which reduces repeat setup work and helps keep the process consistent over time.
Does this only work for commission fees?
No. The same reconciliation platform can be used for other marketplace, settlement, payment, vendor, and bank reconciliation workflows where finance teams need to compare Side A and Side B records.
