Data model overview
A high-level map of the entities you'll encounter as you query and mutate the External API. Read this first — every other concept page drills into one part of this graph.
Organizations
The customer side of your bank. Three core entities: OrganizationInvitation, Organization, and the per-organization ExtendedInformation.
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.
People
The API distinguishes natural people from legal entities, and customer-side people from your own staff. Five types you should know about: User, Administrator (with BoardMember and ExternalAdministrator implementations), Employee, and LegalEntity.
Reviews
A review (BankReportReview) is the bank-side workflow for processing a published bank package. It captures who looked at the package, what they decided, and when. Each review is composed of section reviews — one per document area in the package — so you can approve part of a package while flagging another part for resubmission.
Reference data
Lookup tables and per-bank configuration data. These appear as branchOffice, riskGroup, associationType etc. on other entities — you query them when you need to populate a dropdown, validate an ID before creating an invitation, or browse what your bank supports.