Balancing

Specify this information:
Balance By

This determines the level at which the journal transactions must balance. If this level of balancing is required, you can force the transactions to balance by transaction date, transaction reference, or one of the ten ledger analysis codes. See 'When is a Journal In Balance?'

Allow Bal Txns When Post if no Err
This option allows the system to generate and post balancing transactions if there is an imbalance in the base amount or in any of the currency values that require Amount Balancing, as determined on the Business Unit Setup. The option is only effective when the Post Transactions (On Import) option on the Posting tab is set to Post if no Errors.

Use this option in conjunction with Post if no Errors if you want to permit an imported journal to be posted even if it is unbalanced, whilst nevertheless preventing the journal from being posted if it contains other errors, such as prohibited analysis codes, closed accounts, dates, or periods, or violates a business rule condition.

There are three possible settings for this option:
- Never - imbalances are treated as errors that prevent the journal from being posted.
- Generate Exchange Differences - balancing adjustments are generated for imbalances due to currency conversion rounding differences, and all other imbalances are treated as errors that prevent the journal from being posted. Adjustment transactions are posted to the corresponding Balancing Accounts identified on the Business Unit Setup Value 1, Value 2, Value 3 or Value 4 tab, depending on the currency value being adjusted (providing that the rounding difference is within the threshold for that currency value, also specified on the Business Unit Setup).
- Generate Balancing Transactions - for any imbalances detected, balancing adjustments are posted to the Error Suspense Account, the Other Account or the Reporting Account specified on the Validation tab, depending on the currency value being adjusted.
For an imbalance to be considered as due to a currency conversion rounding difference, the journal must balance in at least one of the currency values.

Note: Analysis codes are validated on the system-generated balancing lines, however, the posting rules for these are not as stringent as for the original transactions being imported. That is, analysis code violations on the system-generated balancing lines do not prevent transactions from being posted, however, the violations are mentioned on the import report. For example, a generated balancing line might have an analysis code missing, for which the analysis dimension is specified as mandatory on the account. In this case, the balancing transaction is posted to the account with a blank analysis code, and an appropriate message is written in the import report. This is intended to facilitate 'fine tuning' of your ledger import process (with respect to balancing, accounts and analysis), whilst not actually preventing the import file from being posted. If necessary, analysis codes can be subsequently added or amended using Account Allocations (ACA).
Save your changes.