Bank Accounts — Workflow

Overview

Bank Accounts follows the standard catalog lifecycle in SARA. Banks, accounts, and cards are created in an active state and can be deactivated or reactivated as needed. There is no approval pipeline.

No approval pipeline

This feature does not have a multi-step approval workflow. Records are managed directly with no intermediate statuses.

Note

For the standard catalog lifecycle pattern, see: Workflows & Pipelines

Status lifecycle

ACTV — Active. The record is in use and available across the system.
INAC — Inactive. The record has been deactivated and is excluded from active operations.

Info

For system-wide status guidance, see: Status

Hierarchy and cascade rules

Banks, accounts, and cards form a three-level hierarchy:

Bank
└── Account (internal_account)
    └── Card (internal_subaccount)

This hierarchy has two important cascade rules:

Cascade deactivation: Deactivating a bank automatically deactivates all its accounts and all cards under those accounts. Deactivating an account automatically deactivates all its cards. This is enforced in a single operation — no manual cleanup needed.

Activation guard: The Deactivate/Activate action on an account is only available when its parent bank is ACTV. Similarly, the action on a card is only available when its parent account is ACTV. This prevents activating a lower-level record while its parent remains inactive.

Warning

Deactivating a bank is a broad operation — it cascades to all its accounts and cards simultaneously. Verify the scope before deactivating.

Permissions

Access and actions are permission-driven. See: Permissions