Convert Belfius Bank Statement to Excel (3 Methods)

There are three ways to convert a Belfius bank statement to Excel: export CSV directly from Belfius Direct Net, convert a CODA file through your accounting software or a dedicated converter, or extract data from a PDF statement using an AI tool. Each method suits a different workflow, and each carries Belfius-specific quirks that generic guides overlook.

The most accessible option, the native CSV export, has a documented bug: for recurring transactions such as standing orders and direct debits, the mededeling (communication) column duplicates the transaction description instead of preserving the actual payment reference. Your reconciliation will fail for every affected transaction because the real communication data is missing.

Belfius (formerly Dexia Bank Belgium) is Belgium's largest retail bank by customer count and operates exclusively within Belgium. According to Febelfin's digital banking survey, 69% of Belgian banking users regularly check balances and transactions online, generating constant demand for reliable export and conversion workflows. Yet every format Belfius produces — CSV, CODA v2, PDF — reflects Belgian banking conventions that most conversion tools treat as edge cases or ignore entirely.

This guide covers all three conversion methods with the technical depth each one requires: the CSV export process and its column duplication bug, CODA v2 format structure and how to get it into Excel, and AI-based PDF extraction for archived or paper statements. Each section addresses OGM-VCS structured communication preservation, the detail most critical to Belgian accounting workflows and most frequently lost in conversion.

Export CSV from Belfius Direct Net

The fastest way to get Belfius transactions into a spreadsheet is the CSV export built into Belfius Direct Net, the bank's web platform. No extra tools required — just a browser and your login credentials.

Here is the export process:

Log in to Belfius Direct Net at belfius.be and navigate to your account overview.
Select the account you want to export and open the transaction history (rekeningoverzicht / historique du compte).
Set your date range. You can filter by predefined periods or enter custom start and end dates. Belfius typically makes 12–24 months of history available online.
Click the download or export icon and select CSV as the output format.
Save the file. It opens directly in Excel or any spreadsheet application.

The resulting CSV contains columns for date, counterparty name, account number, transaction amount, balance, transaction type, and communication fields — everything you would expect for reconciliation or import into accounting software.

The Mededeling Column Duplication Bug

Before you build any workflow around this CSV, you need to know about a documented formatting issue that affects the communication field.

For recurring transactions — standing orders, direct debits, and scheduled transfers — the "mededeling" (communication) column duplicates the content of the "transaction" column instead of containing the actual payment communication or reference number. Rather than showing the OGM-VCS structured communication code or the free-text message attached to the payment, it repeats the transaction type description.

This is not a one-off glitch. The bug is well-documented and has been referenced in open-source Belgian financial tooling that parses Belfius exports.

The practical impact is significant for accounting workflows. If you import this CSV into Excel, Exact Online, Yuki, or BOB50 and try to match payments using the communication field, every recurring transaction will carry incorrect communication data. Automated payment matching breaks. OGM-VCS code lookups against open invoices fail. Manual reconciliation becomes necessary for exactly the transaction types that should be easiest to match automatically — the predictable, recurring ones.

For one-off transfers, the CSV communication field works correctly. But if your account processes a meaningful volume of domiciliëringen (direct debits) or doorlopende opdrachten (standing orders), this bug turns a routine import into a manual cleanup exercise.

Belfius Direct Net vs. Belfius Mobile

Not all Belfius platforms offer the same export options. Belfius Direct Net (the web banking interface) provides both CSV and CODA file exports, giving you flexibility in how you pull transaction data. Belfius Mobile (the smartphone app) has more limited export capabilities and may not offer CSV or CODA downloads at all. If statement exports are part of your regular accounting workflow, you will need to use the web platform.

Watch for Bilingual Column Headers

Belfius generates CSV files with column headers matching your platform language setting — Dutch or French. A Dutch-language export uses headers like "Datum", "Bedrag", "Mededeling", and "Rekening tegenpartij". A French-language export uses "Date", "Montant", "Communication", and "Compte contrepartie".

The moment you automate anything — Excel templates, Power Query connections, accounting software import mappings — column name differences will break your workflow if someone on your team exports from a session configured in the other language. If your firm operates across Belgium's language communities — which aligns with Belgium's bilingual document requirements — standardize on one language setting for all Belfius exports, or build your import templates to handle both header sets.

One additional CSV gotcha: Belgian date formats (DD/MM/YYYY) can be silently misinterpreted by Excel depending on your system locale. A date like 05/03/2026 may become March 5th instead of May 3rd. Use Data > From Text/CSV import with explicit date format settings rather than double-clicking the file, especially if your Excel installation uses a non-European locale.

Convert a Belfius CODA File to Excel

If you work in Belgian accounting, you have almost certainly encountered CODA files. CODA (COded DAily) is the standardized electronic bank statement format developed by Febelfin, the Belgian Financial Sector Federation. Every Belgian bank — Belfius included — uses it as the primary machine-readable format for delivering transaction data. Unlike CSV exports or PDF statements, CODA was purpose-built for automated processing by accounting software.

Belfius provides CODA v2 files, the current version of the specification in use since April 2014. A CODA file uses a fixed-width record structure where each line type (identification, transaction, communication, new balance) follows a rigid character-position layout. This makes CODA files reliable for software ingestion but essentially unreadable if you open one in a text editor or try to paste it into a spreadsheet directly. The data is all there — account numbers, amounts, dates, counterparty details, structured communications — but extracting it requires parsing.

Two practical paths from CODA to Excel

Path 1: Through your accounting software. Most Belgian accountants and bookkeepers already use software that reads CODA natively. Exact Online, Yuki, BOB50, and Octopus all support direct CODA import as a standard feature. The typical workflow is straightforward: download the CODA file from Belfius Direct Net (available from the same export/download interface where you find the CSV option), import it into your accounting application, let it match and book the transactions, then export the relevant data to Excel from within the application when you need a spreadsheet view. This is the path of least resistance if your accounting stack already handles CODA — and for most Belgian practices, it does.

