Thirty minutes on a live system.

You take it. Every journal, document, attachment and configuration is readable over the same API the product uses, with keys you issue yourself, on your first day and on your last. There is no export request, no per-interface licence and no proprietary file format standing between you and your own ledger.

It can post only what your approval rules would let a person post, and only through the same posting engine. Journals are immutable and gated by the accounting period, so a wrong entry is corrected by a reversal that carries the agent’s name, never by an edit. Every resolver starts by proposing; you promote it to acting within caps once you have watched it work, one resolver at a time. Above the cap it proposes and waits.

No. Acreum uses commercial model APIs under terms that exclude training on customer data, and nothing you enter is used to improve a model for anyone else. The agent runs as its own principal with its own key and scopes, so what it can read is exactly what you have allowed, and every call is logged.

Approval rules route by amount, entity, property, account, vendor and submitter, with sequential steps and two-of-three style requirements. The approver list is frozen when a request is raised, so the record still shows who was required and who signed after the org chart changes. Payment runs are approvable in their own right. A closed period locks, and the audit log records who changed what, when, and what it was before.

They get an immutable journal with a period on every line, a versioned close package per period, sub-ledgers that tie to the general ledger by a check rather than a spreadsheet, and a read-only API key scoped to what they need. Most of what an auditor asks for is a query, not a project.

A fixed fee, reconciled to your last certified close. Acreum proposes the mapping from your legacy chart of accounts; your controller approves it account by account; we load through the product API so every migrated transaction passes the same validation as a hand-entered one. Then we throw it away and run it again until it ties. The last one tied to 0.00 across several hundred entities. How long yours takes depends on your history and your chart of accounts, and we will tell you after seeing both rather than before.

One price for the whole system, sized to your portfolio. Every module, the agent and the API are included; nothing is licensed separately and there is no per-module upsell later. We are finalising the tiers and will publish them; until then we quote on the call.

No. Adding a legal entity, a property or a space is a form. Approval rules, dimensions, the filing convention and bank connections are configured from the product by your own team. The documentation is open and published, so Claude, ChatGPT or whichever assistant you use can read it and walk you through a setup or an API call step by step. The migration is the one project, and we run it.

Legal entities are first-class objects with their own books, owners and intercompany relationships. Ownership nests as deep as the deal was papered; consolidation groups compute eliminations from the reciprocal postings; distributions cascade through every tier cent-exact. Managed entities and fee-manager structures are supported alongside owned ones.

Not today. Acreum runs one currency per organisation, and we would rather say so than let you find out in due diligence. If your portfolio needs it, tell us on the call and we will be specific about where it sits on the roadmap.

Bank feeds and balances arrive through Plaid across the banks it covers; statements can also be imported. Vendor payment runs go out by ACH with approval on the run itself. Receipts are matched back from the feed to the journal line, with every automatic match logged against the rule that made it.

Bring it to the demo. Terms are typed, not templated: escalations with floors and caps, percentage rent and breakpoints, free rent, options with notice dates, amendments resolved as of any date. Where a clause does not fit a term, it is entered as an informational term and flagged, never silently approximated.