Meesho Marketplace Reconciliation with OMS

Meesho marketplace reconciliation with OMS helps finance teams compare marketplace records against order management system data, identify differences early, and keep sales and settlement reporting under control. For teams handling high volumes of orders, cancellations, returns, and payment adjustments, manual spreadsheet checks quickly become slow and difficult to audit.

Cointab provides a structured reconciliation workflow for Meesho marketplace data and OMS data. Teams can upload files, map fields once, run reconciliation, review exceptions, and download audit-ready reports for follow-up and month-end close.

Why Meesho marketplace reconciliation with OMS matters

Meesho sellers often need to compare multiple files across the order lifecycle. A single order may appear in the marketplace order report, the sales report, the settlement report, a returns report, and the OMS report.

When those records do not line up exactly, finance teams may face:

• Missing or delayed settlements
• Differences between marketplace sales and OMS order values
• Orders marked canceled on one side but not the other
• Returns or deductions that need explanation
• Manual follow-up for open items
• Slow and inconsistent reconciliation during close

Cointab helps teams handle this with a repeatable Side A and Side B workflow.

Side A and Side B in this use case

In a Meesho reconciliation setup, the two sides usually look like this:

Side A: Your internal OMS records

Side A contains the records your business expects to be correct. For this use case, that is typically the OMS order data or internal sales working.

Examples of Side A fields:

• Order ID
• Order date
• Order amount
• Order status
• SKU or item reference
• Customer or shipment reference

Side B: Meesho marketplace records

Side B contains the external marketplace records received from Meesho.

Examples of Side B files may include:

• All order report
• Sales report
• Settlement report
• Returns report
• Payment or payout related report, where applicable

The goal is to compare both sides and determine which transactions are fully matched, partially matched, unmatched, or skipped.

How the reconciliation workflow works

Cointab turns the process into a reusable workflow rather than a one-time spreadsheet exercise.

1. Create a Meesho vs OMS reconciliation.
2. Upload the required marketplace and OMS files.
3. Map key fields such as date, amount, and identifier columns.
4. Optionally upload supporting data if enrichment is needed.
5. Create derived columns if values need to be cleaned or calculated.
6. Run reconciliation manually or on a schedule.
7. Review the report and focus on exceptions.
8. Download the Excel report for audit, review, or follow-up.

This is useful for recurring daily, weekly, or monthly reconciliation work.

What finance teams typically reconcile

Meesho marketplace reconciliation with OMS is rarely just a single file comparison. Finance teams usually need to compare multiple parts of the order and settlement lifecycle.

Common comparison areas include:

• OMS order vs Meesho order report
• OMS sales value vs Meesho sales value
• Meesho settlement vs expected net payout
• Meesho returns vs internal return records
• Canceled orders vs non-payable orders
• Deductions and fee adjustments vs internal working

Cointab can be configured for the business logic that matters to your team, whether the primary check is order-level matching, settlement-level reconciliation, or a combined workflow.

Matching logic for Meesho and OMS data

Cointab uses structured reconciliation logic to compare records across sides. That is important when the data is not a simple one-to-one match.

The engine can support scenarios such as:

• One-to-one matching by order reference
• One-to-many or many-to-one matching where records are grouped
• Net-to-net comparison when values need to be aggregated
• Partial matching when identifiers align but amounts differ
• Cross-field matching when references appear in different columns

Examples of issues that can be identified include:

• A Meesho sale exists, but no corresponding OMS order is found
• The OMS shows an order, but Meesho does not show a payable record
• The order matches, but the amount differs because of deductions or adjustments
• A canceled order is present on one side but should not be settled on the other

How discrepancies are handled

The reconciliation report separates transactions into clear buckets so finance teams do not need to inspect every row manually.

Fully matched

These are records where the identifier and amount match according to the configured reconciliation logic.

Partially matched

These are records where the order or transaction appears related across both sides, but the amounts do not align exactly. This often needs review for deductions, returns, refunds, or data quality issues.

Unmatched

These are records found on only one side. For Meesho and OMS workflows, this may indicate missing orders, missing settlement entries, or records that need follow-up.

Skipped

These are rows that were not included in the reconciliation because of missing required data, invalid values, duplicates, or a file-format issue.

Each bucket helps the team focus on the right action instead of searching through the entire dataset.

Supporting data and derived columns

Meesho reconciliation with OMS often benefits from supporting files and calculated fields.

Supporting data can be used for enrichment, lookup, or preparation before reconciliation. Examples include:

• Product master files
• SKU mapping files
• Return or status reference files
• Fee or tax mapping files
• Shipment or order metadata

Derived columns are useful when finance teams need cleaned or calculated fields for matching. For example, a team might create a clean order ID, a net amount, or a derived payment value from existing columns.

Cointab supports AI-assisted formula creation, which can help users define calculated fields without building formulas from scratch.

Manual match and exception review

Some Meesho and OMS exceptions need human review. Cointab provides manual match options for records that the system and AI do not confidently match.

This is useful when:

• The partner file is incomplete
• A reference appears in a different format
• The amount needs business review
• A one-off correction is required
• AI does not have enough evidence to make a weak match

Manual matches remain auditable and can be revisited if needed.

Missed files and report refresh

In real finance operations, files do not always arrive at the same time. A settlement report or OMS export may come in late, or a return file may be missed for a period.

Cointab supports uploading a missed file under the same reconciliation and refreshing the report. This helps teams avoid rebuilding the setup when late data arrives.

Reuse the same setup for future periods

Once the Meesho vs OMS reconciliation is configured, the same setup can be reused for future periods.

That means the team does not need to rebuild the workflow every month. They can simply:

• Select the reconciliation
• Select the period
• Upload the latest files
• Run reconciliation
• Review and export the report

This makes recurring reconciliation easier to manage across close cycles.

Reporting and audit readiness

Cointab produces reconciliation reports that finance teams can review internally or share for follow-up. The dashboard keeps past runs available for future reference, along with details such as run date, period, and status.

Useful outputs include:

• Matched records
• Partially matched records
• Unmatched records
• Skipped records
• Transaction-level detail tables
• Filtered exception views
• Downloadable Excel reports

For finance teams, this creates a clear audit trail and a more consistent way to track marketplace-to-OMS differences.

When this reconciliation is most useful

This use case is relevant for teams that manage:

• Meesho marketplace operations
• eCommerce accounting
• Marketplace finance close
• Settlement review and payout tracking
• Sales and returns reconciliation
• Exception management for order data

It is especially helpful when the same reports need to be checked repeatedly and the team wants a controlled, reusable workflow instead of manual Excel-based matching.