Convert KBC Bank Statement to Excel (3 Methods)

You have three practical ways to get KBC statement data into Excel: export CSV from KBC Reach, convert a CODA file through accounting software or a CODA converter, or extract rows from a PDF statement with AI. Each method handles Belgian-specific requirements differently, particularly when it comes to preserving OGM-VCS structured communication references and managing Dutch/French bilingual headers.

KBC's primary electronic export format for accounting is CODA (Coded Statement of Account), a structured banking format mandated by the Belgian banking sector. Unlike banks that offer direct CSV downloads, KBC only provides CSV through KBC Reach, the business banking platform. Retail customers on KBC Touch or KBC Mobile receive PDF statements instead. This means most KBC users need a conversion step to get their transaction data into Excel.

With 84% of Belgians now preferring digital payments over cash according to Febelfin's 2025 Digital Payments Barometer, transaction volume through digital channels continues to grow, and so does the need to get that data into spreadsheets for reconciliation and bookkeeping.

KBC Statement Exports: What You Get from Reach, Touch, and Mobile

Choose the method by platform: KBC Reach users should start with CSV or CODA exports; KBC Touch and KBC Mobile users usually need PDF extraction unless CODA access is enabled for accounting software.

KBC Reach is the business banking portal, and it offers the broadest set of export formats. From Reach, you can download your transaction data as CSV, CODA, or XML (ISO 20022 format). The CSV export is your most direct path to Excel: you can open the file directly in Excel or use Excel's data import wizard to control how columns, delimiters, and date formats are parsed. If you have access to KBC Reach, this is the fastest route with no third-party tools required. Keep in mind that Reach is KBC's business banking platform and is not available to all retail customers.

KBC Touch, the online banking interface for both retail and business customers, is more limited. Statement downloads are primarily available as PDF files. CODA file access may be available if your account has been configured for accounting software integration, but there is no direct CSV export option. KBC Mobile follows the same pattern: you can search up to 10 years of transaction history, but exports are PDF only. For most Touch and Mobile users, getting transaction data into a spreadsheet means converting a PDF or processing a CODA file.

The practical summary: if you are on KBC Reach, download the CSV and open it in Excel. If you use KBC Touch or KBC Mobile, you will need to convert either a PDF statement or a CODA file using one of the two methods covered later in this article.

This is not unique to KBC. BNP Paribas Fortis customers face similar limitations, as our guide to BNP Paribas Fortis statement conversion methods details.

---

Converting KBC CODA Files to Excel

If you have downloaded statement data from KBC through Reach or Touch, there is a good chance you are looking at a CODA file rather than a familiar CSV. Before converting it, it helps to understand what you are dealing with and why Belgian banks use this format in the first place.

CODA (Coded Statement of Account) is a standardized Belgian bank statement format defined by the Febelfin specifications. It is a structured text file, typically carrying a .cod extension, built for automated import into accounting software. Where a CSV file is human-readable columns and commas that you can open directly in Excel, a CODA file uses fixed-width fields and coded transaction types designed for machine parsing. If you try opening a raw CODA file in Excel, you will see rows of unintelligible alphanumeric strings rather than clean transaction data.

CODA is Belgium's standard electronic bank-statement format, so KBC CODA files are best converted with software that understands Febelfin's fixed-width structure and preserves fields such as OGM-VCS references.

For a format-level walkthrough, see the dedicated guide to converting CODA files to Excel. There are three practical routes:

1. Belgian accounting software. If you already use Exact Online, Winbooks, Bob50, or Octopus, you have the most direct path. These applications import CODA files natively because they were built around the Febelfin specification. Import your KBC CODA file, let the software parse the transactions, and then export the resulting data to Excel or CSV from within the application. Because the software already understands the CODA structure, field mapping is handled automatically.

2. Isabel 6. Larger businesses and accounting firms that manage multiple bank relationships often use the Isabel 6 multi-bank platform. Isabel 6 processes CODA files from all Belgian banks in a single interface and can export transaction data in spreadsheet-compatible formats. If you are already on Isabel for payment processing, using it for CODA conversion keeps your workflow consolidated.

3. Dedicated CODA converter tools. Standalone utilities exist that parse the fixed-width CODA format and output CSV or Excel directly, without requiring full accounting software. These are useful when you need the raw transaction data in a spreadsheet and do not want to route it through an accounting package first.

Whichever method you choose, verify that the conversion preserves structured data fields, particularly OGM-VCS payment references. A converter that flattens or truncates the structured communication field will cost you time downstream when you try to reconcile payments. This is covered in detail in the final section of this article.

