ERP for Real Estate: Lease Accounting, Capital Projects, and Portfolio Reporting

A commercial property management firm with 34 buildings across six separate legal entities (a common structure, where each property or group of properties sits in its own LLC for liability reasons) ran its accounting through a mainstream small-business platform that had no concept of a "property" as an organizing unit. Every month-end, their controller manually consolidated financials across all six entities in a spreadsheet, and separately tracked capital improvement projects — a $1.2 million roof replacement, a parking lot repaving — in yet another spreadsheet, because the accounting system had no way to capitalize and depreciate a project against a specific asset tied to a specific property. Close took nineteen business days. None of this was a training problem. It was a fundamental mismatch between what the software was built to organize (a single company's transactions) and what the business actually needed to organize (multiple entities, each holding one or more physical assets, each requiring its own P&L and its own capital project tracking).

This is the real distinction between generic small-business accounting software and an ERP genuinely built for real estate's back office. It has less to do with property listings, tenant leads, or MLS integration — the customer-facing side of real estate software — and everything to do with three structural requirements most business software doesn't natively handle.

Multi-entity structure as a first-class concept, not a workaround

Commercial real estate is overwhelmingly organized around single-purpose entities: each property, or small group of properties, sits in its own LLC to isolate liability. A real estate-capable ERP needs to treat "entity" and "property" as core organizing dimensions from the start — able to produce a clean, standalone P&L and balance sheet for each individual entity, while also rolling all of them up into a consolidated ownership-group view, without a controller manually reassembling that consolidation by hand every close. The property management firm's nineteen-day close existed almost entirely because their system could produce numbers for "the company" as a whole but had no native way to slice by entity or roll multiple entities back up cleanly — every consolidation was a spreadsheet exercise built from scratch each month.

Lease accounting under ASC 842 (or IFRS 16)

Since the ASC 842 lease accounting standard took effect, both lessors and lessees are required to recognize most leases on the balance sheet — a significant change from the prior standard, where operating leases largely stayed off balance sheet. For a real estate firm, this cuts both ways: as a lessor, tracking lease income recognition, straight-lining rent over the lease term, and handling tenant improvement allowances and free-rent periods correctly; as a lessee (for firms leasing their own office or equipment), calculating and tracking a right-of-use asset and corresponding lease liability. This is genuinely specialized accounting logic that generic accounting software doesn't handle out of the box — it typically requires either a dedicated lease accounting module inside the ERP or a certified third-party lease accounting add-on that integrates with it. Getting this wrong isn't just an internal reporting problem; it's a real audit finding for any real estate firm subject to GAAP-compliant external audits or lender covenant reporting.

Capital project and capital improvement tracking

Real estate operating expenses and capital expenditures need to be tracked and treated very differently — a routine HVAC repair is an operating expense hitting the current period's P&L, while a full roof replacement is typically a capital expenditure that gets capitalized and depreciated over its useful life, tied to the specific building it improves. The property management firm's $1.2 million roof project needed to be tracked against budget, tied to specific vendor invoices and change orders as the project progressed, and then correctly capitalized and placed into a depreciation schedule once complete — a workflow that spans project management, AP, and fixed-asset accounting simultaneously. Software that treats capital projects as just another expense category, with no project-level budget tracking or connection to the fixed asset ledger afterward, forces exactly the kind of parallel-spreadsheet tracking this firm was doing, which is both slow and a real source of errors when a capitalized amount doesn't reconcile cleanly back to actual project spend.

Portfolio-level reporting that actually serves real estate decisions

Generic financial reporting — P&L, balance sheet, cash flow — is necessary but insufficient for real estate portfolio management. The reporting that actually drives decisions in this industry includes metrics generic ERPs don't calculate natively: net operating income (NOI) by property, occupancy and vacancy rate trends, rent roll detail with lease expiration timelines (critical for planning renewal or re-leasing efforts before a lease actually lapses), and comparative performance across the portfolio to identify underperforming assets. A system that requires exporting raw transaction data to a separate BI tool or spreadsheet to answer "which three properties in our portfolio have the weakest NOI trend this year" is adding a manual step to a question the underlying ERP should be able to answer directly, if it was actually built with real estate's specific reporting needs in mind rather than adapted from a generic accounting platform.

CAM reconciliation: a fourth structural requirement worth naming

Beyond multi-entity structure, lease accounting, and capital project tracking, commercial real estate has a fourth back-office process that generic software rarely handles well: common area maintenance (CAM) reconciliation. Most commercial leases require tenants to pay a pro-rata share of shared building operating costs (landscaping, common-area utilities, property management fees) estimated monthly throughout the year and then reconciled against actual costs annually, with either a true-up bill or a credit issued based on the difference. Doing this by hand means allocating a full year of shared building expenses across every tenant based on their leased square footage percentage, cross-referencing each tenant's specific lease terms for any exclusions or caps negotiated into their agreement, and generating individual reconciliation statements — a process the property management firm's controller described as the single most error-prone week of their year before the system change, because it required manually cross-referencing lease terms that lived in a separate document management system entirely from the accounting spreadsheets.

A real estate-capable ERP that ties lease terms, tenant records, and building-level expense data together natively can run this allocation automatically against each lease's actual negotiated terms, turning what was a multi-week manual reconciliation project into a scheduled report. This is worth asking about specifically during evaluation, since it's easy to assume "lease accounting" and "CAM reconciliation" are the same capability when they're often handled by entirely separate parts of a system, or not handled at all in software built for real estate's customer-facing side rather than its back office.

What to actually check when evaluating a system for this

• Can it produce a clean, standalone financial statement per entity, and consolidate automatically across a defined ownership group, without manual reassembly?
• Does it include native ASC 842 lease accounting, or does that require a certified third-party add-on — and if the latter, has that integration actually been implemented successfully at another firm of similar size?
• Can it track a capital project's budget and actual spend through completion, then hand off cleanly into a fixed-asset depreciation schedule tied to the specific property?
• Does it produce property-level and portfolio-level operational reporting natively — NOI, occupancy, rent roll and lease expiration — or only generic financial statements?
• What's the actual licensing cost model at your entity count and portfolio size — some ERPs price per legal entity, which can escalate quickly for a firm running the six-plus-entity structure that's standard in commercial real estate. Worth running through a cost-per-user calculator alongside the per-entity math before assuming a quoted price scales the way it looks on the initial proposal.

The property management firm eventually moved to a real-estate-specific ERP with native multi-entity consolidation and lease accounting. Close time dropped from nineteen business days to six, and the capital project spreadsheet disappeared entirely because project spend now flowed directly into the fixed asset ledger on completion. None of that was about better software in a generic sense — it was about software actually built around how real estate firms are structured, rather than business software with real estate treated as an afterthought vertical.