ERPNext Accounting in Belgium

Importing a chart built on the Belgian minimum scheme

Belgian companies keep their books on a chart derived from the legal minimum scheme, with accounts grouped into numbered classes for equity, fixed assets, stock, receivables and payables, cash, costs and income. ERPNext does not need to know about the scheme to use it: the chart is imported from a spreadsheet, and the account numbers and groups follow whatever structure your accountant provides.

The care goes into two mappings at once. ERPNext needs each account typed correctly, since its default postings and standard reports depend on whether an account is marked as receivable, payable, bank, tax or stock. Your accountant needs the class structure intact so the annual accounts can be prepared and filed from it. I build the import with both in view, then check a trial balance by class and an ERPNext balance sheet side by side.

Analysis needs are handled separately. Cost centers and accounting dimensions can tag postings by site, by language region, by business line or by project, without breaking the legal chart into hundreds of extra accounts. I keep the chart close to what the accounting firm expects and push the management detail into dimensions. Payroll journals from your social secretariat are imported as journal entries into accounts agreed in advance. The module overview is on ERPNext Accounting, and ERPNext in Belgium covers the platform decision.

VAT templates, listings and structured payment references

In ERPNext, Belgian VAT comes from three configurable layers: sales and purchase tax templates, item-level tax templates and rules that choose between them. The cases your accountant lists usually include domestic sales at the applicable rates, domestic reverse charge for certain services, intra-Community supplies and acquisitions, imports and credit notes. Each case gets a test invoice or bill, and the postings and invoice wording are reviewed before go-live. Whether a regional app adds anything Belgian in your version is a question for Frappe or your partner.

The figures must then leave ERPNext in the right shape. I build saved reports that total amounts per return grid, list intra-Community supplies by customer VAT number and gather yearly totals per Belgian business customer for the annual listing. Your accountant compares each report with their own calculation for a sample period. Filing remains with them.

Structured payment references are a separate requirement that affects reconciliation. Belgian invoices commonly carry a structured communication that the customer quotes when paying, which lets receipts be matched automatically. ERPNext does not generate this reference in its standard invoice, so it is added with a custom field and a small script that calculates the reference and its check digits, then prints it on the invoice. That script is custom code, so it gets an owner and a place in the upgrade tests. A comparison with a packaged localization is on Odoo Accounting in Belgium.

CODA statements through custom work

CODA is the coded statement format Belgian banks supply to businesses and their accountants. It carries far more detail than a downloaded spreadsheet, including the structured reference a customer quoted, the counterparty account and bank charges as separate lines. ERPNext's statement import is designed around mapped columns from files such as spreadsheets, so reading CODA directly needs either a maintained community app or custom work. Confirm what exists for your version with Frappe or your partner before planning around it.

When custom work is the answer, I write the specification: which CODA records are read, how each becomes a bank transaction in ERPNext, how structured references are matched to open invoices, and which lines go to a review queue. Your developer or partner builds it, and I test it with several real statement files, including a day with a returned direct debit and a foreign currency receipt.

There is a simpler fallback. Some companies receive CODA files through their accounting firm or a statement service that can also provide a spreadsheet export, which ERPNext can import with a column mapping. It is less elegant but avoids custom code. I put both options in front of you with the trade-off spelled out. Builds like this follow the method on my ERP integration page, and finance automation covers matching rules more generally.

Peppol invoices and what the ledger has to handle

Peppol is now central to invoicing between Belgian businesses, and the exact scope for your company is for your accountant to confirm. My page on ERPNext in Belgium discusses why the connection must be planned early. Here the focus is on what the ledger needs once invoices travel through an access point rather than by email.

Outgoing, every sales invoice and credit note must carry clean data: the customer's enterprise number and VAT number, tax lines that match the categories the receiving system expects and a correct structured reference. I check these fields with validation rules so an invoice that would be rejected is stopped inside ERPNext rather than bounced back days later. Rejections that still arrive need a visible queue and an owner.

Incoming is where the work grows. Supplier invoices arriving over Peppol should become draft purchase invoices, matched to purchase orders or receipts where they exist and routed for approval. Tax lines from the supplier must be checked against your own templates, and the original electronic document archived with the posting. Whether this comes from an app or an integration with an access point provider, I document who maintains it and add a full round trip to the regression pack run before every upgrade. The system integration page shows my specification approach.

Multilingual invoices, hosting and when another ledger fits better

A Belgian company may invoice in French, Dutch or German depending on the customer, and ERPNext can store a print language per customer and hold separate print formats. The engagement runs in English, so each layout's wording is supplied or proofread by people who use that language natively, in your company or at a local agency, while your accountant confirms the mandatory invoice mentions. I check that each layout prints correctly with real data.

Hosting choices follow the same logic as elsewhere in the EU. Frappe Cloud handles patching and backups for you; a European server you run yourself puts location and upgrade timing in your hands; a partner can also host under contract. Record the choice in your GDPR register. In Belgium the custom pieces raise the stakes: an upgrade that breaks the CODA import or the Peppol link stops reconciliation or invoicing, so a regression pack and named maintainers are part of the deliverable, not an extra.

ERPNext Accounting is not always the right ledger here. If your accounting firm will only work in its own software, if nobody can own the CODA and Peppol pieces, or if you would rather have more of the Belgian toolkit packaged, consider Odoo in Belgium or Zoho Books in Belgium. My ERP consultant page for Belgium and the Belgium hub explain how I compare options without a stake in the outcome.