Every payment traces back to the limits the agency's people signed, and a caseworker confirms everything above the line.
For Agencies and e-government programmes, the processors that run payments for them, and the people who audit both.
An agency that lets software pay benefits has to answer a question a bank rarely asks: under whose authority did this payment go out? Today the answer is a policy document in one system and a payment batch in another. A person joins the two by checking a sample.
A study Cybernetica wrote for Estonia's Ministry of Justice and Digital Affairs recommends that E-ITS, the national security standard, require human confirmation for payouts (June 2026). A confirmation counts only if the record shows who gave it and under which limits.
Stategram makes that the default. The agency's people sign the limits and the agent pays inside them. Above the line, the caseworker the policy names confirms, and every payment traces back to the signatures it ran under.
The agency's people sign the limits, and every payment lists the version it ran under.
Payments above the threshold wait for the caseworker the policy names.
A move abroad or an open investigation stops the payment before it is made.
An auditor verifies any payment offline against the signed limits.
An example written for this page, with round numbers. It uses only what the policy format has today, and it is not a customer's policy.
Inside the rules the agent acts alone. Above a line, the named person decides. Every change to the numbers is a new signed version.
Two weeks, a fixed fee, your limits and a named approver, and the method to do the next workflow yourself.
We will email you to find a time for a 25-minute walkthrough with the founder. No slides, no sales script.
Pick a time in the founder's calendar, or tell us about your agent first.