Map the service, not just the branch
Start with the business entity, location, provider, service account, frequency and expected document date. A branch can have several accounts with the same provider. One row labelled ‘electricity, East’ may hide a second connection or a shared-premises charge.
Keep an active list of locations and explain changes. If a branch closes, identify which obligations need a final bill, cancellation or evidence review. Removing the location from a dashboard does not cancel its contracts or prove the balance is settled.
Agree what moves from branch to finance
The local collector supplies the document and identifies the relevant account and period. A reviewer checks its details and flags disputes. An authorised approver makes the decision. After payment outside the register, the evidence reviewer checks the matching proof. Name each person and a cover arrangement.
A handoff should contain the bill period, document, reviewed amount, due date, unresolved issue and requested action. ‘Sent to accounts’ is a destination, not an accountable next step. Record the recipient and when the item should next be reviewed.
Use a branch review that asks different questions
Illustrative example: East has a bill awaiting approval, West is missing its broadband document, and North has reported payment without a receipt. East needs a decision, West needs collection and North needs evidence. A single count of three pending bills would conceal the work.
Filter by location and exception, then agree the next person and action. Keep the original due date visible when an internal review date changes. If nobody can establish a payment outcome, preserve that uncertainty rather than asking a branch to pay again.
Test a handover before scaling the register
Choose two locations with different operating arrangements. Ask the usual collector to explain one bill period, then ask their cover to find the same bill, decision and receipt without help. Note which facts are missing from the record rather than assuming a training problem.
Keep the first review small enough to correct account mappings and responsibility. Preserve completed periods; create a new bill record for the next cycle. Compare the central list with local knowledge so an absent row is not mistaken for nothing being due.
What a shared tool should preserve
Check that location permissions are enforced, historical decisions remain available and evidence can be retrieved with the right record. Your business still needs to define authority and investigate exceptions; software cannot establish these from a branch name alone.
attenlo’s owner-private synthetic pilot keeps bills linked to locations, with responsible people, manual review, approvals and payment-receipt checks. Those human checks are not independent bank confirmation. No live provider fetch or payment execution is connected. Use this process in your current register now; request an invitation to discuss fit, not automatic customer admission.