Catch a bad payment before the run, or the morning after.
Sitampu Controls reads your books and every way money leaves, read-only. Each morning it lists yesterday's payments that need a look, and before each payment run it flags the ones to hold.
Every payment that left yesterday is checked. One needs you before the next run.
One list at 6:00 am, not a dashboard.
Each morning Controls checks every payment that left yesterday and says in one sentence what it checked. Anything that needs a person becomes a case, grouped by check, for someone you choose to judge.
- Only one thing interrupts: bank details changed with a payment pending, by push and SMS. Everything else waits for the morning.
- Where the data can't support a check, it says so. Nothing claims to have run when it didn't.
Works with how you actually pay.
Payment tools check only the payments they send. Controls matches every statement line to your books, so every channel gets the same checks.
- Bill pay
- Bill.com and Ramp, connected read-only
- Wires and ACH
- From bank statements, including payments sent from the bank's own portal
- Cheques
- From bank statements, matched to the cheques in your books
- Mobile money
- M-Pesa, MTN MoMo and Airtel Money statements, uploaded or forwarded
- Cards
- Ramp cards and card statements
It never moves or holds your money.
Every connection only reads. Controls tells you which payment to hold and where, in Bill.com or at your bank, and you hold it.
- No write access is asked of any provider
- No payments made, held, collected or refunded
Five checks on the batch before it goes.
Each payment run is checked before it's sent. You get a hold list, and you hold the payment where you pay.
- Bank details just changed
- A supplier added this week
- A payee who shares a staff member's account
- Fewer approvals than your rule needs
- A payment already made, by any channel
The 15 checks, in plain words.
On by default for every payment, every channel. Each says what it found and how often its flags were real.
Who is being paid
- Bank details changed in the last 90 days, with no call-back on record
- Paid within 7 days of the supplier being added
- Paid into an account payroll pays a member of staff
- Paid to someone who isn't on the supplier list
- The bank says the account's name isn't the payee's
- A supplier with no payments in the previous 12 months
How much
- Over 3 times the supplier's usual payment and over 5,000
- Same payee within 2 days, each under a limit, together over it
- Same payee, amount within 1%, within 30 days, by any channel
- Paid without an approved bill for at least the amount
Who approved it, and when
- Fewer approvals than the approval rule requires
- The person who entered the payment also approved it
- Released on a weekend, a public holiday, or between 22:00 and 05:00
Books, bank and cards
- Money left the bank with no ledger entry, or the ledger has a payment the bank doesn't
- A card purchase over the limit, or in a blocked category without a receipt
Add the checks only your business needs.
Describe one in plain words. It becomes conditions you can read, is tried on your last 12 months, and only then turns on. Matching runs in code, never in the model.
Nothing hides quietly.
Loosening a check or adding a quiet rule needs a second person. Quiet rules have an owner, a reason and an end date.
Hand your auditor a file they can rely on.
Every check, case, judgment and quiet rule, sealed with a verify link. Your auditor reads it, or re-runs it in Sitampu Audit from a read-only copy. They never get a seat in your Controls.
From a flag to a decision, on the record.
Today and cases
Flags become cases, grouped by check, each with the payment and what the check found. Someone you choose judges each one, with who and when on the record.
A statement inbox
Forward bank, card and mobile-money statements to your own Sitampu address. Each one is fingerprinted on arrival and matched to your books.
Advances Planned
Mark a payment to a member of staff as an advance. They account for it with receipts by link from their phone, and it is checked each morning until it is closed.
Questions finance teams ask first.
Can Controls move or hold our money?
No. Every connection is read-only. Controls tells you what to hold and where, and you hold it.
What if Controls misses something?
Controls monitors; it doesn't insure. The coverage page and every report show what was checked and what wasn't.
Where is our data?
In London, UK, encrypted at rest. Security and data
Do you work with mobile money?
Yes. Upload or forward M-Pesa, MTN MoMo and Airtel Money statements. Payees are matched by phone number against your suppliers and payroll.
Who judges a case?
Someone you choose, never the person the case is about. Every judgment is recorded with who made it and when.
Will it send alerts all day?
No. Only one thing interrupts: bank details changed with a payment pending, by push and SMS. Everything else waits for the morning list.
Can we add checks of our own?
Yes. Describe one in plain words. It becomes conditions you can read, is tried on your last 12 months, and only then turns on. Loosening or turning off a check needs a second person.
What doesn't Controls check?
Payroll runs, revenue and purchase orders. Where your data can't support a check, Controls says it's not available instead of claiming it ran.
See last year's payments checked, before you pay anything.
Read-only. No card.