The approval of an exception
The officer who approved a credit or policy exception, what the approval meant, and the exact terms they approved.
[ Banking and financial services ]
Every approval, provable for years.
Banks keep customer files, credit decisions, policy exceptions and the policies behind them long after an account closes. Tabellix keeps each one verifiable for its full retention period, including every step an AI agent took.
01 What gets asked
What examiners and auditors ask.
Supervisors, internal audit and counterparties ask the same questions in different words, often years after the decision.
01
02
The policy in force
The version of the credit policy or procedure in force on the date of the decision, not the current one.
03
A complete customer file
Every document and screening result behind an onboarding decision, in one place and unchanged since.
04
What the agent did
Which steps an AI agent performed, for which employee, and where a person confirmed the outcome.
05
Changes to the rules
Who changed a role, a permission or a workflow, who approved the change, and when it took effect.
06
Evidence without system access
A complete package for an examination or a dispute that the examiner can check without an account on your network.
02 How Tabellix answers
Answered by the ledger.
01
Approvals bound to the terms
An approval is a signature with its meaning, bound to the exact field values approved, with a fresh sign-in. An author cannot approve their own request, and the refusal is recorded.
02
The policy in force, pinned
An exception record links to the policy version in force when it was granted, and that link never moves. Release and supersession are ledger transitions.
03
A file that holds its members
A due diligence file is a case record with its documents and screening results as ordered members. Holds, retention and access flow from the case to every member.
04
Agents never above the employee
An agent acts for one employee and gets only what that employee may do and your agent policy allows. You decide which actions wait for a person to confirm, and every call is on the audit trail.
05
Rules changed only by release
Roles, permissions, workflows and agent rules change through configuration releases reviewed as a diff and approved by people other than the author. The release in force is stamped on every audit entry.
06
Packages verified offline
A disclosure is a signed, deterministic bundle the examiner verifies offline. An inspector session gives read-only access, fixed in scope, for at most 72 hours.
03 Typical records
What a bank keeps.
Raw transactions stay in the core. What someone will have to explain later becomes a record.
| Record | Kind | What it holds |
|---|---|---|
| Credit policy CP-0007 | document | Versioned, approved with signatures, reviewed on schedule, and superseded in the same step its successor is released. |
| Customer due diligence file | case record | Identity documents, proof of address and screening results as ordered members; review and approval as its lifecycle. |
| Policy exception, credit limit | event record | The rule, the requested and approved values, the approving officer and the reason, locked at capture and linked to the policy version in force. |
| Statement export | document | Kept as its exact CSV bytes with no viewing copy, and signed over its content digest. |
| Customer complaint | case record | Intake, investigation and response as lifecycle steps; the correspondence as members; retention counted from closure. |
| Examination request | case record | The request list, the records released as sealed disclosures, and an accounting of what each examiner received. |
05 FAQ
Common questions.
01Can a customer's personal data be erased while the bank keeps the record?
Personal data about each customer sits under that customer's own key. Erasure destroys the key and keeps the record's identity, links and history, and the audit trail still verifies. It needs a reason, a fresh sign-in and a person; an agent can never erase.
02Where do security alerts go?
Authentication failures, policy denials, including agent denials, and rate refusals stream to your collector as OpenTelemetry logs, without tokens or content. A collector outage does not slow requests.
03Does Tabellix run in our own data center?
Yes. It runs on Kubernetes in any cloud or on premises, with PostgreSQL, an S3-compatible object store and a key manager you supply. The license is verified offline, and the software never calls home.
04How does a core or onboarding vendor embed it?
Your product keeps its screens and its decisions. It writes cases, records and documents through one contract over gRPC or REST, receives committed events through signed webhooks, and renders forms from the catalog of types and lifecycles. Your brand appears on every customer-visible surface Tabellix provides.
[ Contact ]
Build your product on proof.
Tell us what you build and who audits it. We'll show you how Tabellix fits into your product and how it answers your auditors' most common questions.