How it works

ERP connection to clean close in four steps.

Centinel is a read-only layer over your current ERP. There is no agent to install, schema to alter, or write access to grant. Setup takes under 15 minutes, with audit coverage beginning that day.

Step 1: Connect

Link your ERP through a read-only API token.

Centinel uses your ERP's standard journal-entry API endpoint. Provide a read-only service account token, and leave the rest of your system unchanged. Supported ERPs connect in under 15 minutes.

Create a read-only service account

Create a dedicated read-only service account in SAP, Oracle, NetSuite, Sage Intacct, or Microsoft Dynamics. Centinel never requests write permissions.

Add ERP credentials to Centinel

Add your ERP instance URL and service account credentials to the Centinel onboarding wizard. The connection is checked and verified within seconds.

Start receiving the posting stream

Centinel listens for journal-entry postings through the ERP event webhook or polling API. Each new entry starts an evaluation immediately.

Step 2: Evaluate

Evaluate every entry against your rules as it posts.

When a journal entry posts, Centinel's audit engine checks it against every active rule at once. This adds no delay to your ERP workflow. Processing runs asynchronously, outside the posting path.

Each posting event evaluated in under a second
All active rules evaluated in parallel
Rules use historical posting patterns for context
Multiple entities, with individual or shared rulebooks
SOX-aligned templates for common internal controls
Statistical baselines identify unusual posting patterns
Step 3: Investigate

See the complete record behind every flagged entry.

If an entry fails a rule, Centinel builds a structured exception record with the journal entry data, triggering rule, and assigned reviewer. Each exception includes a defined route to resolution.

  • Journal metadata including account, amount, entity, and posting date
  • Plain-language explanation of the flag and triggering rule
  • Resolution options: approve, escalate, or mark for close-package review
Step 4: Close

Close with documented exceptions, not worries.

By period end, each exception is resolved or documented. Centinel creates a structured close-package report showing your audit committee what was flagged, who reviewed it, and the outcome. Send it to external auditors directly from the platform.

One-click report for the current close period
Compare exception trends across periods
Read-only auditor link, no Centinel account needed
Tamper-evident audit log covering SOX and IFRS 15 requirements