Raising and certifying IPCs

Multi-stage approvals, anomaly detection, per-line signoff.

An Interim Payment Certificate is the central money document on a civil project — Aayu treats it as a first-class workflow, not a flat invoice.

Lifecycle

DRAFT — created via Raise IPC, editable, no approvals.
SUBMITTED — submit kicks off the approval chain (sized by amount).
CERTIFIED — chain cleared; client / consultant signed off.
PAID — payment received from client (manual flag).

Approval thresholds

Every IPC under ₹1 Cr certifies on the certifier's click. ₹1–5 Cr goes through a sequential PM → Finance chain. ≥ ₹5 Cr goes through a parallel PM + Finance dual-control with a 24-hour ADMIN escalation.

Anomaly detection

On submit, every IPC line is scored against the org's historical samples for the same BOQ item (≥3 samples needed). Anything ≥ 3σ from the mean is flagged high-severity; ≥ 2σ is medium. Any high-severity anomaly prepends an ADMIN review stage, regardless of value tier — even a sub-₹1Cr IPC with one bad cost line gets the eyeball gate.

Per-line signoff

Open the line-items table on a SUBMITTED IPC and you'll see Sign / Flag buttons per row. The IPC cannot transition to CERTIFIED until every line has either a SIGNED_OFF row or zero FLAGGED rows. One flagged line is enough to block the whole bill — explicit dissent always wins.

The line table also pre-selects outstanding qty on Record GRN, so a “single drop closes the PO” workflow is one click.

Anything missing here? Email support — include the URL and your firm name.