Business Central journal and document posting errors

Once the posting groups are right, the errors that stop a posting are about the document itself: its date, its dimensions, its number, and the state of the records it references. This reference covers those in the order finance and operations users report them. Posting group errors — "does not exist" and "must have a value in … Posting Setup" — are in posting setup errors; code-level runtime errors in AL runtime errors.

Posting dates

"Posting Date is not within your range of allowed posting dates."

Symptom. A journal or document refuses to post; the same document may post for a colleague.

Cause. General Ledger Setup carries Allow Posting From and Allow Posting To for the company; User Setup carries the same fields per user, and the per-user range wins when present. The error fires when the line's posting date falls outside whichever applies. Two situations dominate: a user back-dates into a closed period, or nobody rolled the range forward after month-end and the whole company is locked out of the new month.

Fix. If the date is wrong, change it. If the period is genuinely open, extend Allow Posting To in General Ledger Setup, or the user's own range in User Setup for the people who close the books. Check both places — a stale User Setup range is the usual reason "it works for me but not for her".

Prevention. Make rolling the posting date range a named step in the month-end checklist, and give only the controller a wider per-user range for closing entries.

"Posting Date must not be later than Work Date" / date warnings on documents

Cause. A document dated in the future relative to the work date, or a VAT date outside the VAT period when VAT date control is on.

Fix. Correct the date; if the future posting is intentional, adjust the work date for the session.

Dimensions

"Select a Dimension Value Code for the Dimension Code X for Customer Y."

Symptom. A line fails validation or posting naming a dimension and a record.

Cause. The record — customer, vendor, item, G/L account, resource, fixed asset — has a default dimension whose Value Posting is Code Mandatory, and the line has no value for that dimension. Common when a new G/L account or item was created without the default dimension the rest of its group carries.

Fix. Set the dimension value on the line's Dimensions page, or on the record's Default Dimensions so every future line inherits it.

Prevention. Use Account Type Default Dimensions to set mandatory dimensions per table rather than per record, and templates for new customers, vendors, and items. Dimensions design covers the model.

"Dimension Value Code must be X for Dimension Code Y for Customer Z."

Cause. Value Posting is Same Code — the record insists on one specific value — and the line has a different one, usually because a user overrode it.

Fix. Use the mandated value, or change the default dimension if the rule is wrong.

"A dimension used in Gen. Journal Line X, Y, Z has caused an error. …"

Cause. The wrapper message on journals; the text after it is one of the above, or a blocked dimension value.

Fix. Read the second sentence and act on that.

"Dimension Value X - Y is blocked" / "The dimension value is blocked"

Cause. The dimension value has been blocked — a closed project, a retired cost centre — but a recurring journal, a default dimension, or an open document still uses it.

Fix. Change the line to a live value; update the default dimension or recurring journal that keeps feeding the blocked one.

Prevention. Before blocking a dimension value, search default dimensions and open documents for it.

Number series

"You cannot assign new numbers from the number series X on DATE."

Symptom. Creating or posting a document fails to get a number.

Cause. The number series line whose Starting Date applies has no numbers left, or the only lines have starting dates after the posting date, or the series is not marked Default Nos. / Manual Nos. appropriately. Year-based series (INV-2026-…) hit this on 1 January when nobody added the new year's line.

Fix. On the number series lines, add a line with a starting date on or before the posting date and a fresh number range, or raise Ending No. on the current line.

Prevention. Set Warning No. on each series line so users are warned before the range runs out, and put "add next year's number series lines" in the year-end checklist. Number series in Business Central covers the design.

"It is not possible to assign numbers greater than X from the number series Y."

Cause. Ending No. has been reached.

Fix. Extend Ending No. or add a new line.

"The number series X does not allow manual numbers" / "does not allow default numbers"

Cause. A user typed a number into a series that only assigns automatically, or left it blank on a series that only allows manual entry.

Fix. Set Manual Nos. or Default Nos. on the series to match how it is meant to be used.

Blocked records

"Blocked must be equal to 'No' in Customer: No.=X. Current value is 'All'."

Symptom. A sales document for the customer cannot be created, shipped, or invoiced.

