Payment allocation

Payment allocation answers where a received amount goes inside the ledger. A single receipt might cover current rent, an earlier balance, utilities, or more than one lease. The ledger should record the receipt once, then show the allocation lines that reduce specific charges. This separation makes later reallocation or reversal possible without inventing a second cash event.

There is no safe universal allocation priority for every rental. The governing lease, payment instructions, written policy, local law, dispute status, and charge type may change what is permitted. A software default such as “oldest charge first” is a configuration choice, not proof that the result is correct for a particular tenancy.

A sound allocation record preserves the source receipt, payer, settlement status, allocation rule or instruction used, charge-level applications, actor, time, and later changes. When the evidence is incomplete or conflicting, the payment belongs in an exception state instead of being forced through a default that could alter delinquency or notice calculations.

Allocation failures include applying returned money, splitting roommate payments without instruction, consuming disputed charges first, or editing charge balances directly. Review both the cash total and the allocation detail: the receipt total should equal the sum of its application lines plus any explicitly unapplied remainder.