What is Nominal Code 0.0.70.98, and How Do I Correct Entries?

Modified on Fri, 12 Sep at 11:13 AM

Nominal code 0.0.70.98, known as the Non-Zero Correction Account, is a system-generated account used to temporarily balance the trial balance when a batch posting does not complete correctly. This guide outlines how to identify and correct entries posted to this account.


Purpose of 0.0.70.98

  • When a batch posting does not balance to zero, the system automatically posts the opposite entry to 0.0.70.98 during the overnight routine.
  • This keeps the trial balance in balance, allowing you to manually journal the amount out to the correct nominal account later.

Steps to Correct Entries in 0.0.70.98

1. Identify the Batch Creating the Entry

  1. Run a Transaction Report for 0.0.70.98:

    • Navigate to Navigator > Nominal Ledger > Transaction Report.
    • In the Code field, enter 0.0.70.98.
    • Set a date range (recommended: up to one year back from the current date).
    • Run the report to view all transactions currently in 0.0.70.98.
  2. Make a Note of Transactions:

    • Record the dates and amounts of each entry in 0.0.70.98.
    • Export the data to a spreadsheet or notepad for easy reference.

2. Investigate the Original Batch

  1. Search for the Batch:

    • Reset the Transaction Report.
    • Leave the Code field blank and enter the first date from your list in Date From and Date To.
    • Run the report.
  2. Filter by Batch Number:

    • Drag the Batch Number column header to the grey bar to group by batch.
    • Look for batches that do not balance to zero.
  3. List Non-Balancing Batches:

    • Note the batch numbers and corresponding amounts.
    • Be aware that a single entry in 0.0.70.98 may be the result of multiple batches.

3. Review and Correct the Batch

  1. Run a Transaction Report by Batch:

    • Reset the Transaction Report.
    • Change the search criteria to Batch instead of Code.
    • Enter the batch number and run the report.
  2. Identify the Correct Nominal Account:

    • Investigate the details of the batch to determine where the amount should have been posted.
  3. Journal the Amount Out of 0.0.70.98:

    • Post a journal to move the amount from 0.0.70.98 to the correct nominal account.
    • Include a clear Reference for future traceability.
    • If the journal relates to a stock record, job number, or similar, ensure you fill in the corresponding fields in the journal.

Key Notes

  • System Behaviour: 0.0.70.98 is a safeguard account and does not indicate a critical error.
  • Accuracy: Double-check the amounts and ensure the journal entry resolves the discrepancy fully.
  • Documentation: Always add a reference to your journal entries for easy identification later.
  • Batch Investigation: Be thorough when investigating batches to prevent recurring issues.

Example Scenario


Below is the value we are looking for in this example.


To review this, run a transaction report on 0.0.70.98 and identify the 2 transaction values

Then double click on the transaction lines to get the nominal dates and not this down



Run a transaction report for the nominal date, and drag the batch up to the grey area to sort (below you can see batch 0)


Then scroll down to find the opposite entry and note down the stock number and batch number.


Run a transaction report by that stock number and drag the nominal code field up to the grey area (this helps identify where there may be a difference)

Reviewing this 1.31.60.83 has a balance that matches the opposite entry in 0.0.70.98 - this is debtors and is a closed deal (can tell this as 1.31.70.97 is zero) so debtors should also be zero.


So the correction here is to post a journal between 0.0.70.98 and 1.31.70.97

0.0.70.98 20500 (do not enter the stock number)
1.31.60.83 -20500 (enter the stock number including the branch)

Repeat the process with the other stock number 
1.31.70.97 (this should be zero on closed deals)

so the journal here would be
0.0.70.98 -150 (do not enter the stock number)
1.31.70.97 150 (enter the stock number including the branch)

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article