Cause. The customer's Blocked field is Ship, Invoice, or All. Ship blocks shipments, Invoice blocks invoicing, All blocks everything including payments. Credit control sets these; so does the Privacy Blocked flag after a data-subject request.

Fix. Confirm with whoever blocked the customer; clear or reduce the block if the sale should go ahead. Privacy Blocked is a separate field and a separate conversation.

Prevention. Document the blocking policy — who blocks, at what overdue threshold, who unblocks. Customer credit limits and blocking covers the design; blocked items and customers the three block levels.

"Blocked must be equal to 'No' in Item: No.=X." / "Sales Blocked must be equal to 'No' …" / "Purchasing Blocked …"

Cause. The item is blocked entirely, or for sales, or for purchasing — retired products, quality holds, discontinued suppliers.

Fix. Use a replacement item (item substitutes help), or unblock if the block is stale.

"Blocked must be equal to 'No' in Vendor" / "in G/L Account" / "in Bank Account"

Same pattern on the other master tables; the fix is the same.

Document state

"There is nothing to post."

Symptom. Post does nothing on an order or journal.

Cause. On a sales or purchase order, Qty. to Ship / Qty. to Receive and Qty. to Invoice are all zero — often because a previous partial posting cleared them, or because a user set them to zero. On a journal, the batch has no lines, or the lines are all filtered out of view.

Fix. Set the quantities to post on the lines; clear the journal filter.

"The lines must be balanced. Balance: X" / journal out of balance

Cause. A general journal batch must balance to zero per document number (or per line when Force Doc. Balance is on) unless a Bal. Account is used. A one-sided line, a rounding difference on a currency conversion, or lines under two document numbers that should be one.

Fix. Add the balancing line or Bal. Account, or fix the document numbers so each group balances.

"This document can only be released when the approval process is complete."

Cause. An approval workflow applies to the document and it has not been approved, or the request was cancelled.

Fix. Send for approval and wait, or have an approver with sufficient limit approve. Check the workflow's conditions if the document should not have needed approval.

Prevention. Keep approval limits and approver users current; a leaver who was the only approver stops every document in their chain. Approval workflows covers the setup.

"Warehouse handling is required for Entry Type = Sale, Item No. = X, Variant Code = , Location Code = Y."

Symptom. A sales order will not ship, or a purchase order will not receive, at a particular location.

Cause. The location has Require Shipment, Require Receive, Require Pick, or Require Put-away switched on, so inventory movements must go through warehouse documents — a warehouse shipment and pick, or a warehouse receipt and put-away — and be registered before the order posts.

Fix. Run the warehouse flow: release the order, create the warehouse shipment or receipt, create and register the pick or put-away, then post. If that location was never meant to run warehouse documents, turn the requirement off on the location card — but only if no open warehouse documents exist there.

Prevention. Decide per location which of the three warehouse modes it runs before the first transaction; warehouse pick and put-away covers the modes.

"Location Code must have a value in Sales Line …"

Cause. Inventory Setup has Location Mandatory on, and the line has no location.

Fix. Set the location on the line or as a default on the customer, vendor, or user's responsibility centre.

Cost and quantity

"Quantity must not be less than Qty. to Ship" / "You cannot ship more than X units"

Cause. The quantities on the line are inconsistent after a partial posting or a manual edit.

Fix. Set Qty. to Ship to at most Outstanding Quantity.

"Item X is not in inventory" / negative inventory prevented

Cause. Inventory Setup has Prevent Negative Inventory on (or the item does), and the shipment would take stock below zero at that location.

Fix. Receive the stock first, adjust the quantity, or — if negative inventory is an accepted practice — allow it on the item.

Prevention. Item availability and order promising covers keeping promised quantities honest.

Reading an error you have not seen

Every Business Central validation error names a field, a table, and the record's key. Open that record, look at that field, and the fix is usually visible. When the message names a setup table instead, it is a posting group problem — go to posting setup errors. When it names no field at all and talks about inconsistencies or locks, it is a runtime problem — go to AL runtime errors. And if a job queue entry is what failed rather than a user, job queue errors explains where the real message is hiding.