How to Set Up a Chart of Accounts for Property Management

Every financial report a property portfolio produces is only as reliable as the chart of accounts underneath it. NOI figures, variance reports, budget comparisons, and consolidated statements all draw from the same source: the account codes that were set up before the first transaction was posted. A chart of accounts built for a generic business produces property reports that don't measure what property managers and asset managers actually need to know. The income lines don't distinguish base rent from recovery income. The expense lines don't separate operating costs from capital items. There is no account for straight-line rent adjustments, no structure for deferred rent balances, and no intercompany accounts for groups that operate across multiple entities.

The consequences compound over time. An incorrect COA doesn't just produce one wrong report. It produces every wrong report that the portfolio generates until the structure is rebuilt. NOI figures that include recovery income in the base rent line are overstated. Expense lines that combine operating and capital items produce suppressed NOI and distorted valuations. Budget comparisons that draw from inconsistently named accounts compare different things under the same heading. By the time the audit arrives, the chart of accounts has become an obstacle rather than a foundation.

This guide covers the full setup of a property management chart of accounts: the structure, the account categories, the numbering conventions, the specific accounts that commercial property portfolios need and generic COAs don't include, and the framework for building a COA that produces reliable reports from day one.

Why Most Property COAs Fail and What the Consequences Are

The Generic COA Problem: Built for Businesses, Not Portfolios

Most accounting software ships with a default chart of accounts designed for a generic business: sales revenue, cost of goods sold, salaries, rent expense, utilities. For a retail business or a service company, this structure works adequately. For a property management operation, it is structurally wrong from the first account.

Property management generates income from multiple sources that behave differently and require separate tracking: base rent, operating expense recoveries, parking income, storage income, signage fees, and late payment charges. A generic COA collapses these into a single revenue line. The result is a revenue figure that can't be analysed by income type, can't be reconciled against the rent roll, and can't support the recovery rate calculations that NNN portfolios require.

The expense side is equally problematic. A generic COA doesn't distinguish between operating expenses and capital expenditures, doesn't have a property management fee account separate from general administrative costs, and doesn't include straight-line rent adjustment accounts or deferred rent balance sheet accounts that GAAP compliance requires. Every one of these omissions produces a reporting gap that grows more expensive to fix as the portfolio grows.

How a Weak COA Distorts NOI, Budgets, and Audit Outcomes

• NOI distortion
   As covered in how to track NOI accurately across a multi-property portfolio, NOI accuracy depends entirely on the operating expense pool being correctly populated and the income pool being correctly categorised. A COA that doesn't separate recovery income from base rent, or that allows capital items into operating expense accounts, produces an NOI figure that can't be trusted and can't be defended at audit.

• Budget distortion:
  A budget is only comparable to actuals if both draw from the same account structure. A COA that groups multiple income or expense types into single accounts makes budget vs actual variance analysis meaningless. The variance report shows a number but can't explain what drove it, because the account that moved contains too many different things to isolate the cause.

• Audit outcomes:
   Auditors verify that income is correctly categorised, that operating expenses don't contain capital items, and that balance sheet accounts for deferred rent and tenant deposits are correctly structured. A COA that doesn't support these verifications produces audit findings that require account restructuring mid-year, restatement of previously reported figures, and a close process that takes significantly longer than it should.

The Structure of a Property Management Chart of Accounts

The Five Account Categories and What Each Covers

A property management COA is organised into five categories, each covering a distinct area of the portfolio's financial activity.

• Assets cover everything the portfolio owns or is owed: investment property, accumulated depreciation, cash and bank accounts, accounts receivable, deferred rent receivables, tenant improvement allowances, prepaid expenses, and intercompany receivables.

• Liabilities cover everything the portfolio owes: accounts payable, tenant security deposits, deferred rent liabilities, intercompany payables, accrued expenses, and debt obligations.

• Equity covers the ownership interest in the portfolio: contributed capital, retained earnings, and distributions.

