For owner-operators, fee managers and fund controllers
The smartest operating system for commercial real estate.
Leases, loans, capital, deals, insurance, taxes, payments and the books — every entity and property you own, on one ledger, with an agent that works the queue under your rules.
Ask an AI about AcreumChatGPTClaudePerplexity
One property of many. Every entity, property and space in the portfolio has a record like this, and they all roll up.
- 300+
- Legal entities run on Acreum today
- 0.00
- Variance to their certified close when they migrated
- All
- Every module, the agent and the API included. Nothing licensed separately
Where the accounting comes from
01 · The lease
It starts as language.
A clause somebody negotiated.
A base rent with a CPI escalation, an operating-expense share, an option. The source of truth, and it stays attached to everything that follows.
Expense recoveries
CAM season, in four seconds.
Every lease against the actual pool: pro rata shares, gross-up, base years, caps that compound, admin fees. Anything it can’t allocate comes back flagged, never silently zeroed, and every tenant number shows its work.
Gross-up · base year · caps · pro rata share · admin fees · day-count proration · true-ups · exclusions · next year’s estimates. How each works
The work finds you. Then it gets done.
Every night, every entity is re-checked. By morning, most of it is handled.
Fifteen sweeps re-derive what needs doing from the data itself and rank it by damage: bank lines to match, a CAM reconciliation that doesn't tie, a policy about to lapse, invoices past due. The agent reads that queue, recommends, and does what your approval rules let it do.
It can post because the ledger can’t break.
Journals are immutable and period-gated. The agent creates documents, the posting engine posts them, and a mistake is a reversal with a name on it — never an edit.
Your approval rules are its limits.
Same rules as your people: amount, entity, account, vendor, confidence. Below the cap it posts. Above it, it proposes and waits.
Every action is attributed.
The agent is a principal with its own key, its own scopes and its own audit trail. Trust is promoted one resolver at a time, by you.
Where the controller lives
The close, the cash, the capital, the deals. One ledger under all of it.
Each is a working screen, not a module you license. Pick one.
Twelve checks re-run against the ledger until they pass. One close per period, a versioned package, and a reopen that supersedes rather than erases.
One system. One price. One API.
There is no privileged path.
Every screen calls the same endpoint you do, with the same scopes, rate limits and approval rules. Connect Claude, ChatGPT or whatever your team already uses — not just to ask questions of your portfolio, but to act on it, inside the same permissions a person would have. Nothing is licensed separately.
The proof
We tied a several-hundred-entity migration to the cent.
Acreum comes out of moving a portfolio of several hundred legal entities off a custom legacy system, every detailed balance-sheet account reconciled against a certified close. That is why gross-up has a per-lease participation flag, why caps compound, and why the reconciliation tells you which leases it couldn’t allocate instead of quietly zeroing them.
Migration is fixed-fee and repeatable: AI proposes the mapping, your controller approves it account by account, we load through the product API, and a rerun costs an afternoon. How it runs
The last migration you’ll ever run.
Thirty minutes on a live system with the people who built it. No slides.