Feature
Affordable housing and Section 8 operations
HAP contracts as a first-class part of the lease: the split is stored, the tenant share is what gets billed, the authority share is a receivable until it arrives, and recertifications are scheduled instead of remembered.
The problem
Section 8 leases break ordinary rent software.
A voucher lease has two payers on different schedules, a share that changes at recertification, and late fees that must not be computed on gross rent. Most systems treat that as a note and a spreadsheet.
- The resident is shown — and chased for — the gross rent.
- Authority payments arrive in lump sums that are matched by hand to periods and contracts.
- Recert dates are tracked in a calendar; a missed one becomes a rent-share dispute.
- Late fees are computed on the wrong basis.
The workflow
Contract → split billing → receivable → recert
Every step runs on the same ledger as every other lease, so reporting and accounting do not need a special case.
- Attach the HAP contract
Authority, contract number, program, gross rent, payment standard, tenant share, authority share, start and end. The lease keeps the gross rent; the contract holds the split.
- Bill the tenant share only
Rent charges post for the tenant’s share. Delinquency and late fees are naturally scoped to what the tenant actually owes.
- Track the authority share
Each period’s expected authority payment is a receivable. When it arrives it posts as a real payment; the portfolio summary shows expected versus received.
- Schedule recertifications
A recert chain per contract with a configurable notice window (default 90 days). Completing a recert applies the new split under a formal lease amendment.
- Validate against rent limits
Gross rent is validated against per-program limits you configure in the compliance rules table.
- Report
Expected-vs-received, recerts due in 90 days, and the standard rent roll and delinquency reports with the split visible.
Illustrative HAP contract panel: split, expected vs received by period, recert due.
Capabilities
What is built, what needs configuration, what is planned
Each row is a real capability in the current build. Labels are derived from the codebase and its test suites, not from a roadmap deck.
How to read the labels
- Built
- Implemented in the current build and covered by its test suite.
- With configured integration
- Implemented; a live outcome requires a provider you configure (keys, contract, or credentials).
- Pilot
- Implemented in part and enabled per pilot customer with tuning.
- Planned
- On the roadmap. Not sold or promised today.
-
HAP contracts on a lease
PilotAuthority, contract number, program, gross rent, payment standard and the tenant / authority split with start and end dates.
-
Split billing
PilotRent charges bill only the tenant share; the authority share is tracked as a receivable and posted as a payment when it arrives.
-
Expected vs received tracking
PilotPortfolio summary of authority payments expected against received, by period and contract.
-
Recertification schedule
PilotRecert chain per contract with notice windows (default 90 days, configurable) and completion that re-runs the split under a formal amendment.
-
Late fees on the tenant share only
PilotLate-fee basis is configurable and defaults to the tenant's obligation, not gross rent.
-
Program rent-limit validation
With configured integrationGross rent validation against per-program limits held in the compliance rules table — you configure the limits for your jurisdiction.
-
HUD-format reporting and EIV workflows
PlannedAgency-specific submission formats.
By role
What each party gets
Affordable-housing teams
Contracts, splits and recert dates in the lease record; a receivables view for authority payments.
Owners
Statements that show what the authority paid and what the resident paid, separately.
Residents
A balance that reflects only their share, with late fees on that share only.
Configuration and pilot notes
Before you rely on it
Things that are set up per operator during a pilot, or that depend on a provider you contract.
- Recert notice windows, the late-fee basis and per-program rent limits are compliance rules configured to your jurisdiction and your housing authority’s practices.
- ResidentAxis is not certified by HUD or any housing authority and does not guarantee regulatory compliance; it tracks what you configure.
- HUD-format reporting, EIV workflows and authority-specific submission formats are planned, not built.
- Program names (Housing Choice Voucher, project-based, state programs) are labels you set on the contract.
Section 8 pilot
Explore a Section 8 pilot
For owners and managers with HAP contracts today, or about to take them on. We start with your contracts, your authority’s recert cadence and your late-fee policy — then configure the split rules to match.
Questions about this area
Does this work with project-based Section 8 as well as vouchers?
The contract model (two payers, a split, a schedule) applies to both. Program-specific reporting formats are on the roadmap.
What happens when the authority pays a lump sum for several units?
Authority payments are recorded per contract and period; a lump sum is split by the manager across the receivables it covers.
Can we run mixed portfolios — some HAP leases, some market?
Yes. A HAP contract is attached per lease; the rest of the portfolio is unaffected.
Related
Connected areas
Resident portal & payments
Balances, receipts, card/ACH via Stripe, Zelle queue, messaging.
Learn moreAccounting & trust
Balanced GL, trust invariant, period close, bank matching, exports.
Learn moreLeases & e-signatures
Template-built leases, rules-based review, locked terms, native signing.
Learn moreBring your HAP contracts to a pilot.
Owners and managers of Section 8 properties get a scoped onboarding around their contracts and their authority’s cadence.