Fondy Payment Gateway Reconciliation Software

Cointab helps finance teams reconcile Fondy settlement data with internal sales, ERP, and bank records in a structured, reusable workflow. Instead of comparing exports manually in Excel, teams can upload files, map fields once, run reconciliation, review exceptions, and export audit-ready reports.

This is useful for eCommerce and payment-heavy businesses that need to understand which transactions were fully matched, partially matched, unmatched, or skipped. It also helps teams investigate refunds, deductions, missing settlements, and timing differences across systems.

How Fondy reconciliation works in Cointab

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

Side A: your records

Side A contains the records your business expects to be correct, such as:

• Website or order reports
• ERP exports
• Internal sales data
• Ledger or books data
• Receivable or settlement working files

Side B: Fondy records

Side B contains the external records received from Fondy, such as:

• Settlement reports
• Payout reports
• Refund-related reports
• Transaction exports

By comparing Side A and Side B, finance teams can identify which orders or payments were settled correctly and which items need review.

Common Fondy reconciliation scenarios

Fondy reconciliation is often part of broader payment reconciliation and finance close workflows. Typical use cases include:

• Website orders vs Fondy settlement reports
• ERP sales vs Fondy payouts
• Bank statement vs Fondy settlement entries
• Sales report vs refund and deduction records
• Internal order data vs Fondy transaction exports

These workflows help teams understand whether the amount expected in the business system matches what was received or settled externally.

What Cointab matches and reports

Cointab's reconciliation engine applies structured matching logic to compare records across the two sides. It supports common finance matching scenarios such as one-to-one, one-to-many, many-to-one, and grouped comparison.

The report clearly separates:

• Fully matched transactions
• Partially matched transactions
• Unmatched transactions
• Skipped transactions

This makes it easier for finance teams to focus on exceptions instead of manually reviewing every row.

Fully matched

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

Partially matched

A partially matched record is one where the records appear related, but the amounts do not fully match. This is useful when a payment was short, overpaid, adjusted, or settled with a deduction.

Unmatched

An unmatched record exists on one side but not on the other. For example, an order may appear in the website report but not in the Fondy settlement file, or a settlement entry may appear in Fondy but not in the internal books.

Skipped

Skipped records are rows that were excluded because they were incomplete, invalid, duplicated, or not eligible for the configured reconciliation.

Supporting files and derived columns

Fondy reconciliation often needs more than two primary reports. Cointab lets teams upload supporting data to enrich or prepare records before reconciliation.

Examples include:

• Product master files
• Order metadata
• Fee or tax mapping files
• Customer or SKU reference files
• Lookup files for IDs, amounts, or statuses

Teams can also create derived columns using AI-assisted formulas. This is useful when the report needs a cleaned identifier, a net amount, or a value calculated from existing fields before matching.

Reconciliation workflow for Fondy reports

A typical workflow in Cointab looks like this:

1. Create a new reconciliation or reuse an existing Fondy workflow.
2. Upload the required Side A and Side B files.
3. Map key fields such as date, amount, and transaction identifier.
4. Add supporting files if enrichment is needed.
5. Create derived columns when business logic needs calculation.
6. Run reconciliation manually or on a schedule.
7. Review matched, partially matched, unmatched, and skipped records.
8. Download the Excel reconciliation report.
9. Push output to downstream systems through email, SFTP, or API if required.

Because the setup is reusable, teams do not need to rebuild the same Fondy reconciliation every month.

Exception handling for Fondy settlements

Fondy reconciliation usually involves reviewing differences such as:

• Missing transaction references
• Refunds or cancelled orders
• Settlement timing differences
• Deductions or fees
• Amount differences between systems
• Records present in one report but missing in another

Cointab helps teams isolate these exceptions quickly so they can follow up with operations, accounting, or partner teams.

When structured rules are not enough, AI can help analyze open items conservatively. If the evidence is weak, the item remains unmatched so the report stays audit-friendly.

Why finance teams use Cointab for Fondy reconciliation

Finance teams need more than a spreadsheet comparison. They need a repeatable process that is easy to review and simple to explain during close or audit preparation.

Cointab supports that by providing:

• Reusable reconciliation setup
• Structured field mapping
• Support for multiple reports and supporting files
• Clear exception categories
• Manual match options for special cases
• Downloadable Excel reports
• Team-based workspace access
• Reconciliation history for future reference

This makes it easier to manage recurring payment reconciliation without rebuilding logic every period.

Reporting and review

After reconciliation is complete, teams can review the report dashboard to see the run status, transaction-level results, and reconciliation summary. Filters help users drill into specific records, compare open items, and review the details behind a mismatch.

The output is designed for finance review, partner follow-up, and audit readiness.

Fondy reconciliation for recurring finance operations

For businesses that use Fondy regularly, reconciliation should be part of a repeatable finance workflow rather than a manual month-end task. Cointab can be used for scheduled runs, recurring file handling, and consistent report generation so the same setup can be used again for future periods.

That makes Fondy reconciliation easier to manage across daily, weekly, or monthly finance operations, especially when teams work with high volumes of payments, settlements, and adjustments.