Annuity Capital Transfer - PSK

Business Requirements Document (BRD)

🧩 Annuity Capital Transfer - PSK

🔖 1.1

📅 Thursday, 11 June 2026

👤 Martijn Bruitsman, Peter Disselkoen, Bernard Bos

⚙️ Thimon van der Sluis

1️⃣ PURPOSE

This document defines the business requirements for Annuity Capital Transfers of type PSK (Protocol Stroomlijning Kapitaaloverdrachten). PSK is an industry protocol established by the Verbond van Verzekeraars and the Nederlandse Vereniging van Banken, governing the tax-neutral transfer of capital from fiscally facilitated products — such as annuity capital (lijfrentekapitaal) — between participating financial institutions.

This Epic covers the registration and storage of PSK form data for incoming Annuity Capital Transfers to GiroPro investor accounts and investors. The primary goals are to ensure all relevant PSK form fields are stored within the investor, to maintain visibility of historical transfer data within GiroPro, and to lay the data foundation required for future automation of outgoing Annuity Capital Transfers and PSK form generation.

2️⃣ SCOPE

The Annuity Capital Transfer of type PSK covers the following functional areas:

• Registration and storage of PSK form data to an investor.
• Linking of PSK records to the corresponding deposit, documents, bank transaction, and journal entries.
• Storage of fiscal policy details as provided on the PSK form.
• Support for incoming Annuity Capital Transfer of type PSK initiated by an external transferring party.

The following is explicitly out of scope for this Epic:

• Outgoing Annuity Capital Transfers; the data model is designed to support this in the future, but the outgoing process itself is not in scope.
  • It is possible to manually transfer outgoing annuity capital with journal entries.
• Generation of outgoing PSK forms.
  • This is a future capability enabled by the data stored by implementing this epic.
• Direct debit or payment initiation.
  • Annuity Capital Transfers are received and processed as an incoming deposit only.
• Validation or enforcement of PSK protocol timelines.
• Communication with external transferring parties.

3️⃣ GLOSSARY

The following terms are used throughout this document:

• Label The party responsible for administering and managing the investor’s investments.
• Investor Individual investor account holder who is transferring fiscally facilitated capital.
• Investor Account The account held by an investor, to which the PSK record and incoming Annuity Capital Transfer are linked.
• PSK (Protocol Stroomlijning Kapitaaloverdrachten) Industry protocol established by the Verbond van Verzekeraars and the Nederlandse Vereniging van Banken. Governing the tax-neutral transfer of capital between participating financial institutions.
• PSK Form The standardised transfer form as defined by the PSK protocol. Completed by the transferring party and accompanying the capital transfer. It contains fiscal policy details required by the receiving party.
• Transferring Party The financial institution (bank, insurer, or investment firm) transferring the annuity capital from the existing party to a different party.
• Deposit Incoming bank transfer to an investor account, in this context representing the transferred capital amount.
• Incoming Annuity Capital Transfer A deposit received from a transferring party on behalf of an investor, accompanied by a PSK form.
• Annuity Capital (Lijfrentekapitaal) Capital accumulated in a fiscally facilitated annuity product, eligible for tax-neutral transfer under the PSK protocol.
• Premium Period Indicators Fields on the PSK form denoting in which fiscal periods premiums were paid.
• Capital Reference Values The value of the capital at specific reference dates as recorded on the PSK form:
  • Value per 31 December 2005 and value per 31 December 2013.
• Document A file stored in the document service, in this context the scanned or digital PSK form linked to the PSK record.
• Journal Entry A ledger journal entry representing the financial booking of the Annuity Capital Transfer.
• Backoffice Internal operations team responsible for manual registration and processing of PSK records.
• Reference Documentation Protocol Stroomlijning Kapitaaloverdrachten (PSK) (PDF) Protocol Stroomlijning Kapitaaloverdrachten (PSK)

4️⃣ FUNCTIONAL REQUIREMENTS

4️⃣1️⃣ PSK Record Management

When an incoming capital transfer is received, the backoffice will register the PSK form data against the relevant investor account and investor. Each PSK record is linked to exactly one investor account and one investor and represents the data from a single PSK form. The system will support storage of all fields present on the PSK form to ensure fiscal traceability and to enable future outgoing PSK form generation.

The following operations will be supported:

• Create and update PSK Record The backoffice will be able to create a PSK record for an investor account, capturing all fields from the received PSK form.
• Link to Deposit The PSK record will be linked to the corresponding incoming deposit on the investor account.
• Link to Document The PSK record will be linked to corresponding documents uploaded in the document service, representing the scanned or digital PSK form.
• Link to Journal Entry The PSK record will be linked to the corresponding journal entries.
• Audit History All backoffice mutations on PSK records are logged and visible in the history service.
• Approval All backoffice mutations on PSK records can be reviewed by enabling approval.

4️⃣2️⃣ PSK Record Data

The PSK record stores all required data fields from the PSK form as provided by the transferring party. The data is registered by the backoffice and is not editable (read-only) by the investor.

Data that appears irrelevant at the time of an incoming capital transfer may become required when the capital is transferred again in the future. For example, when acting as the transferring party for an outgoing capital transfer.

The following fields will be stored:

Investor

• Investor Reference to the investor.
• Investor Account Reference to the investor account to which the PSK record belongs.

