Fondy Payment Gateway Reconciliation with Cointab

Cointab helps finance teams reconcile Fondy payment gateway data against internal sales, ERP, refund, and bank records in one structured workflow. Instead of comparing spreadsheets manually, teams can upload files, map fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped transactions in an audit-ready report.

Why Fondy payment gateway reconciliation matters

Payment gateway reconciliation is more than matching a settlement file to a sales report. Finance teams also need to account for refunds, timing differences, deductions, missing references, and rows that do not appear in every system.

When Fondy is part of the payment flow, teams often need to compare:

• website or order records against Fondy settlements
• Fondy settlement reports against ERP or books data
• Fondy payout or settlement data against bank statements
• sales records against refund reports and adjustment files

Doing this manually in Excel can be repetitive and hard to audit. Formulas may break, file formats may vary, and exception handling often depends on who prepared the report.

How Cointab structures Fondy reconciliation

Cointab uses a Side A and Side B model so finance teams can clearly define what is expected and what is received.

Users can upload CSV, XLS, or XLSX files, select the header row, and map required columns such as:

• transaction date
• amount
• order ID
• transaction ID
• payment reference
• settlement ID
• bank reference

Multiple files can be used on either side when the reports follow the same configured structure.

Common Fondy reconciliation workflows

Cointab supports several practical reconciliation setups for teams that use Fondy in their payment flow.

Website sales vs Fondy settlement

This is a common payment reconciliation workflow for eCommerce and D2C teams.

It helps identify:

• orders that were paid and settled correctly
• underpaid or overpaid transactions
• payments recorded in Fondy but missing from the website report
• website orders that do not appear in the settlement file

Fondy settlement vs ERP or books

Finance teams often need to reconcile external settlements with internal accounting records.

This workflow helps identify:

• settlement entries posted correctly in the ERP
• missing or duplicate accounting entries
• amount differences between settlement and books
• transactions that still need review before close

Fondy settlement vs bank statement

Payment gateway settlements do not always land in the bank on the same day or in the same amount as the original order value.

This workflow helps compare:

• amounts received from Fondy against bank credits
• settlement timing differences
• missing deposits
• partial or unmatched entries that need follow-up

Website orders vs refund report

Refund reconciliation is important when cancelled or returned orders need to be matched against refund activity.

This workflow helps teams understand:

• which orders were refunded
• whether the refund amount matches the original transaction or settlement adjustment
• which refund records are still open or incomplete

Matching logic and exception handling

Cointab applies structured reconciliation logic before leaving any unresolved items for review.

The reconciliation engine supports:

• one-to-one matching
• one-to-many matching
• many-to-one matching
• many-to-many matching
• net-to-net comparison
• partial matching
• contra-style matching where relevant

This is useful when one Fondy transaction maps to multiple order rows, when multiple internal rows need to be grouped into one settlement entry, or when identifiers match but amounts differ.

After the structured rules run, the report clearly separates:

• fully matched records
• partially matched records
• unmatched records
• skipped records

What each status means

• Fully matched: identifiers and amounts align according to the reconciliation rule.
• Partially matched: the records appear related, but the amounts do not fully agree.
• Unmatched: the record exists on one side but not the other.
• Skipped: the row was excluded because it was incomplete, invalid, duplicated, or otherwise unusable.

If a transaction still needs review, users can manually match it when they know the business context.

Supporting data and derived columns

Fondy reconciliation often works better when supporting data is used to enrich the primary reports.

Supporting data can include:

• product master data
• order metadata
• customer or vendor master files
• fee rate files
• marketplace mapping files
• tax or GST mapping files
• delivery partner reference files

Cointab also supports derived columns on both sides. These are calculated fields created from existing data and can be generated with AI assistance.

Typical examples include:

• clean order ID
• normalized transaction ID
• net amount
• refund amount as a negative value
• amount after fee
• combined reference field
• delivered payment amount

This helps teams standardize messy inputs before reconciliation and reduces dependence on manual Excel formulas.

Reusable reconciliation for recurring Fondy runs

Once a Fondy reconciliation is configured, it can be reused for future periods without rebuilding the setup each time.

That means finance teams can keep the same workflow for:

• monthly reconciliation
• quarterly reconciliation
• yearly reconciliation
• custom settlement periods
• running reports across multiple periods

If a file is missed, users can upload it later under the same reconciliation and refresh the report. That is useful when payment gateway, bank, or internal files arrive late.

Automation for daily or periodic reconciliation

For recurring finance operations, Cointab can automate data input and reconciliation runs through:

• email
• SFTP
• API

A Fondy reconciliation can be scheduled to run daily, weekly, monthly, or after all expected files are received. Once the data is loaded, the system can validate the format, run the reconciliation, and prepare the report automatically.

Cointab can also push output back to downstream systems through email, SFTP, or API. This helps finance teams keep accounting, BI, and internal reporting systems updated with reconciled output.

What the reconciliation report shows

After the run is complete, finance teams can review a report dashboard with transaction-level detail.

The report typically includes:

• summary totals
• fully matched summary
• partially matched summary
• unmatched summary
• skipped summary
• transaction tables with filters
• detailed matched views
• downloadable Excel reports
• run history in the dashboard

This makes it easier to review exceptions, support month-end close, and keep an audit trail of what was matched and what still needs attention.

Team-based reconciliation workspaces

Cointab supports shared workspaces so finance teams can work in one place instead of passing spreadsheets around.

That is useful for:

• accounts teams
• reconciliation analysts
• finance managers
• controllers
• audit teams

Shared access, roles, and history help teams maintain visibility into who ran a reconciliation, which files were used, and what changed between runs.

Fondy reconciliation in practice

For finance teams, the value of a Fondy reconciliation workflow is simple: compare the right records, review the exceptions clearly, and reuse the same setup for the next period.

That helps reduce manual spreadsheet work, improve consistency, and make settlement and payment reconciliation easier to manage across internal systems and external partner data.