Meesho Reconciliation Software for Sales, Settlements, and Fees

Cointab helps finance teams reconcile Meesho marketplace data with the records they maintain in their books, OMS, ERP, and bank statements. Instead of relying on spreadsheets and manual file comparisons, teams can upload the required files, map the fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped records in a structured report.

What Meesho reconciliation covers

Meesho reconciliation usually involves comparing your internal records with the reports received from the marketplace and related systems. The exact workflow depends on how your team tracks sales, settlements, fees, payouts, refunds, and returns.

With Cointab, Meesho reconciliation can cover:

• Meesho sales vs settlement matching
• Fee and commission verification
• Refund and return tracking
• Bank statement vs books reconciliation
• OMS reconciliation for order-level completeness
• ERP reconciliation for posting and accounting checks

This helps finance teams identify missing settlements, deduction differences, unmatched orders, partial payouts, and records that need manual review.

Typical Side A and Side B setup for Meesho reconciliation

Cointab uses a Side A and Side B model so the workflow stays clear and auditable.

Side A: your internal records

Side A usually contains the records your business expects to be correct, such as:

• Sales data from your internal system
• OMS exports
• ERP or ledger data
• Order-level working files
• Books and receivables data

Side B: Meesho and related external records

Side B usually contains the external reports received from Meesho or adjacent finance sources, such as:

• Meesho settlement reports
• Fee or deduction details
• Refund or return-related records
• Payout or bank-related records
• Partner or system files used for matching and verification

By keeping the two sides separate, finance teams can clearly see what matched, what did not, and what requires follow-up.

Common Meesho reconciliation workflows

Sales vs settlement reconciliation

This is the most common workflow for marketplace finance teams. The goal is to compare Meesho order-level sales information with the corresponding settlement or payout records.

Teams typically review:

• Which orders were settled
• Which orders are still pending
• Whether the settlement amount matches the expected value
• Whether any deductions or adjustments changed the final payout

Fee and deduction verification

Meesho settlements may include commissions, marketplace fees, and other deductions. Cointab helps teams compare the expected fee logic with the reported deduction values so they can identify overcharges, missing adjustments, or unexpected differences.

Refund and return reconciliation

Returns, cancellations, and refunds can create differences between sales, settlements, and bank movement. Cointab helps teams isolate these items so they can see whether the difference is explained by a return, refund, RTO event, or another operational issue.

Bank vs books reconciliation

Finance teams often need to compare marketplace receipts with bank entries and ledger postings. Cointab can help match receipts, identify missing deposits, and surface open items that need accounting review.

OMS and ERP reconciliation

Meesho order data often needs to be checked against OMS and ERP records to confirm that the order flow is complete and accounting entries are posted correctly. This is useful for spotting missing orders, duplicate records, or timing differences across systems.

How Cointab handles Meesho reconciliation

Cointab is designed to make reconciliation repeatable rather than one-time and spreadsheet-heavy. A typical workflow looks like this:

1. Upload the required files for your Meesho reconciliation.
2. Map the key fields such as date, amount, and order or reference identifiers.
3. Optionally upload supporting files for lookup, enrichment, or calculation.
4. Create derived columns when you need cleaned identifiers, net amounts, or calculated fields.
5. Run reconciliation manually or on a schedule.
6. Review the report to see fully matched, partially matched, unmatched, and skipped records.
7. Export the reconciliation output in Excel format for internal review, audit, or partner follow-up.

If a file arrives late, you can upload the missed file under the same reconciliation and refresh the report.

Matching logic for marketplace data

Marketplace reconciliation is rarely a simple one-to-one file comparison. Meesho-related data may need to be matched across different identifiers, multiple rows, and partial settlement structures.

Cointab supports structured matching logic for cases such as:

• One-to-one matching
• One-to-many and many-to-one matching
• Grouped matching across multiple rows
• Net-to-net comparison
• Partial matching when identifiers match but amounts differ
• Contra-style matching where entries offset each other

This is useful when the same order flows through several reports or when the settlement side groups multiple transactions together.

What finance teams see in the report

After reconciliation runs, Cointab presents a report view that helps teams focus on exceptions instead of reviewing every row manually.

The report can show:

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

Fully matched records

These are transactions where the expected identifiers and values match according to the configured rules.

Partially matched records

These are records where the order or reference links up, but the amounts do not match exactly. This is useful for spotting underpayments, overpayments, deduction differences, or settlement variances.

Unmatched records

These are records found on one side but not on the other. For Meesho reconciliation, that may mean an order appears in your internal data but not in the marketplace settlement, or vice versa.

Skipped records

Skipped rows are not included in reconciliation because of missing data, invalid values, exclusions, or file issues. Visibility into skipped records helps teams understand what was ignored and why.

Supporting data and derived columns

For Meesho reconciliation, teams often need more than just the primary reports. Supporting data can help enrich the workflow before matching begins.

Examples include:

• Product master files
• Order metadata
• SKU mappings
• Store mappings
• Fee rate files
• Return or cancellation references
• Customer or vendor master data

Cointab also supports derived columns. These are calculated fields that can help normalize identifiers, calculate net amounts, or prepare data for matching. Users can create them with AI-assisted formula generation or with standard Excel-style logic.

Manual match for exceptions

Not every exception should be forced into an automatic rule. When records cannot be matched confidently, Cointab allows manual match so finance teams can handle one-off cases with full visibility.

Manual matching is useful when:

• Partner data is incomplete
• Identifiers are missing or inconsistent
• There is a known business reason for the exception
• AI and structured rules do not have enough evidence to match safely

Manual matches remain clearly marked for audit and review.

Reusable and automated reconciliation for recurring runs

Meesho reconciliation is often a recurring workflow, not a one-time project. Cointab lets teams reuse the same setup for each new period so they do not need to rebuild rules every month.

This is helpful for:

• Monthly close
• Quarterly review
• Yearly reporting
• Daily or weekly marketplace monitoring
• Ongoing exception tracking

Cointab also supports automated data flow through email, SFTP, or API. That means teams can reduce manual upload work and keep reconciliation part of their finance operations rather than a separate spreadsheet task.

Why marketplace finance teams use Cointab for Meesho data

Finance teams handling Meesho data usually need three things: clarity, control, and auditability. Cointab is built to support that workflow by making it easier to see what was compared, what matched, what remained open, and what action is needed next.

That is especially useful when teams need to:

• Reconcile high-volume marketplace transactions
• Review deductions and settlement differences
• Keep books aligned with external reports
• Reduce repetitive Excel work
• Prepare audit-ready reconciliation output

FAQs

What can be reconciled in a Meesho workflow?

Teams can reconcile Meesho sales, settlements, fees, refunds, returns, payouts, bank entries, OMS data, and ERP records depending on how their workflow is configured.

Can Cointab compare Meesho reports with internal books or ERP data?

Yes. Cointab is designed to compare your internal records on Side A with Meesho or other external records on Side B, including books, ERP exports, and settlement files.

How does Cointab handle fee or settlement differences?

Cointab flags partially matched and unmatched records so finance teams can review deductions, commissions, refunds, returns, and timing differences instead of treating every variance as a match.

Can recurring Meesho reconciliation be automated?

Yes. Once the setup is configured, reconciliation can be run on a schedule and data can be received or pulled through email, SFTP, or API-based workflows.

What format are the reports available in?

Cointab provides downloadable Excel reconciliation reports so teams can review matched, partially matched, unmatched, and skipped records in a format that is easy to share and audit.