Direct debit, G-account and payment codes

How the IDR recognises direct debit notices, G-account IBANs and payment codes on PDF invoices.

When processing PDF invoices, the IDR recognises not only standard payment details (IBAN and payment reference), but also specific payment situations that affect the payment code in the e-invoice.

Direct debit detection

If an invoice contains a direct debit notice (for example "This amount will be collected automatically"), this affects the payment code in the UBL invoice. The payment code determines how the receiving system handles payment:

  • For a bank transfer: the standard payment code is used
  • For direct debit: the payment code indicates automatic collection

It is important that your ERP system interprets the correct payment code, so invoices with direct debit are not offered for manual payment while the amount has already been collected.

G-account recognition

The Professional version of the IDR recognises G-account IBAN numbers on PDF invoices. A G-account is identifiable by the characteristic "099" sequence in the IBAN. The IDR records the G-account IBAN as a separate field in the e-invoice, separate from the supplier's regular IBAN.

What is a G-account?

A G-account (blocked account) is a bank account into which the hirer or contractor deposits the estimated amount of payroll taxes and VAT. The balance can only be used to pay these taxes to the Tax Authority. The remainder of the invoice amount goes to the supplier's regular bank account.

The G-account is an instrument to limit liability risk in subcontracting (chain liability) and when hiring staff (hirer's liability).

Software requirement

G-account processing must be supported in the integration with your financial package. The software must correctly process two partial payments: one part to the G-account (for payroll taxes and/or VAT) and one part to the supplier's regular bank account. If the package does not support this, eConnect can still supply the data but the payment cannot be split correctly.

Sectors

The G-account was originally developed for the construction sector (and is part of the DICO standard), but is used more widely for temporary staffing, secondment and subcontracting across sectors.

IBAN validation

With a Professional subscription, the recognised IBAN is compared with previously verified IBAN numbers in the verification store. If the IBAN on a new invoice differs from what was recorded earlier, the system generates a warning. This helps detect changed bank details or possible ghost invoices.

Frequently asked questions
What is a G-account and how is it recognised?

A G-account (blocked account) is a bank account into which the estimated amount of payroll taxes and VAT is deposited for subcontracting or hiring staff. The IDR recognises G-account IBAN numbers by the characteristic "099" sequence and records it as a separate field in the e-invoice.

How does a direct debit notice affect invoice processing?

If an invoice contains a direct debit notice (for example "This amount will be collected automatically"), the IDR adjusts the payment code in the UBL invoice. The payment code then indicates automatic collection instead of a bank transfer, so your ERP system does not offer the invoice for manual payment.

Must my software package support G-account processing?

Yes, your financial package must correctly process two partial payments: one part to the G-account and one part to the supplier's regular bank account. eConnect can supply the data, but if the package does not support this split, the payment cannot be processed correctly.


Want to know more about which fields the IDR recognises? Read Which fields does the IDR recognise?.

View all recognised fields

Related