Processes

Close accounts

How close accounts are reshaped as AGI capability advances.

ProcessesClose accounts
Close accounts — illustrated

Business-as-Code

Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.

Close accounts sits inside a larger value-flow — 1 parent structure it composes into. The hierarchy is grounding, not the story: it tells you which aggregate exposure Close accounts inherits.

Where Close accounts sits

Related articles

No articles yet for this entity.

Recent capability events

No capability events for this entity yet.

How the work flows

Trigger: A customer submits a formal request to terminate their account or an internal system flags the account for mandatory closure due to dormancy or policy violations.

  1. Receive and log account closure request or internal mandate
  2. Verify account holder identity and closure authorization
  3. Suspend active services, debit cards, and recurring transactions
  4. Calculate final account balance including pending interest and fees
  5. Disburse remaining funds or collect outstanding negative balances
  6. Update core banking system to reflect closed status
  7. Archive account records and issue final closure confirmation

Outcome: The account is permanently deactivated in the core banking system, final balances are settled, and a final confirmation is issued to the account holder.

Measured by

Closure Cycle TimeCost Per Account ClosurePending Closure BacklogClosure Error Rate