INDUSTRY FIELD GUIDE
Credit union share reconciliation data for AI testing
An amount may appear in a control account before it is attributed to the correct share account.
NAICS 522130 · Credit Unions
An amount may appear in a control account before it is attributed to the correct share account. A reconciliation assistant should keep those records separate. NCUA’s member account deposit reconciliation material provides context for the kind of documentary review a credit union can model with fictional examples. NCUA member deposit reconciliation practices
Write a mock batch with a verified share posting, an amount still in suspense, and a later balancing entry. Give two fictional members similar aliases. Ask the model which accounts are affected and what evidence a reviewer would need to close the open item. Keep the posting order and reconciliation approval distinct. Include a case where the aggregate total balances even though one individual assignment is unresolved.
No real member information, account numbers, settlement data, or private control procedures should leave the credit union. Use artificial amounts and a fictional review key.
Describe a share reconciliation sample
Original Fiund exercise
A balanced control total can conceal an unresolved member assignment
A fictitious credit-union batch uses invented share aliases and practice amounts. It contains no member identity, valid account number or production reconciliation procedure.
| Record | Source | What it 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 for the model
Does the balanced total establish that both share accounts are reconciled, and what remains needed for Y?
Show the reference answer and checks
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.
- Equating a balanced batch with complete member-level reconciliation.
- Assigning suspense to the nearest-looking member alias without approved evidence.
Fields to preserve
- 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.
Test another case
Provide a Y assignment instruction but no reconciliation approval. Require recognition of the proposed target while keeping review completion open.
Use artificial records and original review keys. Exclude member details, settlement information and private control procedures.
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.