No-coderequest forms
Leave, business trip, seal, IT access, or any form you design, with conditional questions and attachments.
Approvals beyond purchasing
One flow for every request
Build any request form without code and set the route once. Approvers act from email or chat, and every record stays searchable.
Request a demoManager → HRrouted by form and answer
The requester's manager by default, then department owners, Finance, HR, IT, or Legal when the form says so.
Email or chatto approve from
Approvers act from the notification, in their own language. Waiting requests get a reminder.
Features
Automation and controls at every step.
Any form, without code
Start from a leave or trip template, or a blank form. Questions can appear only when they apply.
Routes you configure
The requester's manager approves by default. Add steps by department, form or answer, such as Finance when a trip needs an advance.
Approve from email or chat
Approvers act where they already work, in their own language. Requests that wait too long get a reminder.
Use Cases
How finance teams use Acua day to day.
Leave that reaches HR already approved
The employee fills in one form, and the manager approves from chat. HR sees the approved list without chasing anyone.
Trips with an advance go to finance too
Ticking "advance needed" adds a Finance step by your rule. After the trip, AI reads the receipts and the claims link back to it.
Seal and contract requests, document attached
Attach the contract and route it to Legal before the director. The signed version stays on the request for the audit.
IT requests, out of the message threads
Access and equipment requests arrive on structured forms. IT works a queue instead of a thread.
Frequently Asked Questions
How is this different from a purchase request?
General requests have no vendor, amount, or line items and never turn into a purchase order or bill. They are for approvals that are not purchases: leave, trips, seals, access, contracts. Purchase requests live in Procurement with their own forms and routing.
Can routing depend on an amount, like a trip's estimated cost?
Yes, through a numeric question on the form. Add "Estimated cost" to the trip form and route requests over a threshold to the department owner or Finance. The value is a form answer, not a payment amount, so it never posts anywhere.
Which notification channels are supported?
Email and the major workplace chat apps, in the language set for your company. Approvers can act directly from the notification, and requests that wait too long get a reminder.
Who can create or change a form?
Administrators, in the form builder, without any programming. Forms are versioned: a request keeps the version it was submitted on, so changing a form later never alters past requests.
Can employees see their own request history?
Yes. Each employee sees their drafts, pending, approved, returned, and rejected requests with the current approver and the full approval history. Managers see their team's; admins see all.
Can we use it on the phone?
Yes. Requests can be submitted, tracked and approved from the mobile web app and from chat, with photos and files attached from the phone.
Every internal request, on one approval flow
Build a leave form in the demo. Watch it reach the right approver by email or chat.