Myntra Fee Reconciliation
Myntra sellers often need to verify whether marketplace deductions, settlement amounts, and order-level fees match what was expected from their internal sales records and rate cards. When this review is done in Excel, the work can become repetitive, difficult to audit, and hard to scale across large order volumes.
Cointab helps finance teams run Myntra fee reconciliation in a structured workflow. Users upload the relevant reports, map the required fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped transactions in a clear report view.
What Myntra fee reconciliation helps verify
Myntra fee verification is usually about comparing internal order or sales data with marketplace settlement and deduction reports. Cointab helps teams compare the two sides and identify where the expected amount and the actual charge do not align.
Typical items reviewed in this workflow include:
- Fixed or platform-related fees
- Shipping or logistics deductions
- Commission charges
- Pick and pack charges
- Payment gateway-related fees
- Settlement amounts
- Refunds, reversals, and other deductions
The goal is not only to see the total fee, but to understand which orders are driving the difference and why.
How Cointab structures the reconciliation
Cointab uses a Side A / Side B model so finance teams can keep the workflow transparent.
Side A: your records
Side A usually contains the records your business expects to be correct, such as:
- Internal sales report
- Order report
- ERP export
- Ledger or accounting data
- Internal settlement working
- Rate card or expected fee calculation file
Side B: external records
Side B usually contains the records received from Myntra, such as:
- Settlement report
- Fee or deduction report
- Reversal report
- Refund-related report
- Other marketplace-generated files used to explain charges
If needed, teams can also upload supporting data such as product master files, mapping files, return reports, or other reference data to enrich the primary reconciliation.
Reusable setup for recurring marketplace reviews
Myntra fee reconciliation is rarely a one-time activity. Finance teams usually review the same fee categories every month, every settlement cycle, or for every reporting period.
Cointab is built for reuse. Once the reconciliation is configured, teams do not need to rebuild the workflow each time. They can simply:
- Select the reconciliation
- Choose the period
- Upload the files or receive them through automation
- Run reconciliation
- Review the report
This reduces repeat setup work and makes the process more consistent across periods.
What gets mapped in the workflow
For a fee verification use case, users typically map fields such as:
- Order ID or reference number
- Transaction or settlement identifier
- Date
- Amount
- Fee category
- Return or reversal reference
- Any partner-specific identifier needed to connect records
If a report format changes, Cointab can reject the file with a clear error so the issue is visible before reconciliation begins.
Where supporting data helps
Supporting data is useful when the marketplace report alone is not enough to explain a fee difference. It can be used to enrich, merge, or calculate values before reconciliation.
Examples include:
- Product master files
- Marketplace mapping files
- Return reports
- Order metadata
- GST or tax mapping files
- Customer or vendor master data
- Reference files used for VLOOKUP-style enrichment
This is especially helpful when a fee needs to be checked against order context, category, fulfillment type, or a derived net amount.
Derived columns and fee calculations
Cointab supports derived columns on both sides of the reconciliation. These are calculated columns based on existing data, and they can be created with AI assistance.
For Myntra fee verification, derived columns can help users:
- Clean order references
- Normalize identifiers
- Calculate expected fee amounts
- Derive net sales values
- Convert refunds to negative values
- Create lookup fields for matching
This makes it easier to compare what should have been charged against what was actually charged.
How matching works for fee discrepancies
Cointab's reconciliation engine applies structured matching logic before any remaining open items are analyzed further.
The system supports matching patterns such as:
- One-to-one matches
- One-to-many matches
- Many-to-one matches
- Many-to-many matches
- Net-to-net comparisons
- Partial matching
- Contra-style matching where applicable
This matters in marketplace finance because a single settlement line may relate to multiple order lines, or a single order may be represented across several deduction entries.
How the report helps finance teams
Once reconciliation is complete, users can review a report dashboard that clearly separates records into categories such as:
- Fully matched
- Partially matched
- Unmatched
- Skipped
For fee verification, partially matched items are often the most important because they show that the order or settlement reference is related, but the amount needs review. Unmatched items highlight records that appear only on one side. Skipped items show records that were not included because of missing data or a file issue.
Users can filter the report, inspect transaction-level details, and download an Excel report for internal review, partner follow-up, or audit support.
Why fee verification becomes easier with automation
Manual spreadsheet checks are difficult to maintain when the number of orders, returns, and deductions grows. Cointab helps reduce this effort by making the workflow repeatable and reviewable.
Benefits for finance teams include:
- Less manual checking across large files
- More consistent fee reviews across periods
- Clear exception tracking instead of broad spreadsheet comparisons
- Better visibility into where differences originate
- Faster month-end and settlement close processes
- Audit-ready output for internal review and external follow-up
Handling missing files and late reports
In real finance operations, a report may arrive late or be missed in the initial run. Cointab supports uploading a missed file under the same reconciliation and refreshing the report.
This is useful when settlement-related data or partner reports arrive after the first reconciliation run and the finance team needs to update the output without recreating the setup.
Manual review for unresolved items
Some fee differences cannot be resolved automatically. Cointab includes a manual match option for cases where the finance team has business context that is not obvious from the data alone.
Manual review is useful when:
- A fee is tied to a one-off adjustment
- A partner report is incomplete
- Identifiers are missing or inconsistent
- An open item needs human review before closure
Manual matches remain auditable and can be undone if needed.
Automation for recurring reconciliation cycles
Once the Myntra fee reconciliation is configured, teams can automate data flow through email, SFTP, or API integrations. That allows files to be received or pulled on a schedule, validated, loaded into the workflow, and reconciled without repeated manual uploads.
Cointab can also deliver the output back to other systems through email, SFTP, or API so downstream finance, reporting, or analytics workflows stay updated.
A practical fit for marketplace finance teams
Myntra fee verification is a good fit for teams that need to compare internal sales records against marketplace settlements, deductions, and reversal data. It is especially useful when the same reconciliation needs to be repeated across periods and reviewed by multiple people in a shared workspace.
With Cointab, finance teams can keep the setup structured, the logic visible, and the reporting ready for operational review.
