Finance & insurance · case-study · Feb 2026
An ordinary SAP invoice-extraction step was quietly passing two PII fields to the model. Here's what an Inspector caught in Watch mode — at zero risk, nothing rewired.
A finance team automates invoice extraction: SAP hands a document to a model, the model returns structured line items, and the numbers flow on into the ledger. No one calls this "an AI project." It's just a step that got faster last quarter. That is exactly the kind of place AI actually lives in an enterprise — inside an ordinary workflow no one flagged for review.
Look closely at what leaves the building. In the raw invoice payload sit a supplier contact's Social Security number and a date of birth — fields no one intended to send to a model, travelling out with everything else. Nothing is obviously broken. The line items come back fine. But if an auditor asked "what personal data reached the model, and can you prove none of it left your tenant?" the honest answer today is a shrug.
Started in Watch mode, an Inspector sat in front of the same call and observed — touching nothing, changing nothing, just recording what it would have done:
Two PII fields it would have scrubbed before the model ever saw them. Dates it would have normalized. One policy mismatch it would have flagged for a human. All of it signed and on record, on the team's own stack — with nothing actually run. That's the whole idea of Watch: prove the value and see the exposure first, before you hand an Inspector any control.
Related