An approval is only as good as the person behind it. InvexForms asks approvers to confirm with Face ID or fingerprint on a trusted device, so a signature on a requisition proves who authorised it, not just who was logged in.
Trusted by 8,000+ users across leading organizations globally
Why it matters
Most approval fraud doesn't involve breaking into a system. It involves a shared password, an unlocked laptop, or a junior staffer "helping" a manager clear a backlog. The audit trail looks perfect, it just records the wrong human.
Biometric confirmation closes that gap. The approver's own face or fingerprint, on their own registered phone, is required before the approval is written to the record and their signature added to the document.
How it works
Biometric confirmation sits on top of your existing approval chains. Nothing about your workflows, thresholds or delegation rules changes.
The approver pairs their phone from Security settings by scanning a QR code and confirming with Face ID or fingerprint.
On web or mobile they open a request and choose Approve, Approve & Send, Approve & Close or Deny.
The trusted phone shows what's being approved, by whom and for how much. One tap with Face ID or fingerprint confirms it.
Only then is the approval written, with the device, method and timestamp recorded against the request.
Capabilities
Controls for the finance leads who set policy, and shortcuts for the approvers clearing sixteen requests before a board meeting.
Uses the biometric sensor already on the approver's phone. Devices without one fall back to the phone's passcode.
Each approver registers up to two phones. Devices can be renamed or revoked instantly, and a revoked device can't confirm anything.
Require confirmation only above a limit you set, so low-value items clear fast and material spend gets the extra check.
Confirmation requests expire after a short window. An unanswered prompt can never be confirmed later by someone else.
Every confirmation, decline and timeout is recorded against the request with device, method and time, exportable for audit.
Lost phone? One-time recovery codes and an admin bypass keep approvals moving without weakening the policy.
Privacy by design
InvexForms never sees, receives or stores biometric data. Enrolment creates a key pair inside the phone's own secure hardware; only the public half is registered against the account. A confirmation is a signature from that key, released by the phone once it recognises you.
For administrators
Turn biometric confirmation on for everyone, or only above a value that matters to your business. Track who has enrolled, and see declined confirmations as what they are, a security signal.
Administration → Approval security
Create requests, review submissions, approve workflows, upload supporting documents, and track progress directly from your mobile device.
Questions