• Income covers all revenue generated by the portfolio's operations: base rent, operating expense recoveries, parking and storage income, signage income, late fees, and straight-line rent adjustments.

• Expenses cover all costs of operating the portfolio: property taxes, insurance, repairs and maintenance, property management fees, utilities, landscaping, capital improvement accounts (tracked separately from operating expenses), and allocated overhead.

How Account Numbering Works in a Property COA

Account numbering in a property COA follows a hierarchical structure that groups related accounts together and allows the chart to be extended as the portfolio grows without restructuring existing accounts.

The standard numbering convention for commercial property uses five-digit account codes:

• 1000 to 1999: Assets
• 2000 to 2999: Liabilities
• 3000 to 3999: Equity
• 4000 to 4999: Income
• 5000 to 5999: Operating Expenses
• 6000 to 6999: Capital and Non-Operating Items
• 7000 to 7999: Intercompany Accounts (multi-entity portfolios)
• 8000 to 8999: Below-the-line items (depreciation, debt service, taxes)

Within each range, accounts are numbered in increments of 10 or 100 to allow new accounts to be inserted between existing ones without renumbering the entire chart.

Single Property vs Multi-Property COA: What Changes

A single-property COA can track all income and expenses in a flat account structure because every transaction belongs to the same property. A multi-property COA requires an additional layer of segmentation to ensure that income and expenses are tracked by property, not just by account type.

In a multi-property COA, segmentation is achieved either through sub-accounts (a separate income and expense account for each property under each account type) or through class or department coding (a single set of accounts with a property identifier tag applied to each transaction). The class coding approach is more scalable for larger portfolios because it doesn't multiply the number of accounts as properties are added. The sub-account approach is simpler for small portfolios but becomes unmanageable beyond five to ten properties.

The Property COA Setup Framework

A chart of accounts built correctly from the start eliminates the reporting gaps and audit findings that a poorly structured COA produces for years after it is set up. The framework that achieves this operates across three stages: map, structure, and test.

Stage 1: Map — Identify Every Income and Expense Type the Portfolio Generates

Before any account codes are assigned, every income and expense type that the portfolio currently generates or is likely to generate must be identified and listed. This mapping exercise is the most important step in the setup process because every income or expense type that is not identified at this stage will either be miscoded to an incorrect account or trigger an ad hoc account addition that breaks the numbering structure.

The mapping exercise should cover: every income stream in the current rent roll (base rent, recoveries, parking, storage, ancillary), every recurring expense category (property tax, insurance, management fees, maintenance, utilities), every balance sheet item that requires a dedicated account (deferred rent, tenant deposits, TIA receivables), and every intercompany relationship that generates transactions (management fees, loans, cost allocations).

Stage 2: Structure — Assign Account Categories, Numbers, and Hierarchy

With the full list of income and expense types identified, accounts are assigned to categories, numbered within the appropriate range, and organised into a hierarchy that groups related accounts under parent accounts for reporting purposes.

The structure decisions that matter most in a property COA are: whether income is separated by type (base rent vs recoveries vs other income must be separate accounts, not sub-lines under a single revenue account), whether operating and capital expense accounts are completely separate (no capital items in the operating expense range), and whether balance sheet accounts for deferred rent and tenant deposits are correctly positioned as either assets or liabilities depending on the balance direction.

Stage 3: Test — Validate the COA Against Reporting Requirements Before Going Live

Before the COA is activated in the accounting system, it must be tested against the portfolio's reporting requirements. The test asks: if a transaction of every type the portfolio generates was posted to this COA, would the resulting reports produce the NOI figure, the budget comparison, the balance sheet, and the consolidated statement that the portfolio actually needs?

The test is most efficiently run by mapping the portfolio's standard reports to the account structure and confirming that every line in every report draws from a correctly defined account. Any report line that doesn't map cleanly to a dedicated account identifies a gap in the COA that must be filled before the first transaction is posted.

