CRED Marketplace Reconciliation for Finance Teams

CRED marketplace reconciliation helps finance teams match internal order records with external payment, refund, settlement, and fee data from the marketplace. For sellers using CRED Marketplace, the reconciliation process typically involves verifying that sales, deductions, refunds, and net settlements agree with the company’s own OMS, ERP, or accounting records.

Cointab provides a structured reconciliation workflow for this process. Teams can upload the relevant reports, map fields once, run reconciliation, review exceptions, and export audit-ready Excel reports. The same setup can be reused for future periods, which reduces repeat spreadsheet work and makes marketplace reconciliation easier to manage.

How CRED marketplace reconciliation works

Cointab uses a Side A and Side B model:

In a CRED marketplace workflow, finance teams usually want to answer a few core questions:

• Were all orders reflected in the marketplace reports?
• Were refunds and deductions applied correctly?
• Do the settlement amounts match the expected net amount?
• Were fees charged according to the agreed rate card?
• Which records are fully matched, partially matched, unmatched, or skipped?

Cointab is built to answer these questions in a reviewable, finance-friendly way.

Typical files used in the workflow

A CRED marketplace reconciliation setup often uses one or more of the following files:

• CRED payment report
• CRED refund report
• CRED settlement or payout report
• OMS export such as EasyEcom or Shopify
• Fee card or rate card
• Optional supporting data such as product master, store mapping, order metadata, or customer mapping files

Supporting data is useful when the finance team needs to enrich the primary reports before reconciliation. For example, a lookup file can help add missing order details, normalize identifiers, or calculate fee-related values.

What Cointab compares

A marketplace reconciliation workflow can include several layers of checking.

Sales and order matching

Cointab compares internal order data from Side A against the records received from CRED on Side B. This helps identify:

• Orders found in both systems
• Orders present in the OMS but missing in CRED
• Orders present in CRED but missing in the OMS

Payment and settlement matching

Finance teams also need to confirm that settlement amounts align with the expected payable amount after deductions, refunds, and adjustments. Cointab can compare net values and flag differences when amounts do not match exactly.

Fee verification

If the seller has an agreed fee structure, Cointab can use the fee card or rate card as supporting data to calculate expected charges and compare them with the fees actually applied by the marketplace.

This helps teams review:

• Correctly charged fees
• Overcharged fees
• Undercharged fees

Reconciliation workflow in Cointab

The workflow is designed to be simple for finance users while still supporting detailed review.

1. Create a new CRED marketplace reconciliation.
2. Upload the required Side A and Side B files.
3. Map important fields such as date, amount, and transaction reference.
4. Add supporting data if it is needed for lookups or calculations.
5. Create derived columns when the business logic requires a calculated value.
6. Run the reconciliation.
7. Review matched, partially matched, unmatched, and skipped records.
8. Download the report for internal review or audit support.

Cointab also shows live progress while reconciliation is running, which is useful when the files are large or when multiple reports are involved.

How exceptions are organized

The reconciliation report separates records clearly so finance teams can focus on exceptions instead of reviewing every row manually.

Fully matched

These are records where the identifiers and amounts match according to the configured logic. They represent transactions that are aligned across both sides.

Partially matched

These are records where the identifiers match, but the amounts differ. This is useful when an order is related to a marketplace record, but the settlement value, fee, or refund amount needs review.

Unmatched

These are records present on one side but not found on the other. In a CRED marketplace workflow, this may indicate a missing report, a delayed settlement, an incomplete upload, or a record that needs investigation.

Skipped

Skipped records are not included in reconciliation because of missing required data, invalid values, duplicates, or other file issues. Keeping skipped rows visible helps finance teams understand what was excluded and why.

Handling difficult open items

Cointab applies structured matching logic first. If open transactions remain, AI can help analyze them conservatively and explain possible reasons for the mismatch.

This is useful when:

• References are inconsistent
• Descriptions are unstructured
• Identifiers are incomplete
• Multiple records need to be grouped before comparison
• A fee, refund, or deduction needs a closer review

When the system cannot confidently match a record, it keeps the item open rather than forcing a weak match.

Manual match and missed files

Some marketplace exceptions need human review. Cointab supports manual matching for cases where the finance team knows the business context and the totals add up correctly.

If a required file arrives late, the missed file can be uploaded under the same reconciliation and the report can be refreshed. This is important for real finance operations, where marketplace, payout, or refund files may arrive after the initial run.

Reuse for future periods

Once the CRED marketplace reconciliation is configured, the same setup can be reused for future months, quarters, or custom periods.

That means the team does not need to rebuild mappings and rules each time. They can simply:

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

For recurring marketplace operations, this creates a consistent process that is easier to audit and easier to hand over within the finance team.

Automation and team collaboration

Cointab can also support recurring workflows through email, SFTP, or API-based data input. This is helpful when the same CRED marketplace files are received regularly and the team wants to reduce manual uploads.

Once reconciliation is complete, the output can also be pushed back to internal systems through email, SFTP, or API so downstream teams can work with matched, unmatched, and exception data.

Team workspaces, roles, and reconciliation history make it easier for finance, accounting, and marketplace operations teams to collaborate in one shared environment instead of passing Excel files around.

What finance teams get from the report

The final reconciliation report is designed for practical finance review. It includes:

• Summary counts for matched, partially matched, unmatched, and skipped records
• Transaction-level tables
• Filters for deeper analysis
• Exception review
• Manual match history
• Downloadable Excel output

This makes the reconciliation useful for month-end review, partner follow-up, and audit preparation.

When a custom reconciliation is the better fit

CRED marketplace reconciliation is typically handled as a custom reconciliation because each seller may have a different OMS, rate card, file layout, and reporting structure.

A custom setup is helpful when the business needs to:

• Reconcile multiple CRED files together
• Compare CRED data with OMS or ERP exports
• Use supporting files for lookups or calculations
• Create derived amount or identifier columns
• Apply business-specific matching rules

That flexibility makes the workflow suitable for finance teams that need control, visibility, and repeatability across periods.