Myntra Marketplace Reconciliation with Cointab

Cointab helps Myntra sellers reconcile internal sales and order records with marketplace settlements, returns, deductions, tax entries, and bank receipts in a structured workflow. Instead of comparing spreadsheets manually, finance teams can upload files, map fields once, run reconciliation, and review clear matched and exception outputs.

Why Myntra marketplace reconciliation becomes difficult

Myntra reconciliation usually involves more than comparing one sales report to one payout file. Finance teams often need to match:

• Internal order and sales data
• Myntra settlement files
• Return, reversal, and cancellation records
• Tax-related reports such as TCS
• Non-order charges and deductions
• Bank statements for settlement verification

When these records are reviewed manually in Excel, even a simple mismatch can take time to trace. Common issues include delayed settlements, missing references, partial payments, returns posted in a later period, deduction differences, and files arriving late from different teams or systems.

Cointab is designed to make that workflow repeatable. It gives finance teams a structured way to compare Side A and Side B records, identify discrepancies, and keep an audit-friendly trail of what matched and what still needs review.

What sits on Side A and Side B for Myntra reconciliation

Cointab uses a clear reconciliation model:

• Side A: your internal records, such as sales reports, order exports, ERP data, ledger entries, or receivable working files
• Side B: Myntra-side records, such as settlement files, return files, tax files, charge reports, or bank receipt references

Supporting data can also be added where needed. For example, a finance team may upload product master data, SKU mappings, fee rate files, or order metadata to enrich the primary reports before reconciliation.

Typical files used in a Myntra workflow

The exact file structure can vary by business process. Cointab lets teams configure the required columns once and reuse the setup for future periods.

How Cointab supports Myntra reconciliation

A Myntra reconciliation workflow in Cointab usually follows these steps:

1. Create a new reconciliation inside the team workspace.
2. Choose a popular reconciliation template or configure a custom workflow.
3. Upload the required files for Side A and Side B.
4. Map key fields such as date, amount, and reference columns.
5. Add supporting data if the workflow needs lookups or enrichment.
6. Create derived columns if a field needs to be cleaned or calculated before matching.
7. Run reconciliation manually or on a schedule.
8. Review matched, partially matched, unmatched, and skipped transactions.
9. Download the Excel report for internal review, partner follow-up, or audit support.

For recurring Myntra work, the same setup can be reused instead of rebuilding matching logic every month.

Matching logic for sales, settlements, and exceptions

Cointab's reconciliation engine is built for structured matching, not loose spreadsheet comparisons. It can handle common marketplace patterns such as:

• One sales record matching one settlement record
• One sale matching multiple related settlement entries
• Multiple records on one side matching a grouped settlement on the other side
• Partial matches where the reference matches but the amount differs
• Contra or netted entries
• Cross-field identifiers such as order ID, transaction reference, invoice number, or settlement ID

This matters for Myntra sellers because settlement data often includes deductions, reversals, and adjustments that do not line up neatly with the original sale amount.

What the reconciliation report shows

After the run completes, Cointab presents a report dashboard that helps finance teams focus on exceptions instead of reviewing every row manually.

Fully matched

These are records where the expected identifiers and amounts reconcile according to the configured logic.

Partially matched

These are records where the identifiers match, but the amounts do not. For Myntra sellers, this can help surface underpayments, overpayments, fee differences, or deductions that need review.

Unmatched

These are records that appear on one side but not the other. For example, an order may exist in the internal sales file but not in the settlement data, or a settlement credit may appear in the bank statement but not in the expected report.

Skipped

These are records excluded from reconciliation because of missing data, invalid values, duplicates, or another file issue. Skipped rows remain visible so the team can understand what was left out and why.

The report can also be filtered for deeper analysis, and users can manually match transactions when business context supports it.

Common reconciliation outcomes for Myntra sellers

A Myntra marketplace reconciliation workflow often helps teams identify:

• Sales that were not settled in the expected period
• Settlement amounts that are lower than expected
• Deductions that need explanation
• Return or cancellation differences that were posted later
• Tax or TCS entries that require cross-checking
• Bank credits that do not map cleanly back to settlement files
• Non-order charges that affect net payout value

This makes it easier for finance teams to separate routine matched items from the exceptions that actually need action.

Reusable workflow for recurring month-end close

Myntra reconciliation is rarely a one-time task. Most teams need a repeatable process for monthly, quarterly, or custom settlement periods.

Cointab supports reusable reconciliation setups so teams can:

• Run the same workflow again for a new period
• Upload missing files later and refresh the report
• Use scheduled runs when data arrives automatically
• Receive files through email, SFTP, or API for recurring processing
• Push reconciliation output back to internal systems when needed

That makes the workflow useful not only for manual review, but also for ongoing finance operations.

Why finance teams use Cointab for marketplace reconciliation

For Myntra sellers, the value is not just transaction matching. It is having a single place to manage the full reconciliation process with visibility into what matched, what did not, and what needs follow-up.

Cointab helps teams:

• Reduce repetitive Excel work
• Keep matching logic consistent across periods
• Review exceptions faster
• Maintain an audit-ready file trail
• Reuse a proven reconciliation setup instead of rebuilding it each month

FAQs

What data can be reconciled for Myntra sellers?

Cointab can reconcile internal sales or order data against Myntra settlement files, return or reversal reports, tax-related files, non-order charges, and bank statements, depending on the workflow you configure.

Can Myntra reconciliation be automated for recurring periods?

Yes. Once the workflow is configured, reconciliation can be reused for future periods and can also run on a schedule when files arrive through email, SFTP, or API.

What happens when transactions do not match?

Cointab separates fully matched, partially matched, unmatched, and skipped records so finance teams can focus on exceptions. Users can also manually match transactions when the business context supports it.

Can the report be used for review and audit preparation?

Yes. Users can download reconciliation reports in Excel format and review matched, partial, unmatched, and skipped items with a clear transaction-level trail.

What if a file was missed for the period?

A missed file can be uploaded under the same reconciliation and the report can be refreshed so the reconciliation reflects the updated data set.