T12 Data Extraction: Why Unstructured Statements Are So Hard

A trailing twelve-month (T12 or TTM) statement shows a property's actual income and expenses over the most recent 12-month period, typically with monthly detail. It is a core underwriting document because it reflects operating performance rather than a projected pro forma. The challenge is rarely the arithmetic; it is converting inconsistent documents into a reliable dataset.

Why T12 Statements Resist Standardization

T12s commonly arrive as PDFs, scans, spreadsheet exports, or marked-up printouts. While the underlying information may be complete and legible, the documents often lack a consistent schema. Account names and codes vary by property management system and accounting convention. The same item may appear as Rent Income, Gross Potential Rent, Rental Revenue, or only as a numeric code.

Revenue adjustments create additional ambiguity. Concessions may appear as a contra-revenue line, be included in vacancy, or be netted against rental income. Statements can also mix monthly figures, subtotals, quarterly rollups, and annual totals. Extracting every numeric cell without recognizing those relationships can cause double counting and produce figures that do not reconcile.

What Accurate Extraction Requires

A useful extraction captures account names and codes, monthly values, subtotals, annual totals, effective gross income, operating expenses, and net operating income. Every line item should map to a consistent category across properties, while the statement's hierarchy and calculation logic remain intact.

Three validation tests are essential:

• Monthly columns tie to the reported annual totals.
• Line items use standardized categories across properties.
• Effective gross income, operating expenses, and net operating income reconcile to the source statement.

Without these checks, a model can quietly diverge from the seller's figures while still appearing plausible.

Connecting the T12 to Due Diligence

The T12 reports property income in aggregate, while the rent roll shows unit-level leases, in-place rents, and occupancy. Reconciling the two helps confirm that reported revenue is supported by the leases on the books and can expose uncollected rent, concessions, or vacant units that a summary statement may obscure. Both documents need to be structured for this comparison to be efficient.

Building a Repeatable Workflow

Institutional workflows require more than reading one document. Teams need repeatable categorization, outputs that can feed underwriting and reporting systems, and formats such as Excel, CSV, or JSON that preserve the structure for future properties. A practical process confirms the covered period, inventories account names and codes, separates monthly figures from totals, investigates variances, reconciles the major operating metrics, and exports a consistent dataset. The goal is not simply to read a T12, but to impose a dependable structure on statements from different sources.

View the complete T12 data extraction article on Coastwise Analytics