INDUSTRY FIELD GUIDE
Custody corporate action records for AI testing
A custody message may announce a corporate action before positions or terms needed for an entitlement review are available.
NAICS 523991 · Trust, Fiduciary, and Custody Activities
A custody message may announce a corporate action before positions or terms needed for an entitlement review are available. DTCC publishes event and distribution documentation. A custodian can build a synthetic exception that tests identity, date, and event status while keeping real positions private. DTCC corporate action documentation · DTCC distributions overview
Create a fictional event announcement with an explicitly labeled record date and a holdings file for two dates. Include a revised event identifier and a similar action involving another security. Ask which mock holding and event records apply and which evidence remains unverified. The model should produce a review packet without initiating an election or payment.
Exclude account positions, beneficiaries, access instructions, entitlement values, and third-party market feeds unless separately cleared. Use an offline fixture and an authorized reviewer.
Describe a custody event sample
Original Fiund exercise
A record-date holding and an event amendment must refer to the same security
Two invented securities and synthetic unit holdings form an offline documentation task. There are no beneficiary accounts, market feeds, entitlement values or election instructions.
| Record | Source | What it records |
|---|---|---|
| CC1 | Event E1 and amendment E1R | Security S-A; record date day 10. E1R explicitly replaces E1's event terms and retains the day-10 record date. |
| CC2 | Holdings cards | S-A: 8 units on day 9, 6 units on day 10. S-B: 8 units on day 10; security label resembles S-A but identifier differs. |
| CC3 | Processing state | E1R acknowledged. No entitlement calculation, final allocation or payment confirmation provided. |
Question for the model
Which event version and holding card belong in the record-date review packet, and what outcome does the evidence leave unverified?
Show the reference answer and checks
CC1 identifies E1R as the amended S-A event with day 10 as its record date. CC2's S-A day-10 card, six synthetic units, matches that security and date; the day-9 card and S-B's similar label do not. CC3 establishes an acknowledgment but leaves entitlement, allocation and payment unverified. Assemble the matched documents for review without treating the event notice or holding match as a completed distribution.
- Using the nearest earlier holding when an exact record-date card exists.
- Treating an event acknowledgment as confirmation of an entitlement or payment.
Fields to preserve
- Event version and security alias
- Identifies the amended action.
- Record date and holding snapshot
- Defines the temporal match.
- Processing state and missing evidence
- Limits the supported conclusion.
Test another case
Remove the day-10 S-A holding. Require a missing-snapshot finding rather than substitution of S-B or the day-9 quantity.
Use an inert synthetic fixture. Exclude account positions, beneficiaries, real event feeds and any instruction that could initiate an election or payment.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.