FFO vs. AFFO for Property Accounting Software: Technical Guide
You have been in that meeting. Someone from investor relations presents a net income figure, your CFO flags depreciation distortions, an asset manager pulls up a different spreadsheet, and thirty minutes later, the room has three versions of “performance” and no consensus on what the property actually earned.
That is not an organizational problem. That is a metrics problem. Specifically, it is the gap between what GAAP requires you to report and what real estate economics actually look like on the ground.
Funds from Operations (FFO) and Adjusted Funds from Operations (AFFO) exist to bridge that gap. But the formulas are the easy part. The hard part is the accounting infrastructure that makes those numbers defensible, auditable, and reproducible without a team of analysts manually cross-referencing five systems at month-end.
This guide covers both metrics in depth, the mechanics, the common failure modes, and what your property accounting software stack actually needs to produce them reliably.
Key Takeaways
- GAAP depreciation can turn a cash-positive portfolio into a paper loss. FFO corrects for this by adding back non-cash real estate depreciation and stripping out one-time gains or losses from asset sales.
- FFO assumes properties do not deteriorate, which means it ignores the real cash spent on roof replacements, HVAC overhauls, tenant improvement allowances, and leasing commissions. AFFO deducts these to show what the portfolio actually costs to operate.
- The funds from operations formula is straightforward. What breaks reconciliation in practice is a chart of accounts that does not separate real estate depreciation from other depreciation, CapEx that gets coded inconsistently, and lease data that lives in a spreadsheet outside the accounting system.
- Generic ERPs and disconnected property platforms force month-end reconciliation between systems. Purpose-built property accounting software with native ERP integration prevents those gaps at the point of data entry.
- Investors and auditors expect to understand how you define AFFO for your portfolio, not that you followed someone else’s version.
Why Standard Net Income Lies to You
Real estate assets depreciate on paper while they appreciate in reality. Under GAAP, a property that generates $2M in rental income annually will show a dramatically lower net income after straight-line depreciation. Sometimes it will show a loss, despite cash flows being entirely healthy.
Consider a simplified example. A commercial building purchased for $10M with a 39-year straight-line depreciation schedule generates $256,000 in annual depreciation expense. That is $256,000 subtracted from net income every year, regardless of whether the building’s market value moved at all. For a portfolio of 20 such properties, that is over $5M in non-cash charges that distort reported earnings.
Net income, in this context, is an accounting artifact. It satisfies auditors and tax authorities. It does not tell you whether your portfolio is operationally healthy, whether distributions to investors are sustainable, or whether you are actually generating cash.
That is the origin story of FFO. For a deeper look at how the metric was developed and where it applies beyond REITs, this practical guide to FFO in real estate covers the context most technical glossaries leave out.
The Funds from Operations Formula: What It Does and Does Not Solve
NAREIT (the National Association of Real Estate Investment Trusts) formalized the funds from operations formula to give the industry a standardized non-GAAP alternative to net income. At its core:
FFO = Net Income
+ Depreciation and Amortization on Real Estate Assets
+ Losses on Sale of Properties
- Gains on Sale of Properties
- Interest Income (non-operating)
The logic: add back the non-cash depreciation that GAAP requires, strip out one-time gains or losses from asset sales (which are not operational), and you get a cleaner picture of recurring operational performance.
A worked example:
| Item | Amount |
|---|---|
| Net Income | $3,000,000 |
| Real Estate D&A | $1,200,000 |
| Loss on Property Sale | $150,000 |
| Gain on Property Sale | $(600,000) |
| Interest Income | $(80,000) |
| FFO | $3,670,000 |
FFO is a significant improvement over net income for real estate operations. But it has a structural blind spot that becomes more expensive to ignore as a portfolio scales.
What FFO does not account for:
FFO adds back depreciation on the assumption that properties are not actually deteriorating, that their economic value holds. That assumption works at the asset class level over long periods. It does not work at the property level over operational cycles.
A 15-year-old apartment complex does need its HVAC systems replaced. The lobby does need a capital refresh to maintain occupancy rates. A commercial property does have recurring tenant improvement allowances that cost real cash. None of that shows up in FFO.
The result: a portfolio can report healthy FFO while it consumes cash on maintenance CapEx that will eventually compress distributions or require debt finance. For sophisticated investors and institutional LPs, this is the FFO credibility problem.
AFFO: Closing the Gap Between Reported Cash Flow and Economic Reality
Adjusted Funds from Operations (AFFO) takes FFO and makes it honest about what the portfolio actually costs to run.
AFFO = FFO
- Recurring or Maintenance Capital Expenditures
- Straight-Line Rent Adjustments
- Amortization of Leasing Commissions
- Tenant Improvement Allowances
+/- Other Non-Cash Normalization Items
Recurring CapEx is the non-discretionary cash spent to keep properties functional and competitive: roof replacements, HVAC overhauls, elevator maintenance, parking lot resurfacing. Not growth CapEx. Not acquisitions. The baseline cost of not letting assets deteriorate.
Straight-Line Rent Adjustments exist because GAAP requires rental income to be recognized evenly over a lease term, even when the lease has rent-free periods or step-ups. A 5-year lease with a 6-month free period and 3% annual escalations will show GAAP revenue that differs from actual cash collected in every single period. AFFO reverses this to show what is actually received.
Leasing Commissions and Tenant Improvement Allowances are real, recurring cash outflows that FFO ignores. In commercial real estate, they are not discretionary. You pay them to lease space. A 50,000 sq ft office building that turns over 20% of its leases annually may spend $500,000 to $1.5M in TI and commissions that never appear in FFO.
Continuing the worked example:
| Item | Amount |
|---|---|
| FFO | $3,670,000 |
| Maintenance CapEx | $(480,000) |
| Straight-Line Rent Adjustment | $(210,000) |
| Leasing Commissions | $(175,000) |
| TI Allowances | $(140,000) |
| AFFO | $2,665,000 |
The spread between FFO ($3.67M) and AFFO ($2.67M) in this example is not noise. It is $1M in cash obligations that FFO was quietly ignoring. For investor distributions or dividend coverage analysis, that gap matters enormously.
The Real Reconciliation Problem: It Is Not the Math
Experienced real estate finance professionals know what most FFO and AFFO explainers gloss over: the formulas are not the hard part. Any controller with a spreadsheet and an afternoon can calculate FFO. The hard part is the data reliability problem that sits underneath the calculation.
To reconcile FFO to AFFO accurately and consistently, you need:
1. Property-level depreciation that separates real estate D&A from other depreciation
Most general ledger systems do not natively tag depreciation by asset class. A vehicle, a piece of equipment, and a building all hit the same D&A line. FFO is only supposed to add back real estate depreciation, not all depreciation. If your chart of accounts does not distinguish these, your FFO is wrong from the first line.
2. CapEx classification that distinguishes maintenance from growth
This is where the arguments start. Is replacing 40% of a building’s windows maintenance CapEx (should reduce AFFO) or a value-add improvement (discretionary, sometimes excluded from AFFO)? There is no universal answer, but there has to be a consistent answer in your system — one that your property accounting software enforces at the point of entry, not at month-end cleanup.
3. Lease-level straight-line rent across every active lease
Straight-line rent requires you to know the total contractual rent over the full lease term, divide it evenly, and track the difference between GAAP revenue and actual cash receipts. For a portfolio with 200 or more active leases at various stages, each with their own commencement dates, escalation schedules, and free rent periods, doing this in spreadsheets is a reconciliation disaster in the making. The variance between GAAP-recognized revenue and cash received compounds with every new lease and every amendment.
4. TI and leasing commission amortization separated from operational expenses
Tenant improvement allowances are often capitalized and amortized, but for AFFO purposes they should be expensed as incurred. Depending on how your accounting system handles these, you may be double-counting or missing them entirely in your AFFO calculation.
5. Consistent inter-period treatment across entities
Multi-entity portfolios with property-level LLCs, fund-level vehicles, and holding companies need consolidation logic that preserves property-level granularity. The moment you consolidate before extracting FFO and AFFO components, you lose the ability to reconcile at the property level, which means you cannot identify where the variances are coming from.
Where Property Accounting Software Either Earns Its Keep or Fails You
The reconciliation problems above are not theoretical. They show up in real operations, repeatedly.
Property managers who run portfolios out of QuickBooks or generic ERP systems consistently hit the same walls: depreciation is not tagged by asset class, CapEx decisions made in the field are not coded consistently back to the GL, lease data lives in a separate spreadsheet that is manually reconciled to the accounting system, and by month-end the team does forensic accounting rather than management reporting.
The specific failure patterns look like this:
The Classification Drift Problem
A maintenance tech submits a $45,000 roof repair invoice. Someone in AP codes it to building maintenance (operational expense). Someone else on the asset management team recodes it as a capital improvement. Three months later, your CapEx schedule and your maintenance expense ledger are both wrong by $45,000, and no one catches it until the annual audit.
The Straight-Line Rent Lag
A new 7-year commercial lease is signed with 4 months free rent and 3% annual escalations. Your leasing team logs it in a lease spreadsheet. The accounting system does not sync until someone manually enters the lease schedule, which happens 6 weeks after commencement because the team is busy. In those 6 weeks, you have been recognizing actual cash received, not straight-lined GAAP revenue. The prior periods have to be corrected, which creates adjusting journal entries that obscure your actuals.
The CapEx Threshold Inconsistency
Your capitalization policy says anything over $10,000 gets capitalized. But the policy is in a PDF that not everyone has read. Field managers submit invoices, AP processes them, and $8,000 to $12,000 items get coded inconsistently depending on who processed them that week. Over a quarter, the impact on AFFO can be material.
The Consolidation Aggregation Loss
You run a 50-property portfolio across 12 LLCs. When you consolidate for investor reporting, the line items collapse. By the time you are at portfolio-level FFO, you have lost the property-level detail needed to question a number or trace a variance. Your investors ask why AFFO dropped 8% quarter over quarter. You can tell them the portfolio total. You cannot tell them which three properties drove it without going back into individual entity financials, which takes days.
These are not edge cases. They are the operational norm for mid-market property portfolios on systems not purpose-built for real estate financial reporting.
To understand how this fits into the broader discipline of real estate financial management, this overview of property accounting and how purpose-built software supports it covers the foundational context well.
What a Purpose-Built Property Accounting System Needs to Handle
Given the reconciliation requirements above, the right property accounting software for FFO and AFFO workflows needs to do several things that most generic accounting tools do not:
Native lease abstraction with automatic straight-line rent calculation
The system should read lease terms, calculate GAAP straight-line revenue, and post the difference to a deferred rent liability account automatically. No manual spreadsheet. No lag between lease execution and accounting system recognition.
Asset-class-specific depreciation
The GL should distinguish real estate depreciation from other depreciation at the transaction level, not as a reporting-time filter. This is what makes FFO calculation from the trial balance straightforward rather than a manual extraction exercise.
CapEx classification enforcement at data entry
The system should prompt or require the person who enters an invoice to classify it according to the capitalization policy. Hard stops, approval workflows, or classification rules that flag amounts near the capitalization threshold prevent the classification drift problem before it compounds.
Property-level sub-ledgers that survive consolidation
Portfolio reporting should be possible at any level of aggregation without losing the ability to drill down. Net income at the portfolio level should be traceable to entity level, to property level, to unit level, without manual reconstruction.
Recurring CapEx forecasting tied to actuals
AFFO is most useful when you can compare it against prior periods and against budgets. That requires the system to track recurring CapEx actuals in a way that maps to your AFFO reconciliation categories, not just to a generic “capital expenditures” line.
If you are still at the stage of evaluating what the market offers, this comparison of the top 10 property management accounting software options for 2026 is a useful reference point before you make a decision.
How Propertese Handles This Without a Second Accounting System
Most property management software takes the wrong turn here. They build their own accounting engine from scratch, which means you end up with a property operations platform that has just enough accounting capability to be dangerous but not enough to satisfy a finance controller, an auditor, or an institutional LP with serious questions about your AFFO methodology.
Propertese takes a different approach. Rather than replicating accounting functionality, it has native integration with NetSuite, which means your property operations layer sits on top of one of the most robust ERP platforms available, without your team needing to maintain two separate accounting systems or manage a brittle integration between a property platform and a general ledger.
Conclusion
FFO and AFFO are not reporting problems. They are system design problems. The quality of your reconciliation is bound by the quality of the data that flows into it, which means it is bound by how well your property accounting software captures, tags, and preserves financial data at the transaction level.
If your current stack produces numbers that require significant manual reconstruction before they are investor-ready, that is a signal worth taking seriously. Not because the reporting looks bad, but because the operational risk it represents is real.
Propertese is built natively on NetSuite. It was designed specifically for property management organizations that have grown past the point where a disconnected property platform and a standalone ERP can keep up. The combination gives you property operations at the front end and institutional-grade financial reporting at the back, with the lease accounting, depreciation, and CapEx classification logic handled automatically in between.
If your team is working through a reconciliation right now and the process feels more manual than it should, that is worth a conversation. The Propertese team can walk through your specific portfolio structure, how FFO and AFFO reporting is set up, and how multi-entity consolidation works in practice, not just in theory.