Modelling an accumulation dividend (ACCU)

You can model an accumulation dividend as a corporate action of type AccumulationEvent in LUSID. See all supported corporate actions.

Note the following:

• AccumulationEvent is valid for instruments of type Equity and SimpleInstrument.

• An accumulation dividend is declared but never distributed. The fund retains the income and reinvests it internally, so the holder receives neither cash nor additional units. Use CashDividendEvent (DVCA) instead if the dividend is paid out as cash, and DividendOptionEvent (DVOP) or DividendReinvestmentEvent (DRIP) where the holder receives new units.

• The entitlement date is the exDate specified when you load AccumulationEvent.

• The accumulation amount is calculated from the total number of instrument units held on the entitlement date, settled and unsettled.

• Unlike other dividend events, AccumulationEvent has no election lists. You set the dividend currency and rate directly on the event itself.

• We recommend setting paymentDate equal to exDate. LUSID processes the cost adjustment on the ex-date, and as there is no cash settlement there is no period during which an unsettled cash commitment should appear in a valuation.

Loading AccumulationEvent

You must load AccumulationEvent into a corporate action source registered with one or more portfolios. The event then impacts every registered portfolio with a holding in the underlying instrument. See how to do this.

For more information on fields, see the AccumulationEvent schema. Where set, the following date validation rules apply: announcementDate ≤ exDate ≤ paymentDate

Only one participation type is valid, with no elections:

Because there are no elections, there is nothing to choose and nothing to lapse. Every registered portfolio holding the instrument on the ex-date receives the cost adjustment, and you cannot instruct a different outcome for a particular portfolio using an event instruction.

Configuring the economic impact

You must create a FundAccumulationIncome transaction type to handle the automatically-generated output transaction. This is not provided for you. See our recommendation.

You can give a transaction type any economic impact you like. Our recommendation:

• Increases the cost basis of the existing holding in the underlying instrument by the accumulation amount, using a StockMovement.

• Reports the same amount as income against that instrument, using a Carry movement.

• Does not create or update a cash holding, because no cash is paid.

• Does not change the number of units held.

Reference example

[
  {
    "instrumentEventId": "ACCU-GLOBALFUND-2026",
    "instrumentIdentifiers": {
      "Instrument/default/Isin": "IE0000669501"
    },
    "description": "Global Fund Acc share class (0.1594 EUR per unit, retained by the fund)",
    "participationType": "Mandatory",
    "instrumentEvent": {
      "instrumentEventType": "AccumulationEvent",
      "announcementDate": "2026-08-01T00:00:00.0000000+00:00",
      "exDate": "2026-08-15T00:00:00.0000000+00:00",
      "paymentDate": "2026-08-15T00:00:00.0000000+00:00",
      "dividendCurrency": "EUR",
      "dividendRate": 0.1594
    }
  }
]