Purplle Marketplace Reconciliation Using OMS

Purplle marketplace reconciliation using OMS helps sellers compare marketplace records with internal order management data, so finance teams can spot missing orders, amount differences, and payout issues before they affect close, reporting, or follow-up with the marketplace.

Cointab provides a structured reconciliation workflow for this process. Teams upload their Purplle marketplace files on one side and OMS data on the other, map the required fields once, and run reconciliation whenever they need a fresh report. The result is a clear view of which transactions are fully matched, partially matched, unmatched, or skipped.

Why Purplle marketplace reconciliation matters

Marketplace data often moves through multiple systems before finance sees the final number. A single order may appear in the marketplace report, the OMS, a settlement file, and supporting operational reports. If the records are not reconciled properly, teams can miss:

• Orders that were recorded in the OMS but do not appear in marketplace reports
• Orders present in Purplle reports but missing in the OMS
• Amount differences between the marketplace report and internal records
• Deductions, fees, refunds, or other settlement differences
• Rows that were excluded because the data was incomplete or unusable

For finance teams, this is not just a reporting task. It affects revenue visibility, payout tracking, exception handling, and audit readiness.

What records are compared

Cointab uses a Side A and Side B model for reconciliation.

Side A: Your records

This is the data your business expects to be correct. For a Purplle workflow, Side A usually includes OMS data such as:

• Order report
• Sales report
• Internal settlement working
• Order status report
• Ledger or finance export

Side B: External records

This is the data received from the marketplace or related external source. For a Purplle workflow, Side B may include:

• Purplle order report
• Purplle sales report
• Purplle payout report
• Purplle invoice or settlement report

Teams can also upload supporting data if they need it for enrichment, lookups, or calculations before reconciliation.

Typical reports used in the workflow

A marketplace finance team generally reconciles the following reports:

If file formats change over time, Cointab can validate the incoming file against the configured structure and flag missing columns clearly.

How the reconciliation works

The workflow is designed for finance users, not spreadsheet-heavy manual checks.

1. Upload the Purplle and OMS files.
2. Map key fields such as date, amount, order ID, transaction reference, or settlement ID.
3. Add supporting files if needed for enrichment or lookup.
4. Optionally create derived columns using AI-generated formulas.
5. Run reconciliation manually or on a schedule.
6. Review the output report and exception buckets.
7. Download the Excel report for internal review or partner follow-up.

Cointab then applies structured matching logic to compare the two sides. It can handle simple matching as well as more complex cases where one record maps to multiple records, totals need to be netted, or identifiers only partially match.

Reconciliation outcomes you can review

Cointab separates records into clear result groups so teams can focus on exceptions instead of reviewing every line item.

Fully matched

These are transactions where the relevant identifiers and amounts match according to the configured reconciliation logic.

Partially matched

These are transactions that appear related, but the values do not fully agree. For example, the order may match by reference, but the amount may differ because of deductions, adjustments, or other discrepancies.

Unmatched

These are transactions that appear on one side but could not be found on the other side.

Skipped

These are records that were not included in the reconciliation because they were incomplete, invalid, duplicated, or excluded by rule.

This structure is especially useful for marketplace teams that need to identify whether a difference is caused by a missing file, a partner issue, an internal data issue, or a genuine settlement variance.

Supporting data and derived columns

Purplle reconciliation often becomes easier when the team enriches the primary data before matching.

Supporting data can include:

• Product master
• Order metadata
• SKU mapping
• Fee rate file
• Return file
• Store or channel mapping
• GST or tax mapping

Teams can also create derived columns when the raw data needs cleanup or transformation. Examples include:

• Clean order ID
• Net amount
• Amount after fee
• Normalized transaction reference
• Refund amount as negative

If a finance user wants a formula but does not want to write it manually, AI can help generate an Excel-style formula from a plain-language request.

Handling exceptions and open items

Not every mismatch should be forced into a match. Cointab keeps the reconciliation audit-friendly by showing unresolved items clearly and leaving weak evidence unmatched.

For open transactions, teams can:

• Review the reason an item may be unmatched
• Check whether a file is missing
• Investigate deductions, returns, refunds, or delays
• Use filters to narrow down the exception set
• Manually match transactions when business context is available

This makes it easier for finance and marketplace operations teams to separate routine differences from real issues that need follow-up.

Reusable setup for future periods

Once the Purplle reconciliation is configured, the same setup can be reused for future runs. That means the team does not need to rebuild the workflow every month.

For recurring work, users can simply:

• Select the saved reconciliation
• Choose the period
• Upload or receive the required files
• Run reconciliation
• Review the report

This is useful for monthly close, weekly settlement review, and ongoing marketplace control.

Automation for recurring marketplace workflows

For teams that want to reduce manual uploads, Cointab supports automated data input through email, SFTP, or API integrations. That allows Purplle-related files or internal OMS exports to be loaded into the correct reconciliation workflow on a recurring basis.

Once the required files arrive, Cointab can run reconciliation automatically and prepare the report for review. The output can also be delivered back to downstream systems through email, SFTP, or API if the business wants to keep internal accounting or reporting systems updated.

Why this use case matters for finance teams

Purplle marketplace reconciliation using OMS is not only about matching orders. It is about keeping the finance view consistent with operational reality.

A structured workflow helps teams:

• Reduce manual spreadsheet checks
• Spot discrepancies earlier
• Review only the records that need attention
• Keep reconciliation history in one place
• Support month-end close and audit preparation
• Maintain a repeatable process across periods

For marketplace sellers, that means better control over sales, settlements, and exception management without rebuilding the same process every month.

Related reconciliation patterns

The same reconciliation approach can also be used for other marketplace and order-led workflows, such as:

• Marketplace sales vs settlement reconciliation
• Order report vs payment reconciliation
• Bank vs books reconciliation
• Vendor reconciliation
• COD delivery partner reconciliation

The core idea remains the same: compare Side A and Side B, identify differences, review exceptions, and keep the report audit-ready.