Product · 5 Jun 2026 · 4 min read
Ten reporting dimensions on every journal
Slice reports by department, project, region and more, without bending the chart of accounts.
A chart of accounts should explain what a transaction is. It should not have to encode every department, project, location, funding stream, or product line that the business may want to analyse later.
Finovio now supports up to ten dimensions on each journal line, giving those reporting structures their own place while keeping the chart of accounts focused on accounting classification.
Classification at line level
Dimensions are attached to individual lines rather than the journal header. Two lines in the same journal can therefore carry different departments or projects when that reflects the underlying activity.
The same ten indexed fields are used consistently across posted journal lines, draft manual journals, invoice lines, and reconciliation-rule allocations. A value selected earlier in the workflow follows the accounting entry into the ledger instead of being held in a separate note.
Built into manual journal workflows
Active dimensions appear beneath each line in the manual journal editor. Workbook templates include the configured dimension columns too, so larger journals can be prepared outside the browser and checked before they become a draft.
On import and save, Finovio validates dimension values against the selected subsidiary. The value must belong to the correct dimension, come from the subsidiary's active dimension source, and still be active. Invalid or retired values stop the draft rather than creating an entry that cannot be analysed reliably.
One structure across a group
A child subsidiary can derive dimensions from its parent. This gives related entities a shared department or project structure without maintaining the same list repeatedly.
If a subsidiary later moves to local dimensions, Finovio clones the inherited definitions and remaps existing references. Journal lines, invoice lines, ruleset allocations, and draft manual journals continue to point to the corresponding local values.
History stays understandable
Dimension values are anchored by identifier, so renaming or recoding a value does not detach old transactions. Retiring a value prevents new use while retaining its history. Deleting a whole dimension is deliberately stricter: it must first be deactivated, and stored references are then cleared across the affected workflows.
This lifecycle gives reporting a dependable classification layer. Dimension filtering and aggregation can be built on the same journal-line data without multiplying accounts or redesigning the ledger whenever management reporting changes.