INDUSTRY FIELD GUIDE
Commodity broker transaction corrections for AI evaluation
A corrected transaction record may replace a field without creating another trade.
NAICS 523160 · Commodity Contracts Intermediation
A corrected transaction record may replace a field without creating another trade. CFTC materials describe how swap data reporting errors and corrections are handled in one part of the derivatives market. A broker can build a mock sequence to evaluate whether a model preserves the original transaction identity and corrected version. CFTC swap data correction advisory
Invent two order and transaction aliases, an original confirmation, and a later replacement with a clear cross-reference. Give an unrelated transaction the same quantity. Ask which recorded field changed and which transactions remain distinct. Add a missing link so the model must flag uncertainty. A trained reviewer should decide the expected answer and exclude any trading recommendation from the rubric.
Keep positions, clients, prices and strategies, trade venue IDs, execution logs, and access credentials private. Check exchange or platform rights before reusing actual formats or files.
Describe a transaction-correction sample
Original Fiund exercise
A replacement confirmation changes a field without adding a trade
Imaginary transaction aliases and arbitrary quantity units create an offline correction fixture. No security, contract price, position or strategy is represented.
| Record | Source | What it records |
|---|---|---|
| BC1 | Confirmation V1 | Transaction T-A, order O-A, quantity 12 units, category X. |
| BC2 | Replacement V2 | Explicitly supersedes BC1 for T-A/O-A; category corrected to Y. Quantity remains 12. Separate T-B/O-B also has quantity 12. |
| BC3 | Unlinked correction note | Says category Z and quantity 12 but omits transaction, order and supersession references. |
Question for the model
How many distinct identified transactions are present, which field changed for T-A, and can BC3 be applied to either transaction?
Show the reference answer and checks
BC1 and BC2 describe two identified transactions, T-A and T-B; the replacement is a new version of T-A, not a third transaction. T-A's category changes from X to Y while its quantity stays 12. BC3 lacks the identifiers needed to associate its Z correction with either transaction. Equal quantity cannot resolve that gap, so retain the note as an unmatched exception for review.
- Counting a replacement confirmation as another trade in totals.
- Applying an unlinked correction to whichever transaction shares its quantity.
Fields to preserve
- Transaction and order aliases
- Disambiguates equal-quantity records.
- Version and supersedes reference
- Defines the replacement chain.
- Changed field and unmatched-note status
- Separates an evidenced correction from an assumption.
Test another case
Give BC3 an explicit T-B reference but a conflicting order alias. Require a flagged identity conflict rather than a silent update.
Use original dummy records only. Exclude execution logs, clients, venue credentials and licensed platform formats; no trading action or recommendation belongs in the task.
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.