The document carries a VAT date that lies outside the VAT period your company still accepts postings in. Business Central checks the VAT date separately from the posting date, against an allowed VAT date from and allowed VAT date to pair that exists both per user and for the whole company. Move the VAT date into the open range, or have an administrator reopen that range.
Why Business Central raises this error
Since the 2023 release wave 2, documents and entries carry a VAT date so that VAT reporting can be closed independently of the general ledger. With it comes an allowed VAT date range, a from date and a to date that behave exactly like the allowed posting dates, with a personal value on User Setup taking precedence over the company value. Once a VAT return has been filed, finance normally moves the from date forward so that nothing else can slip into a period that has already been reported. The check is deliberately stubborn: it still runs when the VAT date usage setting tells Business Central to take the VAT date from the posting date, so switching that option off does not remove the restriction. Only clearing or widening the allowed range does.
- The VAT return for that period has been filed and the allowed VAT date from value has been moved to the start of the current period.
- The document has a VAT date that differs from its posting date, so the posting date passes its own check while the VAT date fails.
- Your own user record carries a narrower allowed VAT date range than the company setup, so a colleague can post the same document and you cannot.
How to fix it
- Open the document that fails and read its VAT date on the general information; it can differ from the posting date without anyone noticing.
- Search for User Setup (Alt+Q), open your user record and check the allowed VAT date from and allowed VAT date to fields there. A value on your record overrides the company setting.
- Check the same allowed VAT date from and allowed VAT date to pair in the company VAT date setup. When both are blank, no VAT period restriction applies at all.
- If the VAT date is simply wrong, correct it on the document and post again.
- If the period genuinely has to be reopened, ask the finance administrator to change the allowed VAT date range. That setup is administrator territory, so you normally cannot change it yourself, and reopening a reported period should be a conscious decision.
- Do not expect the VAT date usage option to help: turning it off leaves the allowed range validating as before, so the range itself has to be widened or cleared.
How to avoid it in the future
Roll the allowed VAT date range on the day the VAT return is filed, in the same checklist that closes the general ledger period, and write down who is allowed to reopen it. Keeping the VAT date aligned with the posting date on ordinary documents also helps, because the two ranges then close together and a document that passes one check usually passes the other.
Frequently asked questions
I switched the VAT date feature off, why is it still blocking?
The allowed VAT date from and to fields keep validating even when the VAT date usage option is not set to use a separate VAT date. The block only disappears when the allowed range is widened or cleared.
Is this the same as the allowed posting dates?
No. They are two independent ranges. A document can pass the posting date check and still fail on the VAT date, and both have to be open for the posting to go through.
Related reading
- VAT Posting Setup, The Business Central matrix of VAT business and product posting group combinations that determines VAT rates, calculation types, and VAT accounts.
- Posting Date, The date that decides which accounting period a Business Central transaction lands in, distinct from the document date and the VAT date.
- Purchase Invoice, A document recording a vendor's bill for goods or services received, used for accounts payable processing in Business Central.
- How to Run a Month-End Close in Business Central
Other Business Central errors