acumon ← Assurance Sign in
IFRS 9 · Expected Credit Loss

Proof, not assertion.

The assurance platform that re-executes its own conclusions. Every ECL estimate is versioned, evidenced, and reproducible to the byte — so an inspection of the file is faster and cleaner than the spreadsheet audit it replaces.

What makes it different

Generated, not asserted — at every layer.

The properties a regulator asks about are enforced by the system, then shown as evidence — not claimed in a cover note.

Provable reproduction

A stored run re-executes and reproduces its result byte-for-byte. The pair (methodology version, input hash) determines the output, so a conclusion recorded years ago is proven — not trusted.

No checklists

The concluding layer has no “confirmed” box. Each judgment is an active disposition of specific facts — accept, propose, extend, rebut — with mandatory rationale and a hash-sealed sign-off.

AI proposes, you disposition

AI extracts and drafts under a citation-anchored, human-in-the-loop rule — and never calculates. Every call is logged with region, cost and disposition, and scored against a gold set.

Benchmarking under k-anonymity

Position a client against the population for its sector and geography — never describing a cohort small enough to single out a participant. A benchmark that cannot be shown is shown as suppressed, not dropped.

Receivables to loan tapes

Provision matrices, scenario layers, individual DCF assessment, and an account-level PD·LGD·EAD engine — each shadowed by a challenger that turns a point estimate into a defensible range.

Residency & controls, structural

Per-tenant residency enforced across storage, compute and AI-inference planes; an immutable, hash-chained evidence trail; SOC 2 controls generated from live probes on the running system.

Who decides

Three people sign off on the tool. Each gets an answer sheet.

Everything below is generated from the engagement and the running system, on request — assembled by the platform, not by a person the night before.

Methodology panel

Is the method sound?

The Technical Basis Document — every formula, presumption and threshold — generated from the shipped behaviour so it never drifts from what the code does.

  • Guardrails proving non-configurability of non-compliance
  • Worked examples, hand-checkable
  • Composite version stamp per engagement
Procurement & security

Can we trust the platform?

A SOC 2 controls register whose automated controls are evidenced by read-only probes against the live system — operating, not asserted.

  • Per-tenant residency attestations
  • AI Use Statement — models, regions, controls
  • Encryption, SSO/MFA, isolation by row-level security
Regulator & inspector

On what basis did it conclude?

The concluding report with inline references and sealed sign-offs, the AI audit log for the file, and any engine run re-executed on demand.

  • Immutable, hash-chained event trail
  • Contradiction and challenge logs
  • Archive sealed to the assembly window
Coverage

The staging decision, made numeric.

From homogeneous receivables to a bank loan tape — measured the way the standard prescribes, with the horizon driven by the stage.

Stage 1Performing — 12-month ECL. Provision matrix or account-level PD·LGD·EAD over the next twelve months.IFRS 9 5.5.5
Stage 2Significant increase in credit risk — lifetime ECL, with the SICR trigger a disposed judgment, not a silent flag.5.5.3 · B5.5.17
Stage 3Credit-impaired — individual discounted-cash-flow assessment at the original EIR, beside the client’s specific provision.5.4.1(b)
Forward-lookingScenario layer with a non-linearity demonstration — the evidence on which the multiple-scenario floor rests or is rebutted.B5.5.42
ContinuousInterim rollforwards decompose the movement into volume and rate — the book growing versus credit deteriorating.ISA 540.14

An inspection faster and cleaner than a spreadsheet audit.

Bring an engagement, or your methodology. We’ll show you the same file an inspector would see — and re-execute it in front of you.