Transferring Party

• Transferring Party Name Name of the financial institution transferring the capital, as stated on the PSK form.
• Transferring Party Policy Number (Polisnummer) The policy or account number assigned by the transferring party. Required for future outgoing PSK form generation and for traceability back to the originating institution.

Transfer Details

• Policy End Date End date of the annuity capital policy at the transferring party.
• Transfer Value (Overdrachtswaarde) The capital value at the moment of transfer, as stated on the PSK form.
• Termination Value (Beëindigingswaarde) The value of the capital at the moment the policy was terminated at the transferring party. May differ from the transfer value due to interest accrued during the transfer period.
• Total Deposit Amount The total amount actually deposited to the GiroPro investor account, including any interest accrued by the transferring party during the transfer period.
• Payment Date The date on which the transferring party executed the payment.

Fiscal Policy Details

• Fiscal Policy Start Date (Fiscale Ingangsdatum) The date on which the original policy fiscally commenced. Required for fiscal continuity and for future outgoing PSK form generation.
• Policy Term Extended (LooptijdVerlengd) Indicating whether the term of the annuity policy was extended at any point during its lifetime. Relevant for oud regime (pre-2001) policies, where a term extension has fiscal implications.
• Built Up Before 2001 (OpgebouwdVoor2001) Indicating whether capital was accumulated before 1 January 2001.
• Built Up Before 2006 (OpgebouwdVoor2006) Indicating whether capital was accumulated before 1 January 2006. Relevant for the overbruggingslijfrente regime.
• Built Up Before 2014 (OpgebouwdVoor2014) Indicating whether capital was accumulated before 1 January 2014. Relevant for investors who wish to commence annuity payments before the AOW date but no earlier than the calendar year in which they reach age 65.
• Premiums Paid From 1-1-2001 (Vanaf1-1-2001PremieVoldaan) Indicating whether premiums were paid in the fiscal period starting 1 January 2001.
• Premiums Paid From 1-1-2006 (Vanaf1-1-2006PremieVoldaan) Indicating whether premiums were paid in the fiscal period starting 1 January 2006.
• Premiums Paid From 1-1-2014 (Vanaf1-1-2014PremieVoldaan) Indicating whether premiums were paid in the fiscal period starting 1 January 2014.
• Capital Value Per 31-12-2005 (WaardePer31-12-2005) The value of the capital as at 31 December 2005. Relevant for the overbruggingslijfrente regime. Null if not known or not applicable.
• Capital Value Per 31-12-2013 (WaardePer31-12-2013) The value of the capital as at 31 December 2013. Null if not known or not applicable.
• Remarks Free-text field for additional information or special conditions noted on the PSK form, this is explicitly required to be present on every PSK form.

4️⃣3️⃣ PSK Record References

The PSK record maintains references to related entities. These references ensure full traceability from the PSK form data through to the financial processing of the incoming Annuity Capital Transfer.

The following references will be stored on the PSK record:

• Investor Reference to the applicable investor.
• Investor Account Reference to the investor account to which the PSK record belongs.
• Document Reference to the uploaded documents.
• Banking Reference to the bank statement entry.
• Journal Entry Reference to the journal entries involved in the processing cycle.

4️⃣4️⃣ Retrieval via API

The system will expose API endpoints that allow retrieval of PSK records per label or investor account, and retrieval of PSK records by policy number or transferring party name.

4️⃣5️⃣ DATA MIGRATION

Existing PSK records stored in the current system will be migrated to the new data model. The following migration considerations apply:

• All existing PSK records will be migrated and linked to the corresponding investor account and investor.
• Migrated records will be mapped to the new data model fields as defined in section 4️⃣2️⃣.
  • Fields that were not captured in the current system will be left null where permitted.
• Existing links between PSK records and their corresponding deposits will be preserved and validated post-migration.
• If a PSK record exists and a corresponding document is available in the document archive, the document will be referenced.

5️⃣ BUSINESS RULES

The following business rules will be enforced by the system:

• BR-01 — PSK record is linked to one investor account and one investor
  • A PSK record is linked to exactly one investor account and one investor.
  • An investor account and investor may have multiple PSK records (multiple incoming capital transfers).
• BR-02 — PSK record management is backoffice-only
  • Creating and updating PSK records is a manual backoffice process, not available to investors.
  • Investors have read-only access to PSK records linked to them.
• BR-03 — All required PSK form fields must be stored All required fields — section 4️⃣2️⃣ — present on the received PSK form must be stored.
  • Fields not applicable may be left null.
  • Irrelevant data at the time of receipt must still be stored, to enable future outgoing Annuity Capital Transfers.
• BR-04 — Capital reference values are null when not applicable For example, WaardePer31-12-2005 and WaardePer31-12-2013 are stored as null when not known.
• BR-05 — PSK registration does not trigger direct debit
  • The Annuity Capital Transfer is received as an incoming deposit only.
  • GiroPro does not initiate the payment as part of the incoming PSK process.
• BR-06 — Deposit must be marked as capital transfer Deposits linked to a PSK record are marked as accrued benefits (waardeoverdracht) to ensure exclusion from tax reporting.
• BR-07 — Manual backoffice mutations are logged
  • All manual backoffice mutations on PSK records are logged and visible in the history service.
  • All manual backoffice mutations will have a configurable approval setting.