To manage approved message templates, treat the library as something that is maintained rather than accumulated. Templates are easy to add and rarely reviewed. How template libraries degrade The same pattern as any uncurated set. * Near-duplicate templates for the same situation * Templates referring to processes that changed * Nobody sure
The WhatsApp 24-hour window is the period after a customer's message during which you can reply freely. Outside it, outbound contact requires an approved template. Why this shapes your process It is a constraint on timing, not on content. * A reply written the next morning may need
To move to a business WhatsApp number, plan the transition rather than announcing it. Customers keep using the number they already have, sometimes for months. What the move actually solves The problem is not the number. It is everything the personal one cannot do. * Service stopping when one person is
To start automating finance, begin at the point furthest from the accounting record. The request, not the entry, is where automation carries the least risk and removes the most work. Why finance automation feels risky The accounting system is the one nobody wants touched. * Fear that automation will affect the
To give each department its own finance view, scope the data by cost centre ownership. One panel then serves every department head, each seeing their own figures. Why departments are kept in the dark Finance data is usually all-or-nothing, so it defaults to nothing. * Department heads unaware of
To handle transactions between group companies, the operational record has to specify both entities. Groups that leave attribution to whoever is typing discover the errors at closing. Where multi-entity groups struggle Each company is correct in isolation and the group view is not. * The paying entity chosen inconsistently * Costs
To track spend against a project budget, every cost has to reference the project at the moment it is requested. Attributed afterwards, the figures are always approximate. Why budget overruns are found late Attribution happens at accounting rather than at request. * Costs allocated to projects retrospectively * Overruns discovered when invoices
To build a payment calendar, the dates have to come from approved requests rather than from a list someone maintains. A calendar updated by hand is a calendar that drifts. What a manual calendar misses It reflects what someone entered, not what was approved. * Approved payments not yet added to
Deciding how to handle expenses without a document is necessary because they exist. Refusing them entirely pushes the spend outside the process rather than eliminating it. Why a blanket rule fails The expenses happen anyway, and the record is what you lose. * Legitimate costs paid personally and never claimed * Receipts
To route approvals by expense category, you accept that not all spend of the same size carries the same risk. A threshold alone treats them identically. Why value alone is insufficient Two requests for the same amount can require very different scrutiny. * A routine supply order and a new supplier
To handle purchase orders before invoices, the commitment has to exist as a record before the document arrives. Otherwise the period between ordering and invoicing is invisible. What the gap hides Between the decision and the invoice, the commitment exists only informally. * Orders placed with no record until the invoice
To see committed spend, you track the moment of approval rather than the moment of payment. A commitment approved today affects cash weeks before it appears in any accounting view. What approval-level visibility adds The accounting system shows what exists; approval shows what is coming. * Entries visible only once