Banking and finance

Use cases

The five advantages for a bank, each with its illustrative example.

The four steps, in one example

  1. Authorization

    Illustrative example

    A risk manager authorizes an agent to work the applications for a consumer credit line.

  2. Agent act

    Illustrative example

    The agent approves one application and escalates another to an analyst; both acts stay tied to the manager who authorized it. In 2027 refusal of acts outside authority arrives: an approval above the delegated amount will not go through.

  3. Signed record

    Illustrative example

    Each approval, decline or escalation is signed with the manager who authorized the agent and the moment of the act.

  4. Verification

    Illustrative example

    With the evidence package, the supervisor verifies on its own machine the approvals of the quarter in which the agent took part.

Dates are projections of the current development plan, not commitments.

Five advantages for a bank

Each advantage answers a question that internal audit, the supervisor or a customer will ask sooner or later.

The examples are typical cases in banking, not customers or deployments.

  1. Who answers for each act?

    • Today

      Every act of an agent sits under the authorization of an identified person, and that authorization is revoked with immediate effect.

    • 2027

      Refusal of acts that exceed the delegated authority: products, amounts and terms.

    Illustrative example

    A collections agent negotiates payment plans under a manager’s authorization. When the manager changes, their authorization is revoked and the record shows the date. In 2027, with refusal of acts outside authority, the agent will not be able to offer more than the delegated discount.

  2. Does the proof depend on the provider?

    • Today

      Every record is signed and stays in the bank’s own cloud account, not in the model provider’s.

    • 2027 service · 2028 product

      A verifiable evidence package: the signed records are exported and verified on any machine, without access to Unica and without trusting the bank, Teipsum or the model provider.

    Illustrative example

    The external auditor asks for the file of the quarter’s approvals in which an agent took part. With the evidence package, they receive a verifiable file, not screenshots or access to production.

  3. What did the system see that day?

    • Today

      The signed record shows who acted, under whose authorization, and when.

    • From 2028

      Rebuilding what the system saw at a given moment (the data, the policy and the authority in force, and who or what touched each piece of data) and explaining it to the people affected.

    Illustrative example

    A customer complains to the supervisor about a decline from eight months ago. From 2028, the data and the policy of that day are rebuilt, not today’s.

  4. How is each rule shown to be met?

    • 2027 service · 2028 product

      With the verifiable evidence package, human oversight, event logging, explanation and data residency are laid out as controls, by obligation: Ley 21.719 (2024), the EU AI Act (high-risk obligations from 2 December 2027), the supervisor’s rules.

    Illustrative example

    With the evidence package, compliance documents its control of automated decisions with the system’s record, article by article, and not with a report written by hand.

  5. How much work does a review take?

    • Today

      Every act is recorded and signed when it happens: who acted, under whose authorization, and when.

    • 2027 service · 2028 product

      The auditor and the supervisor verify the record instead of reading reports: preparing a review goes from weeks of gathering to one signed export.

    Illustrative example

    With the evidence package, the second line of defence reviews the agents of three areas with the same signed record, instead of three quarterly reports prepared by hand.

Dates are projections of the current development plan, not commitments.