Reconciliation of Snapdeal Marketplace Using Order Management Data

Cointab helps finance teams reconcile Snapdeal marketplace data against their internal order management system (OMS) records. The workflow is designed for teams that need to compare sales, settlement, payment settlement, and reversal reports with their own source-of-truth order data, then review differences in a structured and audit-friendly format.

This is useful when Snapdeal reports and internal OMS data do not line up exactly because of timing differences, partial settlements, reversals, deductions, or missing records. Instead of managing the comparison in spreadsheets, teams can upload the required files, map the relevant fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped transactions.

How Snapdeal marketplace reconciliation works

In this workflow, your internal OMS or database acts as your records on Side A, while Snapdeal reports act as external records on Side B.

Typical Side A data includes:

• Internal order management system exports
• Sales or order detail reports
• ERP or accounting exports
• Internal settlement working files

Typical Side B data includes:

• Snapdeal Order Detail Report
• Snapdeal Settlement Report
• Snapdeal Payment Settlement Report
• Snapdeal Reversal Report

Cointab compares the two sides using identifiers such as order ID, settlement reference, invoice number, or other mapped fields. Finance teams can also use supporting data to enrich or normalize records before reconciliation, such as SKU mappings, product masters, fee files, or lookup tables.

Reports used in the workflow

A Snapdeal reconciliation setup usually brings together multiple reports from both the marketplace and the internal business system.

Snapdeal-side reports

• Order detail report
• Settlement report
• Payment settlement report
• Reversal report

Internal OMS or business-side reports

• OMS order report from systems such as Increff, Unicommerce, Shopify, or an internal database
• Internal sales or settlement working files
• Ledger or ERP exports, where needed for additional cross-checking

When report formats are stable, the same reconciliation setup can be reused for future periods. If a file is missing later, the user can upload it under the same reconciliation and refresh the report.

What the reconciliation compares

The goal is to compare Snapdeal records with internal OMS records and identify where amounts or references do not line up.

Common checks include:

• Order amount against settlement amount
• OMS recorded amount against Snapdeal settlement amount
• OMS recorded amount against Snapdeal payment amount
• Snapdeal reversals against internal order activity
• Orders present on one side but missing on the other

If product details or reference fields differ between Snapdeal and the OMS, Cointab can use supporting data and derived columns to clean identifiers, merge files, or prepare amounts for matching.

Reconciliation outcomes finance teams can review

Cointab separates the output into clear transaction groups so finance teams can focus on exceptions rather than reviewing every row manually.

Fully matched

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

Partially matched

These are records where the identifiers match, but the amounts do not fully align. This is useful when Snapdeal and the OMS refer to the same order, but the settlement amount differs because of deductions, fees, reversals, or other adjustments.

Unmatched

These are records found on one side but not on the other.

Examples include:

• An order present in Snapdeal settlement data but missing in the OMS
• A payment reflected in the OMS but not found in Snapdeal payment settlement data
• A reversal present in Snapdeal but not linked in internal records

Skipped

These are rows excluded from reconciliation because of missing required data, invalid values, duplicates, or file issues. Skipped records remain visible so the team understands what was not included and why.

Why internal OMS data matters

Using OMS data alongside Snapdeal reports helps finance teams validate the full transaction flow, not just the final settlement figure.

It can help with:

• Verifying whether orders were recorded correctly internally
• Spotting settlement differences early
• Reviewing reversals and deductions more clearly
• Matching marketplace records against the business’s source-of-truth data
• Reducing manual spreadsheet checks during period-end close

For teams handling high volumes of marketplace transactions, this makes reconciliation more consistent and easier to review across periods.

Field mapping and supporting data

Before running reconciliation, users map key fields such as:

• Date
• Amount
• Order ID
• Invoice number
• Settlement ID
• Reference number

Users can also add supporting data where needed. Supporting data is not reconciled directly, but it can help prepare the main files through lookups, merges, or calculations.

Examples include:

• Product master
• SKU mapping
• Fee rate file
• Order metadata
• Return report
• Internal mapping file

If a value needs cleaning before comparison, users can create derived columns. Cointab can help generate Excel-style formulas using natural language, which is useful when the team wants to normalize order IDs, calculate net amounts, or build matching fields without manual formula work.

Handling exceptions and open items

After structured matching is completed, finance teams can review open items and unresolved differences.

Cointab supports:

• Review of partially matched and unmatched rows
• Filtering by status, amount, or identifiers
• Manual match for cases that need human review
• AI-assisted analysis of open items when rules alone are not enough

This is especially helpful when the reason for a mismatch is operational, such as a missed file, a reversal, a timing difference, or a deduction that needs follow-up.

Reuse for recurring Snapdeal periods

The same Snapdeal reconciliation setup can be reused for monthly, quarterly, yearly, or custom settlement periods.

Once the structure is defined, users do not need to rebuild the workflow every time. For future runs, they can simply:

• Select the existing reconciliation
• Choose the period
• Upload the required reports
• Run reconciliation
• Review and export the report

This reduces repeat setup work and helps finance teams maintain a consistent reconciliation process across reporting cycles.

Audit-ready reporting and review

Once reconciliation is complete, users can review the transaction-level report and download an Excel file for internal review, partner follow-up, or audit preparation.

The report is designed to show:

• Summary counts
• Fully matched records
• Partially matched records
• Unmatched records
• Skipped records
• Detailed transaction-level output

This makes it easier to explain differences, document exceptions, and keep a record of what was matched during the period.

Typical business value for marketplace finance teams

Snapdeal reconciliation is often part of a wider marketplace finance process. Teams usually need a workflow that is repeatable, visible, and easy to audit.

Cointab supports that by helping teams:

• Reduce repetitive spreadsheet work
• Compare OMS data with marketplace records in one workflow
• Focus on exceptions instead of every transaction
• Reuse reconciliation logic across periods
• Maintain clearer records for review and reporting

For businesses selling on Snapdeal alongside other marketplaces, the same approach can be extended into broader marketplace reconciliation workflows using the same Side A and Side B model.