Purplle Marketplace Reconciliation

Cointab helps finance teams reconcile Purplle marketplace data across orders, sales, returns, payments, settlements, and bank entries. Instead of managing multiple Excel files and manual checks, users can upload reports, map fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped records in a structured report.

How Purplle reconciliation works in Cointab

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

• Side A is your internal or expected record, such as sales, orders, ledger entries, or payout expectations.
• Side B is the Purplle report or bank-side record, such as payment, settlement, or statement data.

This structure makes it easier to compare what your business expects to receive with what was actually reported by the marketplace or credited in the bank.

Reports commonly used for Purplle marketplace reconciliation

A typical Purplle reconciliation workflow may include one or more of the following reports:

• Order report to track order-level activity and references.
• Sales report to compare sales values, taxes, and discounts.
• Return report to account for cancellations, returns, and reversals.
• Payment report to check what Purplle has recorded as paid.
• Settlement report to review deductions, fees, and payout details.
• Bank statement to confirm that settlement amounts were actually credited.

Depending on the reconciliation objective, teams may use all of these reports together or focus only on the reports needed for a specific matching workflow.

Typical reconciliation flow for marketplace teams

A Purplle reconciliation setup in Cointab usually follows a simple workflow:

1. Upload the required files for Side A and Side B.
2. Map key fields such as date, amount, and identifiers.
3. Add supporting data if needed, such as SKU mapping, product master data, fee files, or lookup files.
4. Create derived columns when a clean amount or identifier needs to be calculated from existing data.
5. Run reconciliation manually or schedule it to run automatically.
6. Review the reconciliation report and investigate open items.
7. Download the Excel report for internal review, audit support, or partner follow-up.

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

What finance teams review in the report

Cointab separates the output into clear categories so teams can focus on exceptions instead of checking every row manually.

Fully matched

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

Partially matched

These are records where the identifiers match, but the amounts differ. This is useful for identifying deductions, fees, rounding differences, returns, or short payments that need review.

Unmatched

These are records that appear on one side but cannot be found on the other side. In a Purplle workflow, this may point to missing payments, missing settlement entries, delayed reporting, or internal record issues.

Skipped

These are rows that were excluded from reconciliation because of incomplete data, invalid values, duplicates, or another configured rule.

Why Purplle sellers need structured reconciliation

Marketplace finance teams often deal with multiple reports, changing settlement structures, and delayed payment cycles. Without a structured reconciliation process, it becomes difficult to see where money is missing, where deductions were applied, or whether the bank has received the expected payout.

A reusable reconciliation workflow helps teams:

• reduce repetitive Excel work,
• keep matching rules consistent,
• review exceptions faster,
• support month-end close more cleanly,
• maintain an audit trail of what matched and what did not,
• reuse the same reconciliation setup for future periods.

For recurring marketplace operations, this is especially useful because the same report structure is often processed month after month.

Payment and bank reconciliation together

Purplle reconciliation usually does not stop at the payment report. Finance teams often need to continue into bank reconciliation to confirm that settlements were actually credited.

Cointab helps teams compare settlement-related records with the bank statement so they can identify:

• payments that were expected but not received,
• amounts that do not match the settlement value,
• records present in the bank but missing from the marketplace-side report,
• items that require manual follow-up or correction.

This is useful when marketplace payouts are delayed, split, adjusted, or recorded differently across systems.

Supporting data and derived columns

Purplle reconciliation can become more accurate when supporting files are added to the workflow. These may include product masters, SKU mappings, fee rate files, order metadata, or mapping tables.

Users can also create derived columns when the source file does not contain the exact field needed for matching. For example, they may need to clean an order ID, calculate a net amount, or create a normalized reference before running reconciliation.

Cointab supports this by letting users define derived columns using AI-assisted formulas, while keeping the resulting logic reviewable.

Manual match and exception handling

Not every open item should be forced into an automatic match. When structured rules and AI cannot confidently match a transaction, users can review the exception and perform a manual match if the totals and business context support it.

This is especially helpful for one-off discrepancies, delayed partner files, or cases where identifiers are incomplete but the transaction can still be resolved with internal knowledge.

Reuse and automation for recurring workflows

Once a Purplle reconciliation is configured, teams do not need to rebuild it every month. They can reuse the same setup for future periods, upload the new files, and run the same workflow again.

For recurring operations, Cointab can also automate data input and output through email, SFTP, or API-based workflows. That makes the reconciliation process more consistent for finance teams that need regular reporting and faster exception handling.

Audit-ready reporting for finance teams

Cointab is designed to make reconciliation easier to review and easier to explain. The final report shows the full reconciliation status, transaction-level detail, and the records that need attention.

That gives finance and operations teams a practical view of what was matched, what remains open, and what action may be needed next.

Frequently asked questions

What reports can be used for Purplle marketplace reconciliation?

Teams typically use Purplle order, sales, return, payment, and settlement reports, along with bank statements when payout verification is required. Supporting data can also be added when it helps enrich the primary reports.

Can Cointab reconcile Purplle settlements with bank statements?

Yes. Purplle settlement data can be compared with bank statement entries to identify matched, partially matched, unmatched, or missing credit items.

What happens if a report is uploaded later?

If a file was missed during the original run, it can be uploaded under the same reconciliation and the report can be refreshed.

Can the same Purplle reconciliation setup be reused for future periods?

Yes. Once configured, the same workflow can be reused for monthly, quarterly, or custom periods without rebuilding the setup each time.

Does Cointab support manual matching for open items?

Yes. Users can manually match unresolved transactions when structured rules and AI do not produce a confident match.