Employer Relation

Business Requirements Document (BRD)

🧩 Employer Relation

🔖 1.1

📅 Wednesday, 6 May 2026

👤 Martijn Bruitsman, Peter Disselkoen, Bernard Bos

⚙️ Mike Chernev

1️⃣ PURPOSE

This document defines the business requirements for the Employer Relation Epic. It covers the relationship between investors and their employers, including how employer properties are structured via employer arrangements and contracts, how employer contributions are registered and verified, and how the system will handle employment changes such as terminations and employer switches.

2️⃣ SCOPE

The Employer Relation covers the following functional areas:

• The relationship between an investor account and an employer.
• Registration and management of employer properties via the employer arrangement structure.
• Registration and management of contracts linking employer arrangements to investor accounts.
• Employer contribution, periodicity, and deviation monitoring.
• Withdrawal blocks configured at the employer arrangement level and applied through the contract.
• Registration of employer bank accounts.
• Employee number per contract.
• Employer switching and employer arrangement correction processes.
• Retrieval of employers, employer arrangements, and contracts.
• Deactivation of employer arrangements and contracts.

The following is explicitly out of scope for this Epic:

• Direct debit processing; employer contributions are deposits only.
• Fee structure configuration per employer or employer arrangement.

3️⃣ GLOSSARY

The following terms are used throughout this document:

• Investor Individual investor account holder who is (or was) employed by an employer participating in the scheme.
• Employer Company that offers an investment employer arrangement to its employees.
• Employer Arrangement Arrangement configuration applicable to all contracts connected to that employer arrangement. An employer can have multiple employer arrangements; an employer arrangement can be linked to multiple contracts.
• Contract The link between an employer arrangement and an investor account. The contract stores the per-investor values and overrides that apply to the investor account.
• Investor Account The investor account of an investor, to which a contract is connected.
• Employer Contribution Periodic or one-off payment made by the employer to an investor account. This is a deposit and not a direct debit.
• Deposit Unscheduled incoming bank transfer to an investor account.
• Withdrawal Block Restriction preventing withdrawals. This can be ended with a defined threshold.
• Power of Attorney Authorisation on the investor account that enables the employer contribution to be processed.
• Employee Number Number assigned to an investor account by their employer.
• Inactive Date Date from which the onboarding is closed to new applications.
• Backoffice Internal operations team responsible for manual processing, overrides, and corrections.
• Annuity Product Product where withdrawal block is mandatory.
• Net Product Product where withdrawal block is supplementary rather than mandatory.

4️⃣ FUNCTIONAL REQUIREMENTS

4️⃣0️⃣ Object Hierarchy & Property Inheritance

The Employer Relation defines a hierarchy with product-level configuration, employer arrangement defaults, and per-investor contract values:

Product
  n:n Employer Arrangement (configuration template, shared across contracts)
        1:n Contract (per-investor link and override layer)
              1:1 Investor Account

Main Properties (defined at Employer Arrangement level, apply to all connected contracts unless overridden):

• Employer Contribution Allowed flag
• Withdrawal Block configuration
• Deviation Threshold percentage
• Inactive Date
• Override permissions for properties that may be changed at contract level

Contract Properties and Overrides (defined at Contract level, specific to each investor):

• Withdrawal Block Active flag (can override the global setting)
• Contribution Active flag (can be disabled per investor)
• Employee Number (employer-specific ID per investor)
• Status (active, inactive, terminated)

This structure ensures consistent policy at the employer arrangement level while permitting backoffice flexibility at the contract level (e.g., for exceptions, corrections, or regulatory accommodations).

4️⃣1️⃣ Investor Account – Employer Relationship

At onboarding, each investor account will be linked to exactly one contract. The contract links the investor account to an employer arrangement, and the employer arrangement links to the employer. For products that involve an employer relation, providing the employer and employer arrangement at onboarding is mandatory. The cardinality of the relationship is as follows: a product can be linked to multiple employer arrangements, an employer arrangement can be linked to multiple products, an employer arrangement can have one or more contracts, and each contract has exactly one investor account. The absence of an active contract is valid and represents the state in which the investor is no longer employed by the employer.

