Use case

Approval automation: expenses, time off, purchases and permissions that travel on their own

A guide for companies that lose hours in 'do you approve this?' email chains and want a clear, auditable and fast flow — without funneling everything onto one person.

Approval flow with audit log and WhatsApp notifications in Pilot

The problem

Every growing company runs into the same bottleneck: approvals. Team expenses, time-off requests, purchase orders, special customer discounts, permissions to release payments, authorizations to access sensitive information. What a 5-person company resolves over chat becomes a nightmare in a 40-person company.

The typical situation: someone sends an email asking for approval, the recipient is in a meeting, the requester asks again, the recipient forwards it to someone else because it's not their area, it gets lost in a chain of replies, and in the end nobody knows who approved what or when.

The traditional answers were complex BPM/workflow tools (Kissflow, Pipefy, Monday Forms) or approval modules of giant ERPs (SAP, Oracle). None work well for SMBs: they're either expensive, require consulting to set up, or don't integrate WhatsApp as a mobile approval channel.

How Pilot solves it

Approval automation — done right — combines (a) a configurable flow per request type, (b) notifications to the approver wherever they are (WhatsApp, email, app) and (c) a complete audit log of who approved what and when.

Three principles to get it right

  1. Define flows, not email chains. Each request type (expense, time off, purchase, discount) has its own flow: who approves, what amount requires what level, what happens if no one responds in X hours.
  2. Where the approver is, not where it's convenient for you. If the manager is on a job site all day, they get the approval over WhatsApp and decide it with one tap. Without opening a computer.
  3. Always an audit log. Who requested, who approved, at what moment, with what attachments. This becomes critical for compliance, internal review and external audit.

Step by step

  1. Identify the 5-10 most frequent approval flows in your company: team expenses, time off, purchase orders to suppliers, special discounts, access to sensitive information, payment release, hiring, advances.
  2. For each flow, define the levels by amount/criticality. E.g.: expenses up to US$200 = direct supervisor; up to US$1,000 = area manager; over US$1,000 = general management + CFO.
  3. Define automatic escalators: if the approver doesn't respond in X hours, it escalates to their backup. If no one responds in Y hours, it sends an alert to the director.
  4. Connect the flows to existing systems: expenses to the accounting/billing system; time off to the HR module; purchases to the ERP/Odoo; discounts to the CRM.
  5. Turn on multichannel notifications: the approver gets the request over WhatsApp (with Approve/Reject/Request info buttons), by email (with a link to the detail) or in the mobile app. They pick the channel they prefer.
  6. Set up auto-approvals for trivial cases: expenses under US$50 with valid justification, time off requested more than 30 days in advance with no conflict, recurring office purchases with a usual supplier.
  7. Implement an immutable audit log: every request is recorded with timestamp, requester, approver, attachments, comments. Exportable for external audit.
  8. Measure: average approval time (before vs after), % of approvals that escalated, expenses approved by category, bottlenecks by approver.

Expected outcomes

-70%Average approval time (days → hours)
100%Traceability for audit
+30%Team satisfaction with administrative processes
0Lost email chains

Frequently asked questions

Does it replace Kissflow, Pipefy, Monday Forms or SAP Workflow?
Pilot covers the standard SMB cases (expenses, time off, purchases, discounts, access) with fast setup and multichannel notifications. For hyper-complex BPM flows with hundreds of steps and deep business rules, tools like Kissflow have more depth. For 90% of LATAM SMBs, Pilot solves it.
Does it connect with my accounting system / ERP?
Yes. Native connectors with QuickBooks and Odoo. For other systems, integration via API or webhook. When an expense is approved in Pilot, it's posted to the accounting system. When a purchase is approved, it triggers the order in the ERP.
Does it handle multi-company with different policies per subsidiary?
Yes. Pilot has native multi-company. Each subsidiary can have its own approvers, amount limits and policies. The general director sees a consolidated view. Useful for business groups with several subsidiaries.
What about approvals that require attached documentation (invoice, receipt, quote)?
Yes. Each request can carry attachments (supplier invoice, quote, receipt, budget). The approver views them from WhatsApp or email without downloading them. They're archived with the request.
Does it work offline?
The approver can approve/reject without a connection from the Pilot mobile app; when signal is restored, the action syncs. WhatsApp notifications require the approver's connection, of course.
How long does it take to show results?
Reduced approval time: first week (the first activated flows are already faster than email). Broad adoption: month 1-2 depending on the cultural shift. Audit log benefits: visible from day 1.

How many hours a week do you spend chasing approvals by email?

Book a 30-minute demo. We'll show you how Pilot handles an expense approval flow: request → notification to the approver over WhatsApp → approval with one tap → integration into accounting — all traceable.

Request a demo