San Francisco rent banking Skipped AGAs accumulate. Release them at 7%/year + 10%/notice ceilings — the fullest banking model in California.

How §4.12 banking accumulates

The mechanics are unique among California rent-control regimes:

1. Automatic accrual. Every Rent Year, the SF Rent Board publishes an AGA — the percentage that the rent on a covered unit may lawfully increase that year, computed under S.F. Admin. Code §37.3(a)(1)(B) as 60% of the CPI-U for the prior 12 months ending in October. RY 2026-27 = 1.6%. If the landlord serves a noticed increase that year of less than the AGA — including 0% (no increase served) — the difference between the AGA and the noticed increase is automatically banked.
2. No registration or paperwork. §4.12 does not require the landlord to file with the Rent Board to preserve a banked AGA. The accumulation is statutory; the burden of proving the historical AGA stack falls on the landlord at the time of release, but no registration is required to maintain it.
3. No expiration. Banked AGAs do not expire. A landlord who takes 0% for 10 years can in principle release ~25% of accumulated banking (sum of 10 years of AGAs) over a multi-year schedule.
4. Two ceilings on release pace. The 7%/year cap (§4.12(b)(1)) and the 10%/notice cap (§4.12(b)(2)) constrain how quickly the banked balance can be drawn down — both apply conjunctively. See the two-ceiling section below.
5. Tenancy-bound. §4.12(c) limits banking to the current tenancy. Vacancy resets the balance. See the unit-vs-tenancy section.

The two ceilings: 7%/year and 10%/notice

§4.12(b) imposes two limits on how fast banking can be drawn down. Both apply, conjunctively, to every notice.

§4.12(b)(1): 7% in any calendar year

The cumulative rent increase from banking releases — across one or more notices in a single calendar year — cannot exceed 7% above the current AGA. For RY 2026-27 with a 1.6% AGA, the maximum lawful release in calendar year 2026 is 1.6% + 7% = 8.6% (current AGA plus banking). The 7% cap resets on January 1 of each year, allowing a multi-year drawdown schedule.

§4.12(b)(2): 10% in any single notice

Any individual rent-increase notice cannot exceed 10% above the prior rent (cumulative — current AGA + banking + any other lawful increase included in the same notice). For the RY 2026-27 1.6% AGA, the maximum single-notice release of banking is 10% - 1.6% = 8.4%. The 10% cap is per-notice, not per-year, so a landlord with a large balance who wants to release 7% in 2026 can either issue one notice for the full 7% (within the 10% per-notice cap and the 7% calendar-year cap), or two notices of 3.5% each, or any other split that respects both ceilings.

Why both ceilings matter

Consider a landlord with a 15% banked balance who wants to release as fast as possible:

• 2026: 1.6% AGA + 7% banking release = 8.6% (satisfies both 7% calendar-year cap and 10% per-notice cap). Banked balance: 15% - 7% = 8%.
• 2027: hypothetical AGA of, say, 1.8% + 7% banking = 8.8%. Banked balance: 8% - 7% = 1%.
• 2028: hypothetical AGA + 1% remaining banking retires the balance.

For a landlord with a 30% banked balance — possible after a decade of skipped years — the drawdown is roughly 4-5 calendar years at the 7%/year pace. This is what makes SF banking the most generous California regime: the balance never decays.

The §4.12(c) unit-vs-tenancy rule

§4.12(c) ties banking to the current tenancy, not the rental unit. When the unit becomes vacant and a new tenant moves in, the banked balance from the prior tenant resets to zero. The mechanics:

1. Vacancy decontrol. For SF rental units that are not subject to vacancy control (i.e., units controlled by Costa-Hawkins vacancy decontrol — most stabilized SF units except those with owner-imposed vacancy control under §37.3(d)), the new tenancy can be set at any market rent at move-in. The vacancy effectively retires the prior tenancy's banked balance because the rent baseline resets.
2. New tenancy = new accumulation. Starting from the new tenant's move-in date, AGAs accumulate fresh under §4.12. The new tenant's banked balance is 0% on move-in day and grows by the AGA for any subsequent year in which the landlord doesn't serve the full annual increase.
3. The §4.12(d) reach-back trap. A landlord cannot serve a banking-release notice that draws on AGAs from before the current tenant's move-in. If tenant moved in March 1, 2020, the landlord can bank the AGAs from RY 2020-21, 2021-22, 2022-23, 2023-24, 2024-25, 2025-26, and 2026-27 (assuming the landlord didn't already release them) — but not RY 2019-20 or earlier. Documentation of the move-in date is the audit-trail anchor.

Practical implication: long-tenancy units with consistent under-AGA rent setting accumulate the most banking. Frequent turnover resets the balance and limits the banking value. Many SF small landlords with multi-decade tenants have substantial unrealized banking — but are constrained to the 7%/year + 10%/notice release pace.

How to serve a §4.12 banking-release notice

The notice itself is a §37.3 rent-increase notice, with banking release identified as a component. Required content:

