Fortune 100 Global Bank · Enterprise UX · Banker Entitlements

Banker Entitlements —
Limits, Roles & Approvers

Deciding who can move money, how much, and who signs off — inside a global bank. One create-user flow that stays effortless for the simple case and scales to the hardest.

Wire · ACH · RTP
payment rails entitled
Faster go-live
senior-stakeholder buy-in
Fewer delays
categorized limit & approver flows
3
limit models — same, per type, per account
Same vs different limits — the three modelsFive-step create-user tracker
5
payment rails, each limit-aware
Assign approvers per limit tier
User createdevery rule rolled into one review

To create a user in the bank's platform, an administrator has to define entitlements — which accounts the person can touch, which payment types they can run, the daily and per-transaction limits, and who has to approve each amount. For one user that's a single rule. For another it's a matrix across five payment rails and dozens of control accounts.

The trap is obvious: build for the hardest case and the simple one drowns; build for the simple one and the bank outgrows it in a week.

Simple by default, granular on demand.

The flow leads with the easiest path and marks it plainly — the same limits, roles and approvers for all payments and selected accounts is the preferred choice, one click, done. The two harder models sit right beside it, chosen only when the user actually needs them.

Create User — same limits, the simple path
The simple path — role, daily limit, maximum, an optional lower limit. Most users never need more.
Three ways to set limits
Same
one rule for all selected accounts · the preferred default
Per type
Internal, Wire, ACH, Bill Pay, Real-Time — each its own limits
Per account
every control account tuned individually, bulk-fill to move fast
Different limits per payment type
The same layout, opened up — when limits differ per payment rail, each keeps the identical shape so nothing has to be relearned.
Different limits per control account
The deepest cut — every control account tuned on its own, tabbed by payment rail, with bulk-fill so forty accounts don't mean forty times the work.

Approvals hang off the limits, not a separate silo. For each amount tier — $0–10k, $10–20k and up — the admin picks who signs off, per payment type and per account, from the same searchable list.

Assign approvers per amount tier
Approvers, in context — the panel slides over the setup so you never lose your place, background dimmed to keep focus.

Everything an admin chose — accounts, entitlements, limits, approvers — rolls up into a single review, then commits. No matter how deep the matrix went, it ends the same calm way.

Summary — user successfully created
The summary — the whole entitlement matrix in one readable table, then a clean confirmation.
Set it once — sign-off built in.