[Help wanted] BSP HOT reconciliation: multi-currency + exchange/conjunction cross-refs

[telivity-otaip]

Who this is for

TMC / OTA settlement & accounting people who reconcile BSP HOT (or ARC IAR) weekly and live in discrepancy hell. If you've matched an exchange that isn't a simple ticket-number join — perfect.

Why this hardens the system

Agent 7.1 BSP Reconciliation matches agency records to HOT rows. Real HOT files are hybrid EDI + fixed-width, often multi-currency, and exchanges / conjunctions / ADM-ACM create cross-references beyond ticket number equality.

Files:

• packages/agents/reconciliation/src/bsp-reconciliation/
• packages/agents/reconciliation/src/arc-reconciliation/
• docs/agents/stage-7-reconciliation.md
• CLAUDE.md → Agent 7.1 guards

What we need

1. Document which HOT fields you use for:
   • transaction currency vs reporting currency
   • EXCH / TKTT / RFND / ADM / ACM linkage
   • conjunction sets
2. Matching algorithm notes used in your shop (keys, tolerances, period boundaries).
3. Remittance calendar caveats (weekly / bi-monthly / grace) by market you know.
4. Sample synthetic HOT-like fixtures (never real agency data) that expose multi-currency bugs.

Acceptance criteria

• KB covering multi-currency + cross-ref patterns
• Explicit "do not assume single-currency HOT"
• Fixtures or tests for exchange-linked tickets
• Note that generic X12 parsers miss fixed-width sections
• No live HOT dumps committed

Search keywords

help wanted · BSP · HOT · ARC · IAR · reconciliation · ADM · ACM · conjunction · TMC settlement

How to contribute

Comment with your BSP market (e.g. BSP UK / BSP DE) + the mismatch types you see most. Synthetic fixtures strongly preferred.