Active audit methodology for Big 4 firms.

Enterprise is built around a single corporate consumer (CFO group, internal-audit team, methodology team) buying synthetic data + group-audit datasets for their own use. Audit Firm is built around a partner-led firm — multiple offices, multiple engagement teams, dozens of partners and managers — that needs cross-firm coordination, methodology execution, RMM calibration, and tamper-evident workpaper integrity. Audit Firm includes everything in Enterprise plus active FSM execution, interactive Bayesian RMM, the L4 graph explorer, Merkle WP bundle gen + verify, ISA 600 cross-firm invitations, firm-organization tenancy (Firm / Office / EngagementTeam / User), and a 5-role × 6-resource RBAC matrix.

No. VynFi exports to those tools rather than replacing them. Per-state workpaper templates emit to Caseware Cloud XML and TeamMate JSON natively, so your audit teams keep their existing authoring environment. VynFi's value is the methodology spine + risk + synthetic-data layer that sits beneath those tools — generating the data, scoring the risk, and producing the audit-trailed FSM transitions that your authoring layer renders. Most firms run Caseware or TeamMate alongside VynFi; we're the source-of-truth methodology layer, they're the workpaper editor.

A group auditor invites a component auditor (at any firm — they don't need to be on a VynFi tenant in advance) by email plus a scoped permission set. The invitee accepts via a tokenized link and receives read-only access to the designated artifacts: FSM state for the engagement, RMM scores for assigned accounts, the relevant L4 sub-graph, and the WP bundles they're authorised to inspect. Every cross-firm read is audit-logged with timestamp, actor, and artifact. When the engagement closes (or the invitation expires), access auto-flips to read-only, and the audit trail captures the access termination event.

Yes — the verify endpoint requires no authentication and accepts any sealed bundle. Regulators (PCAOB, FRC, AOB, etc.), peer reviewers, and litigation teams can verify a bundle's integrity without a VynFi account. The endpoint is rate-limited to 60 req/min per IP to prevent abuse, but otherwise unrestricted. This is how Merkle integrity primitives are supposed to work: the verifier doesn't need to trust the issuer; they only need the bundle and the hash function. We've made the verifier trivially accessible because there's no value in gatekeeping it.

Yes — that's the core feature. VynFi's 12-factor Bayesian model produces an objective second opinion, but auditor professional judgment is the final word. Every prior in the model can be overridden interactively, with the override captured in the audit trail (actor, rationale, timestamp). The model re-scores in real time as overrides are applied, surfacing per-account deltas so partners can see exactly how their judgment reshapes the posterior. The Bayesian model is a calibration check, not a replacement — it complements EY GAM, KPMG KAM, PwC Aura, and Deloitte Omnia rather than competing with them.

Microsoft Entra SSO ships at Audit Firm tier launch via Entra External ID and the standard OIDC flow. SAML 2.0 federation is on the roadmap for firms standardised on non-Microsoft identity providers (Okta, Ping, ADFS). SCIM 2.0 provisioning is available on request for firms wanting automated user lifecycle management against their existing IdP. Most Big 4 firms run hybrid Microsoft / Okta estates today, so we expect SAML to land within the first two quarters post-launch.