"OK, pay it." A message from the manager in the purchasing group, and the purchase order was executed. Three months later accounting asks: who approved this steel order? For how much? The answer requires digging through a hundred messages. This article is about turning approval from a message into a clear chain — without slowing the work down.
WhatsApp costs more than you think
Approving on WhatsApp is fast, and that is its only advantage. The problems show up later:
- No reference. The approval of an order worth SAR 40,000 sits in a message among messages about lunch. When you need it, you will not find it easily.
- Approval of what exactly? Was "OK" for the first version of the order or after the price changed? Nobody knows.
- No order. The purchasing manager is supposed to review first, then the finance manager. In practice, whoever replied first counted.
- Execution is not tied to approval. The store may receive and accounting may pay before the approval is complete — because nothing prevents it.
- The printed document is blank. The purchase order that goes to the supplier carries no signature, no name and no approval date.
The approval chain: just three decisions
An approval chain is not complicated. For every document type (purchase order, payment request, manual entry) you decide three things:
- Who signs? People by name or by role (purchasing manager, finance manager, general manager).
- In what order? One after the other. The finance manager does not see the document until the purchasing manager has signed.
- What happens after the last signature? The document executes: the purchase order goes to the supplier, the payment request becomes a voucher, the entry is posted to the ledger.
And three rules that make the chain actually work:
- Rejection closes the document. Not "send it back and see".
- "Return for revision" sends it back as a draft to its author, and when it is edited the chain starts over — because what was changed needs a new approval.
- Any change to lines or price after approval = a change order, not an edit to the approved document.
Example: a steel purchase order
| Step | Who | What they do |
|---|---|---|
| 1 | Purchasing officer | Creates the purchase order from the material request that came from site, with the remaining quantities and the supplier's prices |
| 2 | Purchasing manager | Reviews the supplier and the price, and signs from the phone |
| 3 | Finance manager | Sees the order's effect on cash, and signs or returns for revision |
| 4 | The system | The order becomes "approved": a PDF with signatures goes to the supplier, the store can receive against it, and accounting can create a payment request linked to it |
Note that step 4 is the real difference: execution is tied to approval. No receiving and no payment against an unapproved order.
E-signature: not a picture of a signature
E-signature here means the person logged in with their own account, saw the document in this exact version, and pressed "approve" — and the system recorded their name, the date and the time on the document so that nobody can change them. When the document is printed, the signature, name and approval date appear on it. That is stronger than a signature image pasted onto a PDF.
How not to slow the work down
- Push notifications. When it is your turn you get a notification and sign from wherever you are in a second. Approval does not wait for someone to open a laptop.
- One inbox. Everything waiting for your signature in one place, not spread across groups.
- A short chain for small amounts. A small purchase order's chain can be one person, or empty so it goes straight through. Large ones go through all three.
- A substitute when someone travels. A defined override or delegation permission, recorded when used.
In short
WhatsApp stays for conversation. But approval must live somewhere that knows who approved what exactly and when, and ties execution to the approval. A chain of three decisions and three rules is enough to turn "OK, pay it" into an approved, signed document — without slowing the work down.