Designing GAAP Consolidation Beyond the Spreadsheet

If you’ve ever produced consolidated financial statements by hand, you know the mechanics: pull each entity’s trial balance, eliminate intercompany investment and equity, allocate non-controlling interest when ownership is below 100%, and reconcile the whole thing until it ties out. The process often involves a spreadsheet that teams rebuild, check, and review every close.

Start with ownership as a first-class relationship

LedgerWriter’s planned consolidation model treats corporate ownership as data. A tenant (company A) can own a stake in another tenant (company B) through a defined, queryable relationship. Consolidation needs two distinct pieces of information: who has access and who financially owns what.

What this model is designed to support

With ownership recorded as a relationship, the reporting layer is designed to support the following capabilities:

• Investment elimination as a computed projection. The parent’s investment in the subsidiary and the subsidiary’s corresponding equity are considered when a consolidated statement is generated.
• Non-controlling interest based on the ownership percentage on record.
• Access that follows the accounting relationship. Viewing company A’s consolidated statements, which pull in subsidiary B’s data, requires a sufficient role in A. A’s ownership of B grants report-scoped read access for consolidation purposes.

The goal is repeatable correctness

As entities and ownership percentages change, a projection computed from the ownership relationship and the underlying ledger data gives the report a consistent source. This capability is on the LedgerWriter roadmap; the architecture is the foundation for implementing it carefully.