Export Reconciliation Data and Reports in Cointab

Cointab helps finance teams export reconciliation results in a clear, audit-friendly format. After a reconciliation run is completed, users can review matched, partially matched, unmatched, and skipped transactions, then download the report for internal review, audit support, or partner follow-up.

For recurring workflows, Cointab can also deliver reconciliation output through email, SFTP, or API so finance and operations teams do not need to manually move files every time.

What you can export

Cointab export output is designed for day-to-day finance operations and period-end review. Typical exports include:

Fully matched transactions
Partially matched transactions
Unmatched transactions
Skipped records
Open items that still need review
Exception-level details for follow-up
Final reconciliation summaries

These exports help teams see not just the final status, but also the transaction-level detail behind each result.

Why export matters in reconciliation workflows

Reconciliation is not complete when the matching engine finishes. Finance teams still need to:

review open items
share results with stakeholders
keep an audit trail
follow up on missing files or incomplete data
update internal systems with final outputs

A structured export makes this easier because the same reconciliation result can be reused for reporting, audit support, and operational review.

How export works in Cointab

The standard workflow is simple:

Upload the Side A and Side B files or configure automated input.
Map the required fields such as date, amount, and identifiers.
Run reconciliation manually or on a schedule.
Review the reconciliation report.
Open the matched, partially matched, unmatched, or skipped views.
Download the Excel report or push the output to downstream systems.

This approach keeps the export tied to the actual reconciliation logic, so teams can trust what they are reviewing.

Export formats and delivery options

Cointab supports practical output delivery options for finance teams that handle repeated reconciliations.

Downloadable Excel report

Users can download an Excel report containing reconciliation results and transaction-level detail. This is useful for:

month-end close
internal review
audit preparation
partner escalations
stakeholder reporting

Automated output delivery

For recurring workflows, Cointab can send reconciliation output through:

email
SFTP
API

This is helpful when a team wants the reconciliation result to reach an ERP, accounting system, BI tool, reporting system, or internal finance workflow without extra manual steps.

What finance teams usually export

Different teams use exports in different ways.

Finance and accounting teams

Finance teams often export reconciliation output to support:

books vs bank review
payment reconciliation
settlement reconciliation
vendor reconciliation
customer statement review

eCommerce and marketplace teams

Operational finance teams may export:

sales vs payment gateway results
marketplace sales vs settlement results
COD delivery partner reconciliation outputs
return, fee, deduction, and settlement exception reports

Audit and compliance teams

Audit teams generally need exports that clearly show:

what matched
what did not match
what was skipped
why a record was excluded
who ran the reconciliation and when

Exporting exceptions clearly

One of the most useful parts of export is exception visibility. Cointab separates transaction groups so users can focus on what needs attention instead of reviewing every record manually.

Exports can help teams identify:

missing payments
underpayments or overpayments
settlement differences
unmatched invoices or receipts
late remittances
deductions, fees, refunds, or returns
file issues that caused records to be skipped

This makes reconciliation output easier to act on and easier to explain.

Reusable reporting for recurring reconciliations

Many finance workflows repeat every day, week, or month. Once a reconciliation is configured in Cointab, the same setup can be reused for future periods.

That means teams can:

use the same field mapping again
run the same matching logic again
export the same report structure again
automate the same delivery path again

This is especially useful when the same reports are needed across multiple periods, entities, partners, or business units.

Supporting data and calculated fields before export

Sometimes a report needs to be prepared before reconciliation results are exported. Cointab supports supporting data and derived columns to help finance teams clean and enrich records before export.

Examples include:

adding missing order or invoice details
looking up fee or tax information
combining reports before reconciliation
creating cleaned identifier fields
calculating net amounts or derived values

This helps ensure the exported result reflects the business logic the team actually uses.

Manual review before downloading

Cointab is designed so finance users can inspect the reconciliation outcome before exporting it. Users can:

filter transactions by status
inspect matched, partially matched, unmatched, and skipped records
manually match records when needed
refresh the report if a missed file is uploaded later

This makes the export process more controlled and audit-friendly than a raw spreadsheet dump.

Where export fits in the finance process

Reconciliation export is usually part of a larger finance workflow:

collect source files
map fields once
run reconciliation
review exceptions
export the report
share output with internal teams or downstream systems
retain the run in the dashboard for later reference

In practice, this helps finance teams reduce repeat spreadsheet work and keep reporting consistent across periods.

Common export use cases

Bank vs books

Finance teams export matched and unmatched entries to support cash visibility and period-end review.

Payment reconciliation

Teams export gateway and settlement differences to track missing payments, deductions, refunds, and reversals.

Marketplace reconciliation

Brands export sales, settlement, and return differences to understand net collections and open exceptions.

Vendor reconciliation

Accounts payable teams export invoice and payment differences to resolve outstanding items with suppliers.

Customer reconciliation

Accounts receivable teams export receipt and invoice results to support collections and statement review.

Audit-ready reporting without manual rework

A good reconciliation export should tell the full story behind a set of numbers. Cointab keeps the report tied to the reconciliation workflow, so teams can review the data, download the result, and refer back to the same run later if needed.

That is useful for teams that need:

repeatable reporting
clear transaction status
reusable period-based reconciliations
a visible audit trail
fewer spreadsheet handoffs

What makes the export output useful

The best finance exports are not just data files. They are working reports that help teams answer questions quickly:

What matched?
What is still open?
What was skipped and why?
Which file or side is missing?
What needs manual review?
What should be sent to the next system?

Cointab’s export and delivery options are built around those operational questions.

FAQ

What kind of report can I export from Cointab?

You can export reconciliation results with matched, partially matched, unmatched, and skipped records, along with transaction-level detail for review.

Can exported reports be reused for future periods?

Yes. Once a reconciliation is configured, the same setup can be reused for future runs, and the report structure remains consistent.

Does Cointab only support manual downloads?

No. In addition to downloadable Excel reports, Cointab can deliver output through email, SFTP, or API for recurring workflows.

Can I export exceptions separately?

Yes. Users can review and export exception records such as unmatched, partially matched, or skipped transactions for follow-up and analysis.

What if a required file arrives late?

If a file was missed, it can be uploaded under the same reconciliation and the report can be refreshed to include the new data.