Most tickets a Business Central support desk receives are not faults. They are the system saying, in its own words, exactly what is wrong and what to do about it. If you pay for support by the ticket or by the hour, every one of these is money. The ten most common, what the message means, and who in your own business can fix it in two minutes.
Look at a year of tickets at any Business Central support desk and a pattern appears: a third to a half of them are not faults. They are the system refusing to do something, saying why in plain words, and the user logging a ticket instead of reading the message. Every one of those tickets costs money (if you pay per ticket, per hour or from a bank of tokens, it is a direct cost), it delays the user by hours instead of minutes, and it pulls the support desk away from the things that actually need them.
These are the ten we see most. For each: what the message says, what it means, and who in your own business should fix it. The common thread is that a trained user, or the department's super user, can resolve all of them without a call. If your users cannot, that is a training gap, not a system fault.
What it means: Finance has locked the posting period. General Ledger Setup has an "Allow Posting From" and "Allow Posting To" range (and User Setup can override it per user), and the document's posting date is outside it. Usually the user is posting into last month after it was closed, or has a document dated in the future.
Who fixes it: The user, by correcting the posting date to today or the open period. If the date is right and the period genuinely needs to be open, the finance manager, by widening the range in General Ledger Setup or User Setup for that one person. Never the support desk; they will only ask finance anyway.
What it means: The G/L account, customer, vendor, item or bank account has a default dimension set to "Code Mandatory", and the line has no value for it. The system is doing exactly what finance asked it to do: refuse postings without a department (or cost centre, project, region).
Who fixes it: The user, by filling in the dimension on the line or the header. If the same account keeps prompting, the super user, by setting a default dimension value on the account or customer so it fills itself. Related messages ("Dimension Value is blocked", "The dimension values ... must be the same", "... is not valid for ...") are the same family: a value is blocked, a combination is disallowed, or a value conflicts between header and line.
What it means: The user is not assigned a permission set that covers the thing they tried to do. Often a new starter, a changed role, or a Team Member licence trying to post.
Who fixes it: Your own system administrator (the person with User Setup responsibility), by assigning the right permission set on the user card, in two minutes. If the user is a Team Member, the fix is a licence decision, not a permission one; see who needs which licence. The support desk cannot decide who in your business should be allowed to post.
What it means: The item is not in stock at that location (or bin), or Location Setup prevents negative inventory. Either the stock is physically there and the system does not know, or the sale was taken against stock that does not exist.
Who fixes it: The warehouse super user. Check the location and bin on the line, check the Item Availability by Location, and if the stock is there but unposted (a receipt not posted, a transfer in transit) post it. If it is a genuine shortage, that is a business decision, not a ticket.
What it means: Someone set Blocked on the card (customers: Ship, Invoice or All; vendors and items: Yes). Usually credit control has blocked a customer for non-payment, or purchasing has blocked a supplier.
Who fixes it: Whoever has the authority to unblock: credit control for a customer, purchasing for a supplier, stock control for an item. The message is the system passing on a decision your own colleagues made; the support desk will send it straight back.
What it means: The customer's balance plus this order exceeds the credit limit on the card, and Sales & Receivables Setup has the credit warning switched on.
Who fixes it: Credit control, by raising the limit, taking payment, or deciding the order waits. The user can usually proceed with the warning if their role allows it. This is a business control working as designed.
What it means: A number series problem: the user typed a number the series owns, or the series has run out, or there is no range for the current date (series set up with a starting date each year and nobody added this year's).
Who fixes it: The user, by clearing the number and letting the series assign one. For a series that has run out or has no range for this year, the finance super user, in No. Series → Lines, by adding a new line with the starting date and number. It is a five-minute job that appears on every support desk every January.
What it means: Usually posting setup, not a fault: a General Posting Setup or VAT Posting Setup combination is missing an account, or a rounding or currency account is not set up, so the posting would not balance. The inconsistency dialog tells you which accounts are involved.
Who fixes it: The finance super user, by completing the posting setup (the missing combination of business and product posting group, or VAT business and product group). This one is worth a quick check with your partner the first time it appears, because occasionally it is a real fault; after that it is nearly always setup.
What it means: Two people (or a person and a background job) were editing the same record and the other one saved first. Nothing is broken; the user's copy is stale.
Who fixes it: The user, by closing the page and reopening it. If it happens constantly on one record, the super user finds out who else is in it (often a job queue entry or an integration), which is useful information but still not a fault.
What it means: The user is posting a document with no lines or with zero quantities; or is on a document that has already been posted (it is now a posted invoice, not an order); or is trying to apply a payment with nothing selected. All of them are "you have not told me what to do".
Who fixes it: The user, by looking at the document. The super user, by showing them Posted Sales Invoices and the application pages once.
Every one of the ten is Business Central doing its job: enforcing a period lock, a mandatory dimension, a permission, a stock rule, a credit limit, a number series, a posting setup, a concurrency check. The message names the rule and, usually, the record. A user who has been shown how to read the message once will not log it twice. That is what super users are for: first line in the department, able to fix eight of the ten themselves and to route the other two (permissions, posting setup) to the right person internally.
What should go to the support desk: anything where the message names an object you do not recognise, anything with "internal error" or a GUID in it, anything that worked yesterday and does not today with no setup change, anything after an update, and anything involving an integration. Those are worth the ticket. The ten above are not.
If your ticket volume is high and you suspect most of it is on this list, the health check includes a look at the last six months of tickets, and the super user training that follows usually halves the volume within a quarter.
