The Wrong VAT Payment Notices of August 2026: A Triage Procedure for June and Q2 Files

On 5 August 2026 the FPS Finance published a notice confirming that payment notices had gone out in error, for the periodic VAT returns of June — monthly filers — and of the second quarter of 2026. The government press release on news.belgium.be put the batch at roughly 190,000. What follows is a triage procedure, because not every notice in that batch is wrong.

The administration's own framing of the cause is narrow and worth repeating exactly: a technical problem in the processing of certain VAT payments and provisions inside the new collection chain. In practice it is an allocation fault. A payment that reached the Treasury on time was not attached to the period it was meant to settle, and the file was then read as unpaid.

What the FPS Finance actually committed to

Four statements, and nothing beyond them:

• Payment notices were sent wrongly for the periodic returns of June (monthly filers) and the second quarter of 2026.
• For taxpayers who paid on time, the payment is taken into account on its value date, and no late-payment interest and no fine will be applied as a result of this technical problem.
• Those taxpayers need do nothing further.
• The affected files are currently being regularised.

Note what the fourth statement does not say. It does not say the correction has run. On 23 August 2026 the administration's wording is still the present continuous, so a file you open today may still show the wrong position — and that is not evidence the client's payment went missing.

Scope: June and the second quarter, not the quarter alone

Half of the commentary that circulated in the first week described this as a Q2 problem. It is not. A monthly filer who paid the June return by its due date is inside the batch on exactly the same footing as a quarterly filer who paid Q2 by its own. If you triage only your quarterly clients you will leave the monthly files sitting on an uncorrected position, which is the population most likely to receive a second notice before the first one is resolved.

The carve-out that decides the file

The notice carves out non-payers explicitly: anyone who has not paid, or has paid only partially, is asked to pay without delay and will later receive a new notice with an updated amount.

So the waiver attaches to the administration's fault, not to the underlying debt. "Do not pay twice" is a fair summary. "Ignore the notice, no interest can be charged" is not — and it is the sentence most likely to produce a complaint three months from now, from a client who genuinely had not paid and read your email as permission to wait.

The triage, per notice

1. Read the period on the notice. If it is not June 2026 for a monthly filer or the second quarter of 2026, this batch does not explain it. Treat it as an ordinary notice and work it normally.
2. Open the VAT provision account statement in MyMinfin for the client and look for the movement that should settle that period. You are checking two things: whether a payment is attached to the period at all, and what value date it carries.
3. Pull the bank proof. The statement line for the transfer, with its value date and the structured communication used. The value date is the operative fact in the administration's own commitment, so it is the figure your file has to be able to produce.
4. Compare the amount claimed with the amount due on the return. A notice for a different amount than the return produced is a second question, not this one.
5. Decide. Paid in full and on time: document and stop. Unpaid or partly paid: pay without delay and expect a new notice with an updated amount.

The three documents that belong together

Keep them as one bundle per notice, in the client file, not scattered across a mailbox:

• the provision-account extract for the period, dated as printed;
• the proof of payment, showing the value date and the structured communication;
• a dated copy of the notice itself.

The reason is not archival tidiness. The administration's commitment is expressed in terms of the value date, and the correction is running on files you cannot see. If a later notice, a later query or a set-off against a credit contradicts the position you believe is correct, the bundle is what turns a phone call into a two-minute conversation.

Whether you were right to call the collection service

Two elements circulated widely in the first days that are not on the FPS Finance page in either language: that the notices went out from 3 August, and that there is no need to notify the collection service. Both come from ITAA (blogitaa.be, 5 August 2026), reporting an express confirmation obtained from the administration. If you rely on them — and they are useful — attribute them to ITAA, not to the FPS.

There is a second reason to be precise about that. ITAA's own post of 4 August implied that notifying the collection service was still the recommended step; the "no need" line arrived the following day. A bookkeeper who called or wrote on 3 or 4 August followed the guidance that existed at that hour, did nothing wrong, and has nothing to withdraw. Files touched in those two days do not need to be reopened for that reason alone.

Why the chain produced this

Since 1 May 2026 the VAT current account has in practice been replaced by the VAT provision account in MyMinfin. VAT due on a periodic return is paid to BE41 6792 0036 4210, with the same structured communication as before, until the FPS issues an enforceable title; from that point, payment goes to BE42 6792 0000 0054. Payments made to the old account are forwarded automatically until 31 December 2026.

The same reform narrowed what ticking the refund box on a return actually claims: only the credit arising from that return — the grid 72 amount. Credit standing from earlier periods is no longer swept along with it and has to be claimed separately in MyMinfin.

The second trap: do not concede a figure nobody has reconciled

An allocation fault does not confine itself politely to payment notices. If a query this autumn touches a VAT credit, a set-off, or an opening balance on the provision account, the same processing chain produced that figure. Ask for the movements behind it before agreeing to anything, and reconcile the period against your own record of payments and their value dates. Conceding a balance that nobody has checked is how a technical problem becomes a client's number.

Where this stands on 23 August 2026

This briefing reflects the position on 23 August 2026. The situation was live and unresolved when the administration published its item, and no completion date has been given. Check the FPS Finance page for an update before you act on a file — particularly before you tell a client that a notice can be left alone.