{"id":19176,"plugin_id":"plugins_6a9319929b74819193f3f276f98627c4","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:15:20.733Z","digest":"9a603a479959b4cbc19f9102493ca858b4ac921ebab6a4fd4b16c2547b453f0e","against":null,"payload":{"description":"Use after capture for Go settlement, reconciliation, exceptions, and repair. Do not use for initial authorization.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":279},{"relative_path":"evals.json","size_in_bytes":9812},{"relative_path":"references/ach-returns-and-corrections.md","size_in_bytes":5270},{"relative_path":"references/business-time-and-cutoffs.md","size_in_bytes":3683},{"relative_path":"references/fedwire-finality-and-contingency.md","size_in_bytes":2352},{"relative_path":"references/reconciliation-model.md","size_in_bytes":806},{"relative_path":"skill.json","size_in_bytes":4073}],"name":"go-clearing-settlement-reconciliation","skill_md_contents":"---\nname: go-clearing-settlement-reconciliation\ndescription: \"Use after capture for Go settlement, reconciliation, exceptions, and repair. Do not use for initial authorization.\"\nlicense: Apache-2.0\ncompatibility: \"Go 1.24 or newer; rail cutoffs, calendars, reports, and finality come from current provider and scheme contracts.\"\n---\n\n# Go clearing, settlement, and reconciliation\n\nDo not collapse payment acceptance, clearing, settlement, payout, and bank movement into one success flag. They are separate evidence domains with different timing and finality.\n\n## Preserve evidence\n\nIngest external reports and statements immutably with artifact identity, source version, checksum, retrieval time, business date, completeness/sequence evidence, and parser version. A corrected artifact does not overwrite its predecessor: record `supersedes` lineage and create explicit rematching or reversal work. Make re-ingestion idempotent. Preserve raw evidence under access and retention policy; derive versioned normalized items separately.\n\n## Match at item level\n\nMatch stable external/internal identity first, then amount, currency, lifecycle, account, and time window. Support 1:1, 1:N, and N:1 match groups when the source economics require them. Every normalized economic component belongs to exactly one explained match group or one explicit exception; never reuse an item across groups. Each group must satisfy a currency-preserving equation over captures, refunds, fees, reserves, adjustments, and bank movement.\n\nExceptions include missing internal, missing external, duplicate, amount/currency mismatch, status mismatch, timing break, and incomplete or superseded evidence. Persist the rule and source versions behind every match decision.\n\nAggregate totals are controls, not sufficient reconciliation. Equal and opposite item errors can net to zero.\n\n## Adjust deliberately\n\nAge timing breaks by rail calendars and cutoffs. Separate automated detection from authorized remediation. Adjust with linked immutable ledger entries; never rewrite the original payment or report. Reruns must not duplicate adjustments or erase prior decisions.\n\n## Recovery and operations\n\nUse restartable batches, checkpoints, deterministic matching, bounded concurrency, and work queues with ownership. Publish completeness, unmatched amount/count, age, duplicate count, and source freshness without leaking sensitive data.\n\nRead [references/reconciliation-model.md](references/reconciliation-model.md) for stages and controls. For Fedwire acceptance, cancellation, outage, and resend semantics, read [references/fedwire-finality-and-contingency.md](references/fedwire-finality-and-contingency.md) and verify the deployed circular version.\n\nFor FedACH post-origination processing, read [references/ach-returns-and-corrections.md](references/ach-returns-and-corrections.md). Keep returns, Notifications of Change, reversals, and disputed returns distinct; their value effects, roles, and permitted timing are not interchangeable.\n\nFor rail business days, holidays, processing windows, cutoff extensions, and schedule changes, read [references/business-time-and-cutoffs.md](references/business-time-and-cutoffs.md). Persist the governing schedule and timezone version with each decision; a UTC calendar date, fixed offset, or `Add(24*time.Hour)` is not a rail calendar.\n\n## Output contract\n\nState source evidence, matching key, timing policy, exception taxonomy, adjustment authorization, and replay behavior. Missing or silently auto-matched money is a critical defect.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}