SIVI message 2 (0001b): Cashflow (VB-PUO)

Rules and consistency checks

• Since the final Release 2027 every cashflow block carries netAmount and netDate: directly under the scheme, per cohort and per investment portfolio. contributionAmount and withdrawalAmount are an optional addition, under the scheme and per portfolio with contributionDate and withdrawalDate; SIVI's own sample message fills all three. netAmount is the balance of contribution and withdrawal, so three amounts that do not match contradict each other. In Release 2026 the balance, the separate flows or both are allowed.
• In both routes the total sits directly under the scheme (financialTransaction.cashflow). What excludes each other per scheme is the breakdown: per cohort (SPR route; the amounts sit on the cohort itself) or per investment portfolio (FPR route; every portfolio used has exactly one cashflow). A message that uses both breakdowns within one scheme is "niet geldig" (not valid). The breakdown itself is optional in message 2, but every scheme carries at least one cashflow (manual sections 6.3.1 and 3.2.5).
• When the cashflow is broken down per cohort, the cohort amounts add up to the amount at scheme level. Release 2027 makes that a consistency check (manual sections 6.3.1 and 3.2.5: scheme.netAmount is the sum of cohort.netAmount, and the same for contributionAmount and withdrawalAmount); in Release 2026 it is a reconciliation the receiver can check. In the FPR route the total carries, as a rule, the sum of the portfolios, but whether it must add up is "niet vastgelegd" (not laid down). Mind contributionAmount and withdrawalAmount: the inflow and outflow of a cohort also hold the shifts between cohorts (section 3.2.2); those cancel out in netAmount, not in inflow and outflow separately. Keep the cohort structure the same as in message 1.
• All dates fall within the reporting period (financialInformation.reportingPeriod.startDate to endDate).

Pitfalls

• A prospective message (expected flows) that is not followed later by the realised flows leaves the investment administration with an estimate; agree which variant is leading.
• netDate is often missing, especially per cohort. Since the final Release 2027 that is a schema error: netAmount and netDate are mandatory in every cashflow block. The published schema only counts the valid cohorts (issue #63), so a generic validator lets it pass; a receiver that checks every cohort does not. SIVI's own pre-release sample had this defect.

Errors and fixes

• messageId missing, empty or longer than 70 charactersSchema error on commonTechnical/0/messageId: 'must have required property' or 'must NOT have more than 70 characters'.
• Duplicate messageId after acceptance (HTTP 400 with feedback)The receiver answers HTTP 400 with a feedback message (statusType 0) to a message that looks correct in content.
• afdDefinitionName incorrect (a fixed value since the final Release 2027)Schema error 'must be equal to constant' on afdDefinitionName; the WTP Data Lab validator names the expected value. Typical of a message built on the July 2026 pre-release: it states the right version 001.05 and still fails.
• afdDefinitionVersion incorrect (001.04 versus 001.05)Schema error 'must be equal to one of the allowed values' on afdDefinitionVersion, or the receiver validates against the wrong schema and reports unknown fields.
• startAmount not in two decimals (multipleOf 0.01)Schema error 'must be multiple of 0.01'.
• reportingPeriod: endDate before startDateThe schema accepts the message; the receiver rejects it functionally or books the flows in the wrong period.
• Cohort cardinality exceeded (minContains / maxContains)Schema error 'must contain at least 1 valid item' or 'must contain at most 99999 valid items' on pension.
• participationStatus invalid (ADNDNS)Schema error 'must match exactly one schema in oneOf' on pension.cohort.participationStatus.
• reserveType invalid (AFDRES)Schema error 'must match exactly one schema in oneOf' on reserveType.
• reserveIndicator without reserveType, or reserveType 99 without reserveDescriptionUnder Release 2027 an error of the consistency check at reserveType. Under Release 2026 schema-valid, but the receiver cannot type the reserve and books it as an ordinary cohort; with reserveType 99 without a description it cannot tell which reserve is meant.
• endAge smaller than startAge, or not an integerWith decimals a schema error 'must be integer'; with swapped bounds the schema accepts and the receiver rejects.
• Cohort sum deviates from the scheme totalSchema-valid, but the fiduciary or investment administrator reports a reconciliation difference at scheme level.
• netAmount is not the balance of contributionAmount and withdrawalAmountSchema-valid; the receiver does not know which amount is leading, or double-counts the flows.
• netAmount or netDate missing in a cashflow block (message 2)Schema error 'must have required property' on netDate or netAmount, at a cohort, at the cashflow under the scheme or at an investment portfolio. A generic JSON Schema validator often misses the error at a cohort.
• Scheme with both cohorts and portfolios, or without a breakdown or cashflow (messages 2 and 3)Schema-valid, but the receiver cannot assign the flows or the projection to the right route. The WTP Data Lab validator reports an error at the scheme.
• Error discovered after acceptance: the correction protocolAn accepted and processed message turns out to be wrong in content (wrong amount, wrong cohort).

Difference from Release 2026 (001.04 → 001.05)

Entities added: investment.portfolio

Attributes added: investment.portfolio.refKey, investment.portfolio.description, pension.cohort.netDate

Obligation changed: financialTransaction.cashflow.netAmount (O → V), financialTransaction.cashflow.netDate (O → V), pension.cohort.netAmount (O → V)

Change history

• v1.3.0 (Release 2026): netDate documentation (issue #82); chunking.
• v1.4.0 (Release 2027): SPR route and FPR route; JSON Schema 2020-12.
• Final Release 2027 (12 October 2026): netAmount and netDate mandatory in every cashflow block, also per cohort; the cashflow per portfolio may also carry inflow and outflow; the routes in section 6.3.1 and the new section 3.2.5.

Schema file: VBPUO-001.00-Bericht_2._Cashflow_(0001b).json · JSON-schema (001.05) · GitHub