Income Accounts: What to Include and How to Separate Them

Base Rent Accounts: One Per Property or One Per Lease Type

Base rent is the contractual rent obligation under the lease, separate from any recovery or ancillary income. In a single-property COA, a single base rent income account (typically 4100) is sufficient. In a multi-property COA, base rent is either tracked through property-level sub-accounts (4100-01, 4100-02 for each property) or through class coding against a single base rent account.

For portfolios with mixed lease types (NNN and gross leases in the same portfolio), consider separate base rent accounts by lease type (4100 for NNN base rent, 4110 for gross lease base rent). This separation allows recovery rate analysis without requiring manual filtering by lease type in the reporting tool.

Operating Expense Recovery Accounts: NNN and Modified Gross Structures

Operating expense recoveries are reimbursements of property operating costs passed through to tenants under NNN and Modified Gross leases. They must be recorded as a separate income account, not merged into base rent. Merging recovery income into base rent is one of the most common COA errors in commercial property portfolios and one that directly distorts NOI analysis.

The recovery income account structure should mirror the expense account structure it recovers against. If operating expenses are tracked across property tax (5100), insurance (5200), and maintenance (5300), the recovery income accounts should track CAM recoveries (4200), tax recoveries (4210), and insurance recoveries (4220) separately. This parallel structure allows the recovery rate for each expense category to be calculated directly from the accounts without manual cross-referencing.

Other Income Accounts: Parking, Storage, Signage, and Late Fees

Ancillary income should be tracked in dedicated accounts for each income type rather than aggregated into a single "other income" line. The accounts that most commercial property portfolios require are: parking income (4300), storage income (4310), signage and billboard income (4320), late payment fees (4330), lease termination fees (4340), and miscellaneous property income (4390).

Separating ancillary income by type allows each stream to be budgeted, tracked, and reported independently. A single "other income" account obscures which ancillary streams are growing, which are declining, and which are underperforming against budget.

Straight-Line Rent Adjustment Accounts: The Non-Cash Income Line

Straight-line rent adjustment is a non-cash income account required for GAAP compliance. It records the difference between the straight-line monthly rent recognition and the actual cash billing in each period. For a detailed explanation of how straight-line rent calculations work and why this account is required, see how to set up straight-line rent calculations with GAAP compliance.

The straight-line rent adjustment account (4400) must be a separate income line, not combined with base rent. Combining it with base rent makes it impossible to distinguish cash rental income from non-cash GAAP adjustments in the income statement, which produces a revenue figure that doesn't reconcile to cash receipts and creates confusion at audit.

Operating Expense Accounts: The Full Structure

Property Tax and Insurance Accounts

Property tax (5100) and insurance (5200) are the two largest fixed operating costs in most commercial property portfolios and should always be separate accounts, never combined. Separating them allows each to be tracked against budget independently, supports recovery billing for NNN leases, and makes it straightforward to identify the cost impact of a property tax appeal or an insurance renewal.

For portfolios with multiple properties, property tax and insurance accounts should be tracked by property either through sub-accounts or class coding. A single property tax account across a ten-property portfolio makes it impossible to identify which property is driving a budget variance without drilling into the transaction detail.

Repairs and Maintenance vs Capital Improvement Accounts

The separation between repairs and maintenance (operating, account range 5300 to 5399) and capital improvements (non-operating, account range 6100 to 6199) is the most critical structural distinction in the expense section of a property COA.

As covered in how to separate CapEx from OpEx in property management, misclassification between these two categories is the most common NOI distortion error in commercial property accounting. The COA must make it structurally impossible to post a capital item to an operating expense account. Separate account ranges, separate approval workflows, and separate reporting lines are the controls that enforce this separation at the account level.

