Business Central: "Posting Date is not within your range of allowed posting dates"

How to resolve it

1. 1Read the error carefully and note the Posting Date on the document header (sales, purchase, journal line, or the date typed in the Post dialog).
2. 2Check why that date was used. Posting Date defaults from the Work Date, which is set in My Settings. If you logged in and the work date is old, correct it there first.
3. 3Search for User Setup and open your own row. Look at Allow Posting From and Allow Posting To. If either is filled, those override General Ledger Setup for you.
4. 4Search for General Ledger Setup, open the General fast tab, and read Allow Posting From and Allow Posting To. These apply to every user who has no value in User Setup.
5. 5Decide whether the date is wrong or the window is wrong. For a legitimate late posting, a controller should widen the window (or blank it for a named user) in User Setup rather than opening it for everybody.
6. 6For deferrals, check the separate Allow Deferral Posting From and Allow Deferral Posting To fields in the same two places.
7. 7Retry the post. If the same document also hits an inventory period or accounting period block, resolve those separately as described below.
8. 8Close the window again after the late postings are done, and note who changed it and when.

Work date versus posting date

On-premises check of effective limits (replace CRONUS with your company name):
SELECT [User ID], [Allow Posting From], [Allow Posting To]
FROM [CRONUS$User Setup]
WHERE [Allow Posting From] <> '1753-01-01' OR [Allow Posting To] <> '1753-01-01'

SELECT [Allow Posting From], [Allow Posting To]
FROM [CRONUS$General Ledger Setup]

Controlling the window safely

Common pitfalls

• !Widening General Ledger Setup for everyone to fix one person's problem. Use that user's row in User Setup instead.
• !Forgetting that a filled User Setup value overrides General Ledger Setup, so changing the global window seems to do nothing for that user.
• !Leaving the Work Date on an old value, which re-creates the error on every new document.
• !Confusing this with an inventory period or accounting period closure and editing the wrong setup page.
• !Opening a window and not closing it, so later users post into a period finance considers locked.