Piermont ACH clearing notification gapPayments & Transfers

Task prompt

CP-115 in CX Projects — the “Undelivered transfer” escalation — has come back round because we're about to raise a formal notification complaint with Piermont off the back of it, and I'd rather not do that on a theory. Read the ticket first: the transfer's ledger reference is in there, and so is what CX thinks happened. Find that transfer in the ACH transfer ledger and tell me what our own records say became of it — its numeric ledger id, what it was for in cents, whether the bank's clearing/settlement confirmation was ever recorded against it, and whether it ever posted. Those last two are separate fields, and so is the notice we send the recipient; don't read one as standing in for another. Then size it, because CX's theory is that Piermont skipped the clearing notification on this one. The population I care about is every outbound ACH credit to an external counterparty that was charged to a Piermont-held account — Piermont being the bank behind the account the money left, not the recipient's bank. A transfer counts whatever pot inside that account funded it (people push money out of a savings goal or a bill reserve as well as straight off the balance) and whatever speed it went at. Only two things come out: anything that never reached the ledger's sent state — still submitting, or canceled, returned, errored — and our automation credit rail, which is a different product, so tell me how many of those you set aside. For April 2022 — by the month the transfer was processed, not the month it was created — I want both the number with no settlement confirmation on them and the total that went out that month, because a bare count tells me nothing without the rate. Give me the same pair across full history. Two more things before I put anything in writing to the bank. When does the earliest settlement confirmation on Piermont's book actually show up? And of these transfers processed from September 2022 onward, how many are still sitting there without one? While you're at it, check whether our other bank's ACH credits carry these confirmations at all. One last control, and it's the first thing Piermont will throw back at us: this is not the only transfer that account has sent to that same recipient. Pull the whole run of its ACH credits to that counterparty — how many are there, and how many of those do carry a settlement confirmation? And don't just hand me a bare count for that post-September-2022 set either — tell me how those sit in time before I quote a number at the bank. If they're sprinkled across three years, that's one conversation to have with Piermont; if they bunch, I need to know which single month they bunch in, how many of them land in it, and how many credits we sent that month all told. That's the difference between complaining about one incident and complaining about how they run the rail, and I'm not getting it the wrong way round in writing. Then give me your call: does CX's theory hold up for Ben's transfer, or is the pattern telling us something else? Whichever way it lands I need to be able to defend it to Piermont with the numbers, and if there's a subset that genuinely does warrant the complaint, say which. When you're done: open a Slack channel called “piermont-ach-clearing-audit”, post the summary there — include the transfer's ledger id and the full-history no-confirmation count — and pin it. File a Bank Operations ticket titled “Piermont ACH clearing notification gap” recording the finding and whether an escalation is warranted. And reply with: anchor_transfer_id, anchor_amount_cents, anchor_clearing_confirmed, anchor_posted_to_ledger, piermont_april_2022_gap_count, piermont_april_2022_sent_count, piermont_full_history_gap_count, piermont_sent_total_count, piermont_first_confirmation_month, piermont_gap_count_from_2022_09, piermont_automation_rail_sent_count, other_bank_sent_count, other_bank_gap_count, anchor_counterparty_transfer_count, anchor_counterparty_confirmed_count, residual_cluster_month, residual_cluster_count, residual_cluster_month_sent_total, and systemic_verdict.