Features · URBI AccountingIn Beta
The Accounting Engine, Function by Function
This is the reference page for URBI Accounting, in Beta: what Beta buildings run today, function by function, and what is rolling out to them next. Capture, reconciliation, approvals, vendor payments, budgets, reporting, the ledger, billing, and integrations.
AI invoice and receipt capture
The paperwork reads itself.
Photograph a vendor invoice or email a receipt straight in, and AI reads it: the vendor, the date, the totals, the property, and the account it belongs to. The extraction arrives filled in and waiting, not posted. A person confirms it, which is the rule everywhere in URBI Accounting: AI proposes, people approve, and only the matching rules you define ever act on their own.
- AI invoice extraction
- AI receipt extraction
- Email receipts in for processing
- Vendor, date, and account read from the page
- Confidence scored for human review
- Source document kept with the record
- Nothing posts without a person
New in URBI Kore
- AI processing of invoices and receipts runs in the Beta today. Snap the bill or forward the receipt, and it comes back read and categorized, one approval away from the books.
Bank feeds and reconciliation
Close starts from a short list, not a full stack.
Connect the property bank accounts and the feed syncs on its own. Matching then runs in a strict order: the deterministic rules you define go first and are the only thing allowed to match without a person, the engine works the amounts and dates that remain, and HERO, the assistant inside URBI Kore, reasons through the stubborn lines and hands them to you as suggestions. Statement reconciliation closes the loop against what the bank says. The intelligence doing the reasoning is on the URBI AI page.
- Live bank feeds
- Rules first matching
- Rules are the only automatic match
- Statement reconciliation
- HERO suggestions on stubborn lines
- Every match reviewable before it sticks
- Up to 90 percent pre reconciled before close
New in URBI Kore
- Books arrive pre reconciled before month end, at up to 90 percent accuracy, so the close conversation is about exceptions instead of the whole month.
Expenses and approval chains
Spending with the controls built in.
Every expense runs a sequential approval chain: it moves approver by approver, each with their own limit, and escalates to board sign off when the spend needs a vote rather than a signature. Recurring expenses repeat on their own schedule so the standing costs of the building never get re keyed, and CAM and pass through costs are charged back to the units that carry them. Every approval leaves an audit row behind it.
- Sequential approval chains
- Per approver limits
- Board sign off on larger spends
- Recurring expenses
- CAM and pass through chargebacks
- Receipts attached to the expense
- Audit trail on every money action
Vendor payments
Approved, paid, and posted in one line of motion.
Once a bill clears its approval chain, it is paid by bank transfer from inside URBI, and the payment posts back against the expense so the ledger never drifts from what actually left the account. The vendors themselves live beside the work they did, on the operations and workflow side, with their records, contracts, and history in one place. A refreshed vendor management experience is rolling out through the Beta program.
- Vendor payments by bank transfer
- Payment posted back to the expense
- Payment history per vendor
- Vendor records beside the work
- Refreshed vendor management (Beta rollout)
Budgets and forecasting
A budget that tells you where the year lands.
Build the annual budget, then watch it against actuals as the year moves. AI forecasts where the year finishes and writes the variance narrative in plain language, so the explanation of a swing arrives with the number instead of a week later. When it is time to plan again, it drafts next year from how the property actually spends and reallocates.
- Annual budget build
- Budget versus actual tracking
- AI year end forecast
- AI written variance narrative
- AI drafted next year budget
- Board ready budget output
Reporting and board packages
The board package comes out of the ledger, not a rebuild.
Reporting reads live from the books, so what the board sees and what the ledger holds are the same thing. Export to PDF or Excel, or bundle the set into a board package ready for the table. A rebuilt report library, aware of both cash and accrual basis, is rolling out through the Beta program.
- Board package reports
- PDF export
- Excel export
- Reports read live from the ledger
- Rebuilt report library (Beta rollout)
- Cash and accrual basis aware (Beta rollout)
New in URBI Kore
- AI consolidation rolls every building into one portfolio view, while each property keeps its own ledger, its own reporting, and its own control.
The general ledger
Double entry underneath all of it.
This is a real accounting engine, not a summary layer. Every invoice and every expense posts its own balanced journal entry to a general ledger with a proper chart of accounts, which is why the reports can be the books rather than a report about them. Recurring journal entries, and a staggered period close that locks one bank account at a time instead of the whole property at once, are rolling out through the Beta program.
- Double entry general ledger
- Chart of accounts
- Automatic journal entries from invoices and expenses
- Audit trail on every posting
- Recurring journal entries (Beta rollout)
- Staggered period close, one account at a time (Beta rollout)
Billing, charges, and refunds
Bills that go out, and money that comes back cleanly.
Invoices are raised against units and owners, and the people who owe them pay from a public pay page opened by a secure link, with no account to remember and no portal to hunt for. Refunds go back the way the money came: reversed to the card, returned as cash, or left as a credit sitting on the account. Condo fee billing on real schedules, and a Charges Transaction Center that puts every charge on the property in one place, are rolling out through the Beta program.
- Invoices to units and owners
- Public pay pages opened by secure link
- Refund reversed to card
- Cash refunds
- Credit left on account
- Condo fee billing on real schedules (Beta rollout)
- Charges Transaction Center (Beta rollout)
Integrations and outputs
Your accountant keeps their workflow.
The books can live in URBI without stranding anyone who works outside it. A two way QuickBooks Online sync, with URBI as the system of record, is rolling out through the Beta program, alongside cheque printing for the vendors who still want paper and tax handling set per property. Everything else leaves as PDF or Excel.
- QuickBooks Online two way sync (Beta rollout)
- URBI as the system of record (Beta rollout)
- Cheque printing (Beta rollout)
- Per property tax handling (Beta rollout)
- PDF and Excel export
- Bank connections through the feed
What does joining the Accounting Beta mean?
URBI Accounting is in Beta, inside URBI Premium. Buildings in the Beta program run it on their real books and decide, with us, what the next wave carries.
Early access to the whole engine
Beta buildings run the accounting system now: capture, reconciliation, approval chains, vendor payments, budgets, reporting, the ledger, and billing, with our team beside them through the first close.
You shape what ships next
The Beta wave is being built with the buildings running it. What your books actually need moves up the list, and you watch it land instead of reading about it later.
A start that fits your books
We look at your properties, where your books live today, and your timeline before anything moves, so the Beta begins at a point that makes sense for your year.
Want the story rather than the function list? Read the URBI Accounting overview.
Put Your Books in the Beta
Tell us about your properties and where your books live today. We will walk you through exactly where the Beta stands, what it runs now, and when your building can start.