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.
Numbered scenario: a partial payment with an instruction
A resident owes $1,500 current rent and a separate $125 utility reimbursement.
•
1. A $1,500 settled payment arrives with a supported instruction identifying July rent.
•
2. The system default would otherwise apply the oldest open item first.
•
3. A reviewer checks the lease, policy, local requirements, and instruction before accepting the proposal.
•
4. The ledger retains one $1,500 receipt and charge-level application lines that show the approved treatment.
Failure modes that change the story of a balance
An allocation can be mathematically balanced and operationally wrong.
•
A configurable default is treated as a universal legal rule.
•
The payment posts before settlement and remains after a return.
•
A direct balance edit removes the link to the receipt.
•
A reallocation overwrites the prior chronology instead of reversing and reposting.
Decision artifact: allocation review fields
Require enough context to approve or pause the proposed split.
•
Receipt ID, settlement state, payer, tenancy, amount, and remittance evidence.
•
Open charges with dates, types, dispute state, and governing source.
•
Proposed rule, proposed application lines, and unapplied remainder.
•
Reviewer, decision, reason, timestamp, and any required tenant communication.
Editorial ownership
Written and maintained by the Aptoria editorial team
Repository and source review completed July 28, 2026. Aptoria reviews scope, source fit, examples, limitations, links, and publication gates. This record does not claim attorney, CPA, lender, appraiser, or other independent professional sign-off.
Professional review is not claimed. Verify current law, tax treatment, loan terms, valuation inputs, and property-specific facts with the appropriate qualified professional before acting.
Related terms
Accounting & tax
Unapplied cash
Unapplied cash is money that has settled or been received but is not yet assigned to a valid tenant, lease, owner, charge, or other ledger destination.
Accounting & tax
Tenant ledger integrity
The condition in which every tenant charge, payment, credit, return, and running balance is complete, traceable, and arithmetically consistent.
AI & autonomy
Provider receipt
A durable record from an external service showing what request it accepted, rejected, or completed under a provider-assigned identifier.
From definition to done
Aptoria runs the routine work behind these terms — rent, books, and screening — inside limits you set. Free for your first unit.
Start free