Skip to main content

Bank packages

A bank package is everything an organization submits to satisfy ajour ("up to date") requirements with your bank. Internally it's modeled as bankReport — a single row that aggregates pointers to every component document.

What's in a package​

Components vary by jurisdiction and the bank's configuration, but typically include:

  • Statutes — the organization's articles of association.
  • Summary — the cover sheet describing the change.
  • Accounting — financial statements / accounting evidence.
  • Authorized signatories — who is authorized to sign on the organization's behalf.
  • Business volume — answers to your bank's business volume questionnaire.
  • Board — current board composition; expected number of members is provided when the bank requires it.
  • Tax residency — supporting documentation for tax-residency declarations.
  • Legal entity — supporting documentation for the organization itself.
  • Board-member attorneys — power-of-attorney documents on behalf of board members.

Not every package contains every component. Optional components are marked nullable on the bankReport type — query the live schema in /graphql for the exact field list.

State​

A bankReport carries a few state-related fields rather than a single enum:

  • publishedTime — set when the package is submitted to the bank.
  • finishedDate — set when the package is fully processed.
  • isRejected plus rejectedReason — true when your bank has rejected one or more components.
  • type — OrganizationChangeType (FIRST_TIME, ODD, PARTIALLY_AJOUR_SCREENING, SCREENING).

bankReports excludes cancelled and soft-deleted packages automatically; rejected and published packages are both returned.

Rejection​

When you reject via rejectBankPackageById, each component you mark reject…: true is what the customer must resubmit. The organization is flagged not-ajour and a new ajour flow starts to chase the resubmission. The customer-facing reason text is what you put in the reason field — write it as if speaking to the customer directly.

Ajour lifecycle​

                            ┌──> Published ──> Review ──> Approved
                            │                        │
Organization (ajour) ───────┤                        └──> Rejected (RejectedByBank)
                            │                                     │
                            └────────── (not-ajour flow) <────────┘

When a package is rejected, the organization moves out of the ajour state and into a flow that periodically reminds the customer to resubmit. That flow can be paused via pauseNotAjourFlow and restarted via restartNotAjourFlow.

Where to query / mutate​