This guide covers the most common causes of ledger transaction failures in Dimensions — including invoices failing to process, batch posting errors and nominal code mismatches. Work through the relevant section based on the error or symptom you are seeing.
Identify the type of failure
An invoice is recorded in the error log and will not process — see 'Invoice cannot be processed — error log' below
A batch has been posting for hours or is stuck — see 'Stuck or locked batches' below
A rollback transaction is blocking period end — see 'Rollback transactions' below
An error references an invalid nominal code, T-Code, or VAT code — see 'Nominal code and T-Code errors' below
Missing nominal analysis data error during batch posting — see 'Missing nominal analysis data' below
Invoice cannot be processed — error log
Before contacting support
Work through these checks first. They will help you resolve the issue if it is period- or batch-related, and give support the information they need to investigate quickly if it is not.
1. Find the exact error in the error log
Open the error log and note the following — you will need this when contacting support:
The exact error message shown
The invoice reference number(s) affected
Whether the issue affects one invoice or multiple
2. Check your posting period
In the affected ledger (Sales, Purchase, or Nominal), go to Processing > Period Controls. Check that the date on the affected invoice falls within an open posting period. If the period is closed for that date, the invoice cannot be processed until it is reopened.
3. Check for rollback transactions (period end scenarios)
If this error appears during or after a period end, it may be caused by a rollback transaction in the Nominal Ledger batch rather than a data-level error. See the article Error - 'You cannot continue with the Period End as there are rollback transactions in the current batch (Nominal Ledger)' for self-service steps to identify and resolve this.
If the issue persists, contact support
If none of the above resolves the issue, our support team will investigate, run scripts, or liaise with the hosting or development teams. Have the following ready when you contact us:
The exact error message from the error log
The affected invoice reference number(s)
Whether the issue affects one invoice or multiple
Which ledger is affected (Sales, Purchase, or Nominal)
Whether the invoices are linked to a third-party integration such as FocalPoint or Capture
For help contacting support, see Get support in Dimensions.
Stuck or locked batches
If a batch shows a status of Posting and does not progress for more than 30 minutes, the posting process has likely failed or stalled. The batch will be locked and cannot be edited while in this state.
Note the batch number and the module it is in (Sales Ledger, Purchase Ledger, or Nominal Ledger).
Ask all users to log out of Dimensions and wait 5 minutes. Some batch locks clear automatically once the holding session ends.
Log back in and check whether the batch status has changed. If it now shows as Unposted or Error, you can attempt to post it again.
If the batch remains stuck in Posting after all users have logged out, the batch flag in the database needs to be reset — this requires a support engineer. Raise a support case and include: the batch number, the module, the time the batch entered the Posting state, and whether any errors appeared before it became stuck.
Rollback transactions
A rollback occurs when an error during transaction posting means the process did not complete fully. The transaction remains linked to the user who originally processed it. Rollback transactions appear with an 'R' flag in the batch list.
Rollback transactions must be posted from the batch — they must not be manually cleared or deleted, as this can cause balance errors.
Open the affected ledger batch (for example, Financials > Nominal Ledger batch for a nominal journal rollback).
Look for any transaction with an 'R' flag next to it.
Log in as the user who originally processed the transaction — the batch is linked to their session.
Open the transaction and post it again (green tick). The system will continue the posting from where it stopped.
If no 'R' transaction is visible in the main batch, check the Recurring Journals batch as well.
If the rollback cannot be resolved by reposting — for example, if no user can be identified or the batch is inaccessible — raise a support case including the affected batch number and the ledger.
For the specific period end error 'You cannot continue with the Period End as there are rollback transactions in the current batch', see the dedicated articles for the Sales Ledger and Nominal Ledger versions of this error.
Nominal code and T-Code errors
These errors occur when a transaction references an account code, T-Code, or VAT code that does not exist or is not active in Dimensions. They typically surface in the Interface Exceptions screen or during batch posting.
Invalid T-Code error
If you see a 'Batch XXXXXXX — Invalid T-Code XXXXXX' error, the T-Code referenced in the transaction does not exist in Dimensions. To check or create it:
Navigate to Nominal Ledger from the home page.
Click Setup, then open Nominal Elements.
Filter by Transactional Analysis and search for the T-Code from the error message.
If the code does not exist, right-click in the grid and select New to create it.
Once created, re-process the failed transaction.
Invalid nominal account, account code, or VAT code
If the exception states that a nominal account, account code, or VAT code is not valid, the account does not exist in Dimensions. You have two options:
Create the account — add the missing nominal account or VAT code directly in Dimensions.
Create a translation — map the incoming value to an existing account using the Interface translation rules (System Admin > External Interfaces > Interface Control Panel > Translations tab), so future transactions with the same code are automatically redirected.
Missing nominal analysis data
A 'Missing Nominal Analysis Data' error during batch posting usually affects a single transaction. The Error or Verification box shows the Reference number and line number. You have two options:
Fix and keep — on the Lines tab of the batch, enter a Nominal Account in the Nominal column for the affected transaction. This creates the required entry in the Nominals tab and allows the batch to post.
Remove and post manually — remove the affected transaction from the batch, post the rest as normal, then raise the removed transaction manually against the correct account.