Last updated 2026-10-03

INITIAL_RENT

AI-generated content

This document was generated by an AI assistant from the 'Event Matrix Accounting' Google Sheet and the AccountingEventType Java enum. The "Code references" section is regenerated by adb-doc/scripts/sync-accounting-events.js. Verify accuracy before relying on the details.

Business case (verbatim from the sheet, French): Sequence carrier (sequence 30) used during initial rent processing for the first call.
Sequence carrier used during initial rent processing for the first call.

At a glance

Field	Value
Family	`internal`
Enum constant	`AccountingEventType.INITIAL_RENT`
Prefix	`IR`
Settlement priority	100
Journal (catalog key)	`n/a`
Journal (label)	n/a
Recurrent?	no
Manual?	no
Status	Développé
pieceReference chrono	`IR…`

Accounting entry

Side	Account
Debit	n/a (carrier)
Credit	n/a (carrier)

See plan-of-accounts.md for account labels and journals.md for the full journal list.

Code references

Definition — adb/adb-model/src/main/java/fr/lifeconnect/adb/model/accounting/AccountingEventType.java:79

Call sites in adb (2):

Call sites in adb-accounting (9):

Call sites in adb-contracts (4):

Confluence

Confluence: https://lifeconnect.atlassian.net/wiki/spaces/LCS/pages/1783267329/Initial+Call+for+rent+the+first+one

Open questions

Deliberate divergence (Greg, 2026-10-03) — lease with no deposit. The Cloudflare port (services/accounting/src/posting/initialRentPosting.mjs, computeSecondary) drops the deposit call when the lease has no deposit (no rentDepositAmount, or no amount in it), exactly like a zero deposit, and books the rent, charges and household waste. The JVM NPEs instead (RentalContract.java:567, rentDepositAmount.getAmount()), which moves the CallForDeposit, the rent calls and the InitialRent to ERROR with nothing booked (seen on staging 2026-10-03). Pinned in services/accounting/test/initial-rent-edge-cases.integration.test.mjs; also services/accounting/AUDIT-accounting.md L-10.
Not changed (out of scope): when a generation does end in ERROR (e.g. a negative deposit, NegativeAmountException), the Cloudflare port answers HTTP 200 with state: ERROR, where the JVM answered 400.