How to Convert BNP Paribas Fortis Bank Statement to Excel

BNP Paribas Fortis customers have three main ways to convert a bank statement to Excel or CSV:

• Download transactions directly from Easy Banking Web or Easy Banking Business in CSV format.
• Convert CODA files using accounting software or a dedicated CODA-to-Excel conversion tool.
• Use an AI-powered extraction tool that parses bilingual Dutch/French headers and preserves OGM-VCS structured communication codes automatically from PDF statements.

Which method works best depends on the statement format you have, the level of transaction detail you need, and whether Belgian payment references must be preserved intact for reconciliation.

BNP Paribas Fortis is Belgium's largest bank and operates as a distinctly Belgian entity within the BNP Paribas Group, with its own statement formats, banking portals, and export options. Most online guides treat it as interchangeable with the French parent, leading to advice that does not apply to the Belgian platform.

That distinction matters more than ever as Belgian banking goes digital. According to Febelfin, almost 95% of Belgians used an online or mobile banking service in the final three months of 2025, with viewing past transactions growing from 12% in 2020 to 27% of users. The shift means more professionals are working with digital statements and need structured spreadsheet data for bookkeeping, VAT reporting, and financial analysis.

The challenge is that BNP Paribas Fortis PDF statements contain bilingual Dutch/French column headers and Belgian-specific payment references known as OGM-VCS structured communication codes. Generic PDF-to-Excel converters were not built to handle either. They routinely misalign columns when headers appear in two languages and strip or corrupt the 12-digit OGM-VCS references that accountants rely on to match payments to invoices. Choosing the right method to convert a BNP Paribas Fortis bank statement to Excel saves hours of manual correction and keeps your reconciliation data intact.

Export Options in Easy Banking Web and Easy Banking Business

BNP Paribas Fortis provides two distinct online banking platforms. Easy Banking Web serves personal banking customers, while Easy Banking Business is the portal for business account holders. Business accounts typically offer a wider selection of export formats, so the options below may vary depending on which portal you use.

Across both platforms, BNP Paribas Fortis makes four native export formats available:

• PDF — The default human-readable statement. Useful for archiving or sharing but not structured for spreadsheet work. This is the format you likely already have if you downloaded or received a periodic statement.
• CSV — Comma-separated transaction data that opens directly in Excel or Google Sheets. Each transaction appears as a row with structured fields (date, amount, counterparty, communication), making this the most direct path to a BNP Paribas Fortis statement in CSV format without any third-party tools.
• CODA — Belgium's national electronic banking standard, designed for import into accounting software such as BOB, Exact Online, or Yuki. CODA files carry rich structured data but are not meant to be opened directly in a spreadsheet.
• MT940 — The SWIFT messaging standard used in international treasury management and multi-bank reconciliation. MT940 is structured but not human-readable without conversion or a dedicated parser. If you work across multiple banks or countries, you may already encounter this format. For a deeper look at how MT940 compares to newer XML-based formats, see our guide on understanding MT940 and CAMT.053 bank statement formats.

To download a CSV from Easy Banking Business, navigate to your account's transaction history and use the export or download function above the transaction list. Select CSV as the file format and set your date range. Easy Banking Web offers a similar download path, though personal accounts may show fewer format options.

For most users whose goal is ad-hoc financial analysis, reconciliation, or bookkeeping in Excel, the CSV export from Easy Banking is the most straightforward option. It requires no conversion, no third-party software, and no reformatting. The data lands in your spreadsheet ready for sorting, filtering, or pivot tables.

That said, CSV exports through Easy Banking Business may have limitations on how far back the transaction history extends or the maximum date range per download. If you need several years of historical data or your account only provides PDF statements for older periods, the native CSV export may not cover your full needs. CODA files, by contrast, are typically retained for longer periods and can be requested through your bank contact for archival ranges. The trade-off is that CODA requires conversion before the data is usable in a spreadsheet.

---

