Approved by your rules, then executed.
Past the limits you set, no one person moves your company's money. Approval rules decide who signs, by what a payment does and how much it moves. Execution is a second gate, on the account it leaves from.
Who has to sign this?
The engine answers it for every payment, before anyone can send it. Pick what the money does, drag the amount, and choose the account it leaves from.
Try it Change the payment type, drag the amount, switch the account.
$25,000 to $250,000
- FinanceAny one person in this roleWaiting
- Finance or AdminSomeone who has not approved yetWaiting
Universal Account
- AdminFirst signatureWaiting
- Admin or FinanceSecond signatureWaiting
Signed in Mezzanine. Universal Accounts are provided by 1Money USA, Inc.
Before it can leave: 2 approvals from 2 different people. Then 2 signatures on the Universal Account.
An example policy. Out of the box every tier needs one approval from an Admin or Owner; set your own tiers, limits and approvers.
Past your limits, nobody acts alone
Fraud and costly mistakes get through when one person can act alone. Good internal controls make sure nobody can. Creating, approving and executing are separate steps, and each approval needs a different person.
- Step 1
Create
Anyone you allow to raise payments
Raises the payment with its invoice or contract attached. Raising it releases nothing.
- Step 2
Approve
Finance and Admin, by amount
Each approval needs a different person. The bigger the payment, the more names it needs.
- Step 3
Execute
The account's own signers
Two signatures on a Universal Account, your Safe's threshold, or a person at your bank.
What it protects you from
-
Fraud
A forged invoice, a spoofed request, or a business email compromise (the “our bank details have changed” email) has to convince more than one person before money moves.
-
Mistakes
A wrong amount or the wrong recipient gets a second look while it can still be fixed, not after it has left.
-
Insider risk
Past the thresholds you set, nobody releases a payment alone. Not a new hire, and not the founder.
Rules that hold
-
A different person per slot
Each approval slot needs someone who has not already signed. Nobody approves the same payment twice.
-
One rejection stops it
A single rejection ends the chain. The payment never reaches execution.
-
Off-site execution is tracked
When a payment is sent from a bank or an exchange, someone marks it done or marks it failed, so the record matches what happened.
Not ready to reject it? Flag it. Anyone reviewing a payment can raise a flag with a comment, at any stage. The flag stays on the payment, and a reviewer cannot clear a concern someone else raised.
An audit trail on every payment
Every payment carries its own audit trail: who raised it, who approved it and when, who signed it, and when it settled. Five people touched this compensation run, and each one is on the record.
- Created in Compensation by Elena Park
- Approved, 2 of 2 by Jordan Chu, then Nadia Osei, on different days
- Signed, 2 of 2 by Owen Reyes and Tomas Lindqvist, each with a timestamp: ready to send
- Settled recorded when the payment lands
Changes to the rules themselves are recorded too, in the activity log.
