Create the expected register first
List recurring obligations by business entity, location, provider or payee, service account and frequency. Add an expected document date separately from the payment due date. Those dates may be estimates initially; identify them as estimates and confirm them against an actual bill.
Give each expected bill a responsible person. Its recurring schedule describes what usually happens; the September bill records what happened this month. Do not overwrite August’s documents to make room for September.
Compare arrival with expectation
At a consistent review time, check which expected documents have been received. Mark a document missing only when it has not arrived according to your agreed expectation. Keep the due date and next follow-up visible even if no amount is known yet.
If someone cannot access a provider portal, record a source issue separately. The portal failure describes how you tried to obtain the bill; it does not prove that the obligation is missing, unpaid or settled.
Give each exception a concrete next action
A useful follow-up says ‘North office broadband bill expected on the 3rd; location manager to request the September document before the next review.’ A generic ‘please check bills’ message hides the owner, period and requested outcome.
If the usual owner is away, record who is covering the action. Use a manual escalation route agreed by the business. Do not quietly move the due date to remove an overdue warning.
Work through an example
Illustrative example: broadband is due on the 10th and the bill normally arrives on the 3rd. On the 5th there is still no document. The location manager is asked to retrieve it. On the 6th it arrives with an unfamiliar adjustment. The missing-document issue is resolved, but the adjustment now needs review.
After the bill is approved, someone reports paying it outside your system. Keep it as ‘payment recorded: needs checking’ until the matching receipt is checked. That human check is not bank confirmation. A single ‘pending/done’ column would lose three different problems in this sequence.
What to record at each check
Keep the bill period, expected date, actual arrival, due date, responsible person, reason for follow-up, next action and next review date. When a document arrives, link it to the right bill period. Record what changed and who changed it rather than relying on the latest message in a chat.
Review the process weekly: which bills repeatedly arrive late, which people need clearer handoffs and which expected dates were wrong? Change the future schedule deliberately; preserve the history of past bills.
Where attenlo fits
attenlo’s test pilot keeps expected bills, received documents, problems collecting a bill, approvals and checked payment records distinct. It provides a shared workflow for the same discipline described here. It is owner-private and synthetic-data-only; no automatic bill-provider fetch or payment execution is connected.
You can use the free checklist to improve your current process now, or request a private-beta invitation to discuss a future guided start. The checklist is an operating aid, not a complete compliance or accounting schedule.