Catch it before it posts, not during the audit. Most audit findings aren't fraud. They're a wrong account code, a missing signature, or a purchase that outran its budget. Small mistakes that take a minute to fix the day they happen, and months to untangle a year later.
The check runs where the work happens
Validation sits inside the entry screen, not in a report someone runs at month end. A clerk sees the problem while they still have the document in front of them.
Flagged, not blocked
The system does not refuse a transaction because a model found it unusual. It marks it, says why, and routes it to whoever is accountable for that call. The decision stays with your staff, and the decision is part of the record.
You can see how it decided
Rule-based checks state the rule they applied. Statistical checks state what they compared against. Nobody should have to defend a finding they cannot explain to an auditor.
Questions
Does the AI approve or reject transactions on its own?
No. It flags and explains; a person with the authority to decide still decides. The override is logged with the reason, which is usually what the auditor actually wants to see.
Are the AI features included in every plan?
They are included from iGAT Scale upward and available as an add-on below that. Inference is the one cost that genuinely varies with use, so it is priced separately rather than folded into the base fee.
Related information
01 / 04
Ask us about this
If you need these details in writing for a procurement file, tell us and we will respond.