Engagement acceptance simulator

An intake app wants to accept a sample engagement. VeriProof applies rules the firm set outside the app before work begins.

How the simulation works

The website proposes approval. VeriProof checks the rules.

  1. The website simulates the agent

    Every prepared scenario starts with the website acting as an AI agent and proposing approval.

  2. VeriProof enforces the business rules

    VeriProof checks the proposed approval against the rules prepared for this demo.

  3. The website applies the result

    VeriProof returns one of five outcomes: Allow, Warn, Transform, Escalate, or Deny. The website applies that outcome to the simulated action.

In a real integration, your application applies VeriProof's result before the proposed action proceeds.

  1. Choose what the agent approvesEvery prepared scenario starts with simulated agent approval
  2. See VeriProof's decisionPass, escalate, or stop based on the business rules

Choose a scenario

The engagement request

Each sample engagement ends differently. Pick one, or change the independence facts below.

Sample engagement
Corvella Systems, audit independence conflict
Engagement type
Financial statement audit
Client is a public company
Yes
Prohibited non-audit services are active
Yes
Client fee dependence
8% of office revenue
Change scenario details

The intake app proposes to accept this engagement.

An audit looks acceptable to the intake app. VeriProof stops acceptance because prohibited non-audit services are active.

Records created in this public demo can be seen by other visitors, so use the sample data rather than your own.

Configuration details

How this demo is set up

Review the application settings, rules, and evidence fields used in this simulator.

VeriProof setup

Industry
Professional Services
Application
Engagement Scoping Chat
Environment
Public demo workspace
Rule enforcement
Enforce: check firm rules before acceptance
Rule set
Independence, conflicts, fee-dependence, and partner safeguards

Related frameworks

Industry context: SEC auditor independence · IESBA fee-related independence

The intake app's own checks

The sample app checks client risk and conflicts before proposing an engagement.

  • Propose acceptance for low-risk clients with a clear conflicts check.
  • Send moderate-risk clients to the acceptance committee.
  • Refuse high-risk clients or engagements without conflicts clearance.

The firm rules VeriProof enforces

The firm sets these sample controls outside the intake app.

  • Stop a public-company audit when prohibited non-audit services are active.
  • Require partner review for moderate-risk engagements without sign-off.
  • Require independence review at 15% or more of office revenue.
Review the details saved with each run

When saving succeeds, the record links engagement facts to both decisions.

client_name / engagement_id

The sample reference used to find the acceptance record.

engagement_type / client_is_public_company

The engagement and issuer facts used by independence rules.

prohibited_nas_active / fee_dependency_pct

The active-service and fee-dependence facts.

client_risk_rating / conflicts_check_clear

The risk and conflict facts used by the intake app.

partner_signoff_present

Whether the required engagement partner signed off.

local_decision / governance_action / final_decision

The app decision, rule check, and actual outcome saved separately.