Skip to main content

Administrator changes

The administrator changes node on a bank report (administratorChanges) captures every change to the organization's administrators that the customer recorded in this report — new admins, departing admins, role updates, and per‑administrator changes to attorneys and bank‑account access.

Shape​

administratorChanges itself is thin: an id and an administratorChange list. The interesting structure lives on the list items, which implement the AdministratorChange interface.

AdministratorChange has two concrete implementations:

  • BoardMemberChange — wraps a board member, exposes boardMember (with the underlying user) and boardMemberRoleChanges (one entry per added/kept role).
  • ExternalAdministratorChange — wraps an external administrator (typically appointed via power of attorney rather than elected). Exposes externalAdministrator and externalAdministratorRoleChanges.

Query both with inline fragments — the shared interface fields project at the top level, and the concrete ones go inside ... on BoardMemberChange { … } / ... on ExternalAdministratorChange { … }.

Interface fields​

Every AdministratorChange carries:

  • isNew — the administrator was added in this report.
  • isLeaving — the administrator is being removed in this report.
  • isAuthorizedSignatory plus isAuthorizedSignatoryChanged — current state and whether it changed.
  • hasRolesChanged — at least one role added or removed.
  • hasChanged — true when any of the above is true or any attorneyChange.hasChanged is true.
  • informationFile — a .txt with bookkeeping information about the administrator.
  • attorneysFile / signedAttorneysFile — the attorneys overview PDF and its signed counterpart.
  • attorneyChanges — list of per‑attorney changes (rights, bank card flag, the affected bank account).

Attorneys and bank accounts​

attorneyChanges[].bankAccount exposes accountName, registrationNumber, and accountNumber. rights and bankCard describe what level of access the attorney now has and whether they are entitled to a bank card. Attorney changes are scoped to administrators — there is no top‑level "attorneys" or "bank accounts" node on a bank report; everything attorney‑related is reached via this path.

Required gate​

The whole node is meaningful only when isAdministratorsRequired is true on the parent bank report. When it's false, the package didn't request administrator changes and administratorChanges will be empty.

Where to query​

See Querying administrator changes. To reject a package because of an administrator‑related problem, use rejectAuthorizedSignatories: true or — for the per‑member attorney documents — rejectBoardMemberAttorneys: true on rejectBankPackageById.