Why Bilingual Headers and OGM-VCS Codes Break Generic Converters

Most Belgian finance professionals discover the limitations of generic PDF-to-Excel converters the hard way: columns that don't align, fields that bleed into each other, and structured communication codes that arrive in the spreadsheet mangled beyond recognition. Two Belgium-specific characteristics of BNP Paribas Fortis statements are responsible for the majority of these failures.

The bilingual header problem is structural, not cosmetic. BNP Paribas Fortis issues statements with column headers in both Dutch and French, reflecting Belgium's bilingual business environment. A statement might label the same column "Datum" and "Date," or "Bedrag" and "Montant," depending on the section or page layout. Generic PDF parsers expect a single consistent header row per table. When they encounter two language versions of the same header, they misidentify column boundaries, merge adjacent fields, or treat the second-language header as a data row. The result is garbled output where transaction amounts land in date columns and descriptions spill across multiple cells. This is not a translation issue that a language setting can fix. It is a layout recognition failure that requires the parser to understand that two different strings map to the same column.

The OGM-VCS preservation problem is equally disruptive, and arguably more costly. Belgian payments rely on Belgium's OGM-VCS structured communication system to link each transaction to a specific invoice, tax obligation, or account reference. These codes follow the format +++XXX/XXXX/XXXXX+++ and are the backbone of payment reconciliation for any Belgian business. When a generic Belgian bank statement PDF converter encounters these codes, it frequently strips the +++ delimiters, splits the code across multiple cells at the forward slashes (interpreting them as field separators), or drops the code entirely. A corrupted or missing OGM-VCS code means that transaction cannot be matched to its corresponding invoice. For an accountant reconciling hundreds of payments, even a handful of broken structured communications can add hours of manual lookup.

Any converter claiming to handle BNP Paribas Fortis statements must handle both challenges — bilingual column mapping and intact OGM-VCS preservation — or the output will require extensive manual correction.

---

Converting BNP Paribas Fortis CODA Files to Excel

If you work with a Belgian accounting package, there is a good chance you already receive CODA files from BNP Paribas Fortis without thinking much about what they are. CODA is Belgium's national electronic banking standard, and it serves a single purpose: delivering transaction data from your bank to your accounting software in a structured, machine-readable format. CODA files contain the same transactions that appear on your PDF statements, but encoded in a fixed-width text format that no human would want to read. Software like Bob50, Exact Online, and Yuki imports them automatically.

The question is what to do when you need that data outside your accounting system. If you are running an ad-hoc reconciliation, building a cash flow analysis in a spreadsheet, or sharing transaction details with a colleague or advisor who does not have access to your accounting software, you need those transactions in Excel or CSV. That is where converting a BNP Paribas Fortis CODA file to Excel becomes practical.

You have three main conversion paths:

• Export from your accounting software. Most Belgian accounting packages that import CODA can also export the resulting transactions to Excel or CSV. If you already have CODA files flowing into your system, this is often the fastest route. Check your software's reporting or export module for a spreadsheet output option.
• Dedicated CODA-to-Excel conversion tools. Several standalone converters accept a CODA file and produce a formatted spreadsheet directly. These are useful when you want the raw bank data in Excel without routing it through your full accounting workflow first.
• Open-source libraries for programmatic conversion. If you are comfortable with code, Python packages such as ofxstatement-be-bnp can parse CODA files and output structured data. This approach suits developers who need to automate conversion as part of a larger data pipeline or reporting process.

One important limitation: all of these methods assume you already have CODA files. CODA is the electronic delivery channel, not something you can generate from a PDF statement after the fact. If you only have PDF bank statements from BNP Paribas Fortis (the human-readable format mailed or downloaded from Easy Banking), you need a different approach entirely, whether that is native CSV export from the Easy Banking portal or AI-powered PDF extraction.

---

Extracting BNP Paribas Fortis PDF Statements with AI-Powered Tools

