Become a design partner

Regulatory reporting · controls · evidence

Tallyseal Assure

From a reporting break to an approved fix: one record of changes, fixes and approvals, with the evidence behind them. We’re building with regulated firms.

Become a design partnerAbout Tallyseal
Built for enterpriseFour-eyes sign-offApplication errors roll backHash-chained record

Early stage. Statuses are shown on each example.

Tallyseal Assure

Reporting teams: resolve the break. Show the evidence.

Keep your core banking, ledgers and reporting feeds. We’re building Assure to bring a reporting break, the rule it failed, the proposed fix and its approval into one evidence record. Four-eyes sign-off and a hash-chained record form the foundation; each reporting use below carries its own stage.

Your estate, with Tallyseal Assure

Regulationsregulator rules and updatesBSA/AMLCall ReportBaselSFTRDORAGDPR
Your legacy systemscore banking, ledgers, vendor reporting feeds: kept in place
Tallyseal Assureacross your systems, not instead of them
  • Checks feeds against the rules
  • Puts each break and fix in front of a person
  • Keeps one record, with the evidence
Compliancereviews each fix and approves it, or sends it back
Auditors and examinerssee the record and the evidence behind each decision

Enterprise control, built in, beneath Tallyseal Assure

Four-eyes sign-offwhere you set it
Application errors roll backchanges for humans and AIs alike
Hash-chained recordof each change
Your own identity providerOIDC sign-in, one door
Roles, permissions and scopeas clear records
No back doorsfixes, configuration and data you load use the same door
Standalone codewe're building it
Tallyseal Assure is a product we’re building on Tallyseal to help regulated firms turn regulations and system feeds into one record of changes, fixes and approvals, with the evidence behind them.
Reporting and control work to design together

Basel regulatory reporting

We’re building capital-template checks: flag a break, review an adjustment, obtain second-person approval and retain its evidence.

We’re building

SFTR reporting controls

Designing checks on reporting feeds: a break, a proposed fix and a second-person approval. Your reporting provider still submits the report.

Designing with partners

BSA/AML alert and SAR decisions

Designing the alert review: AI drafts a disposition, an analyst proposes, a second person approves; the history supports examiner review.

Designing with partners

Call Report assurance

Figures traced back to source, with adjustments approved before filing.

Designing with partners

Section 1071 lineage

Small-business lending fields traced to their source documents.

Designing with partners

Change records over legacy cores

Files from an existing system picked up and loaded as records, checked against business rules and recorded, and a bad change to your data comes back exactly.

We’re building

DORA operational resilience

Supports DORA evidence: changes, incidents and fixes shown from one record.

We’re building

GDPR data changes

Supports GDPR work: who changed personal data, under which rule, and how it was put right.

We’re building

These are building and partner-design examples, not claims of completed regulatory coverage. Bring one feed, one reporting rule or one control to work through.

Underneath Tallyseal Assure

Connect. Build and modernise. Run. Prove. With AI at each step.

Not an IDE: an AI development environment. Design it with your experts, build it with AI, and your people approve each change before it goes live.

01Connect

Use what you already have.

Connect by web calls, files, queues, databases or existing code: your team or SI builds each connection on Tallyseal; each result returns through one door.

  • Over the web: rules and processes call the web services your existing apps already have, and each call is on the record.
  • Files and old formats: read spreadsheets, files and legacy record layouts as they are, and turn them into a working app.
  • Code and databases: Your team or SI can easily build calls to routines in your systems and connections to your other enterprise databases on Tallyseal.

What it meansNothing has to be rewritten to start.

02Build and modernise

Ship new products, and shrink the old estate as you go.

Wrap, re-use and extend the apps you already run. Your team or SI checks each new part against the old and switches the old off step by step; we're building the final switch-off check.

  • Build brand new applications with AI.
  • Generated, not hand-written: Tallyseal generates the tables, screens and the API description for changes from your approved definitions, and regenerates them when a rule changes.
  • Re-use: your experts settle the rules buried in existing apps once, and each answer stays linked to the source lines it covers.
  • Import your models: bring in your existing decision tables and process models.
  • Extend: AI drafts and your people approve, and a bad change to your data comes back exactly.

What it meansNew products without waiting on the integration queue, and the old estate shrinks with no big bang, so you stop paying twice.

03Run

Change the business without breaking it.

Bring in AI while the core runs. Application errors roll back changes for humans and AIs alike.

  • Real databases: your data sits in an enterprise database, a standard relational database, with tables built from your definitions.
  • Standalone code: we're building ahead-of-time compiled code you can inspect, which runs in your environment without calling us to process a transaction.
  • Explainable decisions. Trace any value to who changed it, when and why.
  • Fits your enterprise tooling: diff and test rules in your pipeline, export the record to plain files, and keep AI tools in one reviewed catalogue, with the API generated from the same definitions.

What it meansAI-speed delivery on a backend that's deterministic by design.

04Prove

Say yes to AI and stand behind it.

Show the board and the regulator who or what changed what and why, from your own record, with four-eyes sign-off where you set it.

  • Your record, not a sample: each field change records old value, new value, who and why, and exports as a signed evidence bundle for auditors and regulators.
  • The rule in force: each outcome shows the rule in force at the time and who approved it.
  • Checkable without us: evidence follows CRAWCUS, an open spec we publish (CC-BY-4.0), and an open-source verifier lets anyone check it.

What it meansAttest to every change, not a sample, and answer auditors from the record, not a spreadsheet.

Enterprise control, built in

People in the loop

Approval is yours to set: four-eyes sign-off on the work you choose, in your order, and the maker never signs as checker.

Roles and permissions

Roles, permissions and scope are clear records your team can review.

AI as a named actor

AI is named as the actor on each change it makes, and fenced out of the fields you choose.

Enterprise sign-in, one door

Sign in through your own identity provider. People, systems and AI agents use the same door and land on the same record.

No back doors

Fixes, configuration and the data you load go through the same door onto the same record.

Design partners

Build it with us.

We're taking on a small number of firms and delivery partners as design partners. Bring one problem, such as a rule set, a control or a feed, and we'll work through it together.

Email hello [at] tallyseal.com