What Compliance Officer does
Compliance Officer is an autonomous feature of Pemo’s Control Agent. It keeps your card records complete by enforcing your submission policy on every transaction, without your finance team chasing anyone.
Most finance teams lose time at month-end tracking down missing receipts and empty expense fields. Gaps like these break your VAT trail and slow the close. Compliance Officer removes that manual work. When a transaction is missing a required receipt or field, it blocks the card automatically until the cardholder adds what is missing, then unblocks it the moment they comply.
How it works
Compliance Officer runs on the submission policy you set. Your policy defines what makes a transaction compliant, such as an attached receipt or a required field.
Once a policy is in place, the feature checks every transaction against it. If a transaction goes non-compliant, the cardholder’s card moves to a blocked state on its own. When the cardholder adds the missing receipt or field, the card unblocks automatically. No one on your finance team needs to step in.
Because it is autonomous, Compliance Officer acts with no human in the loop. Cardholders are warned before a block through Receipt Chaser, so a freeze is never a surprise.
Setting it up
Set your submission policy. Decide which receipts and fields a transaction must have to count as compliant.
[to confirm: exact path to the submission policy settings][to confirm: whether Compliance Officer is on automatically once a submission policy exists, or whether it has its own toggle and where it lives]That is it. Enforcement runs automatically from then on.
What your team sees
A cardholder who misses a required receipt or field receives a warning first. If the transaction stays non-compliant, their card is blocked. The block lifts automatically once they add what is missing. Admins do not need to unblock cards by hand.
The metric you’ll see
Non-compliant cards blocked shows how many cards the submission policy moved to a blocked state because they went non-compliant. Like every Pemo AI agent metric, it covers the previous 30 days at the organization level, not per user.
Before any card has been blocked, you will see this line instead of a number: “Set a submission policy and any card missing a receipt gets blocked automatically until it’s fixed.”
Two related figures describe your wider compliance posture. Compliant card % is your compliant active cards as a share of all active cards. Compliant transaction % is transactions with a receipt attached as a share of all transactions.
FAQ
Does the card stay blocked?
No. The block is temporary. The card unblocks automatically as soon as the cardholder adds the missing receipt or field.
Do I need to unblock cards myself?
No. Blocking and unblocking are both automatic.
Will a card be blocked without warning?
No. Cardholders receive a warning before a block, sent by Receipt Chaser.
What makes a transaction non-compliant?
A missing required receipt or a missing required field, based on the submission policy you set.
Which cards does it apply to?
Every active card covered by your submission policy.
What time period does the metric cover?
The previous 30 days, measured across your whole organization.