Myntra Shipping Fee Reconciliation with Cointab

Myntra shipping fee reconciliation is a recurring finance task for marketplace sellers who need to verify whether shipping, commission, pick and pack, payment gateway, and reversal-related charges were applied correctly. When order volumes rise, manual checks in Excel quickly become difficult to maintain, especially when the same fees must be reviewed across settlements, returns, cancellations, and adjusted payouts.

Cointab helps finance teams automate this reconciliation by matching the seller's internal records with Myntra's external reports, identifying discrepancies, and producing audit-ready outputs that are easier to review and share across the team.

Why Myntra shipping fee reconciliation is difficult to manage manually

Myntra fee verification is rarely just a single fee check. Finance teams often need to compare:

Internal order or sales data
Myntra settlement reports
Reversal or cancellation reports
Shipping fee or rate-card data
Payment references and payout details
Supporting files used for lookups and calculations

In a manual workflow, teams usually rely on formulas, lookups, and repeated spreadsheet comparisons. That creates several problems:

Fee logic is hard to audit when spreadsheets grow large
Different team members may prepare the analysis differently
Open exceptions can stay unresolved for too long
Missing reversals or deductions may be overlooked
The same reconciliation setup has to be rebuilt every period

Cointab replaces that manual process with a structured reconciliation workflow that can be reused for future runs.

How Cointab supports Myntra fee verification

Cointab uses a Side A and Side B model to keep the process clear:

Side A contains your internal records, such as order, sales, ledger, or working files
Side B contains Myntra reports and other external records that need to be checked against your books

This makes it easier to reconcile the business view of the transaction with the charges reported by the marketplace.

A typical Myntra shipping fee reconciliation setup can include:

Uploading the required reports on both sides
Mapping columns such as order ID, transaction reference, amount, date, or shipment identifier
Uploading supporting data for lookups or enrichment if needed
Creating derived columns when a field needs to be cleaned, normalized, or calculated
Running reconciliation manually or on a schedule
Reviewing matched, partially matched, unmatched, and skipped records
Downloading the Excel report for internal review or partner follow-up

What gets checked in a Myntra shipping fee reconciliation

A useful reconciliation does more than confirm the total fee charged. It helps teams understand exactly where the difference came from.

Common charge areas

Cointab can help teams review and compare records related to:

Shipping fee
Commission fee
Pick and pack fee
Payment gateway fee
Settlement deductions
Reversal or return-related charges
Expected fee versus actual charged fee

Common matching checks

The reconciliation engine can be configured to match on business identifiers and amounts such as:

Order ID
Transaction ID
Settlement ID
Reference number
Shipment or AWB number where relevant
Net amount or fee amount

If the identifiers match but the values do not, the record may be classified as partially matched so the finance team can review the difference.

Handling overcharged, undercharged, and correct fees

For many sellers, the main value of Myntra shipping fee reconciliation is not just finding unmatched records. It is understanding whether a charge was applied correctly.

Cointab helps separate transactions into clear categories:

Fully matched records where the expected and actual values align according to the configured logic
Partially matched records where the relationship is found, but the amounts differ
Unmatched records where no corresponding transaction is found on the other side
Skipped records that were excluded because required data was missing, invalid, or not usable

This structure makes fee review faster because teams can focus on exceptions instead of checking every row manually.

Supporting data and derived columns for marketplace fee checks

Myntra fee analysis often depends on more than the main settlement files. Supporting data can help enrich the primary records before reconciliation.

Examples of supporting data include:

Product or SKU mapping files
Rate cards
Order metadata
Return or cancellation files
Store or category mapping files
Fee calculation helpers

Cointab also supports derived columns. These are calculated fields created from existing data and can be used to normalize identifiers or calculate expected values. For example, a team may create a derived field for a cleaned order reference, a normalized shipping fee, or an amount after applying a business rule.

This is useful when the reconciliation logic depends on a field that is not present in the source file as-is.

Reusable workflow for recurring Myntra reconciliations

Most marketplace teams need the same review every month or every settlement cycle. Rebuilding the process from scratch is time-consuming and increases the chance of error.

With Cointab, the setup can be reused once it is defined. For future periods, teams can:

Select the existing reconciliation
Choose the relevant period
Upload the latest files, or use automated data input
Run reconciliation again
Review the refreshed report

This reusable workflow is especially useful for finance teams that handle repeated marketplace close processes and need consistent output across periods.

Automation for regular marketplace operations

Cointab is designed for recurring finance operations, not just one-time file uploads. Once the Myntra reconciliation is configured, the data flow can be automated through email, SFTP, or API-based input.

That means teams can set up a schedule for:

Daily reconciliation runs
Weekly or monthly reviews
End-of-day processing
Reconciliation after all required files are received

When the required data is available, Cointab can validate the format, load the files, run the reconciliation, and prepare the report automatically. Output can also be pushed back to internal systems through email, SFTP, or API.

Reviewing exceptions and open items

Not every difference should be treated the same way. Some are caused by missing files, some by timing differences, and others by business exceptions such as returns, refunds, or deductions.

Cointab helps teams review open items in a structured way. After the structured matching step, AI can assist with difficult cases by analyzing unresolved transactions and suggesting possible reasons for the difference.

If the evidence is not strong enough, the item can remain unmatched rather than forcing a weak match. That keeps the output conservative and easier to audit.

Manual match when business context matters

Some reconciliation items still need a human review. Cointab supports manual matching for exceptions that the system and AI cannot confidently resolve.

This is useful when:

A partner report arrives with incomplete identifiers
A one-off adjustment needs to be accounted for
The finance team has business context that is not visible in the file data
An item was partially matched and needs a different treatment

Manual matches remain visible in the report so the workflow stays traceable.

Audit-ready reporting for finance teams

Once reconciliation is complete, the report dashboard gives finance teams a clear view of the run, including summaries and transaction-level details.

Typical outputs include:

Total summary
Fully matched items
Partially matched items
Unmatched items
Skipped items
Filters for deeper analysis
Downloadable Excel report

This makes it easier for controllers, audit teams, and marketplace finance teams to review fee differences, prepare month-end files, and keep a record of what was matched and why.

When Myntra sellers typically use this workflow

This use case is most helpful when teams need to reconcile:

Myntra sales versus settlement amounts
Shipping fees against expected rate-card logic
Reversal settlements for returns or cancellations
Deductions across multiple fee types
Order-level charges across high-volume marketplace files

It is also useful for businesses that manage multiple marketplaces and want a repeatable reconciliation engine rather than separate spreadsheet processes for each platform.

FAQs

What data is needed for Myntra shipping fee reconciliation?

At minimum, teams usually need the internal order or sales file and the relevant Myntra settlement or fee report. Supporting files such as rate cards, returns, or mapping data can also be added when the fee logic depends on them.

Can Cointab handle both shipping fees and other marketplace deductions?

Yes. The reconciliation workflow can be used to compare shipping fees as well as other related charges such as commission, pick and pack, payment gateway, and reversal-linked deductions, depending on how the setup is configured.

What happens if a report was missed for the period?

The missed file can be uploaded into the same reconciliation and the report can be refreshed. This helps when a settlement, reversal, or supporting report arrives later than expected.

Can the same Myntra reconciliation setup be reused for future periods?

Yes. Once the workflow is configured, the same reconciliation can be reused for future runs by uploading the latest files or using automated data input.

How are exceptions shown in the report?

Cointab separates records into fully matched, partially matched, unmatched, and skipped categories so finance teams can focus on exceptions and review differences more efficiently.