Hopscotch Marketplace Reconciliation Using OMS
For finance teams selling on Hopscotch, reconciliation often means comparing marketplace reports with OMS records, settlement data, and internal books. When order volumes increase, manual spreadsheet checks can become slow and difficult to audit. Cointab helps teams structure this workflow so they can upload files, map fields once, run reconciliation, review exceptions, and download audit-ready reports.
This use case is built for sellers and finance teams that want a repeatable way to reconcile Hopscotch marketplace activity against their OMS and related finance records. Instead of rebuilding formulas every month, teams can reuse the same reconciliation setup for future periods and focus on the transactions that need review.
How Hopscotch reconciliation with OMS works
Cointab uses a Side A and Side B model:
- Side A contains the records your business expects to be correct, such as OMS order data, internal sales data, or books.
- Side B contains the external records received from Hopscotch, such as invoice, debit note, payment, or settlement data.
Finance teams can upload CSV, XLS, or XLSX files, map the required columns, and run reconciliation from a shared workspace. Common mapped fields include:
- Order date or transaction date
- Amount
- Order ID, transaction ID, invoice number, or other reference fields
- SKU, settlement ID, or additional identifiers where needed
If multiple reports are involved, Cointab can use supporting files to enrich or prepare the main data before reconciliation. This is useful when a seller needs order metadata, SKU mapping, product master data, fee files, or other lookup tables to complete the workflow.
Reports commonly used in this workflow
A Hopscotch marketplace reconciliation setup may include the following report types:
Hopscotch-side reports
- Invoice report
- Debit note report
- Payment report
- Settlement-related report where applicable
- SKU or item reference files
OMS and finance-side reports
- OMS order report
- Internal sales report
- Books or ledger data
- Bank statement, if the workflow also needs payment tracking
- SKU master or product catalog
The exact combination depends on how the seller records sales, deductions, and receipts in the OMS and finance system. Cointab supports both standard and custom reconciliation workflows so teams can align the setup with their internal process.
What the reconciliation helps identify
Once the data is loaded, Cointab applies structured matching logic to find records that match and surface items that need review. For a Hopscotch marketplace workflow, this often includes:
- Fully matched transactions where the OMS record and Hopscotch report align
- Partially matched transactions where the reference matches but the amounts differ
- Unmatched OMS records where an order exists internally but is missing from Hopscotch data
- Unmatched Hopscotch records where a marketplace record is present but not found in the OMS
- Skipped records where the row could not be used because required data was missing or invalid
Typical differences finance teams review include:
- Order amount differences
- Missing or delayed payment entries
- Debit note deductions
- Refund or return adjustments
- Reference mismatches across systems
- Files that were not received for the period
Clear exception grouping helps the team focus on the transactions that matter instead of checking every row manually.
Reconciliation from both perspectives
Marketplace reconciliation is often easier to manage when teams review it from both directions.
OMS to Hopscotch
In this view, the OMS is treated as the starting point and matched against Hopscotch reports. This helps identify:
- Orders recorded in the OMS but not found in Hopscotch
- Amount differences between internal records and marketplace data
- Transactions that are likely valid but need follow-up because they are only partially matched
Hopscotch to OMS
In this view, Hopscotch reports are matched back to internal OMS data. This helps identify:
- Marketplace transactions missing in the OMS
- Differences in invoice or payment values
- Rows that require manual review before month-end close
Finance teams often use both views together to get a complete picture of sales, deductions, and cash flow impact.
Using supporting data and derived columns
Marketplace reconciliation often requires more than a simple one-to-one match. Cointab supports supporting data and derived columns so teams can prepare records before matching.
Supporting data can be used to:
- Add missing order details
- Merge marketplace and OMS data
- Enrich rows with SKU or customer information
- Lookup fee, return, or tax-related values
- Normalize partner-specific identifiers
Derived columns can be created from existing fields when the reconciliation needs a cleaned or calculated value. For example:
- Clean order ID
- Normalized transaction reference
- Net amount after deductions
- Amount excluding tax
- Combined reference key
AI can help generate Excel-style formulas for these derived columns, which reduces manual formula writing while keeping the logic reviewable.
Matching logic for complex marketplace data
Marketplace data is rarely perfect. One order may map to multiple settlement rows, a payment may be split across records, or identifiers may appear in different fields. Cointab supports structured matching across scenarios such as:
- One-to-one matching
- One-to-many matching
- Many-to-one matching
- Many-to-many matching
- Net-to-net comparison
- Contra matching
- Partial matching
The engine first applies rules defined in the reconciliation setup. If open items remain, AI can assist with additional analysis of difficult exceptions. The system is designed to be conservative, so weak matches remain open rather than being forced into a result.
Manual review and missed files
Even with strong matching logic, finance teams sometimes need manual intervention. Cointab includes manual match options for transactions that the system cannot confidently resolve.
This is helpful when:
- A reference is incomplete
- A partner file has gaps
- A one-off exception needs review
- A transaction was partially matched and needs a different treatment
If a report arrives late or a file was missed, users can upload the missing file under the same reconciliation and refresh the report. This is useful for monthly close processes where marketplace reports may arrive after the initial run.
Reusable and automated reconciliation setup
A major advantage of Cointab is reuse. Once the Hopscotch marketplace reconciliation is configured, teams do not need to rebuild it every month. They can simply select the reconciliation, choose the period, upload the required files, and run it again.
For recurring operations, teams can also automate the workflow through:
- SFTP
- API
This allows data to be received, validated, loaded, reconciled, and reported with less manual intervention. Cointab can also deliver reconciliation output back to internal finance, accounting, analytics, or BI systems through the same automation channels.
What finance teams see in the final report
After the run is complete, Cointab provides an audit-friendly report view with:
- Total summary
- Fully matched summary
- Partially matched summary
- Unmatched summary
- Skipped summary
- Transaction-level tables
- Filters for deeper review
- Downloadable Excel report
This gives finance teams a clear record of what matched, what did not match, and what needs follow-up. It also helps with partner communication, internal review, and period-end reporting.
Why this use case matters for finance operations
Hopscotch marketplace reconciliation using OMS is not just about finding mismatches. It is about building a repeatable process for financial accuracy.
With a structured workflow, teams can:
- Reduce manual spreadsheet work
- Track marketplace differences more clearly
- Review exceptions faster
- Keep reconciliation logic consistent across periods
- Support audit readiness with downloadable reports
- Reuse the same setup for future reconciliation runs
For businesses handling marketplace sales, deductions, settlements, and OMS data, that consistency makes month-end close and financial review more manageable.
Frequently asked questions
What does Hopscotch reconciliation with OMS compare?
It compares marketplace records from Hopscotch with internal OMS data and related finance records to identify matched, partially matched, unmatched, and skipped transactions.
Can this workflow include invoice, debit note, and payment reports?
Yes. Cointab can support workflows that use invoice, debit note, payment, and other supporting reports, depending on how the reconciliation is configured.
What if the Hopscotch file arrives late?
You can upload the missed file under the same reconciliation and refresh the report so the workflow reflects the latest available data.
Can the same reconciliation be reused for future periods?
Yes. Once the setup is created, the same reconciliation can be reused for future runs instead of being rebuilt each month.
Does the system support manual review for unresolved items?
Yes. Transactions that cannot be matched automatically can be reviewed manually, which is useful when partner data is incomplete or exceptions need business context.