Operating repairs and maintenance sub-accounts typically include: general repairs (5300), HVAC maintenance (5310), plumbing repairs (5320), electrical repairs (5330), painting and decorating (5340), cleaning and janitorial (5350), and grounds and landscaping (5360).

Capital improvement accounts in the 6100 range cover: building improvements (6100), roof replacement (6110), HVAC replacement (6120), electrical system upgrades (6130), and tenant improvement allowances funded by the landlord (6140).

Property Management Fee Accounts

Property management fees (5400) must be a separate operating expense account, not grouped with general administrative costs. This separation is required for three reasons: management fees are a directly controllable cost that should be tracked against budget independently; they are an intercompany transaction in groups where the manager is a related entity; and they are a recoverable expense in some NNN lease structures where the management fee is included in the CAM recovery pool.

For groups where property management is provided by a related entity, the management fee account feeds directly into the intercompany reconciliation process. The fee posted to account 5400 in the SPV must match the fee income posted to the management entity's revenue accounts. A management fee account that is not clearly separated from other operating costs makes this reconciliation significantly more difficult.

Utilities, Landscaping, and Facilities Accounts

Utilities (5500 to 5590) should be tracked by utility type: electricity (5500), gas (5510), water and sewerage (5520), and waste management (5530). For gross lease properties, all utility costs flow through these accounts as operating expenses. For NNN properties, utility costs incurred in common areas are operating expenses recovered through CAM billing.

Landscaping and grounds (5600), cleaning and janitorial (5610), and security (5620) are further facility management expense accounts that should be separate from general repairs and maintenance to support accurate budget tracking and CAM recovery reconciliation.

Administrative and Overhead Accounts

Administrative expenses directly attributable to the property (5700 to 5790) include leasing commissions (5700), advertising and marketing (5710), legal and professional fees directly related to the property (5720), and property-level administrative costs (5730).

Allocated overhead (5800) is the account that receives shared service cost allocations from the central entity in multi-property and multi-entity groups. It must be a separate account from direct property administrative costs so that the allocation can be identified and adjusted independently when the allocation methodology changes.

Balance Sheet Accounts for Property Management

Investment Property and Accumulated Depreciation

• Investment property (1100) is the carrying value of the property assets on the balance sheet. In a multi-property portfolio, investment property is typically tracked at the individual property level through sub-accounts (1100-01, 1100-02) to support asset-level reporting and disposal accounting.

• Accumulated depreciation (1110) is the contra-asset account that offsets the investment property carrying value. It must mirror the investment property account structure: a separate accumulated depreciation sub-account for each property sub-account, so that the net book value of each property can be reported independently.

Deferred Rent Asset and Liability Accounts

Deferred rent is recorded as either an asset or a liability depending on the direction of the balance in each period. In early lease periods when straight-line income exceeds cash billings, the balance is a deferred rent receivable (asset, account 1300). In later periods when billings exceed the straight-line average, the balance releases from the liability side.

Both accounts must exist in the COA and both must be structured to support the property-level reconciliation of the straight-line schedule to the balance sheet. A COA that has only one deferred rent account (either asset or liability but not both) will produce incorrect balance sheet presentation in periods when the balance sits on the opposite side.

Tenant Deposit Accounts: How to Structure Them Correctly

Tenant security deposits (liability, account 2100) must be recorded as a liability on the balance sheet, not as income. A deposit received from a tenant is a repayable obligation. Recording it as income at receipt and as an expense at refund is an accounting error that inflates income in the period of receipt and inflates expenses in the period of refund.

The tenant deposit account should be structured to track deposits by property and ideally by tenancy, so that the total balance in account 2100 can be reconciled against the deposit register at every period end. A deposit register that doesn't reconcile to the balance sheet account is an audit finding in every commercial property audit.

Intercompany Receivable and Payable Accounts

Intercompany receivables (1400 to 1490) and intercompany payables (2200 to 2290) are the balance sheet accounts that carry the outstanding balances of intercompany transactions between group entities. As covered in how to manage intercompany transactions across multi-entity real estate groups, these accounts must be named by counterparty entity to support the monthly intercompany reconciliation.

