Firstcry Marketplace Reconciliation Using ERP

Firstcry marketplace reconciliation using ERP helps finance teams compare marketplace reports with internal accounting records, identify differences early, and keep settlements, fees, refunds, and order-level entries under control. Instead of checking files manually in Excel, teams can upload the relevant reports, map the fields once, and run a structured reconciliation workflow that highlights matched, partially matched, unmatched, and skipped transactions.

This is especially useful for eCommerce and marketplace finance teams that need a repeatable process for month-end close, settlement review, audit preparation, and exception follow-up.

Why Firstcry reconciliation becomes difficult in Excel

Marketplace reconciliation usually involves multiple reports, different identifiers, and repeated review work. For Firstcry, teams may need to compare sales, invoices, payments, debit notes, settlements, and ERP entries across the same period.

Common challenges include:

• Order-level data spread across multiple files
• Fee deductions, taxes, and adjustments that affect net amounts
• Returns, cancellations, or reversals that need separate review
• Missing or late files from a reporting period
• Different reference formats between Firstcry reports and ERP exports
• Manual VLOOKUPs, formulas, and copy-paste checks that are hard to audit

Cointab replaces repetitive spreadsheet work with a reusable reconciliation setup that is easier to review and simpler to repeat for future periods.

How Cointab handles Firstcry marketplace reconciliation

Cointab uses a Side A and Side B model for reconciliation.

Side A: Your internal records

Side A typically includes the records your business expects to be correct, such as:

• ERP sales data
• Internal order reports
• Invoice or ledger exports
• Bank statement data
• Customer or receivable records

Side B: Firstcry marketplace records

Side B includes the external records received from Firstcry, such as:

• Firstcry invoice report
• Firstcry payment report
• Firstcry debit note
• Settlement-related files

The workflow is straightforward:

1. Upload the required files for both sides.
2. Map key fields such as date, amount, and order or reference identifiers.
3. Add optional supporting data if needed.
4. Create derived columns for cleaned or calculated values.
5. Run reconciliation manually or on a schedule.
6. Review the report and exception buckets.
7. Download the Excel output for internal review or audit.

Reports commonly used in the workflow

A Firstcry reconciliation setup often uses a combination of primary and supporting files.

Primary reconciliation reports

• Firstcry invoice report
• Firstcry payment report
• Firstcry debit note
• ERP export from the internal accounting system
• Bank statement, if cash collection or settlement tracing is needed

Supporting data

Supporting data is optional and is used to enrich or prepare records before reconciliation. Examples include:

• SKU master
• Order metadata
• Tax mapping file
• Product master
• Customer or vendor reference files
• Other lookup tables used for field normalization or enrichment

Supporting data is not reconciled directly, but it can help finance teams align identifiers, calculate net amounts, or combine related records before running the match.

Matching logic for marketplace and ERP records

Cointab's reconciliation engine applies structured matching logic to compare records across the two sides. It can handle straightforward and more complex match patterns, including:

• One-to-one matching
• One-to-many matching
• Many-to-one matching
• Many-to-many matching
• Net-to-net comparison
• Partial matching
• Contra-style cases where records offset each other

This is useful when a Firstcry order appears differently in marketplace reports and ERP data, or when amounts need to be grouped before comparison.

Users can define matching fields such as:

• Order ID
• Transaction reference
• Invoice number
• Settlement ID
• Payment reference
• Bank UTR
• SKU or other internal identifiers

Users can also create derived columns, such as clean order IDs, net amounts, or normalized references, using AI-assisted formula generation.

What the reconciliation report shows

Once reconciliation completes, Cointab presents a report dashboard that separates transactions into clear buckets.

Fully matched

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

Partially matched

These are records where the identifier matches, but the amounts differ. For example, a Firstcry order may match an ERP entry by reference, but the gross or net amount may not be identical because of fees, deductions, or rounding differences.

Unmatched

These are records that appear on one side but not the other. Examples include:

• An ERP entry that is missing in a Firstcry report
• A Firstcry transaction that has not been recorded in ERP
• A settlement item that cannot be linked to an order

Skipped

These are records excluded from reconciliation because of file issues, missing mandatory fields, duplicates, or invalid values. Skipped rows remain visible so finance teams can understand what was not processed and why.

Common exceptions in Firstcry marketplace reconciliation

Finance teams usually focus on exceptions rather than reviewing every row manually. Typical exceptions include:

• Sales amount in ERP does not match the marketplace report
• A fee or debit note has not been recorded in ERP
• Orders are present in ERP but missing in Firstcry reporting
• Orders are present in Firstcry but missing in ERP
• Returns or reversals create amount differences
• Settlement values differ from expected amounts
• A supporting file is missing for the period

If a row remains open after structured matching, AI can help analyze why it may be unmatched and suggest possible reasons or follow-up actions. The output remains reviewable, so finance teams still retain control over the final decision.

Manual review and exception handling

Not every exception should be forced into an automated match. If the system and AI cannot confidently match a transaction, the record can remain open for manual review.

Cointab supports manual matching for cases where the finance team knows the business context and the totals tally. This is helpful for one-off adjustments, incomplete partner data, or cases that require human judgment.

Reusing the same setup for future periods

A major benefit of Cointab is reuse. Once the Firstcry reconciliation workflow is configured, finance teams do not need to rebuild it each month.

For future runs, users can simply:

• Select the reconciliation
• Choose the period
• Upload the files or let them arrive automatically
• Run the workflow again
• Review the latest report

This makes the process easier to standardize across month-end close cycles and recurring marketplace reviews.

Automation for recurring marketplace reconciliation

For teams that reconcile Firstcry data regularly, Cointab can support automated file intake and scheduled runs through email, SFTP, or API-based workflows. That means the reconciliation can be part of a recurring finance process instead of a manual upload task.

Users can also push reconciliation output back to internal systems through email, SFTP, or API, which helps keep downstream reporting and finance operations aligned.

Audit-ready reporting for finance teams

Cointab provides downloadable Excel reconciliation reports that are suitable for internal review, partner follow-up, and audit preparation. The report history remains available on the dashboard, so teams can revisit prior runs, check who ran them, and compare periods when needed.

This makes Firstcry marketplace reconciliation easier to govern, easier to review, and easier to repeat across the finance team.

FAQ

What files are usually needed for Firstcry marketplace reconciliation?

A typical workflow uses Firstcry invoice, payment, and debit note reports alongside ERP exports. Some teams also use bank statements and supporting lookup files such as SKU or tax mappings.

Can the same Firstcry reconciliation setup be reused every month?

Yes. Once the workflow is configured, the same setup can be reused for future periods by uploading the new files and running the reconciliation again.

What happens if a required file is missing?

The reconciliation can be refreshed after the missed file is uploaded under the same workflow. This helps teams handle late partner reports or delayed internal exports.

How does Cointab handle unmatched items?

Unmatched items stay visible in the report so finance teams can review the reason, investigate the source, and decide whether a manual match or correction is needed.