Firstcry Marketplace Reconciliation Using OMS

Firstcry marketplace sellers often need to reconcile internal OMS records with marketplace reports, settlement files, returns, reimbursements, and bank receipts. When transaction volumes grow, manual checks in Excel can become slow, repetitive, and difficult to audit. Cointab provides a structured reconciliation workflow that helps finance teams compare Side A and Side B records, identify discrepancies, and review matched, partially matched, unmatched, and skipped transactions in one place.

How Cointab structures Firstcry marketplace reconciliation

In this workflow, your internal OMS or ERP data is typically used as Side A, while Firstcry marketplace reports and related external files are used as Side B. The goal is to compare what your business expects to have happened with what was reported by the marketplace and related settlement sources.

A typical setup may include:

• OMS order or sales data on Side A
• Firstcry order, settlement, invoice, or payment-related reports on Side B
• Return, reimbursement, or deduction files where relevant
• Bank statement data for payment verification
• Supporting files such as SKU masters or mapping sheets

Once the files are uploaded, finance users map the required fields such as date, amount, order reference, settlement reference, invoice number, or other identifiers. The same reconciliation can then be reused for future periods instead of being rebuilt every month.

What teams commonly reconcile

For Firstcry marketplace operations, reconciliation is usually not limited to one report. Finance teams often need to compare multiple sources to understand the full transaction flow.

Common comparison areas include:

• OMS orders versus marketplace order or invoice data
• OMS sales versus marketplace settlement data
• Marketplace deductions versus expected fees or charges
• Returns and refunds versus the original sale
• Reimbursements or adjustments versus internal records
• Bank receipts versus settlement amounts

This gives the team a clearer view of gross sales, deductions, net settlements, and open items that still need review.

Supporting data that improves matching

Cointab also supports optional supporting data. These files are not reconciled directly, but they can help prepare the primary data before matching.

Examples include:

• SKU master data
• Product mapping files
• Order metadata
• Tax or GST mapping sheets
• Customer or vendor master data
• Delivery or shipment reference files

Supporting data is useful when the same information appears in different formats across systems. For example, a marketplace report may use one identifier while the OMS uses another. A lookup file or mapping sheet can help standardize those references before reconciliation.

How the reconciliation engine handles exceptions

Cointab uses structured matching logic to compare records across sides. It can handle different matching scenarios, including one-to-one, one-to-many, many-to-one, and grouped comparisons.

This is helpful when marketplace transactions do not line up in a simple row-by-row format. For example, one OMS order may connect to multiple marketplace entries, or multiple deductions may need to be grouped against one settlement line.

The reconciliation report highlights:

• Fully matched transactions where amount and identifiers align
• Partially matched transactions where the records are related but the values differ
• Unmatched transactions that appear on one side but not the other
• Skipped rows that were excluded because of missing or invalid data

This helps finance teams focus on exceptions instead of reviewing every line manually.

Common Firstcry marketplace exceptions

Marketplace reconciliations often surface recurring exception patterns. Cointab helps teams isolate them quickly so they can investigate the reason and decide the next step.

Typical examples include:

• An order exists in the OMS but is missing from the marketplace report
• A settlement amount does not match the expected sale amount
• A return or refund appears in one system but not the other
• Fees, deductions, or adjustments reduce the expected payout
• A transaction reference is incomplete or formatted differently across files
• A file for a required period is received late and needs to be added later

These issues are easier to track when the workflow separates matched, partially matched, unmatched, and skipped items clearly.

Derived columns and AI-assisted review

Marketplace data often needs cleanup before it can be matched properly. Cointab allows users to create derived columns from existing fields so they can normalize references, calculate net amounts, or prepare data for matching.

Examples of derived columns include:

• Clean order reference
• Net amount after fee or deduction
• Refund amount as a negative value
• Normalized settlement identifier
• Combined reference for matching

Users can also describe the logic in natural language, and Cointab can help create an Excel-style formula for the derived column. This reduces repeated formula work and keeps the reconciliation setup easier to maintain.

After structured matching is complete, AI can help analyze open items where rules are not enough. This is useful for inconsistent references, partial identifiers, or exception cases that need additional review. AI support remains conservative, so weak matches are not forced into the report.

Reconciliation reports for finance review

Once reconciliation is complete, teams can review a report dashboard that shows the full result set and transaction-level detail.

The report typically includes:

• Total summary
• Fully matched summary
• Partially matched summary
• Unmatched summary
• Skipped summary
• Filters for deeper analysis
• Detailed transaction tables
• Downloadable Excel output

This format makes it easier to use the output for month-end close, partner follow-up, internal review, and audit preparation. If a file was missed earlier, users can upload it under the same reconciliation and refresh the report.

Reuse and automation for recurring marketplace work

A major advantage of Cointab is that the same reconciliation setup can be reused for future periods. Once the Firstcry marketplace workflow is configured, finance teams do not need to recreate the logic every time.

Users can run reconciliation manually or automate the process with:

• Email-based data delivery
• SFTP-based file transfer
• API-based input and output
• Scheduled reconciliation runs

That means the workflow can move from occasional manual checks to a repeatable finance process. Output can also be pushed back to internal systems where required, helping teams keep finance, accounting, BI, or reporting systems updated.

Why this matters for marketplace finance teams

Firstcry marketplace reconciliation is not just about matching numbers. It is about understanding how orders, settlements, deductions, returns, reimbursements, and bank receipts connect across systems.

With Cointab, finance teams can keep that process structured, reviewable, and reusable. Instead of rebuilding spreadsheets every period, they can work from one reconciliation setup, review exceptions faster, and maintain clearer records for reporting and audit readiness.