Meesho Marketplace Reconciliation with ERP
Meesho marketplace sellers often need to compare marketplace data with ERP records to confirm that orders, settlements, fees, returns, and payouts are reflected correctly in books. When finance teams manage this work in Excel, the process can become repetitive, difficult to audit, and hard to scale across periods.
Cointab provides a structured reconciliation workflow for Meesho marketplace reconciliation with ERP. Teams can upload Meesho reports and ERP exports, map the required fields, run matching rules, review exceptions, and download audit-ready reconciliation reports.
What gets reconciled in a Meesho ERP workflow
In this use case, Side A usually contains your internal records and Side B contains Meesho reports.
Side A: your records
Your internal side may include:
- ERP sales export
- Order ledger
- Books data
- Internal settlement working
- Receivables or revenue records
Side B: Meesho records
Your external side may include:
- Meesho all order report
- Meesho sales report
- Meesho settlement report
- Meesho returns report
- Other supporting marketplace files
This structure helps finance teams compare what was expected in the ERP with what Meesho actually reported, settled, deducted, or returned.
Common Meesho reconciliation scenarios
A Meesho marketplace workflow can be configured for several finance checks:
- Sales report vs ERP sales ledger
- Settlement report vs books
- Order report vs ERP order register
- Returns report vs credit notes or reverse entries
- Net sales and deductions review
- Missing or delayed settlement review
Teams often use the same reconciliation setup each period, so the workflow does not need to be rebuilt every month.
Reports typically used
Meesho all order report
This report gives a broad view of orders placed through Meesho. Finance teams typically use it to track order-level references, quantities, item details, and transaction identifiers that can later be matched to ERP records.
Meesho sales report
The sales report helps teams review fulfilled, cancelled, or returned orders and compare the invoice or sales amount against internal records. It is often the main report used for Meesho sales reconciliation.
Meesho settlement report
The settlement report shows the amount Meesho pays out after fees, taxes, deductions, and other adjustments. This is important for confirming whether the settlement value in books matches the marketplace settlement.
Meesho returns report
Returns data helps teams identify returned products, return-related adjustments, and any impact on revenue or settlement. It is useful when a sales transaction appears correct in ERP but the settlement amount differs because of returns or reversals.
ERP report
The ERP side may come from SAP, Tally, or another finance system. The report usually contains the internal sales ledger, order register, receivables entries, or settlement working that the finance team wants to validate against Meesho.
How Cointab handles the reconciliation
Cointab is built to make the workflow transparent for finance teams.
- Upload the Meesho and ERP files, or configure automated file input where needed.
- Map the required fields such as date, amount, and order or transaction identifiers.
- Add supporting files if a lookup, merge, or enrichment step is needed before reconciliation.
- Create derived columns when values need to be cleaned, combined, or calculated.
- Run the reconciliation manually or on a schedule.
- Review matched, partially matched, unmatched, and skipped transactions.
- Download the Excel reconciliation report.
If a file is uploaded later than expected, the same reconciliation can be refreshed after the missed file is added.
What the reconciliation engine checks
Cointab uses structured matching logic to compare records across both sides. That is useful when Meesho and ERP data do not line up perfectly row by row.
The engine can support:
- One-to-one matching
- One-to-many matching
- Many-to-one matching
- Many-to-many matching
- Net-to-net comparison
- Partial matching
- Contra-style matching where required
Matching can use identifiers such as order ID, transaction ID, invoice number, settlement ID, or another business reference. It can also compare amounts, detect partial differences, and group related rows when the business logic requires it.
How to read the reconciliation output
Fully matched
A fully matched record means the Meesho side and ERP side agree based on the configured logic. For example, an order may match by order ID and amount.
Partially matched
A partially matched record usually means the identifiers line up, but the amounts do not. This can point to fees, deductions, rounding, returns, tax adjustments, or another difference that needs review.
Unmatched
An unmatched record exists on one side but not the other. For example, a sales record may appear in Meesho but not in ERP, or an ERP entry may not appear in the Meesho file.
Skipped
Skipped records are not included in reconciliation because they are incomplete, invalid, excluded by rule, or otherwise unusable. Showing skipped items helps teams understand what was ignored and why.
Common differences finance teams investigate
Meesho ERP reconciliation often reveals issues that are easy to miss in spreadsheets:
- Settlement amounts that differ from expected sales
- Missing or delayed orders in ERP
- Returns that were not recorded correctly
- Fees or deductions that need separate treatment
- Order references that do not match cleanly across systems
- Revenue entries that were posted before settlement data arrived
- Transactions that need manual review because the evidence is incomplete
For open items, AI can help analyze possible reasons and suggest likely next steps, while still keeping the final review audit-friendly and conservative.
Why reusable reconciliation matters
A Meesho marketplace workflow is usually not a one-time exercise. Finance teams need the same checks every period, often with new files and different date ranges.
Cointab supports reuse so teams can:
- Set up the workflow once
- Reuse the same mapping and logic for future periods
- Run monthly, quarterly, or custom-period reconciliation
- Schedule recurring runs through email, SFTP, or API-based input where configured
- Push output back to downstream systems when required
This reduces repeat work and makes the process more consistent across team members.
Team collaboration and audit readiness
Marketplace reconciliation often involves more than one finance user. Cointab supports team workspaces so controllers, accountants, and operations users can work in one shared environment instead of passing Excel files around.
The dashboard keeps reconciliation history available for future reference, including the run date, period, file set, and status. This supports internal review, month-end close, and audit preparation.
Meesho ERP reconciliation at a glance
| Area | What it helps verify |
|---|---|
| Sales matching | Orders and invoice values recorded correctly in ERP |
| Settlement matching | Meesho payout values against books or ledger entries |
| Returns matching | Return-related reversals and deductions |
| Exception review | Partial, unmatched, and skipped items |
| Reporting | Downloadable reconciliation reports for review and follow-up |
When a custom workflow is needed
Not every business uses the same Meesho file structure or ERP process. Some teams reconcile only sales and settlements, while others also compare returns, supporting ledgers, or derived values.
Cointab can support custom reconciliation setups when the business needs:
- Multiple files on either side
- Supporting data for enrichment
- Derived columns for calculated values
- Different matching rules for different transaction types
- A reusable setup that matches the company’s reporting format
FAQ
What is Meesho marketplace reconciliation with ERP?
It is the process of comparing Meesho marketplace reports with ERP records to confirm that sales, settlements, returns, and related adjustments are recorded correctly in books.
Which Meesho reports are usually used for reconciliation?
Teams commonly use the all order report, sales report, settlement report, and returns report, along with the relevant ERP export.
Can Meesho reconciliation be reused every month?
Yes. Once the workflow is configured, the same setup can be reused for future periods instead of rebuilding the process each time.
What happens if the Meesho file arrives late?
The missed file can be uploaded into the same reconciliation and the report can be refreshed so the comparison includes the newly received data.
How does Cointab handle unmatched items?
Unmatched items remain visible in the reconciliation report so finance teams can investigate missing files, timing differences, returns, deductions, or other exceptions.
Can teams use this for manual review as well as automation?
Yes. The workflow supports manual uploads and review, and it can also be configured for recurring automated data flow where required.
