OHADA · SYSCOHADA · PCB · CIMA

Automated audits that stand up to OHADA regulators

Run financial, tax and forensic audits against SYSCOHADA, PCB and CIMA rules, with zero client data stored, ever.

Start my first audit See how a run works

Takes you to sign-up.

Audit run

In session only

SYSCOHADA PCB CIMA

  • Journal balance and sequence

    SYSCOHADA

    Passed

  • Related-party posting pattern

    SYSCOHADA

    Flagged

  • Reserve and provision rules

    CIMA

    Passed

  • Chart of accounts mapping

    PCB

    Checking

File analysed in memory, then discarded. Nothing is written to disk.

Accounting suites produce the books. Tax Bridge audits them against OHADA, PCB and CIMA rules, and never stores a line of client data.

Built for audit and compliance leads at banks and insurers, and for accountants and owners of small businesses who have to prove SYSCOHADA and tax compliance.

How an audit runs

From file to cited finding, inside one session

Forensic, financial and tax audits follow the same path. The only thing that changes is the rulebook.

  1. Scope

    Choose the framework

    SYSCOHADA for businesses, the Plan Comptable Bancaire for banks, the CIMA Code for insurers. The audit type is financial, tax or forensic.

  2. Input

    Upload for the session

    Your file is read in memory for this session only. There is no database behind the upload and no copy kept for later.

  3. Analysis

    Rules are checked

    Every rule in the chosen framework runs against your data, with live progress, so you see what has been tested and what is still running.

  4. Report

    Findings cite the rule

    Anomalies and fraud flags are ranked by severity. Each one names the regulatory rule it breaks, so you can act on it or defend it.

  5. Discard

    The data is discarded

    When the session ends the file is gone. Only run metadata, such as framework and rule counts, remains in your history.

Zero storage, by design

Handing a third party sensitive financial data is the risk. So we do not keep it.

Tax Bridge is stateless. There is no client-data store to breach, subpoena or leave behind, because the architecture has none.

Accounting suite or ERP Tax Bridge
What it does Records transactions and produces the books Audits the books against OHADA, PCB and CIMA rules
Your data Held in the vendor system Analysed in session, then discarded
Review Manual sampling and spreadsheets Every rule in the framework is checked
Output Ledgers and statements Severity-ranked findings, each citing its rule
In session
Files are processed in memory while you work. Nothing is persisted.
Metadata only
Your history keeps framework, audit type and rule counts. Never the figures you uploaded.
No client-data store
There is no database of uploads to breach or hand over, because the architecture has none.

Questions

What auditors and owners ask first

Does Tax Bridge store our financial data?

No. Tax Bridge is stateless. Files are analysed in memory during your session and discarded when it ends. Your history keeps run metadata only.

Which frameworks can I audit against?

SYSCOHADA for businesses in the OHADA zone, the Plan Comptable Bancaire (PCB) for banks, and the CIMA Code for insurers.

Which kinds of audit are supported?

Financial, tax and forensic audits. Forensic runs surface fraud flags alongside regulatory anomalies.

How is this different from my accounting software?

Accounting software and ERPs produce the books. Tax Bridge audits those books against the regulatory rules, as an independent check.

Will a finding tell me what rule was broken?

Yes. Each finding is ranked by severity and cites the rule it relates to, so you can act on it or explain it to a regulator.

Audit against the rulebook. Keep none of the data.

Create an account and open the audit workspace.

Start my first audit

Takes you to sign-up.