What is conformance checking?

The intended path is defined once — request, approve, receive, match, pay. Every case is then replayed against it. Cases that skipped a step, ran steps out of order, or added one appear as named deviations with a count and a value.

412 procure-to-pay cases replayed against the intended path.

A deviation is only interesting with a count and a value on it. '36% non-conformant' is a statistic; '₹6.1 Cr paid before receipt' is a control conversation.

A payment made before the goods receipt is not a process opinion, it is a control failure with an amount attached. Conformance turns policy into something that can be counted.

A high deviation rate is often a sign that the written process is wrong rather than that the people are. Before treating deviations as violations, check whether the majority path is the one the business actually intends.

Assuming the written process is the right one

A high deviation rate often means the documented path is out of date, not that people are ignoring it. Check whether the majority path is the one the business actually intends before calling anything a violation.

Defining the path too tightly

A model that allows only one order of steps reports hundreds of deviations that nobody considers wrong, and the real ones get lost in them.

Crestline replays every case against the path you define once, then reports deviations by type with a count, a value and the cases behind them, so a control failure can be opened and read rather than argued about.