• Cal. Civ. Code §827(b) compliance. The state-law notice-period floor for any rent increase: 30 days for increases ≤10%, 90 days for increases >10%. SF can never trigger 90-day because the §4.12(b)(2) per-notice cap is 10%. With the §1013 mailing-add of 5 days, the notice mailed first-class on day 0 takes effect on day 35 (30 days bare + 5 days mailing-add) at the earliest. See the §827(b) deep-dive for the cumulative-trigger trap that can push a SF banking notice into 90-day territory in narrow circumstances (extremely rare in practice given the 10% per-notice cap).
• Component breakdown. The notice must identify the components of the increase: current AGA + banking release amount, with the banking release tied to the historical AGAs being drawn down. The Rent Board's recommended format itemizes the released years.
• Statutory language. §37.3(a) and §4.12 citations, new rent amount, current rent amount, percentage increase, effective date, and the landlord's signature with date of service.
• Vacancy-control disclosure if applicable. If the unit is subject to owner-imposed vacancy control under §37.3(d) or §37.3(e) (rare), the disclosure of that control regime is required.

The free San Francisco notice generator takes (current rent, last-increase date, banking ledger, current AGA) and emits a §37.3 + §4.12 compliant notice with the component breakdown, the §827(b)-compliant effective date, and the §1013 mailing-add applied.

SF banking vs the other 3 California models

The four California rent-banking regimes diverge sharply on accumulation and release. Side-by-side:

• AB 1482 statewide (Cal. Civ. Code §1947.12). No banking. Every year not used is forfeit. The 2026 cap is 8.8% (year ending July 31, 2026); a landlord who took 0% in 2025 still gets 8.8% in 2026, not 8.8% + the skipped 2025 cap. Forfeit-on-skip is the categorical rule.
• LA RSO §151.06.A. No banking. Like AB 1482, every year not used is forfeit. The flat 3% (through June 30, 2026) and the post-July-1 90% × CPI-U (~2.8% projected) are floor caps for the year served — historical skipped AGAs do not stack. See /seo/los-angeles-rso-rent-increase-2026/.
• San Francisco Rent Board Rules §4.12. Full banking with 7%/year + 10%/notice ceilings. The regime walked on this page. Most generous of the four.
• Berkeley §13.76.110. Hybrid banking. Berkeley accumulates unused AGAs but releases them through a petition path under §13.76.150 with a §13.76.110(C) once-per-12-months gate. Releases above the current AGA require a Berkeley Rent Board petition (Reg. 1271 governs the procedure), which is adjudicative rather than automatic. Unlike SF's automatic self-effectuating release, Berkeley banking requires a hearing unless the release is below the AGA.

The full side-by-side analysis with statute citations and 2026 calendar context is at /seo/ab-1482-banking-provision/; the cross-California rent-cap walkthrough is at /seo/california-rent-increase-2026/; the Berkeley-specific deep-dive on the petition procedure is at /blog/why-berkeley-1pct-2026/.

What happens if you over-release banking

Over-release — exceeding 7% in a calendar year, exceeding 10% in a single notice, or releasing AGAs from before the current tenancy — makes the notice unenforceable. Penalty stack:

1. Notice unenforceable to the extent of the overage. S.F. Admin. Code §37.7 voids the notice as to the unlawful portion. The lawful portion (e.g., 1.6% current AGA + 7% banking, totaling 8.6%) remains enforceable; the over-release portion is void.
2. Refund of overcharge. §37.8 + §37.9 give the tenant the right to recover the overcharged portion of any rent already paid, plus 100% interest under §37.10B(a)(1).
3. Treble damages on willful violations. §37.10B(c) authorizes the SF Rent Board to award treble damages on a willful over-release — three times the overcharge.
4. Attorney's fees. §37.10B(c)(1)(A) and Cal. Code Civ. Proc. §1021.5 (private attorney general statute) make attorney's fees recoverable in tenant overcharge actions.
5. Just-cause-eviction defense. A tenant in unlawful-detainer (UD) proceedings can raise a defective banking notice as an affirmative defense under §37.9(a)(2), undermining any subsequent for-cause termination tied to non-payment of the over-released portion.

How RentCeiling tracks SF banking

The free San Francisco calculator takes (current rent, tenancy start date, last-increase date) and returns the RY 2026-27 1.6% AGA plus the banked balance computed against the historical AGA series. The banking ledger is the audit-trail artifact: every accrual year is itemized with the governing AGA, every release is itemized with the served notice date, and the running balance is exportable as a CSV/PDF bundle for audit defense. The SF notice generator emits a §37.3 + §4.12-compliant notice with the component breakdown and the §827(b) effective-date math applied. The /compare hub shows SF banking against the other 9 modeled jurisdictions; the all-California banking comparison walks the four California models head-to-head; the Berkeley-specific deep-dive on petition-path banking is at /blog/why-berkeley-1pct-2026/. Open rule-set at /rules/index.json.

Run the SF banking calculator (free)

Common questions