Every lease, every unit, inside Business Central.
One standalone extension for property owners, managing agents and developers. Lease lifecycle, recurring rent, IFRS 16 lease accounting, maintenance, owner payouts — and a full development suite from project budget to handover. Every posting routes through native BC.
- Leasing · rent billing · CAM · meter · deposits
- IFRS 16 / Ind AS 116 / ASC 842 lease accounting
- Development: budgets, sales, payment plans, handover
- 5 Claude AI features · all reviewable
- Posts through native BC — no parallel ledger
- Standalone (dependencies: []) · per-tenant
Where Real Estate & Property shows up for the people who use it
Rent roll · occupancy · arrears
Sales funnel · budgets · demands
Proposal · CAM · post to Sales
IFRS 16 · ROU · disclosures
Abstraction · leak scan · forecast
Real estate runs on leases and rent rolls. Business Central has neither.
Property businesses on Business Central end up running their actual business — leases, escalations, CAM, rent rolls, payment plans, lease accounting — in spreadsheets alongside BC, then re-keying the numbers back in. The result is a month-end that never ties out and a lease-accounting disclosure assembled by hand. This extension puts the real-estate model inside BC, and posts every number through native Sales, Jobs, Fixed Assets and AP — so finance keeps the system they know while property managers and developers finally get the one they need. Claude helps where a human would want a second pair of eyes, and never where a machine would post without one.
Property Management for owners and agents; Property Development for builders and sales teams. Licence one or both — they share a single portfolio → property → building → unit core.
IFRS 16, Ind AS 116 and ASC 842 — lessee and lessor. Present-value liability, right-of-use asset on BC Fixed Assets, remeasurement versioning, disclosure reports.
app.json declares no required app — not even a localization. Country tax flows from your installed BC localization via event hooks. Upgrade-safe by construction.
Manage property. Develop property. Or both.
The same portfolio → property → building → floor → unit core underpins both suites. Licence the modules that match your business — a landlord and a developer buy different things from the same extension.
The full lease-to-cash lifecycle for anyone who owns or manages let property. Leases with escalations and deposits, recurring rent billing, CAM reconciliation, meter usage, maintenance and work orders, owner payouts computed from rent actually collected, and dual-standard lease accounting for both the lessee and lessor side.
- Lease lifecycle: activate, renew, terminate, assign, novate, sublease
- Recurring rent billing with proration, escalations, free-rent periods
- CAM reconciliation, meter / usage billing, late fees, PDC register
- Maintenance work orders + PM schedules with real cost capture
- Owner payouts + management fees settled through native AP
The sell-side and build-side for developers. Construction project budgets tracked over native BC Jobs, unit reservations and sale agreements, buyer payment plans with milestone / date / handover triggers and co-owner splits, subcontract progress billing with retention, and snagging through handover with defect-liability tracking.
- Project budgets over native BC Jobs — no parallel project ledger
- Unit reservation → sale agreement → commission
- Buyer payment plans: milestone, date or handover-triggered demands
- Subcontracts + progress statements with retention held back
- Snag lists, handover, defect-liability period tracking
Eight engines that make real estate work inside BC.
The features a property team touches on the first of the month, in the maintenance queue, and at lease-accounting close.
Lease lifecycle
Lease headers, charge lines and units with fixed or index-linked escalations, deposits held as a liability (never revenue), free / rent-free periods, and a versioned audit trail. Full lifecycle — activate, renew, terminate, assign, novate, sublease.
Recurring rent billing
Generate a billing schedule, propose the run, post grouped by tenant and currency into standard BC Sales invoices. Proration, CAM reconciliation (credit memo for negative true-ups), meter / usage billing with a rollover guard, and late fees.
IFRS 16 lease accounting
Dual-standard support for IFRS 16, Ind AS 116 and ASC 842 — finance vs operating classification, present-value liability, right-of-use asset on BC Fixed Assets, remeasurement versioning, deferred rent and lessor accounting. Disclosure reports included.
Maintenance & work orders
Service requests and work orders with SLA tracking and preventive-maintenance schedules. Purchase cost captured natively and attributed back to the unit, so the true cost of holding a property is visible.
Owner payouts
Management-agreement fee scales computed from rent actually paid — not billed. Owner payouts settle through the owner's vendor account in native AP, so the ledger is clean and reconcilable.
Development projects
Construction budgets tracked over native BC Jobs, with milestones, subcontracts and progress billing. Retention held back and released on schedule. No parallel project ledger to reconcile.
Unit sales & payment plans
Reserve a unit, confirm a sale agreement, instantiate a buyer payment plan. Demands raised on milestone, date or handover triggers as native BC invoices, with co-owner splits handled automatically.
Role centres & KPIs
Two role centres — Property Manager and Property Developer — with cue tiles and KPIs. Rent roll, occupancy, lease-expiry, sales-funnel and AR-aging queries, plus analysis pages and reports.
Five places AI assists. Three places it never touches.
The AI gateway calls Anthropic Claude directly — the API key lives in BC Isolated Storage. Every one of the five AI features has a complete non-AI fallback, and the gateway is built to never throw an error into a workflow: if AI is unavailable, the feature quietly steps aside and the core process continues.
And the boundary is firm: no AI output ever reaches the ledger without a human. Lease abstraction produces a draft for review, not a posted lease. The arrears assistant drafts a message, it does not send it. A human reviews, a human posts — every time.
- Lease abstraction
Upload a lease PDF; Claude returns the structured terms — parties, dates, rent, escalations, options — with a confidence score. A reviewer accepts, and the app builds a draft lease. Never posts on its own.
- Revenue-leak scan
Claude scans active leases and billing schedules for missed escalations, un-billed CAM, expired free-rent periods and under-charged units — the money quietly leaking out of a portfolio.
- Cash-flow forecast
A natural-language forecast of rent, demands and payouts across the portfolio, so an owner can ask 'what does next quarter look like?' and get a grounded answer, not a spreadsheet export.
- Arrears assistant
For a tenant in arrears, Claude drafts the next dunning step in context — what's owed, how long, what was agreed — for a human to review and send.
- Portfolio query
Ask questions in plain English against the whole portfolio — occupancy by building, leases expiring this quarter, top arrears — without building a report.
- Posting to the ledger
No AI feature posts an invoice, a journal or a payout. Every AI output is advisory; a human reviews and a human posts. The gateway returns a boolean and always has a non-AI fallback.
- Lease creation from abstraction
Abstraction produces a draft lease for review — it never activates a lease or commits it to billing. The reviewer owns that step.
- Statutory tax determination
Tax is the BC localization's job, not the AI's. Claude never picks a GST, VAT or TDS treatment — those flow from the installed localization via event hooks.
From a new lease to posted rent and an owner payout.
The flow a managing agent runs every month. Every step lands in native BC, every AI touch is reviewable, and the owner is paid from rent actually collected — not rent merely billed.
- 1New lease created — units, charge lines, escalations, deposit held as a liability.
- 2(Optional) Claude abstracts the signed PDF into draft terms; a reviewer accepts.
- 3Lease activated — the units flip to Leased, the versioned audit trail opens.
- 4Billing proposal generates the schedule rows with proration and escalations applied.
- 5Rent posting run groups rows by tenant and currency into standard BC Sales invoices.
- 6The installed localization applies GST / VAT / TDS via the rent tax hook.
- 7Tenant pays; late fees and any post-dated cheques are tracked in the PDC register.
- 8CAM reconciliation trues up service charges — a credit memo where the estimate over-billed.
- 9Owner payout reads rent actually paid, applies the management fee scale, and settles the owner's vendor through AP.
- 10Revenue-leak scan flags any missed escalation or un-billed CAM for next month.
Billing run · March 2026 ──────────────────────────── Leases in scope 64 Schedule rows 182 Base rent 128 CAM (estimate) 41 Parking / storage 13 Escalations applied 22 Fixed uplift 17 Index-linked 5 Posted to BC Sales Invoices 58 (grouped) Tenants 58 Currencies 2 (INR, AED) Deposits held (liability) not billed Owner payouts queued 31 (settle from PAID rent via AP) AI revenue-leak scan Missed escalations 2 Un-billed CAM 1 → review
Six decisions that keep it clean for the long run.
Each one is a deliberate constraint — the kind an auditor, a BC administrator and a finance lead all care about.
Standalone by architecture
app.json declares zero required dependencies — not even on a country localization. Every hook into base BC is an event subscriber or a table / page extension; nothing base is modified. Country handling is done through events, so the extension runs on any localization.
Posts through native BC only
There is no parallel ledger. Rent posts through standard Sales and Sales-Post. Payouts, commission and retention post through the General Journal and AP. Right-of-use assets live on BC Fixed Assets. Development budgets run over native Jobs. Finance works in the system they already know.
Tax deferred to the localization
The extension does not compute GST, VAT, TDS or e-invoicing itself. It raises rent-specific hooks (for example OnBeforeApplyLeaseVAT) and lets your installed BC localization apply the statutory treatment. One extension, correct tax in every supported country.
AI is additive and reviewable
The AI gateway calls Anthropic Claude directly, key in Isolated Storage. Every AI task has a complete non-AI fallback, the gateway never throws, and no AI output reaches the ledger without a human review. Turn AI off entirely and every core workflow still runs.
Feature-gated, fail-closed licensing
Eleven feature codes across the property-management and development modules, licensed per tenant. Core and analytics are always-on; the rest activate per module. Licensing fails closed with a 14-day offline grace window — deliberate for a system of financial record.
Versioned, auditable records
Leases, remeasurements and billing schedules carry a versioned audit trail. Escalations are idempotent — re-running never double-applies. Every change is traceable, which matters when an auditor walks a lease from contract to posted rent.
4–6 weeks for a single suite. Longer for both, mostly for finance sign-off.
Implementation scales with the number of suites, the lease-accounting standards in play, and the opening-balance reconciliation — not with engineering. A single-suite management or development rollout is the fast path; a combined, multi-standard deployment takes longer for the finance work.
Per-Tenant Extension while AppSource clears. Same code, same license.
Week 1
Scope agreed — property management, development, or both. Portfolio structure captured (portfolio → property → building → floor → unit). Lease accounting standard confirmed (IFRS 16 / Ind AS 116 / ASC 842). Assisted setup run in a sandbox tenant.
Week 2
Charge types, escalation rules, CAM pools and meter definitions authored. Management-agreement fee scales set. Dimensions mapped. Development project templates and payment-plan structures configured if the development suite is in scope.
Weeks 3–4
One property or one project. Real leases migrated, a real billing run posted, lease-accounting worked through with finance. Owner payout reconciled end-to-end. AI features enabled and confidence thresholds tuned per task.
Week 5
All properties / projects migrated. Opening lease-accounting balances loaded and reconciled. Previous spreadsheets retired. Role centres handed to property managers and developers; reporting handed to finance.
Week 6+
Monthly billing run, CAM reconciliation, lease-accounting close. Development demands raised on schedule. Revenue-leak scan reviewed with the owner. Cash-flow forecast at each portfolio review.
Beyond
Add the development suite to a management deployment (or vice-versa). Layer AI features on once the team trusts the core. Extend to more standards or currencies as the portfolio grows across borders.
Frequently asked questions
Both, from one extension over a shared asset core. The Property Management suite covers owners and managing agents — leases, recurring rent, CAM, maintenance, owner payouts and lease accounting. The Property Development suite covers developers — construction budgets over BC Jobs, unit sales, buyer payment plans, progress billing with retention, and handover. Licence the modules you need; a pure landlord never pays for the development suite, and a pure developer never pays for CAM reconciliation.
Bring one real lease. We'll bill it and account for it live.
A 60-minute working session, not a slide deck. Bring a real lease (or a development project) and your lease-accounting standard. We install in a BC sandbox, build the lease, run a billing proposal, post the rent through native Sales, and walk the IFRS 16 entries with your finance lead.
- Live install in your BC sandbox
- Your real lease — billed and accounted end-to-end
- Honest answer on management vs development scope for you
- Written proposal within one working day