Cred Marketplace Reconciliation

Cointab helps finance teams reconcile Cred Marketplace data against internal records by comparing orders, payments, refunds, settlements, and fee charges in one structured workflow. Instead of managing separate spreadsheets for each report, teams can upload files once, map the required fields, run reconciliation, and review matched and open items in an audit-friendly report.

This use case is especially useful for sellers and finance teams that need to verify whether Cred Marketplace has paid the correct net amount, whether refund adjustments have been applied correctly, and whether fees match the agreed rate card or contract terms.

What gets reconciled in a Cred Marketplace workflow

A typical Cred Marketplace reconciliation usually compares the business's internal records with external marketplace files.

Side A: your internal records

Side A contains the records your business expects to be correct. For this use case, that may include:

• OMS exports
• Sales or order reports
• ERP or books data
• Internal settlement working files
• Refund or returns data
• Rate card or expected fee calculation files

Many teams use internal exports from systems such as EasyEcom or Shopify when those files represent the source of truth for orders and sales.

Side B: Cred Marketplace records

Side B contains the records received from the marketplace or related external files. For this workflow, that may include:

• Cred payment files
• Cred refund files
• Cred settlement or payout data
• Cred fee or charge cards
• Reference files used to explain deductions or adjustments

How the reconciliation workflow works

Cointab follows a repeatable Side A / Side B setup that finance teams can reuse for each period.

1. Upload the required files for Side A and Side B.
2. Map fields such as date, amount, order ID, transaction ID, or settlement reference.
3. Optionally combine payment and refund files into a master view.
4. Use supporting data if a lookup or enrichment step is needed.
5. Run reconciliation manually or on a schedule.
6. Review fully matched, partially matched, unmatched, and skipped records.
7. Download the Excel report for review, audit, or follow-up.

This structure keeps the process transparent. Finance users can see exactly what data was used, what logic was applied, and where differences remain.

Payment and refund reconciliation

For marketplace operations, payment and refund checks are usually the first layer of review.

Cointab can help teams compare:

• Order value in the OMS vs amount received from Cred
• Refunds recorded internally vs refund lines reported by Cred
• Net settlement values after refunds and deductions
• Missing settlement entries or missing payment references

If the order ID or transaction reference matches but the amount differs, the record may appear as a partial match. That gives finance teams a clear starting point for investigating deductions, reversals, refunds, or rounding differences.

Fee verification and charge checking

A second important part of this use case is fee verification.

Cred Marketplace may deduct fees before settling the net amount with the seller. Cointab can compare the expected fee calculation against the fee charged in the marketplace file.

Typical fee review outputs include:

• Correctly charged
• Overcharged
• Undercharged

This helps finance teams confirm whether the marketplace charges align with the rate card or expected commercial terms. If a fee differs, the open item is visible in the report so the team can review the charge, deduction, or adjustment in context.

Common reconciliation outcomes

Cointab separates transaction statuses clearly so teams can focus on exceptions instead of checking every row manually.

Fully matched

A fully matched record is one where the relevant identifier and amount align according to the configured reconciliation logic.

Partially matched

A partial match means the records appear related, but the amounts do not align exactly. This is useful when an order matches by reference but the settled amount differs because of a refund, fee, or adjustment.

Unmatched

Unmatched records are present on one side but not found on the other. In a Cred Marketplace workflow, that may mean:

• An OMS order is missing from Cred data
• A Cred payment appears without a corresponding internal order
• A refund exists on one side but not the other
• A fee or settlement line cannot be traced to an internal record

Skipped

Skipped records are rows that were not included in reconciliation because of missing data, duplicates, invalid values, or rule-based exclusions. Keeping skipped items visible helps finance teams understand what was left out and why.

Supporting data and derived columns

Cred Marketplace reconciliation often needs supporting data to make matching easier.

Supporting files may include:

• Product master data
• Order metadata
• SKU mapping files
• Fee rate files
• Return reports
• Store or channel mapping files

These files are not reconciled directly. They are used to enrich or prepare the primary data before matching.

Cointab also supports derived columns. Finance users can create calculated fields from existing data, and AI can help generate Excel-style formulas from plain-language instructions. That is useful when the matching logic depends on a cleaned order ID, a net amount, or a normalized reference field.

AI support for open items

After structured matching is complete, remaining open items can be reviewed with AI assistance.

This is helpful when references are inconsistent, descriptions are messy, or a business rule is not obvious from the file alone. AI can help analyze why a record may be unmatched and suggest possible next steps, while keeping the result reviewable and audit-friendly.

If the evidence is not strong enough, the record remains unmatched rather than being forced into a weak match.

Manual match and missed file handling

Some finance cases still require human review. Cointab includes a manual match option for items that the system cannot confidently match.

This is useful when:

• A file arrives late
• A partner report is incomplete
• A one-off adjustment needs to be matched manually
• The team has business context that the system should not assume

If a required file was missed, it can be uploaded under the same reconciliation and the report can be refreshed. That is important in real finance workflows, where marketplace files, refund files, or supporting reports often arrive at different times.

Why teams use Cointab for Cred Marketplace reconciliation

Cointab is built to reduce recurring spreadsheet work while keeping the reconciliation process clear and auditable.

For Cred Marketplace workflows, that means teams can:

• Reuse the same setup for each period
• Keep reconciliation rules consistent
• Review matched and open items in one place
• Download audit-ready Excel reports
• Track who ran the reconciliation in a shared workspace
• Automate recurring runs when data arrives through email, SFTP, or API

This makes the process more practical for month-end close, partner settlement review, and ongoing finance operations.

Reconciliation reports and dashboard visibility

Once a run is complete, Cointab provides a report view with transaction-level detail and summary counts.

Typical report views include:

• Total summary
• Matched summary
• Partially matched summary
• Unmatched summary
• Skipped summary
• Filters for deeper review
• Detailed transaction tables
• Downloadable Excel output

Past runs remain available on the dashboard for future reference, which helps teams review prior periods without rebuilding the same workflow again.

Flexible setup for recurring Cred Marketplace reviews

The same reconciliation can be used for monthly, quarterly, yearly, or custom periods. Once the workflow is configured, future runs usually need only the new files and the selected period.

That makes it easier to keep marketplace settlement checks, refund reviews, and fee verification under control without repeating the setup from scratch each time.

FAQ

What files are usually needed for Cred Marketplace reconciliation?

Most workflows use internal OMS or books data on Side A and Cred payment, refund, settlement, and fee files on Side B. Supporting files can also be added if lookup or enrichment is required.

Can payments, refunds, and fees be reviewed in the same workflow?

Yes. Cointab can compare payment, refund, and fee-related records in one reconciliation setup, so the finance team can review net settlement and charge differences together.

What happens if a Cred file arrives late?

You can upload the missed file under the same reconciliation and refresh the report. This helps teams handle delayed partner files without rebuilding the workflow.

Can the same setup be reused for future periods?

Yes. Once a Cred Marketplace reconciliation is configured, it can be reused for later periods with the same file structure and rules.

How are exceptions shown?

Exceptions are separated into matched, partially matched, unmatched, and skipped records. This helps finance teams focus on open items and review differences in context.