Validation pilot
The 14-day validation pilot
One vendor disbursement workflow. One threshold. One approver group. Fourteen days of recorded decisions and gateway-signed receipts your Internal Audit team can test. Execution runs in dry-run mode, so no money moves.
Success is your Internal Audit team confirming the artifact is sufficient. Not a purchase order.
Scope
Deliberately narrow
A pilot that tries to prove everything proves nothing. This one validates a single control end to end.
One workflow
A single vendor disbursement workflow: the one your AP automation or agents already run.
One threshold
A single dollar threshold above which every payment waits for human approval.
One approver group
A single group of authorized approvers, matching the delegation of authority you already maintain.
What we install
- A gateway in front of your disbursement workflow. Payments you route through it are checked against policy, and those over your threshold wait for a human passkey approval of the mission's limits.
- No replacement of your AP platform. Your automation keeps proposing payments exactly as it does today.
- Dry run only. Execution runs in dry-run mode, so no money moves: Yebo issues signed dry-run receipts. Live vendor payouts through Stripe Connect are coming soon.
What you get
- 14 days of recorded decisions and signed dry-run receipts from your real workflow.
- An evidence export formatted for control testing: one signed artifact per authorized payment, re-verifiable offline with the open-source npm verifier, npx yebo-verify@0.2.0.
- A walkthrough script your Internal Audit team can run themselves, including the open-source npm verifier (npx yebo-verify@0.2.0).
What we need from you
- A threshold (for example: $10,000).
- An approver (or a small approver group).
- A sandbox environment for your disbursement workflow.
Day 14
How the pilot ends
Your Internal Audit team samples the pilot's mandates, re-verifies them with the open-source npm verifier yebo-verify 0.2.0, and matches approvers to the delegation of authority. If they confirm the artifact is sufficient for testing the control, the pilot succeeded. If not, you tell us why: that answer is worth more to us than a sale.
You can preview the verification procedure right now, with a device-signed sample payment approval (artifact version 2.0), checked with yebo-verify 0.2.0, on the verification page. No account required.
Fourteen days. One workflow.
If you're 12-24 months from an IPO or in your first SOX cycle, and your AP platform or agents already initiate vendor payments, this is the fastest way to find out whether the evidence holds up.