Firstcry Marketplace Reconciliation Using OMS

Firstcry sellers often need to reconcile order activity, settlements, returns, reimbursements, fees, and bank receipts across multiple reports. When those records also need to line up with an Order Management System, the review quickly becomes repetitive in Excel.

Cointab provides a structured reconciliation workflow for this use case. Your OMS data can be treated as Side A, while Firstcry marketplace reports and related external files can be treated as Side B. Finance teams can upload files, map the required fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped transactions in one report.

What gets reconciled in a Firstcry OMS workflow

A typical Firstcry reconciliation setup may include the following reports and reference files:

Supporting data is optional in Cointab. It is not reconciled directly, but it can help complete missing values, combine reports, or create identifiers that are needed for matching.

How the reconciliation flow works

Cointab follows a clear reconciliation process so finance users can see exactly what was compared and why a transaction matched or remained open.

1. Upload the required Side A and Side B files in CSV, XLS, or XLSX format.
2. Map the required fields such as date, amount, and order or reference identifiers.
3. Add supporting files if you need lookups, enrichment, or calculations.
4. Create derived columns when fields need to be cleaned, combined, or calculated.
5. Run reconciliation manually, or schedule it to run automatically.
6. Review the report once processing is complete.
7. Investigate partially matched, unmatched, or skipped records.
8. Download the Excel reconciliation report for internal review or audit use.

If a file is missed, it can be uploaded under the same reconciliation and the report can be refreshed without rebuilding the setup.

Matching logic for Firstcry and OMS records

Firstcry marketplace reconciliation is rarely limited to simple one-to-one matching. In practice, finance teams may need to compare records in several ways:

• One OMS order against one marketplace record
• One OMS order against multiple marketplace lines
• Multiple OMS lines against one settlement line
• Order-level records against payout or disbursement totals
• Returns or deductions against original sales values
• Net amounts after fees, taxes, or adjustments

Cointab’s reconciliation engine supports structured matching across these scenarios, including one-to-one, one-to-many, many-to-one, many-to-many, net-to-net, partial matching, and contra-style matching where relevant.

Common identifier fields may include:

• Order ID
• Invoice number
• Transaction ID
• Settlement ID
• Payment reference
• SKU
• Bank UTR
• Any custom business reference used in the workflow

Where direct identifiers are inconsistent, users can create cleaned or derived identifiers using formulas or AI-assisted formula generation.

Common differences finance teams review

Once the main matching rules are applied, the remaining open transactions often point to operational differences that need review.

Typical exceptions in a Firstcry OMS reconciliation include:

• Orders present in the OMS but not in the marketplace report
• Orders present in the marketplace report but not in the OMS
• Settlement amounts that differ from expected order values
• Return credits that have not yet been reflected in internal books
• Reimbursements or deductions that need validation
• Records skipped because of missing or invalid data
• Identifier mismatches caused by formatting differences

Cointab separates these into clear report statuses so teams can focus on exceptions instead of reviewing every row manually.

Report statuses visible in Cointab

The reconciliation report clearly shows how each record was classified.

Fully matched

These are records where the relevant identifiers and amounts align according to the configured reconciliation logic.

Partially matched

These are records where the system finds a likely match, but one or more values do not fully align, such as amount differences or incomplete references.

Unmatched

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

Skipped

These are records that were not included in reconciliation because of missing data, invalid values, duplicate rows, or another file-level issue.

This structure helps finance teams understand not just what matched, but also what needs follow-up and why.

Why marketplace teams use Cointab for OMS reconciliation

Cointab is designed to reduce the manual effort involved in recurring marketplace reconciliation work.

Reusable setup

Once the Firstcry workflow is configured, it can be reused for the next period without rebuilding the logic from scratch.

Faster exception handling

Finance teams can focus on open items, partial matches, and discrepancies instead of checking every line manually.

Audit-ready reporting

Users can download reconciliation reports with matched, partially matched, unmatched, and skipped records for review and audit support.

Team-based review

Shared workspaces allow finance, accounting, and marketplace operations users to work from the same reconciliation history.

Automated runs

For recurring workflows, reconciliation can be scheduled and connected through email, SFTP, or API-based data flow where required.

Where AI helps in the workflow

AI is used to support finance users without replacing the structured reconciliation process.

It can help with:

• Generating Excel-style formulas for derived columns
• Reviewing difficult open transactions after the main matching logic runs
• Suggesting possible reasons for unmatched items
• Identifying whether a file may be missing
• Highlighting likely next actions for exception review

AI is used conservatively. If the evidence is weak, the transaction remains unmatched rather than being forced into an unreliable match.

Flexible period handling

Marketplace teams often reconcile by month, quarter, financial year, or custom settlement period.

Cointab supports flexible period handling so the same Firstcry reconciliation setup can be used for recurring runs across different reporting windows. Users can also carry forward open items where needed and keep past reconciliation reports available for later reference.

Manual review when automation is not enough

Even with strong matching rules, some items still require human judgment. Cointab includes a manual match option for transactions that the system cannot confidently resolve.

This is useful when:

• Partner data is incomplete
• Identifiers are missing or inconsistent
• A one-off exception needs manual handling
• A user has business context that is not visible in the files

Manual matches remain clearly marked so the reconciliation trail stays reviewable.

A clearer way to manage Firstcry reconciliation

For finance teams handling Firstcry marketplace data through an OMS, the main value is not just matching rows. It is having a repeatable process that makes exceptions visible, preserves audit history, and reduces repeated Excel work.

Cointab brings that workflow into a structured reconciliation engine with reusable setups, clear report statuses, supporting data, AI-assisted analysis, and exportable reports that fit finance operations.