Landlording

The bank answers whether money reached an account. The tenant ledger answers who owns the receipt and which charges it affects. Tax and accounting records answer how the supported transaction is classified. Collapsing those questions into one “rent received” label creates false certainty exactly where the evidence is incomplete.

The IRS rental guidance distinguishes types of receipts rather than treating every deposit as rent. For example, it generally describes a refundable security deposit intended to be returned as not included in income at receipt, while a deposit used as final rent is advance rent. The facts control the classification; a bank memo or suspense-queue age does not. Source: https://www.irs.gov/businesses/small-businesses-self-employed/rental-income-and-expenses-real-estate-tax-tips

A small landlord owns two buildings and receives a $1,725 transfer labeled only “July.” The bank shows settled cash, but the software cannot match the sender.

Calling the amount extra income overstates performance and may misstate tax or owner reporting. Guessing a tenant can alter delinquency, communication, and later dispute evidence. Returning it immediately can send money to the wrong destination or create a loss if the original event later reverses. The queue may look tidy, but the underlying custody problem survives.

A fourth shortcut is less visible: a person posts the receipt manually, then an integration imports the same settlement during the next sync. Without a stable provider or bank identity, both entries look individually plausible. Duplicate checking belongs before application, not only at month end.

The useful artifact is not a vague task called “check cash.” Record the amount, received and effective dates, settlement lifecycle, external IDs, payer evidence, candidate tenancies, conflict reason, open charges, payment instruction, owner, next evidence, deadline, allowed actions, and eventual disposition.

The card should distinguish apply, keep unapplied, return, reverse, and escalate. Each outcome needs its own authority and receipt. An unresolved identity is not cured by an allocation rule; an allocation conflict is not cured by stronger bank evidence. The workflow advances only when the missing kind of evidence appears.

A resolved receipt should bridge one external money event to application lines plus any remaining unapplied amount. Retain the actor, reason, supporting records, timestamps, resident communication where appropriate, and downstream retests. For record-integrity principles, NIST SP 800-53 describes audit records in terms of event, time, source, outcome, and actor, and protects original audit information. Source: https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final

Then examine cause codes. Ambiguous transfers may point to weak remittance instructions; repeated archived-lease matches may reveal stale payer mappings; missing batch detail may expose an integration design problem. Good handling does more than empty a queue. It makes the next unmatched receipt less likely.