Purplle Marketplace Fee Reconciliation

Purplle marketplace fee reconciliation helps sellers verify whether the fees charged on orders, settlements, and deductions match what was expected from internal records and agreed rate cards. Cointab gives finance teams a structured way to compare Side A and Side B data, calculate expected fees with supporting data, and review overcharged, undercharged, matched, unmatched, and skipped records in one workflow.

How Purplle marketplace fee reconciliation works

In a typical fee verification process, the seller compares internal sales or order records with Purplle payment or settlement data. Supporting files such as a rate card and SKU master help determine the expected commission or marketplace charge for each order line.

Cointab keeps this process transparent and reusable:

1. Upload the required reports for the selected period.
2. Map key fields such as date, amount, order ID, transaction ID, or SKU.
3. Add supporting data such as rate cards, product masters, or mapping files.
4. Create derived columns when a fee calculation needs cleaning, normalization, or formula-based logic.
5. Run reconciliation and review the results in a structured report.
6. Download the Excel output for review, audit, or partner follow-up.

Side A and Side B for marketplace fee verification

Cointab uses a clear Side A / Side B model so finance teams always know what is being compared.

Side A: your internal records

Side A contains the records the business expects to be correct. For Purplle fee reconciliation, this may include:

• Internal sales report
• Order report
• ERP export
• Books or ledger data
• SKU master
• Internal fee assumptions or rate card references

Side B: Purplle records

Side B contains the external records received from the marketplace. For fee verification, this may include:

• Purplle payment report
• Purplle settlement report
• Marketplace deductions or fee statements
• Refund or adjustment details
• Transaction-level remittance records

Supporting data

Supporting data is optional and not reconciled directly. It helps prepare or enrich the main reports before reconciliation. Common supporting files for marketplace fee workflows include:

• Rate card
• SKU master
• Product mapping file
• Category mapping file
• Fee rule file
• Reference data used for lookups or calculations

Why Purplle fee differences appear

Marketplace fees often differ from expectations because multiple business rules affect the final charge. A reconciliation workflow helps teams isolate the reason instead of checking every row manually in Excel.

Common reasons for differences include:

• Incorrect or outdated fee mapping
• SKU or category mapping gaps
• Missing order or settlement lines
• Refunds, cancellations, or returns
• Rounding differences
• Adjustments or deductions applied later
• Late files or incomplete reports
• Internal data that does not match the marketplace reference

Cointab helps teams identify whether the issue is a real fee difference, a missing file, a data quality problem, or an item that needs manual review.

Using derived columns for fee calculation

Marketplace fee review often depends on calculated fields. Cointab lets users create derived columns on both sides so the reconciliation logic can reflect real business rules.

Examples include:

• Expected commission fee
• Net amount after deductions
• Clean order ID
• Normalized SKU
• Amount after rounding
• Fee amount based on category or rate card logic

Users can create these columns using an AI-assisted formula builder. That helps finance teams express business logic in plain language and convert it into a reviewable Excel-style formula.

What the reconciliation engine matches

Cointab's reconciliation engine uses structured logic to compare records across sides. For marketplace fee verification, it can support:

• One-to-one matching
• One-to-many matching
• Many-to-one matching
• Many-to-many grouping
• Net-to-net comparison
• Contra and partial matching

The system can compare identifiers such as order ID, transaction ID, settlement ID, SKU, or payment reference. It can also match records where the identifier is spread across multiple fields or where the amount needs to be netted before comparison.

This is useful when a marketplace fee is tied to more than one transaction line, or when a single settlement line covers multiple orders or deductions.

How Cointab helps finance teams review exceptions

After structured matching is complete, Cointab separates the results into clear categories so teams can focus on exceptions.

Fully matched

The expected fee and the marketplace fee align according to the configured logic.

Partially matched

The record is related, but the amount does not align fully. This often points to a fee difference, rounding issue, or adjustment that needs review.

Unmatched

The record appears on one side but not the other. This may indicate a missing order, settlement line, refund entry, or reporting gap.

Skipped

The record was not included in reconciliation because it was incomplete, invalid, duplicated, or excluded by rule.

AI can also help review difficult open items by suggesting likely reasons for the mismatch and possible next actions. If the evidence is weak, the item remains unmatched so the audit trail stays conservative and reviewable.

Manual review and missed file refresh

Not every fee difference can be resolved automatically. Cointab supports manual matching for cases where the business context is known but the data is incomplete or inconsistent.

This is especially useful when:

• A reference field is missing
• A settlement file arrived late
• A one-off adjustment needs review
• The marketplace report format changed slightly
• The reconciliation team needs to confirm a business exception

If a required file was missed, users can upload it under the same reconciliation and refresh the report. That helps teams handle late reports without rebuilding the setup.

Why this workflow is useful for recurring marketplace reporting

Purplle fee verification is rarely a one-time task. Most finance teams need the same checks every period, with similar reports and matching logic.

Cointab is built for reuse:

• Configure the reconciliation once
• Reuse the setup for future periods
• Run it manually or on a schedule
• Automate input through email, SFTP, or API where needed
• Push reconciliation output back to internal systems when required

This reduces repeat Excel work and gives finance teams a consistent process for monthly close, partner follow-up, and audit preparation.

What the reconciliation report shows

Once the run is complete, the report dashboard provides a clear view of the fee verification result. Finance teams can review:

• Total summary
• Fully matched summary
• Partially matched summary
• Unmatched summary
• Skipped summary
• Transaction-level detail
• Filters for deeper analysis
• Downloadable Excel output

That makes it easier to investigate overcharges, undercharges, missing settlements, and open items without switching between spreadsheets.

A practical workflow for Purplle sellers

A typical Purplle fee reconciliation setup may include:

• Side A: internal sales or order report
• Side B: Purplle payment or settlement report
• Supporting data: rate card and SKU master
• Derived columns: expected fee and normalized identifiers
• Output: matched, partially matched, unmatched, and skipped records

This structure gives finance teams a repeatable way to verify fees, explain differences, and maintain audit-ready records for review.