Skip to main content

Compliance Officer

Compliance Officer is an autonomous feature of Pemo’s Control Agent. It keeps your card records complete by enforcing your submission policy on transactions from linked cards, without your finance team chasing anyone.

When a transaction is missing a required receipt or field, it blocks the card automatically. The card unblocks when the cardholder adds what is missing.

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 transactions from linked cards against it. If a transaction becomes non-compliant, Compliance Officer blocks the cardholder’s card automatically.

When the cardholder adds the missing receipt or field, the card unblocks automatically. No one on your finance team needs to step in.

Compliance Officer acts with no human in the loop. Cardholders are warned by Receipt Chaser before a compliance block, so this kind of block is never a surprise.

Setting it up

  1. Set your submission policy. In the Pemo web app, select More → Submission policies in the left sidebar. Decide which receipts and fields a transaction must have to count as compliant.

  2. Enable Compliance Officer.

Enforcement then runs automatically.

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 non-compliant cards Compliance Officer blocked.

Like every Pemo AI agent metric, it covers the previous 30 days. It is measured at the organization level, not per user.

Before any card has been blocked, the metric shows None yet instead of a number.

Two related figures describe your wider compliance posture:

  • Compliant cards is your compliant active cards as a share of all active cards.

  • Compliant transactions 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 compliance 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? A submission policy covers only the cards linked to it. Cards that are not linked to a policy fall back to the “Default card expenses policy”.

What time period does the metric cover? The previous 30 days, measured across your whole organization.

Did this answer your question?