If an invoice or batch is failing to post to the ledger, the error message will usually tell you what to fix. This article covers the most common posting errors and how to resolve them without raising a support case.
"There are no detail lines to post"
This error appears when you attempt to post a batch that contains no valid transaction lines.
Open the batch and confirm that at least one detail line has been entered and saved.
Check that no lines have been deleted or left in an incomplete state (e.g. missing nominal code or amount).
If the batch appears empty, close it without saving and re-enter the transaction from scratch.
If lines are present but the error persists, check that the posting period is open under Nominal Ledger > Options > Periods.
"The transaction ended in the trigger. The batch has been aborted."
This is a database-level error triggered when a posting violates a system constraint, most commonly a duplicate key or a locked record.
Do not retry the posting immediately — wait 2–3 minutes to allow any database locks to clear.
Check whether another user is currently in the same batch or has the same record open.
Verify that the nominal codes on the transaction lines exist and are active (Nominal Ledger > Chart of Accounts).
If the error recurs, note the exact batch reference and contact support — this may require a database-level investigation.
"The lines selected do not match the Invoice totals"
This occurs during invoice approval when the sum of detail lines does not equal the invoice header total.
Open the invoice and compare the header total to the sum of all detail lines.
Check for rounding differences — a 1p or 1c discrepancy is the most common cause.
Adjust the last detail line by the rounding difference to bring the totals into agreement.
If VAT lines are included, verify that the VAT amount matches the calculated tax on the net total.
"A sales ledger invoice already exists with invoice number X. Please use reset print status to enable these orders to be printed on a new invoice."
This error means the invoice number has already been used. Dimensions prevents duplicate invoice numbers to maintain audit integrity.
Go to Sales Ledger > Invoices and search for the duplicate invoice number to confirm it exists.
If the existing invoice was posted in error, use the Corrections module to reverse it before re-posting.
If the invoice number was generated by the system and has already been used, contact your system administrator to review the invoice numbering sequence.
"Subquery returned more than 1 value"
This is an underlying database error that typically indicates a data integrity issue — for example, duplicate records in a lookup table.
Note the screen you were on and the exact action you were performing.
Do not retry the action, as this may compound the issue.
Contact support with the error message and the batch or transaction reference — this requires backend investigation.
General posting checklist
Confirm the posting period is open (Nominal Ledger > Options > Periods).
Confirm no other users have the same batch or record open.
Confirm all nominal codes on the transaction exist and are active.
Confirm the batch header date falls within the open period.
If using multi-company, confirm you are posting to the correct company entity.