Industry Vocabulary Reference
Professional Services & Management Consulting
Comprehensive enumeration library for the Professional Services & Management Consulting vertical. Covers every subdomain where agentic AI is actively deployed in professional services firms as of March 2026: audit and assurance documentation (GAAS / PCAOB / AICPA / ISA), engagement lifecycle management (scoping, staffing, quality control, independence verification), enterprise and cyber risk assessment (COSO ERM / ISO 31000 / FAIR), regulatory advisory (EU AI Act, SOC 2, ISO 27001, NIS2 / DORA), management consulting (process redesign, M&A advisory, IT advisory), and tax compliance and advisory. Designed for use as OTel span attributes in an agentic AI SDK and as policy vocabulary in an OPA Rego GRC portal, with specific coverage of the three canonical AI applications deployed in professional services governance programmes: Audit Workpaper Assistant, Engagement Scoping Bot, and Risk Assessment Coordinator.
Back to industry coverage library
This page shows selected examples and categories. Download the JSON for the complete vocabulary, including every field, permitted value, and policy pattern in this catalog.
How to use this reference
- Start with the core file if you need the cross-industry governance baseline.
- Choose an industry file for its workflow fields and permitted values.
- Match the OTel attributes to the policy paths your rules use, then verify the recorded fields in a test session.
Catalog context
As of March 2026, agentic AI in professional services is deployed across: AI-assisted audit workpaper generation for GAAS/PCAOB engagements (revenue recognition, lease accounting, goodwill impairment, ICFR testing), engagement lifecycle management (scope definition, staffing, fee estimation, independence checking, proposal generation), enterprise and cyber risk assessment and board reporting (COSO ERM, FAIR model quantification, regulatory change impact), tax provision and uncertain tax position analysis (ASC 740, IRS Circular 230), M&A due diligence and quality of earnings (QoE) analysis, IT advisory and ERP migration scoping, ESG assurance and sustainability reporting (ISAE 3000, CSRD), and regulatory advisory under the EU AI Act and NIS2. The EU AI Act is a significant revenue opportunity for professional services firms that advise high-risk AI providers on Article 9 risk management systems, Article 17 quality management systems, and Article 43 conformity assessment. AI governance consulting is the fastest-growing advisory segment in the professional services market as of early 2026.
Risk note: PCAOB AS 2201 (ICFR audit) requires auditors to evaluate the design and operating effectiveness of controls over financial reporting, which now includes AI systems generating journal entries, valuations, or financial estimates. PCAOB Staff Spotlight: Use of Emerging Technology by Audit Firms (2023) specifically addresses the use of AI in audit, firms must document AI-assisted procedures and maintain appropriate quality controls. AU-C 240 fraud risk procedures apply when AI analytics flag anomalous journal entries; the auditor cannot delegate the fraud risk assessment conclusion to the AI system. SOC 2 Type II examinations of AI-assisted service organisations must specifically address the AI system's change management, access controls, and output integrity as part of the Trust Services Criteria. EU AI Act Annex III high-risk categories may capture AI used in professional services if the system influences access to essential services or makes decisions with legal or similarly significant effects on natural persons, advisory opinions that are delivered to clients through AI merit legal review against Article 6 and Annex III criteria.
Vocabulary file
- Download filename: 13_vertical_professional_services_consulting.json
- Kind: vertical
OTel namespaces
Referenced standards
These references explain the catalog's context. A listed standard does not establish that a configured application meets its requirements.
- AICPA AU-C Sections, Generally Accepted Auditing Standards (GAAS) for non-issuers (US)
- PCAOB Auditing Standards (AS), Auditing standards for SEC registrants and PCAOB-registered firms
- IAASB ISA (International Standards on Auditing), Global audit standards for non-US jurisdictions
- AICPA Code of Professional Conduct, Ethics and independence standards
- FASB Accounting Standards Codification (ASC), US GAAP authority
- ASC 606, Revenue from Contracts with Customers (IFRS 15 equivalent)
- ASC 842, Leases (IFRS 16 equivalent)
- ASC 350-40 / 350-20, Goodwill and Intangible Assets (impairment testing)
- ASC 330, Inventory (lower of cost or net realisable value)
- ASC 820, Fair Value Measurement
- ASC 740, Income Taxes (tax provision, uncertain tax positions)
- ASC 810, Consolidation (related-party and VIE considerations)
- PCAOB AS 2101, Audit Planning
- PCAOB AS 2110, Identifying and Assessing Risks of Material Misstatement
- PCAOB AS 2201, An Audit of Internal Control Over Financial Reporting (ICFR / SOX 404b)
- PCAOB AS 2310, The Confirmation Process
- PCAOB AS 2401 / AU-C 240, Consideration of Fraud in a Financial Statement Audit
- PCAOB AS 2501, Auditing Accounting Estimates
- PCAOB AS 2541, Auditing Inventories
- PCAOB AS 2601, Consideration of an Entity's Use of a Service Organization
- PCAOB AS 2810, Evaluating Audit Results
- PCAOB AS 3101, The Auditor's Report on an Audit of Financial Statements
- AICPA SSAE 18 / AT-C 205, Attestation Standards; SOC 2 examination framework
- ISAE 3000 (Revised), Assurance Engagements Other than Audits or Reviews of Financial Information
- ISAE 3402, Assurance Reports on Controls at a Service Organisation (equivalent to SSAE 18 SOC 1)
- COSO Internal Control, Integrated Framework (2013), Internal controls assessment reference
- COSO ERM 2017, Enterprise Risk Management, Integrating with Strategy and Performance
- ISO 31000:2018, Risk Management Guidelines
- ISO 31010:2019, Risk Assessment Techniques
- FAIR (Factor Analysis of Information Risk), Cyber risk quantification model
- AICPA / CIMA, Chartered Global Management Accountant (CGMA) competency framework for advisory
- IRS Circular 230, Regulations Governing Practice Before the IRS (tax advisory)
- OECD Model Tax Convention, Transfer pricing and international tax advisory
- EU AI Act (2024/1689), AI used in audit opinion generation, regulatory filings, and advisory
- SOC 2 Type II (AICPA TSC 2017), Trust Services Criteria for AI-assisted service organisations
- ISO/IEC 27001:2022, Information Security Management System
- NIS2 Directive (EU) 2022/2555, Network and Information Systems security for PS firms
- DORA (EU) 2022/2554, Digital Operational Resilience Act (applicable to PS firms servicing financial entities)
- GDPR (EU) 2016/679, Client data handling and AI-assisted processing in advisory workflows
- PCAOB Cybersecurity Risk and Internal Controls, Emerging guidance on audit of AI systems
Source references
- https://pcaobus.org/Standards/Auditing
- https://www.aicpa-cima.com/resources/landing/professional-standards
- https://fasb.org/standards
- https://www.ifac.org/knowledge-gateway/audit-assurance/publications/2009/03/clarified-international-standards-auditing
- https://www.pcicomplianceguide.org/
- https://www.riskmanagementinsight.com/media/docs/FAIR_introduction.pdf
- https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32024R1689
Subdomains
| Subdomain | Categories | Sample attributes |
|---|---|---|
| Audit & Assurance Workpaper Management | 5 | ps.workpaper.type, ps.audit.phase, ps.audit.staff_level |
| Engagement Lifecycle Management | 4 | ps.engagement.service_line, ps.engagement.scoping_phase, ps.engagement.complexity_tier |
| Enterprise & Cyber Risk Assessment | 4 | ps.risk.domain, ps.risk.committee_decision, ps.risk.fair_component |
| Advisory Quality and Professional Standards | 2 | ps.advisory.quality_outcome, ps.advisory.liability_risk |
Implementation examples
- Audit & Assurance Workpaper Management: Workpaper Type. Audit Workpaper Assistant tags each session with the workpaper type. OPA policy enforces that fraud_risk_assessment and icfr_deficiency_evaluation workpapers may not be filed without a partner-level sign-off HITL step. Revenue recognition and going_concern_assessment workpapers for SEC registrants require an additional QC review gate per PCAOB AS 2810. (Pcaob As 2101: PCAOB AS 2101, Audit planning must identify key risk areas that must be addressed in the workpaper file)
- Audit & Assurance Workpaper Management: Audit Phase. Audit Workpaper Assistant tags each session with the current audit phase. Policy rules gate certain AI actions by phase, for example, AI may not generate a final opinion draft during the fieldwork phase, and may not add new significant risk factors to the register during the completion phase without escalation. (Pcaob As 2101: PCAOB AS 2101, Audit planning phase must be completed and approved by the engagement partner before fieldwork commences)
- Audit & Assurance Workpaper Management: Audit Staff Level. AI policy evaluation sign-off authority. Sessions initiated by a staff_associate or senior_associate flag any AI-generated significant estimate conclusion as 'pending manager review'. Fraud risk conclusions and going-concern adverse assessments require engagement_partner or concurring_reviewer sign-off before filing. (Pcaob As 2101: PCAOB AS 2101, Engagement partner must plan the nature, timing, and extent of supervision before fieldwork begins)
- Audit & Assurance Workpaper Management: Workpaper Qc Gate. Audit Workpaper Assistant transitions the workpaper through QC gates automatically, emitting an OTel span at each state transition. OPA policy blocks the filed_to_engagement_file state unless partner_signoff_complete is recorded for significant judgment areas. The QC gate state is used in compliance posture dashboards to show what percentage of AI-assisted workpapers have completed the full QC chain. (Pcaob As 2810: PCAOB AS 2810, Evaluating Audit Results requires engagement partner assessment; AI conclusions require partner_review_required gate before filing)
Enforce before the action
Pass the request and your business action to this function. The core SDK checks policy before the action runs and again before its result is released. A deny or review decision means the action never runs.
import { Veriproof } from '@veriproof/sdk-core';
import type { GovernedResult, IndustryFact, JsonValue } from '@veriproof/sdk-core';
const veriproof = Veriproof.fromEnv();
export async function runProtectedAction<TInput extends JsonValue, TValue>(
request: TInput,
action: (input: TInput, signal: AbortSignal) => Promise<TValue>,
): Promise<GovernedResult<TValue, TInput>> {
// Catalog values for this vertical. Replace them with facts from the current workflow.
const industry: IndustryFact[] = [
{ attribute: "ps.workpaper.type", policyInput: "ps_workpaper_type", value: "asc606_revenue_recognition" },
{ attribute: "ps.audit.phase", policyInput: "ps_audit_phase", value: "client_acceptance" },
{ attribute: "ps.audit.staff_level", policyInput: "ps_audit_staff_level", value: "staff_associate" },
];
// Policy runs before action() and again before the result is released.
// A deny or review decision means action() never runs.
return veriproof.govern(
"professional.services.consulting.evaluate",
request,
({ input, signal }) => action(input, signal),
{ industry },
);
}- Replace the sample values with facts from the current workflow. Rules read them under
input.snapshot.industry. - Test both permitted and blocked actions. Confirm that a blocked action never reaches your business function.
- Only
completed,completed_with_warning, andtransformedresults carry a released value.
For review decisions, follow the Human Review guide to configure continuation. Observe remains available when you need to record activity without enforcing a decision.
Set up the Professional Services & Management Consulting example. See the API reference for TypeScript, Python, or .NET.
Try a simulator to see a governed decision in context. To connect your own workflow, verify your work email and start Developer free for 60 days. You can also review the relevant controls with our team.
Live demo → Start free for 60 days → Request coverage workshop →
Selected vocabulary categories
WorkpaperType
Classification of the audit workpaper being generated or reviewed by an AI documentation assistant. Each workpaper type maps to a specific PCAOB or GAAS standard, a specific area of the financial statements, and a defined set of risk factors and required procedures. AI may generate draft workpapers for any type, but the auditor of record must review and sign off before the paper is filed to the engagement file.
Workflow area: Audit & Assurance Workpaper Management
- OTel attribute
ps.workpaper.type- First 8 permitted values
asc606_revenue_recognitionasc842_lease_accountingasc350_goodwill_impairmentasc330_inventory_lcnrvicfr_control_testingicfr_deficiency_evaluationgoing_concern_assessmentasc740_tax_provision
AuditPhase
Phase of the audit engagement during which the AI workpaper session is executed. AI-assisted workpaper generation is appropriate across all phases, but significant judgment areas in the opinion and completion phases require mandatory partner review before AI output is incorporated into the engagement file.
Workflow area: Audit & Assurance Workpaper Management
- OTel attribute
ps.audit.phase- First 8 permitted values
client_acceptanceplanningrisk_assessmentfieldworkinterim_testingyear_end_testingreview_and_supervisioncompletion
AuditStaffLevel
The professional staff level initiating, reviewing, or signing off an AI-assisted audit workpaper session. Governs the sign-off authority for AI-generated conclusions. Significant accounting estimates, going-concern conclusions, and fraud risk responses must be reviewed and approved by a manager or above. Final workpaper sign-off authority for PCAOB engagements requires an engagement partner.
Workflow area: Audit & Assurance Workpaper Management
- OTel attribute
ps.audit.staff_level- First 8 permitted values
staff_associatesenior_associateexperienced_seniormanagersenior_managerdirectorpartnerengagement_partner
WorkpaperQcGate
Quality control review stage status for an AI-assisted workpaper. PCAOB AS 2810 requires that the engagement partner and concurring reviewer evaluate the sufficiency and appropriateness of audit evidence. All significant AI-assisted conclusions must pass through appropriate QC gates before the workpaper is filed to the engagement file. AI may advance papers through administrative QC gates but may not self-approve significant judgment areas.
Workflow area: Audit & Assurance Workpaper Management
- OTel attribute
ps.workpaper.qc_gate- First 8 permitted values
draft_in_progressself_review_completesupervisor_review_requiredsupervisor_review_completemanager_review_requiredmanager_review_completesenior_manager_review_requiredsenior_manager_review_complete
AuditOpinionType
Classification of the audit opinion issued or recommended by an AI-assisted engagement. AI may draft the opinion letter and supporting documentation but may not issue any audit opinion, only an engagement partner may issue the final opinion. The opinion type is recorded at the end of the audit engagement session for governance and evidence purposes.
Workflow area: Audit & Assurance Workpaper Management
- OTel attribute
ps.audit.opinion_type- First 8 permitted values
unqualified_cleanunqualified_with_emphasisqualifiedadversedisclaimer_of_opiniongoing_concern_emphasiscritical_audit_matter_identifiedmaterial_weakness_identified
EngagementServiceLine
Service line classification for the professional services engagement being scoped. Used by Engagement Scoping Bot to route scope conversations to the appropriate knowledge base, fee benchmark, and staffing model. Independence and ethics rules vary significantly across service lines, audit and tax services have stricter independence requirements than pure advisory services.
Workflow area: Engagement Lifecycle Management
- OTel attribute
ps.engagement.service_line- First 8 permitted values
financial_statement_auditinternal_controls_audit_soxagreed_upon_proceduresreview_engagementcompilation_engagementsoc_examinationtax_compliancetax_advisory
EngagementScopingPhase
Current phase of the engagement scoping lifecycle. Engagement Scoping Bot progresses through these phases within a single session, and the phase is recorded on each step span. AI-generated fee estimates, resource plans, and delivery commitments are treated as draft outputs until the partner_approval phase marks them as firm.
Workflow area: Engagement Lifecycle Management
- OTel attribute
ps.engagement.scoping_phase- First 8 permitted values
client_intakerequirements_discoveryrisk_and_complexity_assessmentscope_definitionresource_planningfee_benchmark_retrievalfee_estimationindependence_check
EngagementComplexityTier
Complexity classification for the professional services engagement derived by the Engagement Scoping Bot based on client size, regulatory exposure, multi-jurisdiction scope, and AI involvement. Complexity tier governs the required level of partner oversight and affects fee benchmarks and resource planning defaults.
Workflow area: Engagement Lifecycle Management
- OTel attribute
ps.engagement.complexity_tier- Permitted values
standardcomplexhighly_complexexceeds_firm_guidelinesscope_not_yet_determined
IndependenceCheckOutcome
Outcome of the AI-assisted independence and conflict-of-interest screening for an audit or assurance engagement. AICPA ET 1.200 and SEC Rule 2-01 require independence to be maintained throughout the engagement. AI may perform the initial screening, but detected threats must be reviewed and resolved by a qualified partner or the firm's ethics office.
Workflow area: Engagement Lifecycle Management
- OTel attribute
ps.engagement.independence_check_outcome- First 8 permitted values
clearedcleared_with_safeguardsconflict_detected_referredthreat_identified_resolvablethreat_identified_unresolvableengagement_declinedon_hold_pending_resolutionprior_period_issue_identified
EnterpriseRiskDomain
Risk domain classification for the enterprise risk area being assessed by the Risk Assessment Coordinator. Each domain has a designated specialist agent and a domain-specific risk assessment methodology. The orchestrator agent coordinates multi-domain risk assessments and consolidates findings into the enterprise risk register.
Workflow area: Enterprise & Cyber Risk Assessment
- OTel attribute
ps.risk.domain- First 8 permitted values
strategic_marketoperational_resiliencecyber_information_securityfinancial_credit_liquidityregulatory_compliancethird_party_vendor_supply_chainesg_climate_sustainabilityai_model_governance
RiskCommitteeDecision
Decision outcome from the risk committee or board review of an AI-generated risk assessment or risk register update. High-severity risk ratings and strategic mitigation recommendations must be reviewed and approved by the Risk Committee before the board report is distributed. The AI coordinator may not distribute risk reports without a recorded risk_approved or conditional_approval outcome.
Workflow area: Enterprise & Cyber Risk Assessment
- OTel attribute
ps.risk.committee_decision- First 8 permitted values
risk_approvedrisk_approved_with_conditionsdeferred_additional_analysisdeferred_pending_external_dataescalated_to_boardescalated_to_regulatorrejected_insufficient_evidenceaccepted_with_enhanced_monitoring
FairModelComponent
Component of the FAIR (Factor Analysis of Information Risk) quantitative risk model computed by an AI risk quantification sub-agent. FAIR produces probabilistic loss estimates (10th, 50th, 90th percentile annualised loss exposure) by decomposing risk into its fundamental components. FAIR sub-agents must cite their calibration data source for any TEF or LM assumption.
Workflow area: Enterprise & Cyber Risk Assessment
- OTel attribute
ps.risk.fair_component- First 8 permitted values
tef_threat_event_frequencyvuln_vulnerabilitylef_loss_event_frequencypsl_primary_stakeholder_lossslef_secondary_loss_event_frequencysl_secondary_losslm_loss_magnitudeale_annualised_loss_expectancy
This page uses the vocabulary JSON distributed with the documentation. Check its version when comparing it with an installed SDK.
Download the vocabulary JSON for offline review or automated comparisons.
Use the SDK reference for configuration and supported APIs. Keep vocabulary selection separate from the compliance team's assessment of applicable requirements.