{21/05/2026: Preliminary discussion about this in Business Prod.
There will be a NEW SEPARATE and specific screen only for journal autobalancing (mainly to discourage incorrect practices but keeping flexibility). Permissions will have to be granted as technically using a temporary account or auto balancing is not ideal re accounting principles. Based on the discussion we had with George during Business prod (check linked video above), I've drafted a sample article interacting with Copilot which reflects the new changes. This is to be used as reference for when the new screens and setting will be implemented in the system. ONCE REWRITING THIS ARTICLE, PLEASE LISTEN TO THE VIDEO AGAIN TO CHECK WHETHER ALL WAS INCLUDED IN THE SAMPLE AND PROCEED WITH THE NEEDED MODIFICATIONS.
⚠️ ASK GEORGE TO GO THROUGH THE NEW SCREENS ONCE THEY WILL BE THERE AND TO GO THROUGH THE PREREQUISITES AGAIN
ROUGH SAMPLE REFERENCE ARTICLE
ROUGH SAMPLE REFERENCE ARTICLE
Here is the fully aligned article, with the corrected logic (“complete the double entry” via contra entries), your practical examples, and consistent terminology throughout.
Auto Balance in Journals
The Auto Balance setting allows users to ensure that journals remain balanced by automatically generating contra entries per date against a predefined account. This supports accurate accounting while handling real-life timing differences in transactions.
How Auto Balance Works
When creating a journal using auto balance, the user selects an auto balancing account at the top of the entry. This account is used by the system to generate balancing entries where required.
The user then enters the journal lines, including their respective dates and nominal accounts. The system evaluates the entries per date, ensuring that each date satisfies the double-entry requirement.
If, for a given date, the entries do not form a complete double entry, the system will:
Automatically create a matching contra entry
Post it to the selected auto balancing account
This contra entry completes the double entry for that date, ensuring that total debits and credits are equal without altering the original entries.
Each date within the journal is therefore treated independently and remains fully balanced.
Why This Setting Exists
In accounting, it is essential that journals balance at each individual date, as financial records and reports rely on accurate balances at specific points in time.
However, in practice, some transactions naturally span multiple dates or are recorded in batches. In these situations, it is not always possible to form a complete double entry within the same date using only the original transaction lines.
The auto balance setting addresses this by:
Completing missing sides of entries per date
Using a dedicated account to temporarily hold these contra postings
Preserving both the true timing of transactions and compliance with double-entry principles
This ensures that operational realities do not compromise accounting accuracy.
Who Can Use It
This functionality is intended for:
Accountants and finance teams handling journal entries
Users working with aggregated or timing-sensitive data
Authorised users, as permissions can control access
Practical Scenario
The auto balance setting is particularly useful in real-life situations where transactions cannot naturally balance on the same date or are recorded in batches.
Bank transfers between accounts
A common example is a transfer between two bank accounts that settles on different dates.
For instance:
On 1st of the month, a transfer is initiated from Bank Account A (recorded as a debit)
The funds are received in Bank Account B on 3rd of the month (recorded as a credit)
Although this correctly reflects the movement of funds, the entries do not form a complete double entry on each date:
On the 1st, the credit side is missing
On the 3rd, the debit side is missing
With auto balance enabled:
On the 1st, the system creates a contra credit entry in the auto balancing account
On the 3rd, the system creates a contra debit entry in the same account
This ensures that:
Each date forms a complete double entry
The timing of the transaction is preserved
The temporary difference is clearly tracked in a single account
Employee expense reimbursements (batched processing)
Another example is employee expense reimbursement processed in batches.
For example:
Employees incur expenses on different dates during the week
Receipts are collected and not immediately recorded
At the end of the week, a single aggregated journal is entered
In this case:
Entries may be grouped by date or summarised
Individual dates may not naturally form complete double entries
With auto balance enabled:
The system creates contra entries per date in the auto balancing account
Each date satisfies the double-entry requirement
Any temporary differences are clearly isolated for later review or allocation
Benefits and Accounting Assurance
Using the auto balance setting provides the following benefits:
Balanced journals per date
Each date satisfies the double-entry principleAccurate trial balance
The trial balance will always reconcile, as total debits and credits remain equalPreservation of transaction timing
Entries reflect the actual dates of events without forcing artificial adjustmentsClear traceability
All contra entries are recorded in a single, dedicated accountSimplified reconciliation
Balances in the auto balancing account can be reviewed and allocated as neededReliable financial reporting
Reports such as the general ledger, trial balance, and financial statements remain consistent and accurate
Summary
The Auto Balance setting ensures that journals remain balanced per date by automatically creating contra entries against a predefined account. This allows organisations to handle real-world timing differences and aggregated postings while maintaining compliance with core accounting principles and ensuring accurate financial reporting.
}}
Table of Contents
Introduction
The Journal Auto‑Balancing setting helps keep your journals balanced when a transaction does not meet the double-entry accounting rules. This happens when the total batch amount is not zero, meaning debits and credits are not balanced.
{{TO BE REMOVED POTENTIALLY 👇 AS BEHAVIOUR CHANGED --> asked George. CHECK COMMENT IN BOLD ABOVE}}
The total batch amount is not zero (an error is triggered at posting)
Debits and credits do not balance on the same date, meaning a contra entry is missing per date (an error is triggered at posting).}}
When enabled, the Journal Auto-Balancing setting, it automatically creates missing contra entries so that each journal date includes both a debit and a credit and the total batch balances correctly.
Enabling the Journal Auto-Balancing Setting
To enable the Journal Auto-Balance company go to Settings & Pref > General > Company Maintenance > Additional Settings button at the top right.
How it Works
When posting a journal, the system will inform you that the Auto Balancing setting is enabled, and ask if you're sure to proceed.
When you select Post, the system automatically creates contra entries for each unbalanced journal line item, using the previously created Auto-Balancing Account.
This way the Total Batch Amount is zero and there's a debit and a credit offsetting each other for each recorded date.
📋 Note: If the journal is already balanced, no additional entries will be generated against the Journal Auto-Balancing account. Only the recorded debits and credits will be posted against the specified accounts.
If an entry falls into a separate accounting period (e.g. 01/06 instead of 31/05 ) the system would impede the auto-balance process.
Example
Example
You need to record gas, food and printing paper expenses for the month of May in a journal and post it against your Nominal Ledger. Find out how it should be posted in the collapsible section below.
Proper Posting
Proper Posting
SAMPLE JOURNAL:
Transaction Date | Debit | Credit | Accounts | Offset to Date? |
04/05/2025 | 50€ (VAT incl.) |
50€ | Fuel
*Cash Account |
✅ |
17/05/2025 | 100€ (VAT incl.) |
100€ | Groceries
*Cash Account |
✅ |
27/05/2025 | 20€ (VAT incl.) |
20€ | Stationary
*Cash Account |
✅ |
Credits and debits are offsetting each other on every transaction date, as they should. 🎉 No error will be triggered.
Common Habit {we should not promote this --> it's against the accounting practices}
Some accountants, though, decide to speed up the above process by creating a single credit line totalling all the recorded debits (or vice versa), if the account involved is always the same. (e.g. *Cash Account). 👇
Transaction Date | Debit | Credit | Accounts | Offset to Date? |
04/05/2025 | 50€ (VAT incl.) |
| Fuel
|
❌ |
17/05/2025 | 100€ (VAT incl.) |
| Groceries
|
❌ |
27/05/2025 | 20€ (VAT incl.) |
| Stationary |
❌ |
31/05/2025 |
| 170 (VAT incl.) | *Cash Account | ❌ |
While the Total Batch Amount would still be zero (170€ debits (VAT. incl.) = 170€ credits), there isn't a credit and a debit offsetting each other for each transaction's date, which is against the double-entry principle.
Therefore, the system will throw an error message as the transaction is not balanced on each date. ⬆️
🪄 The solution? Enable the Auto-Balancing setting, repost your transaction as you would normally do, and you're good to go. No error messages will be shown.
❗ Please note that the data specified above are purely to make this example as clear as possible. In most of the cases, those expenses are accounted for via purchase invoices. More on them 👉 here.
Related Articles




