Employer Relation

Business Requirements Document (BRD)

🧩 Employer Relation

🔖 1.2

📅 Friday, 22 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, 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 employers and employer arrangements.
• Employer contribution, periodicity, and deviation validation.
• Withdrawal blocks enforced at the employer arrangement level.
• Registration of employer bank accounts.
• Employee number per investor account.
• Employer switching and employer arrangement correction processes.
• Retrieval of employers and employer arrangements.
• Deactivation of employer arrangements.

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 a participating employer.
• Employer Company that offers an employer arrangement to its employees for making investments.
• Employer Arrangement Arrangement configuration applicable to all investor accounts connected to that employer arrangement. Employer can have multiple employer arrangements, investor account can have only one employer arrangement.
• Investor Account Investor account of an investor, to which an employer and employer arrangement are connected.
• Employer Contribution Periodical 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 (selling assets). This can be ended with a defined date.
• 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️⃣1️⃣ Investor Account – Employer Relationship

At onboarding, each investor account will be linked to exactly one employer and one employer arrangement. For products that involve an employer relation, providing the employer at onboarding is mandatory. The cardinality of the relationship is as follows: an employer and employer arrangement may have zero or more linked investor accounts, an investor account has one employer and one employer arrangement. The absence of a linked employer and employer arrangement is valid and represents the state in which the investor is no longer employed by an 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. Employer contribution functionality and any applicable withdrawal block will be removed from the investor account.
• Employer Switch Investor account will be connected to a different employer when they change jobs, if the new employer is or can be registered in the system. This action will be a manual backoffice process.
• Correction of Incorrect Onboarding It will be possible to correct an incorrect assigned employer or employer arrangement at onboarding. This action will be a manual backoffice process.
• Employee Number The system will allow storage of an employee number per investor account. The external id can be used for this. It accommodates an investor to have multiple investor accounts if they work for multiple participating employers.
• Audit History All manual backoffice mutations are logged and visible in the history service.

4️⃣2️⃣ Employer Arrangement Structure

Employer properties are stored directly in the employer entity. The separate configuration called an employer arrangement makes variations possible. Investor account is linked to both an employer and 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 Arrangement Name Free-text field, used as common identifier.
• Employer Reference to the employer entity.
• Employer Arrangement Code Free-text field, used as additional 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.
• Inactive Date Date from which onboarding for this employer arrangement is closed.
• Deviation Threshold Maximum allowed deviation percentage between the expected and actual employer contribution.

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

The system will be able to process the desired employer contribution per investor account. This contribution may be one-off or recurring. The contribution is processed as a deposit per investor account and 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 verified 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 not allocate the deposit and offer the option to manually reverse or allocate it.
• Power of Attorney When a power of attorney is needed the employer contribution can be allowed or disallowed. Optionally a document can be uploaded to the applicable investor account.

4️⃣4️⃣ Employer Bank Account Registration

The employer bank account will be connected to the investor account’s bank accounts for deposits, the following will be supported:

• Storage of one or more bank accounts per employer, linked to the applicable investor account.
• A single employer may use multiple bank accounts for deposits to different investor accounts.
• Employer bank accounts are managed at employer level and automatically synced to linked investor accounts.

4️⃣5️⃣ Employer Retrieval via API

The system will expose an API endpoint that allows retrieval of all employers, optionally including their employer arrangement(s).

4️⃣6️⃣ PERIODICITY

The employer contribution will support the following recurrence options:

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

The periodicity defines the expected frequency of employer contributions. The system does not actively monitor the recurrence or initiate direct debits, but it does validate whether deposit amounts fall within the configured deviation threshold.

4️⃣7️⃣ DATA REQUIREMENTS

The following data fields will be available:

Employer

• Employer Code - free-text field, unique identifier.
• Employer Name - name of the employer.
• One or more bank accounts - bank account entity.
• Status - active and inactive.

Employer Arrangement

• Employer - employer entity.
• Employer Arrangement Code - free-text field, unique identifier.
• Employer Arrangement Name - free-text field.
• Employer Contribution Allowed - true or false.
• Employer Contribution Deviation Threshold - percentage.
• Withdrawal Block Active - true or false.
• Withdrawal Block Period (number of months after date of birth) - number.
• Inactive Date - date (optional).

Investor Account

• Employer.
• Employer Arrangement.
• Employee Number - external id property.
• Status - active, inactive, closed.
• Employer Bank Account - connected as bank account for deposits.
• Employer Contribution Periodicity - recurrence.

Employer arrangement properties that can be overridden per investor account.

• Employer Contribution Allowed - true or false.
• Employer Contribution Amount - number
• Employer Contribution Deviation Threshold - percentage.
• Withdrawal Block Active - true or false.
• Withdrawal Block End Date - date.
• Inactive Date - date (optional).

Investor Account Contract

A contract is a system-generated summary entity linked to an investor account. It consolidates investor account configuration and restrictions into a single representation. A contract is automatically created when an investor account is created and automatically updated whenever the related investor account configuration changes. The contract primarily serves as an aggregation layer for downstream processing and integrations. It does not contain business functionality itself and is not used for transactional or decision-making logic within. It is not directly editable and is not exposed in the user interface and only accessible via the API as part of an investor account.

The contract contains configuration data such as:

• Linked product.
• Overriding cost plan.
• Excluded assets.
• Validity dates.

The employer relation data, the employer and employer arrangement, will be added to the contract.

4️⃣8️⃣ DATA MIGRATION

Existing employers, employer arrangements, 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 preserved and validated post-migration.
• Employer bank accounts currently stored at investor accounts will be migrated.
• Employee numbers, where recorded, will be migrated to the investor account.
• 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 and employer arrangement at onboarding An employer and employer arrangement is mandatory at onboarding for employer relation investor accounts. Missing references will be rejected.
• BR-02 - One employer and one employer arrangement per investor account Investor account may be linked to at most one employer and one employer arrangement.
• 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 Variations per investor account are permitted, manual backoffice changes will be logged in the history service.
• BR-06 - Annuity products require a withdrawal block Mandatory for annuity products, supplementary for net products.
• BR-07 - Employer contribution is deposit only Direct debit is not supported, an employer initiates the deposit. The expected amount is stored for validation only.
• BR-08 - Contribution deviation triggers manual review Deviations exceeding the configurable threshold are not processed, allowing the backoffice to initiate a reversal or manual processing.
• BR-09 - Multiple employer arrangements per employer permitted One employer may hold multiple employer arrangements, no duplication of employer required.
• BR-10 - Employee number stored at investor account Employee number is stored at the investor account to support investors with multiple investor accounts across employers.
• BR-11 - Multiple employer bank accounts permitted An employer may register multiple bank accounts.
• BR-12 - Manual backoffice mutations All manual backoffice mutations are logged and visible within the history service. All manual backoffice mutations will have a configurable approval setting.