A single "intercompany receivable" account that carries balances from multiple group entities makes it impossible to reconcile individual intercompany relationships without drilling into transaction detail. The correct structure is a separate receivable and payable account for each intercompany relationship: intercompany receivable from Management Co (1400), intercompany receivable from SPV 2 (1410), intercompany payable to Holding Co (2200), and so on.

The Complete Property Management COA Reference

The following table covers the standard account structure for a commercial property management COA across all five categories.

How to Structure a COA for Multi-Entity Property Groups

Entity-Level vs Property-Level Account Segmentation

In a multi-entity property group, accounts must be structured to support both entity-level reporting (what each SPV or operating entity earned and spent) and property-level reporting (what each individual property generated in NOI). These two dimensions don't always align: one SPV may own multiple properties, and one property may be owned through a complex entity structure.

The most scalable approach for multi-entity portfolios is to maintain a standardised COA across all entities (every entity uses the same account codes) combined with property-level class or department coding (each transaction is tagged with a property identifier). This produces entity-level reports by running the COA accounts for a single entity, and property-level reports by filtering transactions by property class across all entities.

Intercompany Accounts: How to Number and Name Them

Intercompany accounts in a multi-entity COA must be named by counterparty entity, not described generically. Intercompany Receivable — Management Co (1400) and Intercompany Payable — Holding Co (2300) allow the monthly reconciliation to be run by counterparty directly from the account balance, without filtering by transaction description.

The naming convention must be consistent across all entities in the group. If the management company's account names its receivable from SPV 1 as "Intercompany Receivable — SPV 1 Ltd," then SPV 1's COA must name its corresponding payable as "Intercompany Payable — Management Co" with a matching reference structure. Inconsistent naming between entities is the most common cause of intercompany reconciliation failures in multi-entity property groups.

Consolidation and Elimination Accounts

Consolidation elimination accounts are used in the consolidation working papers to remove intercompany balances from the consolidated statements. They are not posted in the entity-level COA. However, the entity-level COA must be structured so that every intercompany balance that needs to be eliminated can be identified by account code without manual transaction-level filtering.

The test is: can an accountant running the consolidation identify the full intercompany elimination requirement by looking at account balances alone, without opening individual transactions? If yes, the intercompany account structure is correct. If no, the COA needs additional account-level segmentation before the consolidation can be run efficiently.

Common COA Setup Errors in Property Management and How to Prevent Them

Income and Expense Accounts Not Separated by Property

The Error: A ten-property portfolio uses a single base rent income account and a single repairs and maintenance account across all properties. The monthly reports show total portfolio rent and total portfolio repairs, but no property-level breakdown.

The Fix: Implement property-level segmentation through sub-accounts or class coding before the first transaction is posted. Retrofitting property-level segmentation to an existing COA after transactions have been posted requires reclassifying every historical transaction, which is a significant and disruptive exercise.

CapEx and OpEx Sharing the Same Account

The Error: Capital works are posted to the repairs and maintenance account (5300) because the invoices look similar to routine maintenance and the person posting them doesn't have a clear capitalisation policy to refer to.

The Fix: The capital improvement accounts (6100 range) must exist in the COA and must be clearly separated from the operating repairs accounts (5300 range). The account names should make the distinction unambiguous: "Repairs and Maintenance (Operating)" and "Building Improvements (Capital)" leave less room for misclassification than generic account names.

Recovery Income Merged Into Base Rent

The Error: CAM recovery billings are posted to the base rent income account (4100) because there is no dedicated recovery income account in the COA.

The Fix: Separate recovery income accounts (4200, 4210, 4220) must be created before NNN or Modified Gross leases are entered into the system. Recovery income merged into base rent produces a base rent figure that overstates contractual rent, makes recovery rate analysis impossible, and distorts the income categorisation that NOI reporting requires.

