Enforcing a Department Dimension and Removing a Manual Rent Allocation
Litware's controller wants department reporting that cannot be bypassed. Two dimensions exist: DEPARTMENT (global dimension 1, six values) and PROJECT (global dimension 2). Requirements: every expense entry must carry a department; project is optional; bank fee postings must be allowed without a department; customers and vendors carry a default department that flows onto documents but buyers may change it. After go-live, a dimension analysis shows 18% of expense entries with a blank department, three users posted to departments outside their own, and month-end still needs a manual journal to split the 60,000 rent across the six departments.
1. Which settings make DEPARTMENT mandatory on expense postings while still allowing the bank-fee exception and clean balance-sheet entries?
Read the worked answer
Two layers, and the account layer is the one that decides. On the DEPARTMENT dimension card, set Value Posting to Code Mandatory so the dimension is treated as required wherever it is used. Then set it per account, because the posting check reads the account:
- Expense accounts:
Dimension Value Posting= Code Mandatory, plus aDefault Dimensionon the account withValue Posting= Code Mandatory so the field prefills and the user must supply a value. - Balance-sheet accounts (bank, VAT, receivables, payables): Same Code, so those entries inherit the department from the expense line instead of failing the check and blocking the posting.
- The bank fee account: No Code, which is the documented exemption and lets it post with a blank department.
Why not only the dimension card. The dimension-level flag sets the expectation, but account-level settings are what make exceptions possible; without them the bank fee account either blocks or forces a meaningless department value onto a bank charge.
Test before sign-off. One journal line with a blank department (must block), one to the bank fee account (must pass), and one hitting a balance-sheet account to confirm Same Code inheritance.
2. Three users posted to departments outside their own. What can standard Business Central actually restrict, and what should you recommend honestly?
Read the worked answer
What cannot be done. Business Central has no per-user security on individual dimension values. Permission sets work on tables, fields and companies, not on the value DEPT-SALES, so a requirement of 'this user may only post to their own department' cannot be met by configuration alone.
What can be done.
- Set per-user
Default Dimensionsso each user's journal and document lines prefill their own department; a wrong value then requires a deliberate overwrite rather than being the path of least resistance. - Block dimension values that are no longer valid so they cannot be selected at all.
- Add an approval workflow on the general journal so any manual journal is reviewed before it posts.
- Monitor with a dimension analysis and a G/L entry review by user.
Recommendation to state. Use default dimensions plus monitoring for the current requirement, and say plainly that hard segregation needs a workflow approval or a custom validation. Promising that a permission set will achieve it is the failure mode this question is testing.
3. The 60,000 rent is split across six departments by manual journal each month. Design the split so it posts once, and state the caveats.
Read the worked answer
Design. Change the rent account to Account Type = Allocation and add six allocation lines pointing at the department expense accounts, using Allocation % (each department's headcount over total headcount, summing to 100) or integer Shares (12, 9, 7, 5, 4, 3). Post the rent invoice to the allocation account once; Business Central writes one G/L entry per target account on the same document number and posting date, so the split sits inside the purchase invoice's audit trail instead of a second manual journal.
Caveats that decide the design.
- The allocation entries inherit the dimensions of the source line, so you cannot give each target a different DEPARTMENT value from the allocation itself. If department-level reporting of the split is required, use six recurring general journal lines or six separate accounts instead - the allocation account is the wrong tool.
- Input VAT on the invoice line follows the allocation. If VAT must not be split, post it on a separate line or exclude it.
- The source allocation account must net to zero; a residual balance means the percentages do not total 100.
- Headcount changes are handled by editing the allocation, not by creating a new account each quarter.