The system will support the following operations:

• Deregistration of Employment It will be possible to register that an investor is no longer employed by their employer. This action will be a manual backoffice process. Upon deregistration, employer contribution functionality and any applicable withdrawal block will be removed from the active contract.
• Employer Switch The investor account will be connected to a different employer through a new or updated contract when the investor changes jobs, provided the new employer is already registered in the system.
• Correction of Incorrect Onboarding It will be possible to correct an incorrect employer arrangement or contract assigned at onboarding. This is a backoffice amendment, recorded in the audit history.
• Employee Number The system will allow storage of an employee number per contract. The External ID can be used for this. This allows an investor to have multiple investor accounts if they work for multiple participating employers.

4️⃣2️⃣ Employer Arrangement Structure

Employer properties are stored directly in the employer entity. The separate configuration called an employer arrangement makes variations possible. A contract links an investor account to an employer arrangement. This structure enables one employer to offer multiple employer arrangements, for example, different products or different contribution configurations, without duplicating the employer.

The employer arrangement will have the following properties, including but not limited to:

• Employer Reference to the employer entity.
• Product Reference to one or more products for which the employer arrangement is available.
• Employer Arrangement Code Free-text field, unique identifier.
• Employer Arrangement Name Free-text field, used as common identifier.
• Employer Contribution Allowed Flag that controls whether employer contribution is allowed and active.
• Withdrawal Block Flag indicating whether a withdrawal block is active, combined with a period.
• Deviation Threshold Maximum allowed deviation percentage between the expected and actual employer contribution.
• Inactive Date Date from which onboarding for this employer arrangement is closed.
• Override Permissions Configuration defining which properties may be overridden at contract level.

4️⃣2️⃣1️⃣ Contract Structure

The contract is the operational link between an employer arrangement and an investor account. It stores the values that are specific to one investor account and any allowed overrides of employer arrangement properties.

The contract will have the following properties, including but not limited to:

• Employer Arrangement Reference to the employer arrangement.
• Investor Account Reference to the investor account.
• Employee Number Employer-specific employee number for the investor account.
• Status Active, inactive, or terminated.
• Employer Contribution Amount Expected employer contribution amount.
• Contribution Periodicity Expected contribution frequency.
• Employer Contribution Active Flag indicating whether employer contribution is active for this contract.
• Withdrawal Block Contract-level withdrawal block value, where allowed by the employer arrangement.
• Withdrawal Block End Date Optional end date for the withdrawal block.

4️⃣3️⃣ Employer Contribution & Power of Attorney

The system will be able to record the desired employer contribution per contract. This contribution may be one-off or recurring. The contribution is processed as a deposit into the investor’s investor account; it is not a direct debit.

The following operations will be supported:

• Store Desired Contribution Record the expected contribution amount and its periodicity (see section 4️⃣6️⃣).
• Verify Actual Contribution The actual incoming deposit from the employer will be verifiable against the stored expected amount.
• Deviation Detection and Reversal When the deviation between the expected and actual contribution exceeds a configurable threshold, the system will flag the deposit and offer the option to manually reverse it.

4️⃣4️⃣ Employer IBAN Registration

Employer IBANs will be stored and maintained at employer level. The contract links the investor account to the employer arrangement, and the employer arrangement links to the employer; this relation is sufficient to determine the applicable employer IBAN for deposits. This prevents employer bank account changes from requiring updates to all related contracts.

• Storage of one or more IBANs per employer.
• A single employer may use multiple bank accounts for deposits to different investor accounts.
• Employer bank account changes will be managed at employer level and will apply through the existing employer arrangement and contract relations.

4️⃣5️⃣ Employer Retrieval via API

