Nocs With One Deterministic Articles

Handle ACH Returns and NOCs with One Deterministic Event Pipeline

For many platform teams, `ACH Returns` and `Notice of Change (NOC)` handling belongs in the main payment path, not in a side inbox for exceptions. If you split receipt, matching, posting, and customer-facing status too early, problems show up fast. Your books diverge from the product, actions get duplicated on replay, and unresolved items sit in logs with no clear owner.