Purplle Marketplace Reconciliation Using OMS

Purplle marketplace reconciliation often involves multiple reports, different file formats, and recurring checks between marketplace data and your internal OMS records. Cointab helps finance teams compare these records in a structured workflow, identify differences early, and export audit-ready reconciliation reports.

With Cointab, you can treat your OMS as Side A and Purplle marketplace reports as Side B. The platform maps the required fields, matches transactions using structured rules, and separates fully matched, partially matched, unmatched, and skipped records so the team can focus on exceptions instead of reviewing every row manually.

Why Purplle marketplace reconciliation is complex

Marketplace reconciliation is rarely limited to a single report. Finance teams usually need to compare:

• Internal OMS order data
• Marketplace order reports
• Sales reports
• Settlement or payout reports
• Return or cancellation files
• Fee, deduction, or adjustment records

When these reports are reviewed in Excel, the workflow can become repetitive and difficult to audit. Teams may also face issues such as:

• Orders appearing in one report but not another
• Amount differences caused by fees, deductions, or partial settlements
• Missing rows due to late file delivery
• Different identifiers across systems
• Manual formula errors in large files

A structured reconciliation workflow helps reduce these issues by keeping the matching logic, exception handling, and report output consistent across periods.

How Cointab handles OMS reconciliation for Purplle data

Cointab supports both popular reconciliations and custom workflows. For Purplle marketplace reconciliation using OMS data, the setup is typically a custom reconciliation where your internal OMS files are compared against marketplace-side reports.

Side A: your records

Side A usually includes records that your business expects to be correct, such as:

• OMS order exports
• Internal sales reports
• Ledger or order working files
• Product or SKU mapping files

Side B: external marketplace records

Side B includes reports received from the marketplace, such as:

• Order report
• Sales report
• Payout or settlement report
• Return or adjustment report

Once the reports are uploaded, Cointab maps the required columns, such as:

• Order ID or reference ID
• Transaction date
• Amount
• Settlement reference
• SKU or item identifier

If a supporting file is needed, such as a product master, fee file, or mapping file, it can be added to enrich or prepare the primary data before reconciliation.

Typical reconciliation flow

A Purplle marketplace reconciliation in Cointab usually follows this workflow:

1. Upload the OMS and marketplace reports.
2. Map the key fields once for each report.
3. Add supporting files if required for lookups or calculations.
4. Create derived columns when a cleaned or calculated field is needed.
5. Run reconciliation manually or on a schedule.
6. Review live progress while the job runs.
7. Open the reconciliation report and inspect matched and unmatched records.
8. Download the Excel report for internal review or audit use.

If the team misses a file, it can be uploaded later under the same reconciliation and the report can be refreshed.

What the reconciliation engine checks

Cointab uses structured matching logic to compare data across the two sides. Depending on how the Purplle reports and OMS files are structured, the engine can handle:

• One-to-one matching
• One-to-many matching
• Many-to-one matching
• Many-to-many grouping
• Net-to-net comparison
• Partial matching
• Contra or offsetting entries

This is useful when a single order is split across multiple records, when multiple deductions need to be grouped, or when one transaction in the OMS maps to more than one marketplace entry.

The system can also use comparisons such as equals, contains, similar, and subset-based matching where appropriate.

How exceptions appear in the report

After reconciliation is complete, Cointab presents the results in a clear report dashboard. Finance teams can review each status and drill into the record-level detail.

Fully matched

These are records where the order reference and amount match according to the configured logic.

Partially matched

These are records where the identifier matches, but the amount does not. This is important for reviewing deductions, short payments, overpayments, fees, or other settlement differences.

Unmatched

These are records that appear on one side but not the other. For example, an OMS order may be missing from the marketplace report, or a marketplace settlement may not map back to an internal record.

Skipped

These are rows that were not included in the reconciliation because of missing data, invalid values, duplicates, or other file issues. Skipped rows remain visible so the team knows what was excluded and why.

Supporting data and derived columns

Marketplace reconciliation often needs more than two primary files. Cointab allows supporting data to be uploaded when a file is needed for lookup, enrichment, or preparation.

Common examples include:

• SKU mapping files
• Fee or rate sheets
• Return files
• Order metadata
• Customer or product masters
• Tax or adjustment mapping files

Users can also create derived columns using AI-assisted formulas. This is helpful when a finance user knows the business rule but does not want to build the formula manually.

Examples of derived columns may include:

• Clean order ID
• Net amount
• Refund amount as negative
• Combined reference field
• Normalized settlement amount

Why finance teams use Cointab for marketplace reconciliation

Cointab is designed to reduce repeat work while keeping the workflow transparent and reviewable. For a Purplle marketplace reconciliation, that means the team can:

• Reuse the same setup for future periods
• Compare OMS and marketplace records in a consistent way
• Focus only on differences and exceptions
• Track who ran the reconciliation and when
• Export reports for internal review and audit preparation
• Keep reconciliation history in one shared workspace

This is especially useful for teams that reconcile recurring marketplace files every week or month and want to reduce spreadsheet dependency.

Review and exception handling

If Cointab cannot confidently match a transaction, the record remains open rather than forcing a weak match. That gives finance teams better control over exception handling.

Open items can be reviewed using filters and detailed tables, and users can manually match records when they know the business context and the totals tally. This keeps the reconciliation audit-friendly while still allowing practical finance overrides when needed.

Reusing the setup for future periods

Once the Purplle marketplace reconciliation is configured, the same setup can be reused for later periods. Finance teams can upload the next set of files, run reconciliation again, and review the new report without rebuilding the workflow from scratch.

This makes it easier to support recurring month-end checks, settlement reviews, and ongoing marketplace control processes.

FAQs

What reports are usually needed for Purplle marketplace reconciliation?

Typical inputs include OMS order data, marketplace order or sales reports, payout or settlement reports, and any supporting files needed for mapping, fees, or returns.

Can Cointab reconcile both directions between OMS and marketplace reports?

Yes. The workflow can be set up to compare OMS records against marketplace records, or the reverse, depending on how the finance team wants to review differences.

What happens when an order is missing or the amount does not match?

The transaction is surfaced in the reconciliation report as unmatched or partially matched, so the team can investigate missing records, fee differences, deductions, or other exceptions.

Can the same setup be reused for future Purplle periods?

Yes. Once the reconciliation is configured, the same workflow can be reused for future reporting periods with new files and the same field mapping and matching logic.