The Fedwire Funds Service completed its ISO 20022 migration in July 2025. Structured messages can carry richer payment information, but that does not guarantee a merchant’s accounting software will receive a usable invoice reference. The practical test is whether the reference survives the entire path from payer to the employee applying cash.
Map the fields across the handoffs
List the identifier the customer uses, the reference shown by the receiving bank, the fields available in a report or export, and the accounting field used to match the payment. Ask the bank what its particular service exposes. A message format’s technical capability and a customer-facing product’s export are different things.
Have staff follow a sample transaction across those records. Note truncation, missing leading zeros, changed punctuation and references placed into a free-text description. Preserve the original received value alongside any normalized version. A cleanup rule should not overwrite the evidence needed to investigate an incorrect match.
Test a partial payment and a combined payment
In an illustrative example, one $6,000 transfer covers two invoices for $2,500 and $3,500. The bank credit alone proves receipt of $6,000, not how the customer intended it to be allocated. The test should show whether the remittance details reach staff and whether the accounting system can split the receipt with a reviewable record.
Run a second example in which the payment covers only part of one invoice. Confirm how the unpaid balance remains visible and how staff avoid marking the whole invoice paid. Include currencies, deductions and customer account identity where relevant. Use synthetic test data or an approved test environment rather than exposing real customer information unnecessarily.
Give exceptions a named owner
Create an exception queue for missing references, ambiguous matches and differences between the bank amount and the expected receipt. Each entry needs the source record, amount, age, proposed allocation and staff owner. Do not silently post an approximate match merely to make the queue smaller. Resolve the difference or retain it for review.
Bound the role of AI
An AI assistant can suggest candidate invoices or summarize a remittance message. Require it to show the source reference and the reason for each suggestion. Compare its output with the actual invoice ledger. It should not invent an allocation for an unmatched receipt or rewrite the payer’s original message.
Businesses operating across Florida, New York and New Jersey can use the same field map while assigning a local owner for each bank account. Continue through the New Jersey receivables reading path or Eric’s alternative financing guide when preparing cash-flow records. Review the Federal Reserve’s ISO 20022 FAQ with your bank for service-specific questions. References checked October 17, 2026; these examples do not establish that every payment rail or bank report uses the same fields.
Eric Kuvykin
Publisher and editorial director covering payments, fintech, merchant services, banking, AI, technology and operating strategy for small and medium-sized businesses.
