You can model a consent solicitation, or the fee paid after a bondholder meeting, as a corporate action of type ConsentEvent in LUSID. See all supported corporate actions.
Note the following:
ConsentEventis valid for instruments of typeBond,ComplexBond,InflationLinkedBond,EquityandSimpleInstrument.The entitlement date is the
recordDatespecified when you loadConsentEvent.Fee amounts are calculated from the number of settled instrument units held on the entitlement date. Unsettled units are not eligible.
A consent does not change the holding itself. The only economic impact is a cash fee, and only if the issuer offers one and the chosen election carries it. If no fee applies, LUSID generates no transaction.
For bonds, fees are quoted per 1,000 of face value. LUSID uses the current notional on the
recordDate: the principal for aBond, the amortised face for aComplexBondand the inflation-adjusted face for anInflationLinkedBond. For equities and simple instruments, fees are quoted per unit.The transaction date of the automatically-generated output transaction is
recordDate, and the settlement date ispaymentDate.Optionally, set
consentTypetoChangeInTerms(the issuer seeks consent to change the terms, such as a covenant) orDueAndPayable(the issuer seeks consent to change the due-and-payable conditions). It is for information only and does not affect the economic impact. If you omit it, LUSID recordsUnknown.
Loading ConsentEvent
You must load ConsentEvent 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 ConsentEvent schema. Where set, the following date validation rules apply:earlyResponseDeadline < responseDeadline ≤ marketDeadline
Note:
paymentDateis required if any election carries a fee, that is, anyCashOfferElectionor anyConsentGrantedElectionwith aconsentFeePrice. Otherwise, it must be omitted, or LUSID rejects the event.
You must choose one of the following participation types:
Participation type | Election(s) | Election choices | Further action required? |
|---|---|---|---|
| Exactly one | Set the following on the single election: ✅ Is chosen | ❌ No. The single election always occurs automatically, and pays the fee to every eligible holder. You cannot instruct a |
| At least one
Election keys are free-form, but must be unique across every election on the event. | Set the following on every election: ❌ Is default You can set the following on at most one election: ✅ Is chosen | ❓Depends. If an election has Is chosen set, it occurs unless you instruct to take a different election per portfolio. If not, you must instruct, else no election occurs and no fee is received. |
Note that, once the issuer's consent threshold is reached, the proposed change binds every holder, whichever election they took. LUSID does not model the change itself; if it alters the terms of the instrument, update the instrument separately.
Use Mandatory when a fee is paid to every eligible holder without an instruction, for example a fee announced after a bondholder meeting. If the fee is paid only to holders who instructed, use a Voluntary event. Do not also load a Mandatory event confirming that payment, or instructed holdings are paid twice.
Some issuers offer a higher fee for consenting before an early deadline. To model this, specify one election per fee, for example two ConsentGrantedElection with different keys and fees, and set earlyResponseDeadline for information.
Instructing to take a different election per portfolio
If you load ConsentEvent as Voluntary, you can instruct a particular portfolio to take an election. If you do not, the portfolio takes the chosen election, or no election if none is chosen.
To do this, load an event instruction into a portfolio. Note this is not an event, and you do not load it into a corporate action source, which means you can instruct differently in different portfolios. See how to do this.
Note the instructionType must be ElectForHolding or ElectForPortfolio, with electionKey set to the key of the election you want.
Configuring the economic impact
You should create a ConsentAccept transaction type to handle the output transaction that is automatically generated by the following elections. This is not provided for you. See our recommendation.
Chosen election | Transaction generated? | Amount |
|---|---|---|
| ✅ Yes |
|
| ✅ Yes |
|
| ❌ No | N/A |
| ❌ No | N/A |
The transaction is booked against the underlying instrument, with units equal to the eligible units and a price of zero. If the holding is short, the amount is negative.
You can give a transaction type any economic impact you like. Our recommendation:
Creates or updates a cash holding in the fee currency.
Reports the cash as income using the
ProfitAndLoss/Total/Othermetric.Does not change the units and cost of the underlying instrument, so
ProfitAndLoss/Realised/*andProfitAndLoss/Unrealised/*metrics are unchanged.
Reference examples
A consent solicitation with a fee for consenting
An issuer seeks consent to change the terms of a bond, and pays USD 2.50 per 1,000 of face to holders who consent. Holders can also deny consent, abstain or take no action, none of which pays a fee. No election is chosen, so each portfolio must be instructed.
[
{
"instrumentEventId": "CONS-ACMEBOND-2026",
"instrumentIdentifiers": {
"Instrument/default/ClientInternal": "ACMECORP-BOND-2031"
},
"description": "Consent solicitation - Acme Corp 2031 bond (change in terms, USD 2.50 per 1,000 for consenting)",
"participationType": "Voluntary",
"instrumentEvent": {
"instrumentEventType": "ConsentEvent",
"consentType": "ChangeInTerms",
"recordDate": "2026-08-01T00:00:00.0000000+00:00",
"responseDeadline": "2026-08-15T00:00:00.0000000+00:00",
"marketDeadline": "2026-08-15T00:00:00.0000000+00:00",
"paymentDate": "2026-08-20T00:00:00.0000000+00:00",
"consentGrantedElections": [
{
"electionKey": "CONY",
"isDefault": false,
"isChosen": false,
"consentFeePrice": 2.50,
"consentFeeCurrency": "USD"
}
],
"consentDeniedElections": [
{ "electionKey": "CONN", "isDefault": false, "isChosen": false }
],
"abstainElections": [
{ "electionKey": "ABST", "isDefault": false, "isChosen": false }
],
"lapseElections": [
{ "electionKey": "NOAC", "isDefault": false, "isChosen": false }
]
}
}
]A portfolio holding 1,000,000 settled units of a bond with a principal of 1 on 1 August 2026, instructed to take CONY, receives USD 2,500.00 (2.50 ÷ 1,000 × 1 × 1,000,000), with a transaction date of 1 August 2026, settling on 20 August 2026. A portfolio instructed to take CONN, ABST or NOAC, or not instructed at all, receives nothing.
A fee paid to every holder after a bondholder meeting
A bondholder meeting pays GBP 0.50 per 1,000 of face to every holder on the record date, without an instruction. There is no instruction window, so set responseDeadline and marketDeadline equal to recordDate.
[
{
"instrumentEventId": "CONS-OSPREY-2021-FEE",
"instrumentIdentifiers": {
"Instrument/default/ClientInternal": "OSPREY-BOND"
},
"description": "Bondholder meeting fee - GBP 0.50 per 1,000 paid to all holders",
"participationType": "Mandatory",
"instrumentEvent": {
"instrumentEventType": "ConsentEvent",
"consentType": "ChangeInTerms",
"recordDate": "2021-09-02T00:00:00.0000000+00:00",
"responseDeadline": "2021-09-02T00:00:00.0000000+00:00",
"marketDeadline": "2021-09-02T00:00:00.0000000+00:00",
"paymentDate": "2021-09-17T00:00:00.0000000+00:00",
"cashOfferElections": [
{
"electionKey": "CASH",
"isDefault": true,
"isChosen": true,
"cashOfferPrice": 0.50,
"cashOfferCurrency": "GBP"
}
]
}
}
]A portfolio holding 147,000 settled units of a bond with a principal of 1 on 2 September 2021 receives GBP 73.50 (0.50 ÷ 1,000 × 1 × 147,000), settling on 17 September 2021. A portfolio short 147,000 units pays GBP 73.50.