{
  "title": "Payment clearing and return records for AI evaluation",
  "source_page": "https://fiund.com/industries/payment-clearing-return-records-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A field-correction notice does not have the same effect as a return",
    "context": "An offline clearing fixture uses dummy payment aliases and arbitrary practice units. No bank coordinates, usable payment reference or operational exception rule appears.",
    "records": [
      [
        "AC1",
        "Original events",
        "Payment P-A=25 units and payment P-B=25 units. Each has a distinct inert source reference."
      ],
      [
        "AC2",
        "Linked follow-ups",
        "Return R-A explicitly targets P-A. Field-correction notice N-B explicitly targets P-B and changes a dummy label only; no return for P-B supplied."
      ],
      [
        "AC3",
        "Unmatched note",
        "Event U ends in the same digit as P-A, amount 25, but carries no full origin reference or event-type confirmation."
      ]
    ],
    "question": "Which original payment has a documented return, which has only a label correction, and can U be matched by amount and last digit?",
    "answer": "AC2 links R-A to P-A as a return. It links N-B to P-B as a dummy label correction, without documenting a P-B return. AC3's amount and last digit do not establish a complete origin match or event type, so U stays unresolved. Preserve each follow-up's stated effect and source relationship instead of treating all later messages as financial reversals or inferring a new payment status.",
    "failureModes": [
      "Classifying a field-correction notice as a returned payment.",
      "Matching an exception by amount and a partial reference instead of a documented origin link."
    ],
    "fields": [
      [
        "Original payment alias",
        "Defines the target event."
      ],
      [
        "Follow-up type and origin reference",
        "Distinguishes return from field correction."
      ],
      [
        "Changed field and unmatched status",
        "Records the narrow supported effect."
      ]
    ],
    "holdout": "Add a later explicit P-B return with its own event ID. Require it to be reported as separate evidence rather than changing N-B's original type.",
    "boundary": "Use inert fictional records. Exclude real references, account details, credentials and controls; the task initiates no transfer or payment action."
  }
}