Hopscotch Marketplace Reconciliation with ERP

Marketplace sellers often need to reconcile Hopscotch reports with ERP records, bank entries, and internal sales data. That usually means matching orders, invoices, settlements, debit notes, refunds, returns, deductions, and fees across different systems. When the numbers do not line up, finance teams need a clear way to find the reason quickly and keep the reconciliation audit-ready.

Cointab helps finance teams set up a reusable Hopscotch marketplace reconciliation workflow using the Side A / Side B model. Users upload their files, map the required fields, run reconciliation, review the results, and download structured reports for internal review and follow-up.

Why Hopscotch marketplace reconciliation matters

Marketplace reconciliation is rarely a simple one-file comparison. A single order may appear in the sales report, invoice report, payment report, settlement report, debit note, bank statement, and ERP ledger. Differences can arise because of:

• settlement timing differences
• marketplace deductions and fees
• refunds and returns
• partial payments or partial settlements
• amount rounding differences
• missing or delayed reports
• inconsistent identifiers between systems

Manual Excel checks can become slow and difficult to audit, especially when the same workflow is repeated every day, week, or month.

Side A and Side B in this workflow

Cointab uses a structured reconciliation setup so finance teams can compare the records they expect against the records received from the marketplace or related systems.

This structure makes it easier to compare transaction values, track differences, and understand which side needs review.

How Cointab handles Hopscotch reconciliation

Cointab gives finance teams a repeatable workflow instead of a one-time spreadsheet check.

1. Create or select the reconciliation

Users can set up a custom reconciliation for their Hopscotch workflow or reuse an existing setup if the reporting structure stays the same across periods.

2. Upload or automate the data flow

Users can upload CSV, XLS, or XLSX files manually. Where recurring automation is needed, data can also flow through email, SFTP, or API.

3. Map the key fields

For each report, users map the important columns such as:

• transaction date
• amount
• order ID
• invoice number
• payment reference
• settlement ID
• bank UTR
• other business identifiers

4. Add supporting data when needed

Supporting data can be used to enrich the primary files before reconciliation. Common examples include SKU masters, fee rate files, return reports, customer or vendor masters, and mapping files.

5. Create derived columns if required

Finance teams can create calculated fields on either side. Cointab’s AI can help generate Excel-style formulas from simple prompts, which is useful when the reconciliation needs a cleaned ID, a net amount, or a normalized reference field.

6. Run reconciliation and review the report

The reconciliation engine applies structured matching logic and then analyzes open items where rules alone are not enough. Users can then review the report, filter transactions, and inspect the detailed matched and unmatched records.

Common mismatch scenarios in marketplace-to-ERP reconciliation

Hopscotch reconciliation usually focuses on identifying where the difference comes from, not just whether a record matched.

Typical scenarios include:

• Reconciled orders where ERP and marketplace values match
• Partially matched transactions where the identifiers match but amounts differ
• Less amount recorded in ERP where the internal record is below the marketplace value
• More amount recorded in ERP where the internal record is above the marketplace value
• Missing in ERP where the marketplace record exists but the internal record does not
• Missing in Hopscotch where the ERP record exists but the marketplace record is absent
• Skipped rows where a record was excluded because of missing data, invalid values, or file issues

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

What the reconciliation engine can match

Cointab is designed for structured transaction matching across different record patterns. Depending on the data, it can handle:

• one-to-one matching
• one-to-many matching
• many-to-one matching
• many-to-many matching
• net-to-net comparisons
• partial matching
• contra-style matching where relevant

The engine compares identifiers and amounts using structured logic, then keeps unresolved items available for review rather than forcing weak matches.

What the report shows

After reconciliation, users get an audit-friendly report that separates records clearly.

Fully matched

These are transactions where the identifiers and amounts match according to the configured rules.

Partially matched

These are transactions where the records are related, but the values do not fully match. This often happens when the amount on one side differs because of fees, deductions, returns, or timing differences.

Unmatched

These are records present on one side but not found on the other side. This is where finance teams usually investigate missing settlements, missed uploads, or data issues.

Skipped

These are rows that were not included in the reconciliation because of missing required fields, invalid values, duplicates, or other file-level issues.

Users can filter the report, open transaction-level details, and download the Excel output for internal review, partner follow-up, or audit support.

Why finance teams use Cointab for Hopscotch reconciliation

Cointab helps teams reduce repetitive spreadsheet work and keep the reconciliation process consistent across periods.

Key benefits include:

• reusable reconciliation setup for future runs
• manual upload and recurring automation options
• AI-assisted formula creation for derived columns
• AI support for difficult open-item analysis
• manual match for exceptions that need human review
• dashboard history for previous reconciliation runs
• audit logs and team workspace controls

Handling late or missed files

In real finance operations, reports may arrive late. If a file was missed, users can upload it under the same reconciliation and refresh the report. This keeps the workflow practical for marketplace, bank, and ERP reconciliation cycles where files do not always arrive at the same time.

Who this use case is for

This reconciliation workflow is useful for:

• marketplace finance teams
• eCommerce accounting teams
• controllers and finance managers
• accounts receivable and accounts payable teams
• reconciliation analysts
• audit and compliance teams
• marketplace operations teams

It is especially relevant for businesses that need a repeatable way to compare internal records with external marketplace data and explain differences clearly.

FAQs

What files are usually needed for Hopscotch marketplace reconciliation?

The exact file set depends on the workflow, but typical inputs include internal ERP or sales data, Hopscotch invoice or payment reports, settlement files, debit notes, and bank statements. Supporting files such as SKU masters or mapping files can also be added when needed.

Can the reconciliation be reused for future periods?

Yes. Once a Hopscotch reconciliation is configured, the same setup can be reused for future periods. Users only need to select the reconciliation, upload the required files, and run it again.

How does Cointab handle unmatched transactions?

Cointab separates unmatched records clearly so finance teams can review the exceptions instead of checking every row manually. Users can also use manual match where the business context is known and the totals tally.

Can Hopscotch reconciliation be automated?

Yes. After the workflow is set up, data can be received or pulled through email, SFTP, or API, and reconciliation can be scheduled to run automatically when the required files are available.