01
The stored-truth problem
Truth is reconstructed, not stored.
Financial truth doesn't live anywhere. It's rebuilt at month-end from a dozen tools that don't agree.
One ledger. The truth is stored once, with the evidence attached.
About Lunari · The problem we exist for
Finance runs on fragmented systems.
A dozen tools that don't talk. A close that becomes a salvage operation. A truth reconstructed every month, never stored. Lunari was built to end that pattern.
lunari.cloud / close · december
Close · December 2025
Day 3 of 5 · Balance sheet
Reconciled
5 / 8
63% reconciledLocks 17:00 UTC · Owner Priya M.
CodeAccountBalanceOwnerStatus
1010Cash · USD operating4,218,440 USDPMReconciled
1020Cash · EUR operating1,884,210 EURPMReconciled
1200Accounts receivable9,442,118 USDSRReconciled
1410Prepaid expenses422,118 USDJTIn review
2100Accounts payable3,118,402 USDMAReconciled
2400Accrued payroll918,221 USDJTOpen
2600Deferred revenue6,221,840 USDSRIn review
3000Common stock1,000 USDPMReconciled
Financial truth is not stored. It is reconstructed. Every month. That is the problem Lunari solves.
Operating thesis · written on the wall
Six problems · named plainly
What we found inside the finance function.
06 problems → 06 answers
02
The patchwork problem
The stack is a museum of point tools.
BlackLine, FloQast, Coupa, Bill.com, Tipalti, Zuora — fine alone, brittle together.
One platform. One data model under every module.
03
The dirty-data problem
AI bolted onto ledgers nobody normalised.
The output is fluent, confident, and frequently wrong. The model can't see the business clearly.
Event-sourced ledger. PO, invoice, journal and audit share keys.
04
The bolt-on audit problem
Governance arrives after the fact.
Audit modules sold once you're live. By then the evidence chain is already broken.
Immutable log, evidence linked, SOD enforced in code.
05
The lean-team problem
Fewer people, same closing date.
Headcount cut. IFRS 17, ASC 842, SOX still growing. The integration tax is now a survival issue.
Built for the team closing five entities in three currencies.
06
The slow-close problem
Ten to fifteen days, every month.
Two weeks of variance hunting and PBC chasing. The close hasn't moved in twenty years.
Day-1 close. The work happens continuously, not after period-end.
A working example
The three-way match, in one screen.
In most finance stacks, matching a PO to a receipt to an invoice means three logins, two CSV exports, and a controller squinting at an email thread. In Lunari, it's one row — the evidence is already linked, the variance is already flagged, and the journal is already drafted.
- ✓PO, GRN, and invoice live on the same record.
- ✓Variance > 2% routes to AP automatically.
- ✓Approval logged in the audit trail, not an inbox.
- ✓Journal posts on approval — no batch run.
lunari.cloud / p2p / invoice 4421
Invoice INV-44218 · Northwind Logistics
Three-way match$ 18,420.00 USD
Purchase order
PO-2118
- Pallet handling · 200u$ 14,000.00
- Freight surcharge$ 3,200.00
- Documentation$ 1,220.00
Goods receipt
GR-991
- Pallet handling · 200u$ 14,000.00
- Freight surcharge$ 3,200.00
- Documentation$ 1,220.00
Invoice
INV-44218
- Pallet handling · 200u$ 14,000.00
- Freight surcharge$ 3,200.00
- Fuel adjustment$ 1,220.00
Line 3 description differs from PO — within tolerance, routed to Megan for one-click approval.
The stack we replace
A category of tools, retired by one platform.
Lunari removes the seams. These are some of the tools customers switch off when they move onto the platform.
- BlackLineReplaced
- FloQastReplaced
- CoupaReplaced
- Bill.comReplaced
- TipaltiReplaced
- ZuoraReplaced
Why now
Three pressures the old stack
cannot absorb.
The conditions that allowed fragmentation to feel acceptable have ended. Lean teams, AI expectations, and regulatory load have made integration tax a survival issue.
01
AI expectation
Teams must deliver more analysis with AI in the loop. Only possible on data that's clean, linked, event-sourced.
02
Lean teams
Headcount cut and unlikely to return. Every hour reconciling between tools is an hour the team doesn't have.
03
Regulatory load
IFRS 17, ASC 842, SOX, e-invoicing. Compliance must be a property of the system — not a project on the side.
How we answer
Four architectural choices that change the work.
Most platforms are built around screens. Lunari is built around data. Every choice below is downstream of one belief — that the ledger should know about the world, and the world should be able to prove the ledger.
I.
One data model, not seventeen integrations.
PO, invoice, journal, reconciliation, and audit evidence share the same primary keys. Nothing to reconcile between systems — because there is only one system.
II.
Evidence attached, by default.
Every number on every screen carries a link back to the document, the approval, and the bank message. We refuse to ship a feature that breaks that chain.
III.
Governance written in code, not policy.
Segregation of duties, immutable logs, and approval thresholds are enforced by the platform — not by a quarterly access review.
IV.
Bought once. Grown into.
One contract. One onboarding. Every module shares users, roles, entities, and chart of accounts. The next module takes hours, not months.
Founder & CEO
Solange Asangapong
Where this comes from
Built by someone who lived the problem.
More than a decade closing books at scale — across entities, currencies, and frameworks including IFRS, US GAAP, ASC 606, ASC 842, SOX, and SEC reporting. The work spanned ERP implementations, shared service centre buildouts, and multi-jurisdiction compliance at Visa, Schlumberger, and a Pan-African multi-entity group.
This wasn't discovered from the outside. It was lived — late on the fifth working day, in front of a spreadsheet that should never have been load-bearing.
- Visa
- Schlumberger
- IFRS · US GAAP
- SOX · SEC
How we work
Small team. Long horizon. Finance people in the room from the first commit.
i.
Hire in cohorts
We grow the team slowly enough that you'll know your account by name — and they'll know your chart of accounts.
ii.
Ship like a journal
Every release goes out with the evidence attached. Changelog, migration notes, and the reasoning behind each decision.
iii.
Listen to the close
Our roadmap is shaped by the controllers using Lunari at 9pm on day three — not by the demo we want to ship next quarter.
If any of this sounded like
your month-end —
we'd like to walk you through what the close looks like when the truth is stored, not reconstructed.
Ready when you are
One ledger. One data model. One audit trail.
We onboard a small cohort each cycle. Request a demo and we'll be in touch within two business days.