FirstCry Marketplace Reconciliation with Cointab
Cointab helps FirstCry Marketplace sellers reconcile internal sales records with marketplace reports, payment files, settlement data, and bank statements in one structured workflow. Finance teams can match transactions, identify discrepancies, review exception items, and export audit-ready reports without rebuilding the process every month.
Why FirstCry marketplace reconciliation matters
FirstCry sellers often need to compare several data sources before they can close the books confidently. Sales orders, invoices, debit notes, payment files, settlement statements, and bank receipts may all reflect the same transaction in different ways.
Without a structured reconciliation workflow, teams usually rely on spreadsheets, formulas, and manual checks. That can make it harder to:
- confirm which orders were paid and settled
- identify returns, cancellations, and debit note adjustments
- spot short payments, missing settlements, or delayed credits
- reconcile marketplace reports against bank receipts
- keep month-end close and audit preparation under control
Cointab replaces repetitive spreadsheet work with a reusable reconciliation setup. Users upload files, map fields once, run reconciliation, and review results in a clear report.
How Cointab handles a FirstCry reconciliation
Cointab uses a simple Side A and Side B model.
- Side A is your internal record set, such as sales, orders, ledger entries, or ERP exports.
- Side B is the external record set, such as FirstCry invoice reports, debit notes, payment reports, settlement files, or bank statements.
A typical FirstCry marketplace reconciliation follows this flow:
- Upload the reports for Side A and Side B.
- Map key fields such as date, amount, and order or payment identifiers.
- Optionally add supporting data for lookups, merges, or enrichment.
- Optionally create derived columns for cleaned IDs, net amounts, or calculated values.
- Run reconciliation manually or on a schedule.
- Review matched, partially matched, unmatched, and skipped transactions.
- Download the Excel report for review, follow-up, or audit support.
This approach makes the workflow repeatable for monthly, quarterly, or custom periods.
Reports commonly used in FirstCry marketplace reconciliation
The exact files available to each seller can vary, but a FirstCry reconciliation usually relies on a combination of internal and external reports.
| Report type | Typical role in reconciliation |
|---|---|
| Internal sales or order report | Acts as the source of truth for the seller's expected transactions |
| FirstCry invoice report | Helps confirm order-level details, item values, and shipped sales |
| FirstCry debit note report | Captures returns, cancellations, and adjustments that affect final revenue |
| FirstCry payment report | Shows payments settled or released by the marketplace |
| Bank statement | Confirms whether marketplace settlements actually reached the seller's account |
If the workflow needs additional detail, supporting files such as product masters, mapping sheets, or order metadata can be used to enrich the primary data before reconciliation.
What Cointab matches in FirstCry reports
Cointab's reconciliation engine applies structured matching logic to compare records across the two sides. For a FirstCry workflow, users typically match on one or more of the following:
- order ID
- invoice number
- payment reference
- settlement ID
- bank UTR
- amount
- transaction date
- other business identifiers
The engine supports common reconciliation patterns such as:
- one-to-one matching
- one-to-many and many-to-one matching
- many-to-many grouping
- net-to-net comparison
- partial matching
- contra-style matching where needed
This is useful when a single order is split across multiple records, or when multiple FirstCry entries need to be grouped before the totals can be compared.
How exceptions appear in the report
After structured matching is complete, Cointab separates results into clear transaction groups so finance teams can focus on the exceptions.
Fully matched
These are records where identifiers and amounts match according to the reconciliation rules. For example, an internal order record matches the FirstCry payment report for the same amount.
Partially matched
These are records where identifiers match, but the amounts differ. This often points to deductions, returns, adjustments, or a short settlement that needs review.
Unmatched
These are records that appear on one side but not the other. In a FirstCry workflow, this could mean a sale that has not been settled yet, or a bank receipt that does not appear in the marketplace report.
Skipped
These are rows that were not included in the reconciliation because of missing data, invalid values, duplicates, or file format issues. Skipped records remain visible so the team understands why they were excluded.
Common issues finance teams review
A FirstCry marketplace reconciliation often helps identify issues such as:
- sales recorded internally but not reflected in the payment file
- settlement amounts lower than the expected invoice value
- returns or cancellations that reduce the final amount received
- debit notes that need to be tied back to original orders
- payments that appear in the bank but not in the marketplace report
- missing files for a specific period
- rows that need manual review because identifiers are incomplete
These exception views help teams spend time only on unresolved items instead of checking every transaction manually.
FirstCry bank reconciliation
Many sellers also need to confirm that marketplace settlements reached their bank account correctly. Cointab can support this by comparing FirstCry settlement data with the bank statement.
This helps finance teams review cases such as:
- settlement received in the bank at the expected amount
- settlement amount lower than expected
- settlement amount higher than expected
- bank entries that do not appear in the FirstCry settlement file
Bank reconciliation is especially useful when a seller works with multiple bank accounts, multiple settlement cycles, or delayed payout timing.
Reuse the same reconciliation for future periods
One of the main advantages of Cointab is reuse. Once a FirstCry reconciliation is configured, the same setup can be used again for future periods without rebuilding the workflow from scratch.
That makes it easier to:
- reconcile monthly, quarterly, yearly, or custom periods
- keep the same field mapping and matching logic
- add late or missed files and refresh the report
- run the same process repeatedly for ongoing finance operations
- reduce manual errors caused by repeated spreadsheet setup
Users can also configure automated data input through email, SFTP, or API where recurring file delivery is part of the workflow.
Audit-ready reporting for finance teams
Cointab presents reconciliation results in a report dashboard that is easy for finance teams to review and share internally. Users can drill into transaction-level details, apply filters, review exceptions, and download the Excel report for audit support or partner follow-up.
This is useful for teams that need a clear record of:
- what was matched
- what remains open
- what was skipped and why
- which files were used for the run
- when the reconciliation was completed
- who ran the workflow in the shared workspace
For marketplace finance teams, that visibility is often just as important as the matching itself.
Why teams use Cointab for FirstCry reconciliation
Cointab is built to reduce repetitive reconciliation work while keeping the process transparent and reviewable. For FirstCry sellers, that means a single workflow can be used to compare orders, invoices, debit notes, payments, settlements, and bank receipts without relying on inconsistent spreadsheet logic.
The result is a more structured reconciliation process that supports day-to-day finance operations, period close, and audit preparation.