Skip to content

Rebuild Object Values

A housekeeping operation that reassembles the fast-balance store — the monthly account balances from which the Nominal Ledger Report and the Analytical Balance take the opening balance of a period.

Where to find it: Modules → Database Maintenance → Maintenances → Rebuild Object Values

A worked example

Rebuild transactions

No parameters. The service wipes the store and rebuilds it from all transactions and Forward Balances: per account, month (for a transaction — by the row's date, for a forward balance — by the document's date), currency and combination of objects; a row without a date does not go into the store. Every amount is rounded by the current by default rule of the company's Rounding setting — the same way as when an entry is posted. The service does not change the entries themselves; it only removes transaction and forward balance rows left without a header.

In a multi-company database the service rebuilds the store of every company, not only the one it was started in. It all runs in one transaction: if something breaks halfway, the store stays as it was before the run.

Why it is needed

Normally the store keeps itself up to date: every posting, change or deletion of an entry updates its balances at once. A rebuild is needed when the store has drifted away from the entries:

  • Rounding was changed — months written earlier stay on the old rule, new ones follow the new rule;
  • entries were edited directly in the database, bypassing the system;
  • the store was written by an older version (before 24.09.2026 forward balances went into it by another rule: unrounded, under the wrong currency and without all combinations of objects).

Typical situations

The Nominal Ledger Report gives different balances for the same day. A report for 01.10–14.10 and a report from the start of accounting to 14.10 differ by a few cents. The opening balance comes from the store and the period's movements from the entries; a difference means the store was written by another rule. After a rebuild both reports agree.

The service takes a few minutes. It walks every entry row: on a database with 64 thousand rows, about 2.5 minutes. Wait for the "Operation completed successfully!" message. You can post documents and run reports meanwhile: changes that arrive while the service runs go into the store after it finishes.

Where to look next