Write down the handoff before a bill is urgent
Use this worksheet with your team. Approval authority comes from your business policy, not an arbitrary amount or this template.
| Responsibility | Decision to record | Cover arrangement |
|---|---|---|
| Collector | Where the document comes from and when it is expected | Name a backup collector |
| Reviewer | Account, period, amount, due date and unresolved issues | Name a reviewer with access to the document |
| Approver | Who is authorized for this obligation and scope | Agree delegated authority in advance |
| Evidence reviewer | Which receipt matches the recorded payment | Keep unresolved outcomes open for review |
Define the roles
Name the person who collects the bill, the person who checks its details, the authorised approver and the person who reviews payment evidence. In a small team one person may hold more than one role; explicitly identify where independent review is important for your risk and policy.
Decide who covers each role during absence. Authority must come from the business, not from whoever happens to have a copy of the invoice. Agree any amount thresholds internally rather than copying an arbitrary approval limit from a template.
Make a bill reviewable
Before sending a request, collect the supplier or service account, entity, location, period, amount, due date and document. Explain any adjustment or mismatch. The approver should be able to identify exactly what they are deciding on without searching another inbox.
If key details are missing, return the item for review with the reason. Do not use an approval as a shortcut for resolving an unclear billing period or disputed amount.
Record the decision and its scope
An approval should identify the exact bill period and the facts that were reviewed. Keep the decision maker, time and any conditions. If consequential details change, treat the changed facts as needing another review under your policy, not as automatically covered by an old message.
Illustrative example: an approver agrees to a September maintenance bill, then a replacement invoice changes the amount. Preserve the earlier decision in the history and bring the revised bill back into review. A green status alone cannot explain that change.
Keep execution and evidence separate
Payment approval is permission, not confirmation that a payment happened. After execution, collect the receipt or confirmation reference and match it to the right bill. Pending or uncertain outcomes should remain visible until they are resolved.
Do not retry a payment solely because a screen timed out. Use the provider’s appropriate status and support process to establish the outcome. This guide does not specify a particular payment integration or settle a bank transaction.
Run a short exception review
Focus the daily discussion on decisions that are stuck: missing documents, disputed details, absent approvers and recorded payments without matching receipts. For each item, record the next person, action and review time. Keep checked records accessible with their documents.
Review the process itself after a few cycles. Repeated approval delays may mean a decision is unclear, not that the team needs more reminders. Track elapsed handoff time from your own records before promising a productivity improvement.
Use the same policy when choosing a tool
Ask whether a tool preserves the bill, decision, owner and evidence together, and whether its actual permissions match your needs. Check capabilities in the working product rather than assuming a roadmap includes multi-stage routing or automatic payment release.
attenlo’s open beta supports manual review, responsible people, approval and payment-receipt checks by a person, not independent bank confirmation. Payments through Bharat Connect are in development. Try the open beta for free; sign in on attenlo.app to start.