CPA and audit

inTheEU Assist  ·  Case study  ·  July 2026

For a CPA or audit practice, the record of what was checked, by whom, and against what version of the data is not paperwork attached to the work. It is the work. This page sets out how an engagement's chain of custody would be planned and run on inTheEU Assist, not a record of a completed deployment.

Engagement review and sign-off, audit workflow

How the workflow would be structured

Each client engagement would be set up as its own isolated case, with its own documents, knowledge pack, and reviewers. Nothing from one engagement, a working paper, a flagged discrepancy, a trained model adapter, is visible to or reusable within another engagement.

Document analysis and discrepancy flags would be proposed by an agent configured for the engagement, each one hashed to the source document it was drawn from. A generated report or working paper would carry the signature of the agent, the skill that produced it, and the reviewing professional, not just a timestamp in a shared log.

Where human approval sits

A flagged discrepancy would move from proposed to reviewed to approved or rejected, never auto-applied. A generated report would require the reviewing partner's explicit sign-off before it is treated as final. That sign-off is signed and permanently attached to the engagement record, not a checkbox in a separate system.

What this draws on today, and what it does not

Per-engagement isolation, the proposed-to-approved review lifecycle for flags and outputs, and the signed audit chain tying a report back to its source and its reviewer are working parts of the platform. What is not part of this: any pre-built accounting standard interpretation or automated audit opinion. The practice's own partners and reviewers remain the professional authority throughout; the platform makes their review provable.

Some of the architecture underlying this capability set is documented in filings still in progress. This page describes what the platform is designed to do, at a level appropriate for planning a pilot, not an implementation specification.

Platform features and interface are subject to continuous improvement. Descriptions in this guide may not reflect the exact layout or wording of the latest released version.