{
  "title": "Credit union share reconciliation data for AI testing",
  "source_page": "https://fiund.com/industries/credit-union-share-reconciliation-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A balanced control total can conceal an unresolved member assignment",
    "context": "A fictitious credit-union batch uses invented share aliases and practice amounts. It contains no member identity, valid account number or production reconciliation procedure.",
    "records": [
      [
        "CU1",
        "Batch B total",
        "Received 150 units: reference X for 90 and reference Y for 60."
      ],
      [
        "CU2",
        "Posting detail",
        "X verified to share S-A for 90. Y held in suspense for 60 because aliases 'Lee-A' and 'Lee-A2' conflict; neither share assignment approved."
      ],
      [
        "CU3",
        "Control and review",
        "Control total: posted 90 plus suspense 60 equals 150. Later balancing entry clears the control difference but contains no Y-to-share instruction or reviewer approval."
      ]
    ],
    "question": "Does the balanced total establish that both share accounts are reconciled, and what remains needed for Y?",
    "answer": "CU1 through CU3 reconcile the aggregate 150 units as 90 posted and 60 in suspense. Only X has a verified share assignment, to S-A. CU3's balancing entry addresses a control difference and supplies no approved Y assignment. Y still needs authoritative identification of its share target and the required review evidence. Similar aliases and a zero aggregate difference cannot establish that each individual posting is correct.",
    "failureModes": [
      "Equating a balanced batch with complete member-level reconciliation.",
      "Assigning suspense to the nearest-looking member alias without approved evidence."
    ],
    "fields": [
      [
        "Batch, item and control amount",
        "Supports aggregate reconciliation."
      ],
      [
        "Share assignment and suspense state",
        "Preserves unresolved attribution."
      ],
      [
        "Approval reference and reason",
        "Separates balancing from authorized assignment."
      ]
    ],
    "holdout": "Provide a Y assignment instruction but no reconciliation approval. Require recognition of the proposed target while keeping review completion open.",
    "boundary": "Use artificial records and original review keys. Exclude member details, settlement information and private control procedures."
  }
}