01
Connect the work.
All-in-one ledger
Accounting, spend, revenue, payroll, treasury, close and reporting share one ledger. Source documents, transactions and reports stay connected instead of moving between disconnected tools.
Lunari · Finance operating system
Agentic AI.
All-in-one ledger.
Accounting, spend, revenue, payroll, treasury, close and reporting— connected in one platform. AI-assisted workflows move the work forward, with evidence attached and your team in control.
lunari.cloud / close · december
LUNARICLAPARTRAU
Close › December 2025 › ReconciliationsAll entitiesOpen
December 2025 closeDay 3 / 5
Reconciled
24/32
Unexplained
$18.4K
Locks
17:00Z
AcctAccountCcyBalance
1010Cash · USD operatingUSD4,213,880
1015Cash · CAD operatingCAD1,884,204
1200Accounts receivableUSD9,442,117
1310Prepaid expensesGBP612,940
2100Accounts payableUSD3,120,455
2320Accrued liabilitiesCAD1,047,332
2600Deferred revenueUSD6,220,019
3100Intercompany clearingGBP228,764
Owner · Priya M. · Reviewer · D. OkaforLock period →
Finance needs more than another AI tool. It needs one connected operating system. That is what Lunari brings together.
Operating thesis · written on the wall
Agentic finance · connected by design
One platform. Work that moves. Control that stays.
02
Move work forward.
Agentic AI + workflows
Bring AI into the finance workflow, not a separate chat window. Connected records give AI the context to assist with the work, while your team retains judgement and approval authority.
03
Keep control.
Evidence + approvals
Every transaction keeps its supporting evidence. Shared roles, approval rules and audit trails keep accountability in the workflow—from the first invoice to the financial statements.
Six problems · named plainly
What we found inside the finance function.
06 problems → 06 answers
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.
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.
How it works
One supplier invoice. Four steps.
In most finance stacks, this means three logins, two CSV exports, and a controller squinting at an email thread. In Lunari, it's this:
- 1.The invoice arrives.
Forwarded to your Lunari inbox, it becomes a draft bill in the same system as your ledger.
- 2.It's matched and coded.
PO, receipt, and invoice live on the same record. Variance over threshold routes to AP automatically.
- 3.Your team approves.
Approval follows the rules you set for entity, vendor, or amount — logged in the audit trail, not an inbox.
- 4.It posts to the ledger.
The journal posts on approval, evidence attached. Follow the entry through entity and group reports.
lunari.cloud / p2p / invoice 4421
LUNARIInvoice · INV-44218
Northwind Logistics$18,420.00
Purchase order
PO-2118Goods receipt
GR-991Invoice
INV-44218Line 3 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.
The questions CFOs ask first
Asked in every first meeting. Answered plainly.
“How long does implementation take?”
Weeks, not quarters. Because every module shares one data model, there is no integration project per module — we configure your entities, chart of accounts, and approval matrices, migrate opening balances, and reconcile them with you before go-live.
“What happens to our history?”
Opening balances and open items are in place for go-live, and historical transactions can follow. Every migrated balance is reconciled against your old system before we call it done.
“Do we have to replace everything at once?”
No. Start with the suite that hurts today — close, spend, cash, or revenue. Each one reads the same ledger, so the next module takes hours to switch on, not months.
“Who runs Lunari afterwards?”
Your finance team does. Workflows, approval rules, and reports are configured by the people who own the process — no consultant required for every change request.
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.