Skip to content
Framework

Bank account & signatory management: connect Treasury authority to the legal entity record

Banking authority is not just a Treasury list. Signers, POAs, directors, ownership and KYC all connect back to the legal entity — which is why governance changes should trigger Treasury action.

Legal · Finance · Operations

Entiti · Operating guidanceReviewed September 2, 2026 · Store only the bank information your operating model needs and apply appropriately restrictive permissions.

Authority register
Illustrative

Illustrative · Morgan Lee

A role change can leave authority open.

Director role ended September 18. Treasury confirmation is still needed.

A role change can leave authority open.
EntityBank relationshipMandate
Ashcombe Holdings LtdExample Bank · OperatingConfirmation pending
Ashcombe Services LtdExample Bank · PayrollUnder review

No full account numbers, balances or payment controls are exposed.

01 · Authority

Separate the role from the authority.

A director appointment, a bank mandate and a Power of Attorney are different records. They may have different owners, conditions and effective dates.

  • Connect each authority to a person and a specific entity.
  • Record its scope, signing rule, effective date, expiry and supporting evidence.
  • Keep a Treasury owner and review date visible.
Authority detailIllustrative
Illustrative · Sources retained

Bank mandate · Ashcombe Holdings Ltd

Person
Morgan Lee
Authority
Joint signer
Business owner
Treasury
Evidence
Mandate confirmation
Last confirmed
September 10, 2026
Current review
Confirmation pending

Illustrative authority terms; actual mandates follow bank and entity requirements.

02 · Change review

Treat a role change as a review trigger.

When a person leaves or ownership changes, identify the related authority records. The responsible team decides what must change and verifies the outcome.

  • Review resignations, appointments, POA expiry, ownership changes and closure.
  • Assign affected bank, KYC and delegated-authority items to their owners.
  • Retain external confirmation before marking the change complete.
Authority changeIllustrative
Illustrative · Controlled work

From notice to confirmed outcome

  1. Legal records the eventPreserve the notice and effective date.
  2. Treasury reviews the impactIdentify mandates, POAs and KYC requests.
  3. Authorized team completes the changeKeep the request and external confirmation.
  4. Record is updatedRetain evidence and the independent authority end date.

03 · Data scope

Store the information the job needs.

Entiti’s proposed role is to connect legal identity and authority context. Specialist Treasury and banking systems can remain responsible for balances, transactions and payments.

  • Use a bank relationship or masked reference when full details are unnecessary.
  • Restrict sensitive banking fields and supporting documents.
  • Report expiring authority and unconfirmed changes separately from payment status.
Data ownershipIllustrative
Illustrative · Ashcombe portfolio

Keep system responsibilities clear

Keep system responsibilities clear
InformationResponsible system or team
Legal entity and governanceApproved legal record
Mandate and authority evidenceLegal / Treasury review
Balances and transactionsTreasury / banking system
Payment executionAuthorized payment process

Questions by function

Start with the question your team needs answered.

The same entity context supports different responsibilities. Select a function to see what matters to that team.

Your team’s view
Illustrative

Legal

Which authority depends on this role?

Review mandate, POA and delegated-authority relationships separately.

Questions

The practical questions, answered plainly.

Clear boundaries help the team know what to do next.