Myntra Fee Reconciliation for Finance Teams

Cointab helps Myntra sellers and finance teams reconcile marketplace fees against internal sales, order, and settlement data without rebuilding spreadsheets every month. Upload the relevant reports, map the fields once, run reconciliation, and review the fee differences in an audit-ready format.

Why Myntra fee reconciliation becomes difficult

Myntra fee reviews often involve more than one report and more than one charge type. Finance teams may need to compare internal sales data with settlement reports, reversal reports, and fee-related exports to understand what was charged, what was deducted, and what finally reached the bank.

Manual tracking in Excel can quickly become difficult when:

• Order volumes are high
• Fees are split across multiple charge types
• Returns, cancellations, and exchanges affect settlement amounts
• Different reports use different identifiers or file formats
• The same reconciliation logic has to be recreated for every period

Cointab replaces repeated spreadsheet work with a structured reconciliation workflow that keeps the process transparent and reusable.

What you can reconcile in a Myntra fee workflow

Cointab is flexible enough to compare any two sides of financial or operational data. For a Myntra fee workflow, that usually means reconciling your internal records on one side with Myntra reports on the other.

Side A: your records

Side A can include:

• Internal sales report
• Order report
• ERP or accounting export
• Ledger data
• Internal settlement working
• Returns or refund working

Side B: Myntra and related external records

Side B can include:

• Myntra settlement reports
• Reversal settlement reports
• Fee or charge reports
• Payment-related settlement data
• Bank statement extracts for settlement checking

Depending on the workflow, teams often review fee components such as:

• Fixed charges
• Shipping fees
• Commission fees
• Pick & pack fees
• Payment gateway fees

How the reconciliation workflow works

Cointab follows a simple workflow that finance users can reuse for each period.

1. Upload the required files for Side A and Side B.
2. Map the key fields such as date, amount, and identifiers.
3. Add supporting data if needed, such as product, return, or mapping files.
4. Create derived columns where a fee or identifier needs to be calculated or cleaned.
5. Run reconciliation manually or on a schedule.
6. Review matched, partially matched, unmatched, and skipped records.
7. Download the Excel report for review, follow-up, or audit support.

If required, Cointab can also handle automated data input through email, SFTP, or API so recurring Myntra fee checks do not depend on manual file collection every time.

Matching logic that finance teams can review

Cointab's reconciliation engine uses structured matching logic to compare records across both sides. This is useful when a fee line item does not match in a simple one-to-one way.

The engine supports:

• One-to-one matching
• One-to-many and many-to-one matching
• Many-to-many grouping
• Net-to-net comparison
• Contra matching
• Partial matching

For Myntra fee reconciliation, this matters when one settlement amount relates to several sales records, when fee deductions need to be netted, or when identifiers appear in different fields across reports.

What the report shows

Once reconciliation is complete, Cointab presents the results in a clear report dashboard.

The report typically includes:

• Total summary
• Fully matched records
• Partially matched records
• Unmatched records
• Skipped records
• Filters for deeper review
• Transaction-level details
• Downloadable Excel output

Fully matched records

These are records where the expected amount and the reported amount align according to the configured logic. This is useful for confirming that a fee line or settlement line has been applied as expected.

Partially matched records

These are records where identifiers match, but the amounts differ. For fee reconciliation, partial matches are especially useful because they often point to a charge difference that needs review.

Unmatched records

These are records present on one side but not found on the other. In a Myntra workflow, that may indicate a missing settlement line, a missing internal record, or a file that has not yet been received.

Skipped records

Skipped records are visible too, so finance teams can see what was excluded and why. That helps keep the reconciliation audit-friendly and prevents confusion about missing rows.

Supporting data and derived columns

Myntra fee review often needs more than a simple file-to-file comparison. Cointab supports optional supporting data to help prepare the primary reports before reconciliation.

Examples include:

• Product master files
• Return reports
• Marketplace mapping files
• SKU mapping files
• Customer or vendor master data
• Fee or rate lookup files

Users can also create derived columns when a field needs to be cleaned, combined, or calculated before matching. That is useful for:

• Normalizing order IDs
• Calculating net fee amounts
• Converting partner references into internal references
• Creating lookup fields for matching
• Building amount fields from multiple inputs

AI can help generate Excel-style formulas for these derived columns, which reduces manual formula writing while keeping the logic reviewable.

Handling exceptions and open items

Not every record will match automatically. Cointab helps finance teams focus on exceptions instead of reviewing the full file row by row.

Open-item analysis can help identify:

• Whether a file may be missing
• Whether a refund or return may explain the difference
• Whether the amount difference looks like a fee deduction
• Whether the record should be reviewed manually
• Whether the partner or internal team needs follow-up

If deterministic rules and AI do not produce a confident match, the transaction can remain unmatched. That keeps the workflow conservative and audit-friendly.

Manual match when business context is needed

Some fee differences are best handled by the finance team directly. Cointab includes manual match options for transactions that cannot be matched automatically.

This is useful when:

• The partner report is incomplete
• An identifier is missing
• A one-off exception needs review
• The user knows the business context behind the difference

Manual matches remain clearly marked, so the history of the reconciliation stays visible.

Reuse the same setup for future periods

A major advantage of Cointab is reuse. Once a Myntra fee workflow is configured, the same setup can be used again for future periods instead of recreating the workbook every month.

Finance teams can typically:

• Select the reconciliation
• Choose the period
• Upload the new reports
• Run reconciliation
• Review the report

That makes monthly, quarterly, or custom-period fee reviews easier to manage and more consistent across team members.

Useful for audit-ready finance operations

For finance teams, the value is not only in finding differences. It is also in having a clear, repeatable process that supports month-end close, partner follow-up, and audit review.

Cointab helps teams keep:

• A clear record of what was reconciled
• Visibility into what matched and what did not
• Downloadable Excel reports for review
• A shared workspace for team collaboration
• A history of reconciliation runs for future reference

For Myntra fee reconciliation, that means the team can move beyond manual charge checking and use a structured workflow that is easier to review, explain, and repeat.