The bilingual header and OGM-VCS challenges described above are exactly where AI-powered extraction differs from conventional converters. Instead of relying on fixed layout templates that expect headers in a single language at set coordinates, AI models interpret document structure contextually. They recognize that "Datum" and "Date" refer to the same field, and that a +++XXX/XXXX/XXXXX+++ string is a structured communication code, not a formatting artifact. No BNP Paribas Fortis-specific template is required.

Bilingual header recognition is where this matters most for BNP Paribas Fortis customers. Whether your statement labels a column "Mededeling" or "Communication," "Valuta" or "Devise," the AI identifies what each field represents based on its content and position within the document's logical structure. You can provide natural language extraction instructions specifying exactly what you need, such as "Extract date, description, amount, and structured communication code from each transaction," and the AI maps those instructions to the correct fields regardless of the header language.

OGM-VCS code preservation is equally straightforward. You can instruct the AI to keep the complete +++XXX/XXXX/XXXXX+++ format intact in a dedicated column. Because the extraction follows your prompt instructions rather than a fixed parsing rule, the structured communication codes survive as a single, unbroken value ready for reconciliation. No manual cleanup of split or truncated reference numbers.

The workflow requires three steps:

1. Upload your BNP Paribas Fortis PDF statement to an AI-powered bank statement extraction tool.
2. Provide extraction instructions — specify the fields you need, or let the AI analyze the document structure automatically.
3. Download the result as an Excel or CSV file, typically within seconds per page.

For recurring monthly conversions, you save your extraction prompt once and reapply it to each new statement, eliminating repetitive configuration. The platform handles all major languages and scripts natively, so mixed Dutch/French content within a single document is not an edge case.

You also get output formatting control that generic BNP Paribas Fortis bank statement converters cannot match. You can name columns to match your accounting software's import template, enforce consistent date formats across bilingual statement pages, and add rules like showing credit entries as negative values. These instructions become part of your saved prompt rather than a post-processing step in Excel.

For finance professionals processing a limited number of statements, the platform is free to use for up to 50 pages per month with no credit card required, which covers several months of typical BNP Paribas Fortis statement conversions. Higher volumes are available on a pay-as-you-go basis without a subscription.

---

Which Conversion Method Fits Your Workflow

The right approach depends less on which tool looks best on paper and more on what you actually have in front of you and how often you need to do this.

If you can export CSV directly from Easy Banking, start there. For one-off conversions where the date range you need falls within the portal's export window, downloading a CSV gives you usable spreadsheet data in under a minute. No extra software, no conversion step, no cost. This covers a surprising number of ad-hoc requests, particularly if you just need recent transactions for a quick reconciliation or cash flow check.

If you already receive CODA files from BNP Paribas Fortis, you have structured transaction data that most accounting software can parse. When you need that data in Excel for ad-hoc analysis, pivot tables, or a format your accounting package does not natively produce, converting CODA to Excel preserves the structured communication codes and transaction references that matter for Belgian reconciliation workflows. This path works especially well as a recurring monthly process since the CODA file format stays consistent across periods.

If you are working from PDF statements, the decision gets more nuanced. PDFs are the format you are most likely stuck with when dealing with older statements, archived records, or date ranges that fall outside the Easy Banking export window. Generic PDF-to-Excel converters routinely fail on BNP Paribas Fortis statements because of bilingual Dutch/French headers and OGM-VCS structured communication codes that do not survive template-based parsing. AI-powered extraction tools handle these Belgium-specific formatting challenges without requiring you to configure templates or manually correct output. For accountants processing BNP Paribas Fortis bank statement to spreadsheet conversions across multiple client accounts, saved extraction prompts turn what would be a manual monthly task into a repeatable workflow.

Volume matters as much as format. A business owner converting one statement per quarter has different needs than an accountant handling monthly reconciliation for ten clients. For recurring work, invest the initial setup in whichever path supports repeatability: saved extraction prompts for PDF-based workflows, or automated CODA delivery for structured data pipelines.