Myntra Pick and Pack Fee Verification

If your team reviews Myntra charges as part of marketplace finance operations, a structured reconciliation workflow helps verify pick and pack fees against the expected rate card, identify differences, and keep settlement reviews audit-ready. Instead of checking every order manually in Excel, you can upload the relevant reports, map the fee logic once, and compare reported charges with calculated amounts.

What Myntra pick and pack fee verification covers

Myntra pick and pack fees are typically reviewed as part of marketplace settlement and fee verification work. Finance teams often need to confirm whether the fee charged for each order matches the expected rate based on the configured level, shipping category, or seller rules used in the working file.

A fee verification workflow helps teams:

• compare the fee reported by Myntra with the fee calculated from the rate card
• flag overcharged and undercharged rows
• isolate exceptions instead of reviewing every transaction manually
• keep supporting calculations available for internal review and audit
• reuse the same setup for the next period

How the reconciliation workflow works

Cointab uses the same structured reconciliation approach for marketplace fee verification as it does for other finance workflows.

1. Define Side A and Side B

For this use case, Side A can contain your internal order or fee working, while Side B contains Myntra reports such as settlement, fee, or charge details.

Typical examples include:

• Side A: internal sales or order records, fee working, or rate-card based expected charges
• Side B: Myntra reported pick and pack fees, settlement data, or transaction-level charge reports

2. Upload the files

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

• order ID or reference number
• date
• fee amount
• shipping category or level
• any supporting identifier used in the working file

3. Add supporting data if needed

Supporting data is useful when the fee calculation depends on another file. For example:

• rate card file
• order metadata
• shipping or category mapping
• product or seller master
• enrichment file used for lookups or calculations

4. Create derived columns

If the expected fee needs to be calculated from business rules, users can create derived columns. These can help with tasks such as:

• assigning the correct fee level
• calculating the expected pick and pack fee
• normalizing order references
• combining multiple fields into one matching key

AI can help generate Excel-style formulas from plain-language instructions, which is useful when finance users know the rule but do not want to write the formula manually.

5. Run reconciliation

Once the files and rules are in place, Cointab performs structured matching and compares the reported Myntra fee with the calculated fee. The run can be repeated for new periods without rebuilding the setup.

Example rate-card verification logic

A rate-card setup can be configured so each order is allocated to the correct fee level before comparison.

This structure allows the team to calculate the expected charge for each order and compare it with the amount reported by Myntra.

What the report shows

After the reconciliation run is complete, the report highlights the fee outcome at transaction level and summary level.

Summary views

The dashboard can show:

• total pick and pack fee reviewed
• correctly charged fees
• overcharged fees
• undercharged fees
• skipped records

Transaction-level views

Users can filter and inspect rows that are:

• fully matched, where reported and calculated fees align
• partially matched, where the order is linked but the amounts differ
• unmatched, where a reference is missing on one side
• skipped, where the row could not be included because of missing or invalid data

This makes it easier to focus on exceptions rather than manually checking the entire report.

Why fee verification matters for finance teams

Pick and pack fees may look small at the individual order level, but they can add up across a large marketplace business. A consistent reconciliation process helps teams:

• catch rate-card mismatches early
• identify fee leakage or incorrect charge application
• support settlement review and partner follow-up
• maintain cleaner month-end records
• reduce spreadsheet dependency
• keep the review trail available for audit and internal controls

Manual review and exception handling

Not every fee difference should be matched automatically. Some rows may need manual review because of missing references, partial data, or a rule that does not fit the standard pattern.

Cointab supports a controlled exception workflow so finance teams can:

• review unresolved rows
• manually match transactions when the business context is clear
• keep unmatched and skipped records visible
• refresh the report if a missed file is uploaded later

Reusing the same setup for future periods

Once the Myntra fee verification workflow is configured, the same setup can be reused for monthly, quarterly, or custom reconciliation periods. That means the team does not need to rebuild fee logic every time a new settlement cycle is reviewed.

This is especially helpful when the workflow includes:

• repeated rate-card validation
• recurring settlement reviews
• periodic charge verification
• exception tracking across multiple periods

When this use case fits best

Myntra pick and pack fee verification is a strong fit for teams that handle marketplace finance work and want a transparent way to compare expected charges with reported charges. It is especially useful when the team needs a reusable process for fee validation, reconciliation reporting, and internal review across multiple periods.

FAQ

How does Cointab verify Myntra pick and pack fees?

Cointab compares the fee reported in Myntra data against the expected fee calculated from the configured rate card or working file. The system then highlights differences, matched rows, and exceptions for review.

What files are needed for this use case?

Typically, teams upload the Myntra report on one side and the internal fee calculation or order working on the other side. Supporting files such as rate cards or mapping files can also be added when needed.

Can the fee calculation be customized?

Yes. Users can configure custom reconciliation logic and create derived columns for fee calculations, identifier cleanup, or supporting lookups.

What happens when a fee does not match?

The transaction is shown as an exception, which may appear as partially matched, unmatched, or a difference in the summary. Finance teams can review the row and decide whether it needs a correction, a follow-up, or a manual match.

Can the same workflow be reused for later settlement periods?

Yes. Once the workflow is set up, it can be reused for future periods without recreating the same reconciliation from scratch.