FirstCry Marketplace Reconciliation

FirstCry marketplace sellers often manage multiple reports across sales, invoices, debit notes, settlements, and bank statements. Reconciling those records manually can take time, especially when returns, fees, deductions, and delayed payouts need to be reviewed together.

Cointab helps finance teams automate FirstCry marketplace reconciliation with a structured workflow. Users upload the required files, map the key fields once, run reconciliation, and review a report that clearly separates fully matched, partially matched, unmatched, and skipped transactions.

Why FirstCry marketplace reconciliation becomes complex

FirstCry sellers usually need to compare internal business records with partner-generated reports. In practice, that means matching data across several sources and periods, not just checking whether a payment arrived.

Common reconciliation challenges include:

• Sales orders that do not line up neatly with settlement files
• Returned or cancelled orders that need to be removed or adjusted
• Debit notes and deductions that affect final receivables
• Delayed settlements that make month-end closing harder
• Bank receipts that do not exactly match settlement amounts
• Large file volumes that make Excel-based review repetitive and error-prone

For finance teams, the goal is not only to match records, but also to understand why exceptions exist and what action should follow.

How Cointab handles FirstCry marketplace reconciliation

Cointab uses a Side A and Side B model to keep the workflow clear.

• Side A is your internal source of truth, such as sales, order, or ledger data.
• Side B is the FirstCry-side data, such as invoice reports, debit notes, payment reports, or settlement reports.

A typical workflow looks like this:

1. Upload the required reports for the reconciliation.
2. Map fields such as date, amount, and reference identifiers.
3. Add supporting files if needed for lookups or enrichment.
4. Create derived columns when a clean amount or reference needs to be calculated.
5. Run reconciliation manually or on a schedule.
6. Review the reconciliation output and exception summary.
7. Download the Excel report for review, audit, or follow-up.

This gives teams a repeatable setup that can be reused for future periods instead of rebuilding the process every month.

Reports typically used in the workflow

A FirstCry reconciliation usually revolves around a few core reports.

Invoice report

The invoice report provides order-level transaction details and serves as a key reference for matching sales activity.

Debit note

Debit notes capture returns, cancellations, and other deductions that can change the final payable amount.

Payment report

The payment report shows the amounts that have been settled or paid out to the seller.

Settlement and bank data

For bank reconciliation, settlement data can be compared with bank statements to confirm that expected payouts were received correctly.

Cointab supports CSV, XLS, and XLSX files, and users can define the header row, date column, amount column, and identifier fields such as order ID, transaction ID, invoice number, settlement ID, or bank reference.

What the reconciliation report shows

After reconciliation runs, Cointab presents a report dashboard with clear status buckets and transaction-level detail.

Fully matched

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

Partially matched

These are records where the related identifiers match, but the amount differs. This often points to returns, deductions, rounding differences, or a settlement adjustment that needs review.

Unmatched

These are records present on one side but missing on the other. For FirstCry sellers, that may mean an order is present in the internal record but missing in the payment file, or a settlement appears in the partner report but not in the seller's books.

Skipped

Skipped rows are records that were not included in reconciliation because of missing data, invalid values, duplicates, or file format issues. Skipped records remain visible so finance teams can understand what was excluded and why.

Bank reconciliation for FirstCry settlements

Marketplace reconciliation often extends into bank reconciliation. Once the settlement report is available, Cointab can compare settlement values against the bank statement to identify differences.

This helps finance teams review situations such as:

• Settlement received in the bank exactly as expected
• Bank amount lower than the settlement value
• Bank amount higher than the settlement value
• Bank entry present but not found in the settlement report

That layered view helps teams separate marketplace-level exceptions from bank-level exceptions and close books with more confidence.

Supporting data and derived columns

Not every reconciliation is limited to the main reports. Some teams also upload supporting files to enrich or prepare the data before matching.

Examples include:

• SKU mapping files
• Product master data
• Return reports
• Fee rate files
• Order metadata
• Internal reference files

Users can also create derived columns with AI-assisted formula generation. That is useful when the reconciliation needs a clean order ID, a net amount, or a calculated field based on business logic.

Examples of derived columns include:

• Clean order reference
• Net payable amount
• Amount after fee
• Refund amount as negative
• Normalized settlement reference

How exceptions are handled

Cointab applies structured matching logic first. If transactions still remain open, AI can help analyze the unresolved items and suggest likely reasons or next actions.

Common exception patterns in FirstCry marketplace reconciliation include:

• Returned orders affecting settlement values
• Partial payouts or deductions
• Missing or delayed reports
• Reference mismatches across files
• Records that require manual review because deterministic matching is not enough

If the system cannot confidently match a record, it remains unmatched rather than forcing a weak match. Users can also perform manual matches when they know the business context and the totals tally.

Reuse and automation for recurring runs

FirstCry reconciliation is usually a recurring finance task. Cointab is built to make that workflow reusable.

Once a setup is configured, teams can:

• Reuse the same reconciliation for future periods
• Upload only the new files for the next run
• Refresh the report if a file arrives late
• Schedule reconciliation on a daily, weekly, or monthly basis
• Automate data input through email, SFTP, or API
• Push reconciliation output back to downstream systems when needed

This reduces repeated setup work and makes the process more consistent across periods and team members.

Why finance teams use Cointab for marketplace reconciliation

Cointab is designed to make reconciliation more transparent and easier to review. Finance teams get a structured workflow, clear matching logic, reusable setup, and audit-ready reports without relying on repeated spreadsheet handling.

For FirstCry sellers, that means a practical way to manage sales reconciliation, settlement review, and bank matching in one place while keeping exceptions visible and auditable.

FAQs

What data sources can be used in a FirstCry reconciliation?

Cointab can compare internal sales or ledger data with FirstCry invoice reports, debit notes, payment reports, settlement files, and bank statements. Supporting files can also be added for enrichment or calculation.

Can FirstCry reconciliation be reused for future periods?

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

What happens if a report is received late?

If a file was missed or received later, it can be uploaded under the same reconciliation and the report can be refreshed.

Does Cointab support manual matching?

Yes. If a transaction cannot be matched confidently by structured rules or AI, users can manually match records when the totals and business context support it.

Can FirstCry reconciliation include bank matching?

Yes. Sellers can compare settlement data with bank statements to verify whether the expected payout was received and identify differences where needed.