Flexible Input Format for Reconciliation

Flexible input format matters when finance teams reconcile data from different systems, partners, and periods. In practice, reports rarely arrive in one perfect template. One file may come from an ERP export, another from a payment gateway, and another from a marketplace settlement report. A reconciliation platform needs to handle those differences without forcing the team to rebuild the workflow every time.

Cointab supports a structured reconciliation setup where users upload files, map fields, and run reconciliation in a repeatable way. Instead of manually converting reports into a single spreadsheet layout, teams can work with the files they already receive and configure how each report should be read.

Why flexible input format matters

A rigid input format creates avoidable work for finance teams. Before reconciliation even begins, someone has to clean files, rename columns, adjust dates, combine sheets, or copy data into a template. That slows down month-end close, increases the chance of errors, and makes the process harder to audit.

A flexible input format helps teams:

• accept source files in supported spreadsheet formats without reworking the entire workflow
• map the right columns once, then reuse the setup for future periods
• keep Side A and Side B data aligned even when partner reports differ in structure
• reduce manual spreadsheet preparation and formula maintenance
• make the reconciliation process easier to review and explain

This is especially useful for payment reconciliation, bank reconciliation, marketplace settlement reconciliation, vendor reconciliation, and customer reconciliation, where the underlying business logic is consistent but the incoming reports may vary.

What Cointab supports

Cointab is designed around a practical finance workflow rather than a hard-coded file template. Users can upload supported files, configure the required fields, and reconcile records based on the data structure that fits the business process.

Typical setup includes:

• uploading CSV, XLS, or XLSX files
• selecting the header row
• mapping date, amount, and identifier columns
• uploading multiple files under the same configured report format
• using supporting data for lookups, enrichment, or preparation
• creating derived columns when a field needs to be calculated or normalized before reconciliation

This approach works well when one business process uses several reports across different systems, such as sales reports, payment gateway reports, settlement files, bank statements, vendor statements, or ERP exports.

How flexible input format works in the reconciliation flow

Cointab keeps the workflow clear and repeatable.

1. The user starts a new reconciliation in a team workspace.
2. The user selects a popular reconciliation or creates a custom reconciliation.
3. Side A and Side B files are uploaded.
4. Required fields such as date, amount, and identifiers are mapped.
5. Optional supporting data is uploaded if needed.
6. Derived columns can be created using formulas, including AI-assisted formula generation.
7. The reconciliation is run manually or on a schedule.
8. Cointab applies structured matching logic and analyzes remaining open items.
9. The user reviews matched, partially matched, unmatched, and skipped transactions.
10. The report can be downloaded in Excel format for audit and follow-up.

This flow is designed to be reusable. Once configured, the same reconciliation setup can be used again for the next period without rebuilding the process from scratch.

Why this is better than a single-template workflow

When a platform only accepts one fixed template, finance teams often spend time adapting their work to the software. Flexible input format reverses that burden. The software adapts to the reconciliation process instead.

That creates several advantages:

Less manual file conversion

Teams can work with source files closer to their original format. That reduces copy-paste steps, formula drift, and the risk of introducing errors during preprocessing.

Better compatibility with real finance operations

Internal records, partner statements, and external reports do not always look the same. Flexible mapping makes it possible to compare records even when the columns or naming conventions differ.

Easier reuse across periods

Once the file structure is configured, future reconciliation runs can follow the same pattern. That is helpful for recurring work such as daily settlement checks, monthly close, and recurring partner reconciliations.

Cleaner exception handling

If a file does not match the configured structure, Cointab can reject it with a clear error message. That helps teams identify missing or incorrect columns early instead of discovering the issue after reconciliation has already started.

Stronger audit trail

Because the setup is structured and visible, finance teams can review what was uploaded, what was mapped, what matched, and what remained open. That supports internal review and audit readiness.

Flexible input format for popular and custom reconciliations

Cointab supports both popular reconciliations and custom reconciliations.

Popular reconciliations are useful when the source reports follow a standard structure, such as:

• sales vs payment gateway reconciliation
• bank vs books reconciliation
• marketplace sales vs settlement reconciliation
• COD delivery partner reconciliation

Custom reconciliations are useful when the business has a unique workflow or multiple reports to compare. For example, a finance team may need to reconcile internal sales data against several payment providers, or compare a vendor ledger against a vendor statement.

In both cases, flexible input format makes the setup practical. Users can define how the reports should be read, which columns matter, and how the records should be compared.

Support for matching, enrichment, and calculations

Flexible input format is not only about file upload. It also supports the preparation steps that usually happen before reconciliation.

Cointab can help teams:

• use supporting data to enrich a report before matching
• build derived columns from existing fields
• normalize identifiers such as order IDs, invoice numbers, transaction references, or UTRs
• calculate net amounts, fee-adjusted amounts, or negative refund values
• prepare cleaner inputs for structured transaction matching

This is useful when the reconciliation depends on a business rule that is not stored directly in the source file. For example, a team may need to derive a payment amount only when an order is delivered, or calculate an adjusted settlement amount after fees.

What finance teams gain

A flexible input format helps finance teams move from spreadsheet maintenance to a controlled reconciliation workflow.

The practical benefits are:

• faster setup for recurring reconciliations
• fewer manual transformations before reconciliation
• more consistent handling across team members
• better visibility into matched, partially matched, unmatched, and skipped records
• easier audit review and follow-up
• less dependency on one-off spreadsheet logic

For teams that reconcile high-volume or multi-source data, this can make a meaningful difference to month-end close, exception management, and reporting discipline.

A more scalable way to reconcile

Flexible input format is valuable because reconciliation data is rarely static. File structures change, partner reports evolve, and finance teams often need to compare different data sources over time. A reusable workflow that accepts supported file formats, maps the needed fields, and keeps the logic transparent is easier to maintain than a hard-coded process.

Cointab is built for that kind of workflow. It helps finance teams upload files, map fields once, run reconciliation, and review results in a structured way that can be repeated across periods and business use cases.

Frequently asked questions

What file formats does Cointab support for reconciliation?

Cointab supports CSV, XLS, and XLSX files for reconciliation workflows.

Can I upload different file structures for different periods?

Yes. You can configure a reconciliation once and reuse it for future periods, as long as the required report structure is followed.

What happens if a file is missing a required column?

The file can be rejected with a clear validation message so the issue is visible before reconciliation continues.

Can I use supporting files that are not directly reconciled?

Yes. Supporting data can be used for lookups, enrichment, merging, and calculations before reconciliation.

Is flexible input format useful for custom reconciliations?

Yes. It is especially useful when Side A and Side B reports come from different systems or have different structures that still need to be matched in a repeatable way.