Funds Accounts
Funds accounts represent financial accounts retrieved from account servicing providers (banks, neobanks, payment institutions) via account information services. The FXM module models accounts with their balances, associated parties, statuses, and access consents, following Open Banking patterns for account data representation.
Account structure
Funds accounts
Each account record captures details as provided by the account servicing provider.
| Field | Purpose |
|---|---|
| Account servicing provider | The bank or provider that serves the account |
| Provider account references | Identifiers supplied by the account information provider or bank |
| Account status | Whether the account is enabled, pending, disabled, or deleted |
| Currency | The account currency |
| Usage type | Business or personal use |
| Account type | Provider-supplied account type |
| Account dates | Opening date, maturity date, and last known update date |
| Account names | Provider-supplied name, custom account name, and holder name |
| Account code | Institution-assigned account code and code scheme |
Access consents
Before account data can be retrieved, the account holder must grant consent to the AISP. The platform records these consents following the Open Banking consent model.
| Field | Purpose |
|---|---|
| Consent service provider | The account information provider receiving access |
| Account servicing provider | The bank or provider granting access |
| Consent status | For example, authorised, awaiting authorisation, or revoked |
| Consent permissions | The account data elements the provider may retrieve |
| Access period | The transaction date range covered by the consent |
Consents are linked to both the AISP and the ASPSP as parties. The consent_permissions field stores an array of granular permission codes that control which account data elements the AISP may retrieve.
Balances
Balance snapshots are recorded over time. Each account can have multiple balance records across different types, currencies, and dates.
| Field | Purpose |
|---|---|
| Account | The funds account the balance belongs to |
| Balance value | Balance excluding credit line |
| Available balance | Balance including available credit |
| Balance date | Date and time of the balance snapshot |
| Balance type | Closing, opening, interim, expected, or other standard balance type |
| Currency | Balance currency |
| Credit line | Credit line type and value, where available |
Balance types
Balance types follow standard banking conventions:
CLOSING_AVAILABLE/CLOSING_BOOKED/CLOSING_CLEARED-- end-of-day balancesOPENING_AVAILABLE/OPENING_BOOKED/OPENING_CLEARED-- start-of-day balancesINTERIM_AVAILABLE/INTERIM_BOOKED/INTERIM_CLEARED-- intraday balancesEXPECTED-- projected balanceFORWARD_AVAILABLE-- future-dated available balanceINFORMATION-- informational balancePREVIOUSLY_CLOSED_BOOKED-- prior period closing balance
Privacy-enhanced balance view
The public balance view applies privacy protections:
- account identifiers are replaced with privacy-safe values
- monetary values are rounded for safer exposure
- timestamps are reduced to date-only granularity
Parties
Parties (individuals or organisations) are linked to funds accounts with a role designation.
| Field | Purpose |
|---|---|
| Account | The funds account |
| Party type | Sole account holder, joint account holder, or delegated party |
| Party | The individual or organisation linked to the account |
| Party site | The relevant address or site, where available |
| Contact point | The relevant contact detail, where available |
Statuses
Account statuses track the date range of transactions that have been retrieved for an account.
| Field | Purpose |
|---|---|
| Account | The funds account |
| Earliest transaction date | Earliest retrieved transaction date |
| Latest transaction date | Most recent retrieved transaction date |
This metadata helps the platform determine what transaction history is available and when to request incremental updates from the AISP.
Access model
Funds accounts, balances, parties, statuses, and transactions are visible only to users who have access to the account. Child information follows the visibility of the parent account.