The system will expose API endpoints that allow retrieval of all employers, optionally including their employer arrangement(s), products, and contracts.

• Must Have: Retrieve all employers, with optional inclusion of employer arrangement data.
• Must Have: Retrieve employer arrangements, with optional inclusion of product and contract data.

4️⃣6️⃣ PERIODICITY

The employer contribution will support the following recurrence options:

• One-off: A single deposit with no recurrence
• Monthly: A contribution expected once per calendar month
• Quarterly: A contribution expected once per calendar quarter
• Annually: A contribution expected once per calendar year

The periodicity defines the frequency at which the system expects to receive and verify an employer deposit. It does not trigger direct debit.

4️⃣7️⃣ DATA REQUIREMENTS

The following data fields will be available:

Employer

• Employer Code - free-text field, unique identifier.
• Employer Name.
• One or more bank accounts.
• Status - active and inactive.

Employer Arrangement

• Employer.
• Product(s).
• Employer Arrangement Code - free-text field, unique identifier.
• Employer Arrangement Name - free-text field.
• Employer Contribution Allowed - true or false.
• Default Withdrawal Block - true or false.
• Withdrawal Block Threshold Condition - flexible input.
• Deviation Threshold - percentage.
• Inactive Date - optional date.
• Override Permissions - configurable list of properties that may be overridden at contract level.

Contract

• Employer Arrangement.
• Investor Account.
• Employee Number - External ID property.
• Status - active, inactive, terminated.
• Employer Contribution Amount.
• Contribution Periodicity.
• Employer Contribution Active - true or false.
• Withdrawal Block - not set, true or false.
• Withdrawal Block End Date - optional end date.

Investor Account

• Contract.
• Employer.

4️⃣8️⃣ DATA MIGRATION

Existing employers, employer arrangements, contracts, and investor account data will be migrated. The following migration considerations apply:

• All existing employers and their employer arrangements will be migrated to the new data model, including employer arrangement code, name, contribution flags, and withdrawal block.
• Existing investor account – employer and investor account – employer arrangement connections will be converted into contracts and validated post-migration.
• Employee numbers, where recorded, will be migrated to the contract.
• Historical contributions will be available in the new system for verification and audit purposes.

5️⃣ BUSINESS RULES

The following business rules will be enforced by the system:

• BR-01 - Mandatory employer at onboarding Employer and employer arrangement are mandatory at onboarding for employer relation products. A missing reference will be rejected.
• BR-02 - One active contract per investor account An investor account can have only one active contract for an employer relation product.
• BR-03 - Employment deregistration is backoffice-only Deregistering employment is a manual backoffice process, not available for investors.
• BR-04 - Withdrawal block is enforced An active withdrawal block will be enforced by the system.
• BR-05 - Backoffice may override withdrawal block Exceptions per contract are permitted when allowed by the employer arrangement. Overrides will be logged for audit.
• BR-06 - Annuity products require a withdrawal block Mandatory for annuity products, supplementary for net products.
• BR-07 - Employer contribution is deposit only No direct debit is used; the employer initiates the transfer. The system stores the expected amount for verification only.
• BR-08 - Contribution deviation triggers manual review A deviation greater than the configurable threshold will be flagged, and backoffice can initiate reversal. The threshold will be configurable.
• BR-09 - Multiple employer arrangements per employer permitted One employer may hold multiple employer arrangements; no duplication of the employer is required.
• BR-10 - Employee number stored at contract The employee number is stored at the contract to support investors with multiple investor accounts across employers.
• BR-11 - Multiple employer bank accounts permitted An employer may have multiple bank accounts registered. Employer bank accounts are maintained at employer level and are not duplicated on contracts.
• BR-12 - Withdrawal Block The end date threshold for the withdrawal block should support: x months after the investor account holder’s date of birth.
• BR-13 - Employer arrangement override permissions Employer arrangements define which properties may be overridden at contract level.