No Straight-Line Rent Adjustment Account

The Error: The COA has no account for straight-line rent adjustments. GAAP-required non-cash income is either not recorded at all or posted to the base rent account, blurring the line between cash and non-cash income.

The Fix: Account 4400 (Straight-Line Rent Adjustment) must be created as a separate income account before any lease with a free rent period or stepped escalation is entered. Its absence is a GAAP compliance gap that auditors will identify in the first review of the income statement.

Intercompany Accounts Missing or Unnamed

The Error: A five-entity property group has no dedicated intercompany receivable or payable accounts. Intercompany balances are posted to general accounts receivable (1300) and accounts payable (2200), mixed with external transactions.

The Fix: Dedicated intercompany accounts must be created for every intercompany relationship before the first intercompany transaction is posted. Intercompany balances mixed into general AR and AP accounts are invisible to the consolidation process, cannot be reconciled between entities, and require transaction-level filtering to identify, which is impractical at scale.

How the COA Connects to Reporting, Budgeting, and Audit

A chart of accounts is not a static setup document. It is the live structure that every financial report, every budget comparison, and every audit procedure draws from. The quality of those outputs is determined by the quality of the account structure beneath them.

• Reporting. Every line in an NOI report, a budget variance report, or a consolidated statement maps to one or more account codes. A COA that has the right accounts in the right structure produces reports that answer the questions property managers and asset managers actually ask. A COA that doesn't have the right accounts produces reports that require manual adjustment before they can be used, which introduces errors and delays that accumulate with every reporting cycle.

• Budgeting. Budget vs actual variance reporting requires that the budget and the actuals are structured against the same account codes. A COA that changes structure mid-year, or that uses different account names across different entities, makes the budget comparison unreliable. For a detailed approach to building budgets that align correctly with the COA structure, see how to build an annual property budget across multiple properties and entities.

• Audit. Auditors verify income categorisation, expense classification, balance sheet account accuracy, and intercompany reconciliation by reference to the COA. A well-structured COA makes every one of these verifications straightforward. A poorly structured COA turns every audit into an investigation. IREM's property income and expense reporting standards and NCREIF's institutional reporting guidelines both inform best-practice COA design for commercial property portfolios, and auditors familiar with these standards will apply them in their review.

The FASB's financial statement presentation standards require that income and expense items are presented in a way that faithfully represents the entity's financial performance. A COA that merges income types, combines operating and capital expenses, or omits required GAAP accounts does not meet this standard regardless of how accurately the transactions within it are posted.

For commercial property portfolios managing COA structure across multiple entities, lease types, and reporting requirements, a property accounting platform that enforces consistent account structures across all entities eliminates the categorisation inconsistencies that corrupt reporting at scale. RIOO's property accounting tools and income and expense management features are built on NetSuite's accounting engine, which supports a standardised COA across all entities in the group, property-level segmentation through class coding, and financial reporting that draws directly from the account structure without manual reformatting.

Frequently Asked Questions 

Q1. What is a chart of accounts in property management?
A chart of accounts is the complete list of account codes used to record every financial transaction in a property management operation. It organises accounts into five categories: assets, liabilities, equity, income, and expenses. Every income receipt, every operating cost, every balance sheet movement, and every capital expenditure is posted to a specific account code in the COA. The structure of the COA determines what the financial reports can and cannot show: a COA with the right accounts in the right structure produces reliable NOI figures, budget comparisons, and balance sheets. A COA with missing or incorrectly structured accounts produces reports that require manual correction before they can be used.

