The register
worth buildingOracle Fusion / Workday, built properly
Grouped rows per business unit with subtotals and a grand total, variance in parentheses in the accounting convention, a “Reconciled By” column naming a human, breadcrumbs, a filter bar, Save View and Export. This is what the software actually looks like inside a company this size, and it is unusually well made for what it is.
Against it — Zero visual ambition by design. It will impress a controller and bore a designer.
Close overview
worth buildingEnterprise BI, done right
A grouped column chart by location, a gross-to-recognised waterfall, a deferred-balance line, and a wide summary table with three months side by side. The waterfall is the single best explanatory chart for this problem — it shows exactly where gross revenue goes before it becomes recognised revenue, which is the whole story in one panel.
Against it — Conventional. Every finance org has seen this layout, which is both the strength and the limit.
Corporate design system
worth buildingWhat a public company ships to its own finance team
Clean white, one restrained brand blue, accessible contrast, a summary strip, a priority-split bar chart and a paginated exception table with muted status pills. Recognisably built on a mature design system rather than assembled ad hoc — the most obviously *maintainable* option here.
Against it — The most anonymous of the three. Competent, familiar, forgettable.
Treasury operations
worth buildingConservative bank, two-column discipline
Navy header, strict two-column split — reconciliation status left, exception queue right — monospaced figures for exact alignment, uppercase section heads, ageing buckets. Only navy, red and green beyond grey. Severe, and severity reads as seriousness in a finance room.
Against it — Old-fashioned enough that it needs to be deliberate rather than accidental, or it reads as dated.
Close pack
interestingThe document finance actually circulates
A printable month-end exceptions report: a summary matrix of recognised, deferred and contested by category, then a numbered schedule with reference numbers, owners and target resolution dates, ruled totals double-underlined. It is the only option whose output someone could hand to an auditor unchanged.
Against it — It is a report, not a tool — no interaction, no live state. Best as one view among three, or as an export.
Controls memo
interestingBig Four deliverable as software
Numbered sections, a narrative summary paragraph opening the page the way an audit memo would, a legend explaining the notation, footnote markers, and a Prepared By / Reviewed By block. The narrative-before-numbers move is genuinely good and nothing else here does it.
Against it — Heavy. A dashboard that opens with a paragraph is a dashboard people stop reading.
Sober dark
workableDark without the science fiction
Warm dark grey rather than black, no glow anywhere, desaturated status chips in dusty red and sage. Proves dark can be done without looking like a spaceship, and the reconciliation table carries source balance beside GL balance with the difference between them.
Against it — Dark still reads as a developer tool rather than a finance system, which is the opposite of the brief.
Market workstation
off-briefInstitutional density, light theme
The density register is right — many panes, hairline rules, decimal-aligned figures, nothing decorative.
Against it — It rendered a bond-rates workstation instead of a reconciliation screen, and put a real vendor’s mark on it. Read the density, ignore the content.