Path 2: Use a dedicated CODA-to-Excel converter. Standalone tools and online converters can parse the fixed-width CODA records and map them into spreadsheet columns — date, amount, counterparty name, counterparty account, communication, and so on. This approach makes sense when you need to analyze transactions outside your accounting system, perform ad hoc reconciliation against other data sources, or when you simply do not use accounting software with CODA import support.

When the CODA-to-Excel conversion actually matters

The need to convert a Belfius CODA file to Excel typically arises when you need a standalone spreadsheet for a client deliverable, when you are doing forensic-style transaction analysis that is easier in Excel than inside your accounting tool, or when a colleague or client sends you a .cod file and you lack the software to import it directly.

One significant advantage of the CODA path over Belfius's CSV export: CODA files preserve OGM-VCS structured communications correctly. The format was designed from the ground up with Belgian payment conventions as a core requirement, so structured communication references come through intact and properly formatted. If your work depends on accurate structured communication data — and in Belgian accounting, it frequently does — CODA is the more reliable source format for your Excel conversion.

Extract Data from a Belfius PDF Statement with AI

Belfius provides PDF bank statements in two ways: downloadable from Belfius Direct Net under the "Documents" section, and as periodic statements mailed or made available to account holders. These PDFs contain complete transaction data — dates, amounts, counterparty details, structured communications, running balances — but formatted for human reading, not for import into accounting software. Tables span multiple pages, transaction descriptions wrap across lines, and OGM-VCS codes sit embedded within free-text communication fields.

AI-powered extraction takes a fundamentally different approach than CSV export or CODA conversion. Instead of relying on a machine-readable data feed from Belfius, the AI reads the rendered PDF page the same way you would — identifying column headers, parsing transaction rows, and recognizing data types. It then structures that information into clean spreadsheet rows with correctly typed columns (dates as dates, amounts as numbers, text as text).

For Belfius users, the distinction is practical: because AI extraction works from the fully rendered document, it captures the actual mededeling/communication field as displayed on the statement — completely bypassing the column duplication bug present in the native CSV export. What you see on the PDF is what you get in your spreadsheet.

OGM-VCS preservation in AI extraction

For Belgian accounting workflows, the 12-digit OGM-VCS structured communication code (+++NNN/NNNN/NNNNN+++ format) is the primary key for matching payments to invoices. AI extraction correctly identifies these codes within Belfius statement communication fields and preserves them in their original format. This matters when reconciling against open invoices in Exact Online, Yuki, or BOB50, where a corrupted or missing structured communication breaks automatic matching. For deeper background on how these codes work, see our guide on the Belgian OGM-VCS structured communication format.

How to extract Belfius PDF statements with Invoice Data Extraction

AI-powered bank statement data extraction handles Belfius PDF statements through a three-step workflow:

1. Upload your Belfius PDF statements. Drag and drop one or multiple PDF files — the platform processes batches of up to 6,000 documents in a single job, so you can upload an entire year of monthly statements at once. Multi-page statements (common for business accounts with high transaction volumes) are processed accurately across all pages.

2. Tell the AI what to extract. Write a prompt specifying the fields you need. For Belfius statements, a prompt like this works well:

"Extract the transaction date, value date, description, counterparty name, amount, structured communication (OGM-VCS), and running balance from each transaction. Preserve OGM-VCS codes in +++NNN/NNNN/NNNNN+++ format."

You can save this as a reusable prompt in your prompt library for recurring Belfius extractions.

3. Download your structured output. The platform returns an Excel (.xlsx), CSV (.csv), or JSON (.json) file with each transaction on its own row. Every row includes a reference to the source file and page number, so you can trace any extracted value back to the original statement for audit purposes.

When AI extraction is the right choice

This method fills gaps the other two approaches cannot. Archived statements from periods no longer available in Belfius Direct Net's export interface — whether stored as downloaded PDFs or scanned paper statements — become usable data again. Statements received from clients or counterparties who bank with Belfius can be processed without needing access to their Belfius Direct Net account. And because the extraction works from the visual document, it handles bilingual Belfius statements (Dutch/French) without configuration — the AI recognizes transaction patterns regardless of the display language.

Preserving OGM-VCS Structured Communications Across Methods

The OGM-VCS structured communication (+++NNN/NNNN/NNNNN+++) is the reference code that links Belgian payments to invoices. If this code is corrupted or lost during statement conversion, automated reconciliation breaks and you are left matching payments manually. For accounts receivable matching, direct debit reconciliation, and automated payment allocation, OGM-VCS preservation is a non-negotiable requirement.

Here is how each method compares:

Method	OGM-VCS Integrity	Key Limitation
CSV export	Unreliable for recurring transactions	Mededeling bug replaces actual OGM-VCS codes with generic descriptions; non-recurring codes may need format verification after Excel import
CODA files	Preserved by design	OGM-VCS stored in a dedicated field with its own record type; most dependable source
AI PDF extraction	Captured from rendered document	Reads codes exactly as printed; not affected by CSV bug or CODA availability

If OGM-VCS accuracy is critical to your process — and for most Belgian accounting workflows, it is — the CSV export alone is insufficient. The mededeling duplication bug creates a data loss problem you will not notice until reconciliation fails: transactions appear to have communication data, but for recurring items, the actual OGM-VCS code has been replaced.

CODA is the gold standard when your accounting software supports it. For situations where CODA files are unavailable or you need data in a flexible spreadsheet format, AI PDF extraction provides a reliable alternative that captures OGM-VCS codes without depending on Belfius's CSV export logic.