Hopscotch Marketplace Reconciliation Using OMS

Hopscotch sellers often manage reconciliation by comparing internal OMS records with marketplace reports, invoices, or settlement files. When order volumes grow, that review becomes repetitive and difficult to audit in spreadsheets. Cointab helps finance teams structure this workflow so they can upload files, map fields once, run reconciliation, and review exceptions in a clear report.

Why Hopscotch sellers reconcile OMS data

For marketplace businesses, the OMS usually contains the internal view of orders, items, prices, and status updates. Hopscotch reports provide the external view of what was processed, invoiced, settled, or adjusted.

Reconciling these two sides helps teams identify:

• orders that match exactly
• orders where the amount differs between systems
• orders present in the OMS but missing in Hopscotch
• orders present in Hopscotch but missing in the OMS
• records that need manual review before close or settlement follow-up

This makes it easier to track revenue, deductions, returns, fees, and missed records without rebuilding formulas every month.

Side A and Side B in this workflow

Cointab uses a simple reconciliation model:

Side A: Your OMS records

Side A contains the internal records your business expects to be correct. For this use case, that usually includes OMS exports such as:

• order ID
• invoice number
• item details
• order date
• amount
• shipping or fulfillment references
• status fields

Side B: Hopscotch marketplace records

Side B contains the external records received from Hopscotch. Depending on the workflow, this may include:

• sales report
• invoice report
• settlement report
• payment-related records
• adjustment or deduction information

Users can upload CSV, XLS, or XLSX files, map the required columns, and define which fields should be used for matching.

What Cointab compares

Cointab can compare records using identifiers, amounts, and matching rules configured for the workflow. Common fields include:

• order ID
• transaction ID
• invoice number
• settlement ID
• reference number
• SKU
• amount
• date

The reconciliation engine supports common marketplace scenarios such as:

• one OMS order matched to one Hopscotch record
• one internal record matched to multiple external records
• multiple records grouped and compared as a net amount
• partial matches where the identifier aligns but the amount does not
• contra or adjustment-style entries where the totals need to be netted

What the reconciliation report shows

Once reconciliation runs, finance teams can review a structured report with clear record statuses.

Fully matched

These records match across both sides according to the configured logic. They help confirm that the OMS and Hopscotch data are aligned for that item or order.

Partially matched

These records are related, but the amounts do not match exactly. Partial matches are useful for spotting deductions, short payments, fee differences, or other adjustments that need review.

Unmatched

Unmatched records are present on one side but not found on the other. This may point to missing uploads, late reports, cancellations, missing settlements, or data transfer issues.

Skipped

Skipped records are not included in matching because of missing data, invalid rows, duplicate entries, or another file issue. Seeing skipped records clearly helps teams understand what was excluded and why.

How the workflow runs in Cointab

A typical Hopscotch reconciliation workflow follows a repeatable sequence:

1. Upload OMS data on Side A and Hopscotch data on Side B.
2. Map required fields such as date, amount, and identifiers.
3. Optionally upload supporting data for lookup or enrichment.
4. Optionally create derived columns using AI-assisted formulas.
5. Run reconciliation manually or on a schedule.
6. Review matched, partially matched, unmatched, and skipped records.
7. Use filters to analyze exceptions in detail.
8. Download the Excel reconciliation report.
9. Manually match items that need business review.
10. Reuse the same setup for the next period.

Supporting data and derived columns

Some marketplace workflows need more than a direct file-to-file comparison. Cointab supports optional supporting data that can help prepare the primary records before reconciliation.

Examples include:

• product master files
• SKU mapping files
• fee or rate files
• return reports
• customer or store mapping files
• order metadata files

Users can also create derived columns on either side. For example, a finance team may want to normalize an order reference, calculate net amount, or convert a business rule into an Excel-style formula.

This is useful when the OMS and Hopscotch data use slightly different structures, naming conventions, or reference formats.

Exception handling and manual match

Not every open item can be matched automatically. Cointab supports manual matching for cases where the finance team knows the business context but the available data is incomplete.

Manual match is helpful when:

• a report arrived late
• an identifier is missing
• a partial settlement needs review
• a one-off correction must be recorded
• AI and structured matching do not have enough evidence

This keeps exceptions visible and auditable instead of hiding them inside spreadsheet formulas.

Why finance teams use Cointab for marketplace reconciliation

Marketplace reconciliation is not only about matching records. It is also about creating a repeatable process that supports month-end close, partner follow-up, and audit readiness.

Cointab helps teams:

• reduce repetitive Excel work
• reuse the same reconciliation setup for future periods
• isolate exceptions quickly
• review differences with clearer reporting
• keep reconciliation history available on the dashboard
• work together in a shared team workspace
• automate recurring file input and reconciliation runs when needed

For Hopscotch sellers, this means the OMS-to-marketplace process can move from manual review to a structured workflow that is easier to operate and easier to explain.

Common questions finance teams ask

What if a Hopscotch file is missed?

Users can upload the missed file under the same reconciliation and refresh the report. This is useful when marketplace or settlement files arrive later than expected.

Can the same setup be reused next month?

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

Can reconciliation be automated?

Yes. Cointab supports automated data input and scheduled reconciliation runs through email, SFTP, or API-based workflows, depending on the plan and setup.

Can we see why a record was skipped or unmatched?

Yes. Skipped, unmatched, and partially matched records are shown separately so finance teams can review exceptions and follow up with the right context.