---

Extracting Data from KBC PDF Statements Using AI

If your KBC statements exist only as PDFs downloaded from KBC Touch or KBC Mobile, there is no built-in export path to CSV or structured data. You are left with a formatted document designed for reading, not for spreadsheets. Manually retyping transactions is error-prone and impractical beyond a handful of rows.

For PDF-only statements, upload the statement, specify the transaction fields you need, and export the parsed rows to Excel.

With Invoice Data Extraction, you can extract data from bank statements with AI in three steps:

1. Upload your KBC PDF statement. The platform accepts native PDFs of any length, so multi-page statements covering a full quarter or year of transactions are handled as a single file. There is no need to split the document or process pages individually.

2. Prompt the AI with your extraction requirements. You describe what to extract in plain language. For a KBC bank statement, a prompt might look like this:

   "Extract the transaction date, value date, description, amount, and running balance from this KBC bank statement. Preserve the OGM-VCS structured communication references exactly as they appear. Use column headers in English."

   You can be as specific or as brief as you need.

3. Download the structured Excel file. The output is a properly typed .xlsx spreadsheet where dates are formatted as dates, amounts as numbers, and OGM-VCS references are preserved as text strings rather than truncated or reformatted by Excel's auto-detection.

The AI processes the full document and maintains transaction sequence across page breaks, producing a single consolidated spreadsheet regardless of how many pages your KBC statement contains. Each row in the output references its source page, so you can cross-check any value against the original PDF.

Use the prompt to specify counterparty names, debit/credit columns, OGM-VCS preservation, and bilingual header normalization. Save the prompt once the output matches your monthly reconciliation template.

Working across Belgian banks. The same extraction approach applies to PDF statements from other institutions. If you manage accounts at both KBC and Belfius, you can use a similar workflow for converting Belfius bank statements to Excel, adapting the prompt to each bank's statement format while producing a consistent output structure across all of them.

---

Preserving OGM-VCS References and Handling Bilingual KBC Statements

Every Belgian accountant knows the sinking feeling: you convert a batch of KBC statements, open the Excel file, and discover that your OGM-VCS structured communications have been mangled. The +++123/4567/89012+++ reference that should match an open invoice is now sitting in a cell as a bare number with its leading zeros stripped and its usefulness destroyed. Getting the conversion right for Belgian-specific data requires attention to three areas that generic guides never address.

Keeping OGM-VCS References Intact

The +++XXX/XXXX/XXXXX+++ format is Belgium's standard structured communication system for identifying payments against invoices, tax assessments, and other obligations. If your conversion process corrupts these 12-digit references, you lose the ability to match payments automatically. The most common failures are Excel interpreting the reference as a number (dropping leading zeros), stripping the +++ delimiters, or truncating the field entirely.

How you handle this depends on your source format:

• CODA files store OGM-VCS references in a dedicated structured field. The reference survives conversion as long as your tool or accounting software correctly maps that field to a text column in Excel. Verify the field mapping before processing a full batch.
• CSV exports from KBC Reach include the reference in the communication or description column. The risk here is at the Excel import stage. If you open the CSV directly, Excel may auto-format the reference. Import the file using Excel's data import wizard and set the communication column to Text format before loading.
• PDF statement extraction requires the conversion tool to recognize the +++XXX/XXXX/XXXXX+++ pattern within transaction descriptions and preserve it as a text string, not a numeric value. Any tool that strips special characters or applies number formatting will break these references.

For a deeper explanation of how the Belgian OGM-VCS structured communication system works and its role in payment workflows, we have a dedicated guide that covers the format in detail.

Dealing with Dutch and French Headers

KBC serves customers across Belgium's language regions, which means statement headers arrive in Dutch for Flemish accounts and French for Walloon and Brussels accounts. The field names differ: "Datum" versus "Date", "Bedrag" versus "Montant", "Mededeling" versus "Communication", "Rekeningnummer" versus "Numero de compte".

This becomes a practical problem when you manage multiple KBC accounts across language regions or consolidate statements from different clients. Merging two spreadsheets where one has "Bedrag" and the other "Montant" as the amount column creates inconsistency that breaks formulas, pivot tables, and import templates. A reliable conversion workflow should normalize these headers to a single consistent set of column names in the output, regardless of the source language. If your tool does not do this automatically, build a header mapping step into your process before combining data from mixed-language statements.

The same workflow also applies to CBC statements: CBC uses the same group infrastructure, CODA specification, and comparable statement layouts, so KBC/CBC accounts can share one conversion template.