ENTERPRISE RESOURCE PLANNING
Procure-to-pay that proves who approved what
ERP systems hold the keys to a company's money: supplier master data, purchase orders and the payouts that follow. UniKey puts a signed, per-action authorization in front of each step, so the system acts on proof rather than on whoever holds a login.
THE PROBLEM TODAY
Credentials stand in for permission
Supplier master data
Changing a supplier's bank account is one form away from redirecting every future payout.
Approvals on trust
An approval is a click in a session. If the session is stolen, so is the approval.
Audit after the fact
Reconstructing who authorized a payment means stitching logs together, long after the money left.
WITH UNIKEY
Actions that carry a Trust Packet
Each one is signed by the party with the authority to take it, and verified before it executes.
-
Place an order
Orders placed through the API carry a Trust Packet from the buyer, verified before the order is created.
-
Verify a bank change
The supplier confirms a new bank account from its own portal, by email or from its device, before it is used.
-
Issue a refund
Refunds are composed and confirmed on their own screen and bound to the order they reverse.
-
Release a payout
Payouts go to the account the supplier authorized, with an Authorization Certificate as the record.
{
"action": "update_supplier_bank",
"subject": "accounts@wilson-supply.com",
"signer": "wilson-supply.com",
"audience": "erp@uusa-demo.com",
"params": {
"supplier_id": 42,
"routing_number": "021000021",
"account_type": "checking"
},
"expires_at": "2026-10-05T14:05:00Z"
}
Illustrative. The verifier looks up the signer's public key in DNS, checks the Ed25519 signature, refuses a packet it has seen before or one past its expiry, and only then lets the action run.
DEMO VIDEOS
Watch it work
UDA ERP runs a storefront, sales and procure-to-pay. The recordings show a supplier's bank change requested by email and held until it is verified, with a Trust Packet for each step.
MORE INDUSTRIES