This guide covers the three most common categories of ledger transaction failure in Safe Financials. Work through the relevant section based on the error or symptom you are seeing.
1. Nominal code mismatches
Nominal code errors occur when a transaction references an account code, T-Code, or VAT code that does not exist or is not valid in Safe Financials. 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 Safe Financials. 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.
Invalid nominal account, account code, or VAT code
If the interface exception states that a nominal account, account code, or VAT code is not Valid, the account does not exist in Safe Financials. You have two options:
Create the account — add the missing nominal account or VAT code directly in Safe Financials.
Create a translation — map the incoming value to an existing account using the Interface translation rules, so future transactions with the same code are automatically redirected.
To set up a translation, go to System Admin > External Interfaces > Interface Control Panel, select the relevant source, and use the Translations tab.
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 account.
2. Batch rejections
Batch rejections occur when Safe Financials refuses to post a batch, either from an external interface (such as KOFAX) or from within the application itself.
KOFAX invoice validated but not posted to the ledger
If an invoice is validated in KOFAX and sent to Safe Financials but does not appear in the ledger, it is likely sitting in the Interface Batch screen. To check the rejection reason:
Click System Admin > External Interfaces > Interface Control Panel.
Select the Source ID that refers to the KOFAX system.
On the Batches tab, locate the relevant batch number.
Right-click the batch and select Exceptions Log to see the rejection reason.
The most common rejection reason is a Supplier Currency Code mismatch — the supplier account in Safe Financials has a different currency code from the transaction sent by KOFAX. To resolve this, either update the supplier's currency code (Purchase Ledger > Suppliers > find the account > Suppliers subtab > Currency Code) or create a new supplier account with the correct currency code.
3. Interface error patterns
Interface errors occur when transactions fail during import from an external system into the Safe Financials interface. The Interface Exceptions screen is your primary diagnostic tool.
Checking the Interface Exceptions screen
Click System Admin > External Interfaces.
Select Interface Exceptions.
Filter by date range and source system to find relevant exceptions.
Note the error message — this determines the resolution path (see sections above for nominal code and batch errors).
Invoice cannot be processed — error log
If an invoice fails to process and is recorded in the error log, work through these checks before raising a support case:
Check the posting period — in the affected ledger (Sales, Purchase, or Nominal), go to Processing > Period Controls and confirm the invoice date falls within an open period.
Check for rollback transactions — if the error appears during or after a period end, a rollback transaction may be blocking the batch (see Rollback transactions above).
Check for batch conflicts — confirm no other user has the same batch open or locked.
If none of the above resolves the issue, the error log entry will contain the detail needed to raise an accurate support case.