Q2. How should base rent and recovery income be separated in the COA?
Base rent and recovery income must be separate account codes, never combined. Base rent (typically account 4100) records the contractual rent obligation under each lease. Recovery income (accounts 4200 to 4220) records operating expense reimbursements paid by tenants under NNN and Modified Gross leases. Combining these into a single account produces a revenue figure that overstates contractual rent, makes recovery rate analysis impossible, and distorts the income categorisation that NOI reporting requires. For portfolios with multiple recovery types (CAM, tax, insurance), a separate recovery account for each type allows the recovery rate for each expense category to be calculated directly from the accounts.

Q3. How should CapEx and OpEx be separated in the COA?
Capital expenditures and operating expenses must be in completely separate account ranges. Operating repairs and maintenance accounts (typically in the 5300 range) cover expenditures that maintain the property in its current condition. Capital improvement accounts (typically in the 6100 range) cover expenditures that extend useful life, improve functionality, or add new capability. The account names should make the distinction unambiguous, and the capitalisation policy must specify the dollar threshold and classification tests that determine which range an item is posted to. Separate account ranges make it structurally difficult to post a capital item to an operating expense account accidentally, which is the most common NOI distortion error in commercial property portfolios.

Q4. Does a multi-property portfolio need separate accounts for each property?
A multi-property portfolio needs property-level segmentation but not necessarily separate accounts for each property. The two approaches are sub-accounts (a separate income and expense account for each property under each account type) and class or department coding (a single set of accounts with a property identifier tag applied to each transaction). Class coding is more scalable for larger portfolios because adding a new property doesn't add new accounts to the COA. Sub-accounts are simpler for small portfolios of five properties or fewer. Regardless of the approach, every income and expense transaction must be identifiable by property for NOI reporting to work correctly.

Q5. What balance sheet accounts does a property management COA need?
The key balance sheet accounts specific to property management are: investment property and accumulated depreciation (to track asset values), deferred rent receivable and liability (to carry the straight-line rent balance), tenant security deposits as a liability (not income), TIA receivable (for landlord-funded tenant improvements), and intercompany receivable and payable accounts for each related entity relationship. These accounts are not present in generic COA templates and are the most commonly missing accounts in property management COAs built on standard bookkeeping software.

Q6. How should intercompany accounts be structured in a multi-entity property COA?
Intercompany receivable and payable accounts must be named by counterparty entity, not described generically. A separate account for each intercompany relationship (Intercompany Receivable from Management Co, Intercompany Payable to Holding Co) allows the monthly intercompany reconciliation to be run by account balance directly, without filtering transaction detail. The naming convention must be consistent across all entities in the group. Intercompany balances that are mixed into general accounts receivable or payable are invisible to the consolidation process and cannot be reconciled efficiently at month end.

Q7. How does the chart of accounts affect NOI reporting?
The chart of accounts determines every line in the NOI report. If the COA doesn't separate base rent from recovery income, the NOI report can't distinguish them. If the COA doesn't separate operating expenses from capital items, capital expenditures will appear in the operating expense pool and suppress NOI. If there is no straight-line rent adjustment account, the GAAP-required non-cash income line is missing from the income statement. Every NOI reporting gap traces back to an account that is missing, incorrectly named, or incorrectly positioned in the COA structure.

Q8. How often should a property management chart of accounts be reviewed?
The COA should be reviewed at least annually, at the start of each budget cycle, and whenever a significant portfolio change occurs: new property acquisitions, lease type changes, new intercompany relationships, entity restructurings, or changes to the portfolio's reporting requirements. The review should check that every income and expense type the portfolio generates has a correctly positioned account, that no accounts have been used for purposes outside their defined scope, and that the account structure still supports all the reports the portfolio needs to produce. A COA that hasn't been reviewed since it was first set up will almost always contain accounts that are being misused and gaps that are being worked around with manual adjustments.

A chart of accounts is the single most leveraged decision in property accounting setup. Get it right and every report the portfolio produces is reliable from day one. Get it wrong and every report requires manual correction, every audit requires additional investigation, and every portfolio growth event makes the underlying problem harder to fix. The time to build the right COA is before the first transaction is posted, not after the first audit finding.