The method, wherever you run it

The auditor wants everyone who could approve a payment or post a journal as at year-end, every access change in the year and who made it, and each leaver’s last day beside the day their login closed. How to have that evidence ready before you are asked.

Approve and Reject on a push notification get payments out on time, and they can also approve a record that changed, be pressed by whoever holds an unlocked phone, or show an amount on a lock screen. How AWRA builds the button, and why the approver’s phone settings are part of the control.

One portal login per supplier means a password on a sticky note and a departed salesperson who can still sign in. Supplier contacts with their own rights, a list of where each is signed in, alerts on unusual sign-ins, and integration tokens that act as one person.

A client’s contract manager challenges the quarterly “98% within target” and asks for every ticket, every pause and proof nobody moved a priority. What the helpdesk records on its own, what nobody can quietly change, and how to build the evidence pack by Friday.

A framework agreement is negotiated once and then undone order by order: re-quoted, priced a little above the rate, or drawn past its ceiling. A call-off should start from the agreed price, count against the ceiling the moment it is raised, and still pass the same approval as any other quote.

On a desk ticket the requester will say if it is not fixed. On a field job they are only reachable while the engineer is still there, so the sign-off has to be taken then — once, on a finished ticket, refused rather than half-saved when the drawing fails, and withdrawn when the ticket is reopened.

Accepted is the least useful thing a supplier can say about a purchase order. What an acknowledgement has to carry — a promised date, and per line confirmed, partial, backordered or unavailable — and how shipment notices and a dispute thread keep both sides on one record.

The auditor signed off last year in March and asks in October how you know nothing has posted to it since. What a closed period refuses, why a reopening is the only door and what it writes down, and the four exhibits that answer the question before it is asked.

Approvals stall the week the one person who can sign is away, and the usual fixes — sharing a password or giving everyone the permission — each leave a record that says something untrue. What an honest hand-over has to say, how out-of-office cover works in approval chains, and where it deliberately stops.

The reporting tool needs to read and the supplier sync needs to write vendors. Why write access belongs in its own named scope rather than a checkbox on one all-purpose key, and why a key should never gain power when the product does.

An auditor tests an asset register in two directions: from the list to the floor to prove things exist, and from the floor to the list to prove nothing is missing from it. Then she asks how each disposal was authorised and what it fetched. What the record shows for each, what nobody can quietly rewrite, and how to prepare.

A supplier file proves compliance on the day of approval and says nothing about today. How supplier documents become a register with expiry dates, why a gap puts a supplier under review whatever its score, and why a contract should refuse a call-off while a required document is missing.