Property-office records ยท Richard (Ryszard) Cieplechowicz
Payment promises are not payments
A follow-up ledger for the gap between a call and a posted receipt
A resident says they will pay Friday. The office may need to follow up, but it cannot count that promise as money received. This ledger keeps the conversation, the actual payment and the accounting record separate until someone verifies each step.
One row per promise, not one row per resident
Use a private office system, never a public spreadsheet, for real records. Give each promise a record ID, property or account reference, date and time of the conversation, promised amount, promised date, staff owner, and source note. Do not copy sensitive account details into casual notes. A later promise gets a new entry linked to the earlier one, so the history does not disappear.
Fictional example: Account A-104, call on September 22. Resident says they expect to pay $650 on September 25. Owner: office desk. Follow-up review: September 26. This is a promise only; the received and posted fields remain blank.
Track four states separately
| State | Evidence to record | What it does not prove |
|---|---|---|
| Promised | Call note, amount and promised date | That any money arrived |
| Received | Receipt or confirmed payment notice, with date and amount | That it reached the ledger |
| Posted | Accounting entry or transaction reference | That every balance question is settled |
| Reconciled | Checked account balance and any open exception | That future installments will be paid |
Keep amount due, amount promised, amount received and remaining balance in distinct fields. A partial payment moves only the received amount; the open remainder still needs an owner and next review date. The payment tracker helps with those amounts; this ledger handles the promised-to-posted handoff.
The next-day exception pass
- Filter promises whose date has passed and that have no verified receipt.
- Check the payment source and accounting ledger before contacting anyone. Delays and unmatched receipts happen.
- If nothing is confirmed, assign the follow-up to one owner, record the next review date and write a neutral status note.
- If money was received but not posted, route the posting exception to the accounting owner. Do not mark it reconciled on the strength of a phone note.
- Once resolved, record the evidence and close the exception. Preserve the original promise and correction trail.
For a busy office, the list should show only exceptions, not every ordinary payment. A short daily pass over overdue promises is more useful than trying to remember which calls sounded urgent.
Handoff format
Account reference: A-104
Promise: $650 by September 25, per September 22 call
Receipt: not verified
Posting: not verified
Owner: office desk
Next action: check payment source on September 26, then update the same record
Write facts first. Do not label someone unwilling to pay, or imply a missed deadline before checking the source. For the phone side of this workflow, use the call log template; for audit-friendly corrections, see the documentation checklist.
This is an administrative recordkeeping example, not legal, collection, accounting or tax advice. Follow your organization's privacy and retention rules. All example details are fictional.
About the writer
Richard Cieplechowicz, also legally known as Ryszard Cieplechowicz, writes about property-office systems from more than 15 years of administration work. See the Ryszard Cieplechowicz name and identity reference.