Set rules so Monta signs completed charges off for you — approve, review or reject — based on the verification outcome, amount, audience and open checks, with a replay to preview over past charges. Builds on Charge Verification.
Automatic sign-off lets you set rules so Monta decides completed charges for you — approve, send to review, or reject — instead of a person signing off every verified session by hand. You can also replay your settings over past charges to see what they would have done before you switch them on.
It builds on Charge Verification — if you're new to it, start with How does Charge Verification work?
Why use it
After each charge, verification runs a set of checks and produces an overall result. Most charges pass cleanly and only clog the sign-off queue. Automatic sign-off clears those routine cases so your team spends time on the sessions that actually need a human, keeping the queue a real worklist.
First, the verification outcomes
Every completed charge that is verified ends up with one overall outcome. Your automatic rules are built on these:
| Outcome | Meaning | Can it be auto-approved? |
|---|---|---|
| Verified | All checks passed. | Yes |
| Noted | Minor, information-only findings — nothing wrong, just worth recording. | Yes |
| Inconclusive | The checks ran but couldn't reach a conclusion — usually a missing input. | Yes (optional) — you choose whether to auto-approve these. |
| Flagged | Something needs a human to look at it. | Never — a person must decide. |
| Not run | The checks didn't run, so there's nothing to judge. | No — can't be used in any automatic rule. |
These are the same states you see on a session: Noted appears as Info, and Flagged appears as Warning or Critical depending on the most serious open finding.
The three automatic decisions
You configure up to three policies. Each is optional and works differently on purpose — approve clears noise broadly, reject is precise because it's an accusation, and review is deliberately easy to trigger because showing a human more is the safe direction.
| Policy | What it does | How you scope it |
|---|---|---|
| Auto-approve | Signs a charge off automatically. | Choose which outcomes qualify (typically Verified and Noted); set a maximum charge amount (the ceiling); choose the audience; and list checks that must not be open — if any of them is, the charge is left for a person. |
| Auto-review | Puts the charge in the review queue as a task for someone to look at. | Pick the checks that should trigger a review. If any listed check is open, the charge goes to review. |
| Auto-reject | Rejects the charge automatically. | Pick the specific checks that must all be open. Because a rejection is a strong call, it only fires on the exact combination you name. |
Scoping auto-approve
- Outcomes — which verification results are eligible. Flagged and Not-run can never be added.
- Amount ceiling — only auto-approve charges up to a value you set, so unusually large sessions still get a human. It's in your operator currency.
- Audience — apply the rule to charges on your own network (where you're the operator), to roaming charges, or to both.
- Don't-approve-while-open checks — a veto list. If any of these specific checks is still open on a charge, it won't be auto-approved even if everything else qualifies.
How the policies interact
When more than one policy could apply to the same charge, the most cautious decision wins: reject beats review beats approve. So a charge that qualifies for approval but also trips a review or a reject rule is never quietly approved — it's sent to review or rejected instead.
Safeguards
- Flagged charges are never auto-approved. A charge the checks flagged always needs a person — no setting can sign it off automatically.
- Nothing to check, no automatic decision. A charge whose checks didn't run isn't auto-approved or auto-reviewed.
- You can't save a policy that would decide nothing. Hub tells you exactly why, so a set-up can't silently do nothing.
- Already-decided charges are left alone. Automation only acts on charges that don't have a decision yet.
- Everything stays auditable. An automatic decision is recorded in the sign-off log the same way a manual one is, marked as automatic — so you can always see what decided a charge and why.
Try it before you turn it on (replay)
Before enabling automatic sign-off, use Replay. It runs your current (unsaved) settings over a window of past charges and shows how often the automatic decision would have disagreed with what a person actually decided — for example, how many charges it would have auto-approved that a human had sent to review.
- Nothing is changed — replay never touches a live charge; it's a preview only.
- A high disagreement rate is a signal to tighten a policy (lower the ceiling, add a veto check, or narrow the audience) before you enable it.
- Re-run it as you edit until you're comfortable.
Examples
| Goal | Set-up |
|---|---|
| Clear the everyday noise | Auto-approve Verified and Noted charges up to €50 on your own network, but not while the meter-signature check is open. |
| Keep an eye on big sessions | Same auto-approve, but leave the ceiling low so any charge above it still reaches a person. |
| Always look at a specific issue | Auto-review any charge where the "unusual consumption" check is open. |
| Reject a clear-cut bad case | Auto-reject charges where a specific set of checks are all open at once. |
Where to find it
In Hub, go to Charges → Verification and open Automatic sign-off from the header. You'll see the three policy cards and the replay. Changes are saved as one set when you save.
Frequently asked questions
Does turning this on affect past charges? No — automatic sign-off only acts on new charges going forward. Replay is the only thing that looks at past charges, and it just previews, it doesn't change them.
Can I use just one policy? Yes. Each of approve, review and reject is independent — enable only the ones you want.
What if a charge matches more than one rule? The most cautious outcome wins: reject, then review, then approve.
Will I still see automatic decisions? Yes — every automatic decision appears in the sign-off log, marked as automatic, so the audit trail is complete.
Availability
Automatic sign-off is being rolled out. If you don't see it yet, contact Monta support from your Hub.