corBASE
NOI normalization for affordable housing underwriting.
Open corBASEbase™ transforms property financial documents into auditable, committee-ready NOI Normalization Reports — every number traced to its source document, line and month.
corBASE and Section 42 Pro are Corvin.AI products. You'll be asked to sign in if you aren't already.
NOI normalization for affordable housing underwriting.
Open corBASENot yet available.
Coming later
NOI normalization is the step between a seller's T-12 and your model: removing one-time items and resetting management fees, taxes, insurance and reserves to the costs a new owner will carry. Affordable deals can add HAP income and utility allowances to that list. base™ works through it in seven steps, with an analyst confirming each one.
Upload the seller's files as they came: T-12, rent roll, insurance, tax bills.
Confidence scores on each line show reviewers where to look first.
An analyst confirms the extracted figures before they are used.
Seller accounts map to HUD-standard categories, so deals compare line for line.
Your versioned rules decide adjustments the same way on every deal.
Follow reported NOI to normalized NOI, one adjustment at a time, with the reason for each.
Sign off on the bridge and export it with the evidence trail intact.
Open any adjustment in base™ and follow it back to its source: the document, the line and the month. You also see the rule version that produced it and the analyst who approved it. When a lender or an auditor asks where a number came from, the answer sits with the number, not in someone's inbox.
Document, line and month for each figure, with no re-tracing by hand.
Mapping changes show who made them and when, so nothing moves quietly.
The rule and version behind each adjustment, so old deals stay explainable.
Linked flags show reviewers why an adjustment was proposed.
Rationale, approvals and timestamps put each sign-off on record.
The number that hurts you in committee is the one nobody can trace.
The AI in base™ reads your documents, explains each adjustment in plain English and flags lines that need a second look. It never changes a figure on its own. An analyst accepts or rejects each suggestion, and the decision is logged, so your team keeps the speed of extraction without handing the final number to a model.
Plain-English reasons, drawn only from your documents, so nothing is invented.
NOI drivers, assumptions and risks in one summary, each linked to its source.
Lines that need a second look, flagged before they reach the bridge.
AI can suggest a change. Only an analyst can make one.
Acquisitions teams use base™ to underwrite a seller's T-12 on an LIHTC or HUD-assisted deal. The same policy then follows the asset into refinancing, monthly asset management and portfolio reviews, so the NOI you approved at acquisition is the NOI you track after closing.
Underwrite a seller's T-12 on your policy, with adjustments backed by their source lines.
Give lenders a normalized NOI with the source behind the numbers.
Track normalized NOI month over month on one consistent policy.
Compare properties on like-for-like numbers instead of ad-hoc spreadsheets.
Give two analysts the same T-12 and you can get two NOIs: one reserves $300 a unit a year, the other $450; one keeps the seller's management fee, the other resets it to market. The gap is policy, not arithmetic. base™ applies one versioned policy to every deal, whoever runs it.
Analysts confirm extracted lines instead of keying them in.
Versioned rules apply the same way, whoever on the team runs them.
Asset management inherits the same policy and file acquisitions built.
When a lender or auditor asks, the answer is already on file.
Export the full NOI Normalization Report to Excel and PDF, with the bridge, the adjustment detail and the evidence trail intact.
The exported NOI Normalization Report, bridge and evidence trail intact.
Seller financials are confidential, and base™ handles them that way. Data is encrypted in transit and at rest, each client's data is isolated, and your documents are never used to train third-party AI models. Mappings, rules and approvals are logged with timestamps, so you can show an auditor who did what.
Encrypted in transit and at rest, with client data kept separate.
Your documents never train third-party models.
Every mapping, rule and approval is recorded with a timestamp.
NOI normalization restates a T-12 at the run-rate a buyer will carry: one-time items out; fees, taxes, insurance and reserves reset to your terms.
Yes. Policies are versioned rule sets. Start from HUD-standard categories and adapt them to your shop.
In base™ the AI doesn't decide them. It extracts, explains and flags; every adjustment is confirmed by an analyst and recorded with rationale.
No. base™ doesn't build pro formas or model tax credits. It supplies the normalized NOI and evidence trail your model starts from, exported to Excel and PDF.