Signed for Enterprise
Your agents prepare the run. The right people sign it.
When your AI agents prepare payment runs in your accounting software, anything outside your mandate waits for the right people to sign the exact payee, account and amount on their own phones. You keep the proof.
An agent is not an approver.
AI agents now prepare payments inside finance software. They work fast, and they act on whatever they’re given, including a fake invoice or an email saying a vendor changed banks.
Most controls ask one question: did a signed-in user send this? An agent working under someone’s login passes every time.
Signed asks a better one: did the required people approve these exact details, on their own phones?
How a payment gets through.
The gate sits in your accounting software, where your agents prepare payment runs. Your bank still sends the money.
- 01
Prepare
Your AI agent prepares the payment run in your accounting software.
- 02
Check
The run is checked against the mandate finance signed. Anything inside it moves on. Anything outside it waits.
- 03
Sign
Each required approver gets a notification, sees the payee, account and amount, and signs on their own phone. Change any of them and the signatures reset.
- 04
Release
With the agent’s key and every required signature in place, the run goes to your bank, which sends the payment.
- 05
Record
Every check and signature is written to a tamper-evident record.
Step through a held payment
Simulation only. No real keys, phones or payments.
Waiting in your accounting system. Nothing has gone to the bank.
Accounting system
Vendor payment run
Business checking
- Payee
- Acme Industrial Supply
- Account
- Ending 4821
- Amount
- $48,250.00
Rule: Two signatures for payments over $25,000
Approver 1: John Doe, Controller
Not signed
Approver 2: Jane Doe, Chief financial officer
Not signed
John Doe
- Payee
- Acme Industrial Supply
- Account
- Ending 4821
- Amount
- $48,250.00
Tap to sign
Evidence record
- 9:58 AMRun prepared: $48,250.00 to Acme Industrial Supply, account ending 4821.
- 9:58 AMHeld by rule: two signatures over $25,000. 0 of 2 in.
Read this demo as text
- Start: the $48,250.00 payment to Acme Industrial Supply, account ending 4821, is held at 0 of 2 signatures.
- After John Doe signs: still held at 1 of 2. One person can’t release it. The CFO, Jane Doe, is next.
- After Jane Doe signs: every required signature is in, and the run is ready for the bank. Your bank still sends the money.
- If the amount changes to $49,000.00: every signature stops counting, because each covered $48,250.00. The run is held again at 0 of 2.
- Start over returns the demo to the beginning.
Decide who signs what.
Finance signs the mandate. Signed applies it to every payment your agents prepare.
WhenA payment is over your threshold, such as $25,000
Who signsTwo approvers
Why it worksNo one person can release a large payment alone.
WhenA request names an executive, like “the CFO asked for this”
Who signsThat executive, on their own phone
Why it worksA fake request fails when the real executive never made it.
WhenThe payee is new, or its bank details changed
Who signsAn extra approver, then a waiting period
Why it worksSlows the payment so someone can verify the change outside email.
WhenA payment is under the threshold
Who signsOne approver, within a low limit
Why it worksCaps what one fooled approver can release alone.
WhenA routine run of known payees, each under the threshold
Who signsNo one. It goes through inside the mandate
Why it worksYour team only sees what needs them. New payees and large items still wait.
Know who signed what, and prove it.
Every decision adds an entry to a tamper-evident record: who signed, what they saw, when, on which phone and under which rule. Export it for your auditor, your bank or your insurer.
- Tamper-evident
- Any change to the record shows. It doesn’t mean the record can’t be changed or deleted.
Evidence record
Run 0142 · Business checking
- Payee
- Acme Industrial Supply
- Account
- Ending 4821
- Amount
- $48,250.00
- Rule
- Two signatures over $25,000
- 1
John Doe, Controller
Enrolled phone C01 · 10:02 AM
Signed the payee, account and amount above
- 2
Jane Doe, Chief financial officer
Enrolled phone F02 · 10:07 AM
Signed the payee, account and amount above
All signatures in at 10:07 AM. Released to the bank.
Bank match: checked against the bank’s record after payment.
Illustration. No real keys, phones or payments.
Built for the bad day.
IfAn approver is out
What Signed doesEach rule can name a pool, like any two of four. Payments keep moving.
IfThe cloud goes down
What Signed doesOur own data center backs up the cloud, so Signed keeps running. If both are ever down, the gate is designed to stay closed. Downtime doesn’t approve a payment.
IfAn admin tries to switch the gate off
What Signed doesSwitching off needs the same signatures as a payment, and it’s recorded.
IfAn agent’s key doesn’t match
What Signed doesThe run stays held. Nothing reaches the bank, and the attempt is recorded.
Know exactly where the gate ends.
The gate covers only payments that start in your connected accounting system. Here is what it stops, what it slows and what it can’t.
Bank matching flags it after payment. It doesn’t prevent it.
Fake executive request
Stopped, when your rules require itThe real executive has to sign on their own phone.
Fake vendor bank change
Slowed, not stoppedAn extra approver and a waiting period apply.
Stolen approver password
StoppedThe attacker doesn’t have the approver’s phone.
Details changed after signing
Stopped before releaseEvery earlier signature is void and the run is held again.
Every required approver is fooled, or two insiders collude
Not stoppedThe record names everyone who signed.
A wire typed straight into the bank’s website
Outside the gate at launchIt goes around the gate. Bank matching flags it afterward.
Bring AI into your accounts payable workflow without giving up the pen.
We’re shaping Signed with a small group of finance teams. If AI agents prepare your payments today, or will soon, let’s talk.