Review automatic ledger bookings

Automatic booking rules connect loan instalments, payments and allocations to ledger accounts. Finsaku compares the configured account amounts before and after a supported loan operation and posts the change. Use Automatic Booking to review the rules used by your tenant.

Task detail	Description
For	Ledger administrators and operations users checking how loan activity reaches the general ledger.
Requires	View ledger configuration to inspect rules, and View ledger transactions to check postings.
Available when	Your account can open Administration → Ledger → Automatic Booking. Postings depend on the rules configured for the tenant.
Before you begin	Identify the loan operation, currency and expected account movements. Check the chart and required currency rates.
Expected result	You can explain which configured amounts changed, locate the resulting bookings, or identify why no booking was made.

Read the configured rules

Open Administration → Ledger → Automatic Booking. The page title is Automatic booking configuration.

Open in Finsaku: review automatic booking rules

This page is read-only. It has no add, edit or delete action. Use Reload to fetch the current rules after a configuration change; reloading does not create ledger transactions. Arrange rule changes with the administrator responsible for your organisation's ledger setup.

Column	What it tells you
Direction	Debit or Credit, used to calculate the rule's contribution to its account.
Account	Account code and name. The account's currency determines which loans the rule can affect.
Description	The configured explanation of the amount being booked.
Amount source	Installment lines, Payment allocations or Payments.
Installment line types	The included line types, All line types, or Not applicable for a Payments source.
Payment Type	A specific payment type, All payment types, or Not applicable for an Installment lines source.

Rules and account codes are tenant configuration. An empty table is not evidence that a loan operation failed: without configured amounts, the operation can complete without an automatic ledger transaction. If a loading error is shown, resolve that error before interpreting the table as empty.

Distinguish the amount sources

Amount source	Included amounts	Available restrictions
Installment lines	Full amounts on active instalments; allocated amounts on cancelled instalments.	One or more line types, or All line types. Payment type does not apply.
Payment allocations	Amounts allocated to instalment lines, including retained allocations on cancelled instalments.	Line types and payment type. Both restrictions must match when specified.
Payments	Recorded payment amounts linked to the loan, whether or not their full amount has been allocated.	Payment type. Instalment line types do not apply.

For line types, any listed type can match. All line types means there is no line-type restriction. All payment types means there is no payment-type restriction. A rule contributes only when its account currency matches the loan currency.

The distinction between payment totals and allocated amounts allows a configuration to record received money separately from its use against principal, interest, fees or other instalment lines. Check your tenant's rules to see which accounts receive those amounts. Do not infer an account movement from a payment's allocation outcome alone.

When bookings are created

Automatic booking checks run around these operations:

Loan operation	Booking date
Issue a loan through an application issuing action, including an applicable application changing an existing loan	The issue date.
Add or delete an instalment	The date the operation is performed.
Record or allocate a payment through the loan's payment operation	The date the operation is performed.
Delete the last loan payment, where that action is permitted	The date the deletion is performed.

The payment date and ledger booking date can therefore differ. Use the ledger booking date when searching for the resulting transaction.

Finsaku totals the configured debit and credit contributions for each account before and after the operation. It posts only the difference. A newly issued loan starts from no previous amounts. A removed amount can produce a movement in the opposite direction. If all configured account amounts remain unchanged, no transaction is created.

Where an account requires references, automatic bookings include the loan under Contract and its borrower under Party. An account that does not require a reference does not receive that reference automatically. A loan filter will therefore not find a transaction whose bookings have no loan reference.

These checks happen as part of the supported operation. Opening the configuration page or changing a rule does not itself create bookings for earlier loan activity.

Check the result against the loan operation

After a successful operation, open Workspace → Ledger → Transactions and search the applicable booking date. If the configured accounts require a loan or party reference, use Contract or Party to narrow the results.

See Review ledger transactions and account balances for the filters and transaction details.

Open in Finsaku: inspect the resulting transactions

Compare the transaction with the operation that produced it:

For issuance or an instalment change, compare the affected instalment line types and amounts with the Installment lines rules.
For a payment, compare the recorded payment amount with Payments rules and its distribution with Payment allocations rules. The two totals can differ when part of the payment is not allocated.
For a deletion or recalculation, compare the change in configured amounts. The booking is the difference, so it need not repeat the original transaction's full amount.
Check account currency, converted base amounts and any required loan or party references. On-balance and off-balance lines must balance separately.

Account balances appear only when Account is selected and Contract, Party and Currency are empty. These opening and closing balances use the selected account and dates, including its child accounts.

Resolve missing or rejected bookings

Finsaku saves the loan operation and its automatic ledger transaction together. If posting is rejected, the loan operation is rolled back. For example, a missing currency rate, an inactive mapped account or an unbalanced set of movements can prevent a payment allocation from completing.

Loan operation and booking outcomes

Result of the automatic booking check	Outcome
Configured amounts changed and the posting is valid	The loan operation and ledger transaction are saved together.
The posting is rejected	The loan operation is rolled back. Neither change is saved.
No configured amount changed	The loan operation completes without a ledger transaction.

Situation	What to check
The operation succeeded but there is no transaction	Confirm that rules exist, their account currencies match the loan, and the operation changed a configured amount. Check the operation's booking date and remove loan or party filters if the mapped accounts do not require those references.
The transaction differs from the payment amount	Compare payment totals and allocated amounts separately, then compare before-and-after account amounts. Several contributions to one account are combined.
Posting reports an unavailable account	Check that each mapped account is an active Detail account with the intended currency.
Posting reports no currency rate	Check the booking date and rate history.
Posting reports an unbalanced transaction	Have the ledger administrator review the full set of matching rules. Debits and credits must balance in base currency, and on-balance and off-balance movements must each balance separately.
The response was interrupted or unclear	Check the loan, payment or instalment result and the transaction list before retrying. An uncertain response alone does not establish whether the operation was saved.

After correcting the cause of a confirmed failed operation, retry the loan operation and check its saved result and ledger transaction. Do not add a separate manual booking merely to bypass an automatic-posting error; a later successful retry will create the configured booking as part of the loan operation.