Purplle Marketplace Reconciliation

For brands selling on Purplle, reconciliation often involves more than comparing a single sales report to a payout file. Finance teams may need to match orders, sales, returns, settlements, deductions, payouts, and bank receipts across multiple reports. Cointab helps structure that work into a repeatable reconciliation workflow.

Why Purplle reconciliation becomes complex

Marketplace finance teams usually deal with several data sets for the same period. One file may show the order value, another may show the final sale amount, a third may include returns or cancellations, and a settlement report may reflect deductions, charges, or timing differences. Bank statements add another layer, because settlement timing and bank credits do not always line up cleanly with marketplace reports.

This creates a familiar set of issues:

• Orders appear in one report but not another
• Sales values differ from settlement values
• Returns, refunds, and cancellations need separate review
• Payouts may be delayed or partially settled
• Bank credits may not match the expected settlement amount
• Month-end close takes longer because exceptions remain open

Cointab is built to help finance teams compare these records in a transparent, auditable way.

How Cointab structures Purplle reconciliation

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

• Side A contains your records, such as internal order data, sales reports, ERP exports, or ledger data
• Side B contains external records from Purplle-related reports, settlement files, payment records, or bank statements

For a Purplle workflow, teams can map the relevant files, define key fields such as date, amount, order ID, transaction ID, settlement ID, or bank reference, and then run reconciliation using a reusable setup.

Typical reports used in the workflow

A Purplle reconciliation setup may include:

• Order report
• Sales report
• Return or cancellation report
• Payment or payout report
• Settlement report
• Bank statement

Supporting files can also be added when needed, such as product master data, fee mapping, tax mapping, or order metadata used for lookups and enrichment.

What the reconciliation process looks like

A finance team can set up the workflow once and reuse it for future periods. The typical flow is:

1. Upload the required Purplle-related files
2. Map the header row, date column, amount column, and identifier columns
3. Add any supporting data needed for lookups or enrichment
4. Create derived columns if the reconciliation needs cleaned or calculated fields
5. Run the reconciliation manually or on a schedule
6. Review matched, partially matched, unmatched, and skipped records
7. Download the Excel reconciliation report

If a file arrives late, it can be uploaded under the same reconciliation and the report can be refreshed.

Matching logic for marketplace transactions

Purplle reconciliation is rarely a simple one-to-one match. In many cases, one order may connect to multiple settlement or return entries, or multiple report lines may need to be grouped before comparison.

Cointab supports structured matching patterns such as:

• One-to-one matching
• One-to-many matching
• Many-to-one matching
• Many-to-many matching
• Net-to-net matching
• Partial matching
• Contra matching

This is useful when a sales line, deduction, return, or payout must be evaluated together rather than in isolation.

How AI helps in open-item analysis

After structured matching is complete, Cointab can use AI to help review remaining open transactions. This is especially useful when references are incomplete, descriptions are inconsistent, or the reason for a difference is not obvious from the raw file.

AI can help finance users with:

• Creating derived columns using natural language
• Reviewing difficult open items
• Identifying likely reasons for unmatched transactions
• Suggesting possible next actions for investigation

The output remains reviewable and audit-friendly. If there is not enough evidence for a strong match, the record should remain unmatched rather than being forced into a weak match.

What finance teams see in the report

Once reconciliation finishes, Cointab presents a report dashboard that helps teams focus on exceptions instead of checking every row manually.

Fully matched

These are records where the identifiers and amounts match according to the configured logic.

Partially matched

These are records where the identifiers line up, but the amounts do not. This often points to deductions, timing differences, rounding, refunds, or incomplete settlement information.

Unmatched

These are records present on one side but not found on the other. For example, an order may appear in internal records but not in a Purplle-related report, or a bank credit may not map back to the expected settlement.

Skipped

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

Where manual review still matters

Some transactions need human review even after automated matching and AI analysis. Cointab supports manual match for exceptions that the system could not confidently resolve.

This is helpful when:

• A reference is missing
• A transaction spans multiple rows
• The partner file is incomplete
• A one-off exception needs finance review
• The business context is clear, but the data is not

Manual matches are clearly marked so the reconciliation history stays auditable.

Why reusable reconciliation matters for Purplle sellers

Most Purplle sellers do not want to rebuild the same reconciliation logic every month. Once the workflow is configured, the same setup can be reused for future periods with new files.

That matters because it reduces repeat work and keeps reporting consistent across periods. Teams can run monthly, quarterly, yearly, or custom-period reconciliations without recreating the structure each time.

Cointab can also support recurring automation through email, SFTP, or API-based data flow. That makes it easier to move from manual spreadsheet work to a controlled finance process.

A better fit for finance operations

A Purplle reconciliation workflow is often part of a broader finance process that includes sales tracking, settlement review, bank matching, return analysis, and audit preparation. Cointab is designed to support that broader workflow with clear file mapping, structured matching, exception visibility, and downloadable reports.

For finance teams, the practical benefit is simple: fewer spreadsheet dependencies, clearer exception handling, and a reusable reconciliation process that can be reviewed by the full team.

Common Purplle reconciliation questions

The following questions often come up when setting up marketplace reconciliation for Purplle sellers.