B_02.01 — Contractual arrangements general

Purpose

This template serves as the central registry of all ICT contractual arrangements. Each row represents one contract between the financial entity (or group) and an ICT third-party service provider.

Contracts are classified into three types:

  • CA_1 — Standalone arrangement (not linked to any overarching contract)
  • CA_2 — Overarching arrangement (master agreement)
  • CA_3 — Subsequent arrangement (linked to an overarching CA_2 contract)

The procurement or vendor management team typically maintains this template, with input from legal and compliance. It should be updated whenever new contracts are signed, renewed, or terminated.

Fields Reference

CodeField NameTypeReq.Description
c0010Contractual arrangement reference number*textYes
Unique reference number for the contractual arrangement
Max length: 255
c0020Type of contractual arrangement*selectYes
Whether standalone, overarching, or subsequent agreement
Show 3 allowed values
  • CA_1Standalone
  • CA_2Overarching/Master agreement
  • CA_3Subsequent/Associated agreement
c0030Overarching contractual arrangement reference numbertextNo
Reference number of the overarching arrangement (if subsequent)
Max length: 255
c0040Currency of the annual expense or estimated cost*currencyYes
Currency for monetary values (ISO 4217)
c0050Annual expense or estimated cost*monetaryYes
Annual expense or estimated cost of the arrangement

Relationships

Validation Rules

  • CA_3 must reference an overarching arrangement. Any contract of type CA_3 must have its overarching arrangement reference field populated with a valid reference to a CA_2 contract in this same template.
  • CA_1 must NOT reference an overarching arrangement. Standalone contracts should have an empty overarching reference field. Populating it for CA_1 creates a logical inconsistency.
  • Unique arrangement references. Each contract must have a unique reference identifier within the register.
  • Currency must be valid ISO 4217. When a cost is specified, the currency code must be a valid ISO 4217 three-letter code.

Example

FieldValue
Arrangement ReferenceCA-2025-001
TypeCA_1 (Standalone)
Overarching Reference(empty)
CurrencyEUR
Annual Cost50,000

Common Mistakes

  • CA_3 without overarching reference. Subsequent arrangements must always be linked to their parent CA_2 contract. Missing this link is the most common error.
  • Missing currency for cost. When an annual cost is provided, the currency field is mandatory. Leaving it blank triggers a validation error.
  • Incorrect arrangement type. Classifying a master agreement as CA_1 instead of CA_2 breaks the linking logic for all its subsequent CA_3 arrangements.