ClairAudit

Evidence straight from the client’s systems.

Connectors are built on the Model Context Protocol and share one interface: test the connection, read the schema, fetch entities. Credentials are encrypted, and writing back to a client system is exceptional and doubly approved.

Model Context Protocol

A long railway signal interlocking frame with a row of numbered levers in a workshop.
Interlocking lever frame for Invercargill signal stationA. P. Godber, Alexander Turnbull Library · Public domain

Connector packages, by source.

Each connector handles retries, rate limits and paging for its source. Accounting connectors expose the entities fieldwork needs; the Xero connector, for example, reads accounts, journals, invoices, credit notes and bank transactions.

ERP and finance
  • SAP S/4HANA
  • Oracle Fusion
  • Oracle NetSuite
  • Microsoft Dynamics
  • Workday
  • Xero
  • QuickBooks
Evidence and banks
  • Confirmation.com
  • Bank APIs (PSD2)
  • Bloomberg
Data platforms
  • Snowflake
  • Databricks
  • PostgreSQL
CRM and work
  • Salesforce
  • HubSpot
  • Jira
  • ServiceNow
  • Slack
  • GitHub
Documents
  • Microsoft 365
  • Google Drive
  • Filesystem
IT controls
  • AWS CloudTrail
  • Azure Monitor

Availability of individual connectors depends on your plan and the client’s system configuration.

Read by default. Writes need two signatures.

Most connectors are read-only by design. Where a connector supports write-back, a job cannot be submitted until it has been approved twice.

  1. AES-256-GCM

    Credentials encrypted at rest

    Connector credentials and OAuth tokens are encrypted with versioned keys, rotated on a 90-day job.

  2. Approval 1

    Partner or administrator

    Approves the write-back job for the engagement.

  3. Approval 2

    Tenant administrator

    Approves it for the organisation before it can run.

  4. Trail

    Every write is logged

    Each write-back appends an entry to the hash-chained audit trail.

No connector? The client uploads to a request list.

Prepared-by-client requests are shared as a secure token link, with no account to create. The client sees only their own request list.

Uploads are limited to 50 MB and to document types an audit uses: PDF, Office files, CSV and images.

Connector documentation

Bring an engagement. We will walk the file with you.

A demo covers your audit methodology, the standards you report under, and how agents, citations and review gates would fit your team. Pricing is discussed on the call.

Request a demo Read the docs