For a US manufacturer paying a supplier when its enterprise resource planning (ERP) system records delivery, the decisive question is which instruction caused the loss. New York law separates the company's standing rule, the released payment order, the bank's execution and the supplier's receipt. That separation determines who can stop the transfer and who must pursue recovery.
Identify the instruction that becomes a payment order
As at 18 November 2026, J.P. Morgan's Advanced Programmable Payments description describes customer-defined rules responding to events, balances and external data, with an audit trail. The joint J.P. Morgan and MIT report, pages 15–17, describes triggers, conditions, actions and payment-state transitions. Its delivery-notification example on pages 22–24 describes a possible application. J.P. Morgan's Blockchain Deposit Accounts page also describes connections to traditional deposit accounts inside and outside the bank's network. The manufacturer's arrangement requires bank confirmation of the particular account, entity, currency, data connection and payment route before deployment.
The manufacturer instructs its bank to pay the named supplier when delivery is recorded. Treasury approves the rule and the supplier account. The ERP supplies the business event. The bank-hosted program evaluates the event and produces an instruction or performs an agreed action. The mandate and message history must establish who gives any resulting payment instruction and which bank receives it.
Under § 4-A-103(1)(a), a payment order must direct a receiving bank to pay a fixed or determinable amount. It must require reimbursement by the sender and meet the transmission requirement. It cannot state a condition to payment other than the time of payment. A standing instruction to pay only if delivery occurs therefore fails that condition test while it remains conditional.
A later unconditional instruction attributable to the manufacturer can qualify once the rule has evaluated the delivery event. An automated message can carry that instruction; a further human click is not a statutory requirement. If the only customer instruction remains conditional and the bank changes its ledger without a qualifying unconditional order attributable to the customer, that customer-to-bank step falls outside Article 4-A. Its authority and remedy require analysis under the deposit agreement and programming mandate. A record labelled “released” must satisfy the statutory elements, including attribution and transmission. Classify any later interbank order separately. § 4-A-103; § 4-A-104.
The stages should be recorded separately:
- Rule approval. Responsible actor and record: Treasury signs the permitted supplier, amount formula, event condition and rule version. Legal significance: Establishes the scope of the mandate and delegated authority.
- Delivery event. Responsible actor and record: ERP owner records the delivery reference, event identifier and timestamp. Legal significance: Supplies the business input; the event may still require evaluation.
- Payment release. Responsible actor and record: The program generates the customer-attributed instruction; the bank records its receipt and contents. Legal significance: Test every element of § 4-A-103 against this instruction.
- Sending-bank acceptance. Responsible actor and record: An originator's bank that is not the beneficiary's bank issues its implementing payment order. Legal significance: Execution constitutes acceptance under §§ 4-A-209(1) and 4-A-301.
- Beneficiary-bank acceptance. Responsible actor and record: The supplier's bank records the applicable payment, notice or funding event. Legal significance: Apply § 4-A-209(2), including its timing restrictions; acceptance can precede the supplier reading a statement.
An on-us transfer can fall within Article 4-A when the manufacturer gives a qualifying order to the bank that also holds the supplier's account. The beneficiary's bank accepts under § 4-A-209(2); it does not “execute” that order in § 4-A-301's technical sense. Separate branches count as separate banks under § 4-A-105(1)(b). Identify the actual offices before describing a payment within one banking group as on-us. §§ 4-A-105, 4-A-209, 4-A-301.
Establish the governing law for each relationship
The following New York analysis assumes the relevant customer-bank relationship is governed by New York law. The signed mandate should state that choice. Under § 4-A-507, the default for each sender-receiving-bank pair is the receiving bank's location. The beneficiary-bank relationship and the question when the originator pays the beneficiary follow the beneficiary bank's location. An agreed choice can change these defaults. A qualifying system choice requires its own analysis, including the relevant parties' notice. Under § 4-A-507(4), the affected parties' agreement prevails over a conflicting system choice.
- Manufacturer and originator's bank. Law to identify before applying the remedy: Their governing-law agreement; otherwise the receiving bank's jurisdiction.
- Each sending bank and its next receiving bank. Law to identify before applying the remedy: That pair's agreement and any applicable system rule; otherwise the next receiving bank's jurisdiction.
- Supplier and beneficiary's bank. Law to identify before applying the remedy: Their agreed law; otherwise the beneficiary bank's jurisdiction.
- Manufacturer and ERP vendor. Law to identify before applying the remedy: The ERP and integration contracts, including their law and forum clauses.
Use federal Regulation J only when the transfer architecture uses the relevant Federal Reserve service. Subpart B concerns Fedwire; Subpart C concerns FedNow. Their application to a remote corporate customer depends on the regulation's scope and choice-of-law provisions. A bank's separate Federal Reserve settlement transfer does not necessarily bring the customer's underlying payment under Regulation J. For an internal book transfer without such a service, the product's speed or blockchain design supplies no federal-rail connection. Federal Reserve commentary, §§ 210.25 and 210.40.
This article addresses a newly authorised arrangement under the law as at 18 November 2026. New York's relevant Uniform Commercial Code (UCC) amendments took effect on 3 June 2026. The amended security-procedure definition expressly addresses known email addresses, internet protocol (IP) addresses and telephone numbers. Earlier transactions require the saving-clause analysis. L. 2025, ch. 579, §§ 23–31, 88; § 12-A-201.
Apply the authority and error tests separately
For an unauthorised wire transfer, UCC Article 4-A starts with company authority. Section 4-A-202(1) binds the manufacturer to an order it authorised or is bound by under agency law. The treasurer's personal approval is relevant only within the company's actual authority arrangements. Another authorised officer or agent may have power to act. Conversely, possession of credentials does not by itself establish that power.
An order lacking actual authority can still bind the customer under § 4-A-202(2). The bank and customer must have agreed an authentication procedure; that procedure must be commercially reasonable. The bank must prove good faith and compliance with its obligations under the procedure and applicable recorded restrictions on acceptance. Commercial reasonableness is a legal question assessed against the customer's circumstances, instructions, offered alternatives and comparable practice. Under § 4-A-202(3), the chosen procedure is deemed commercially reasonable if the customer rejected an offered commercially reasonable alternative and expressly agreed in a record to be bound by orders complying with the chosen procedure.
Section 4-A-201 defines agreed procedures for authentication and for detecting error. A known email address, IP address or telephone number alone is insufficient. An authentication control does not necessarily detect a duplicated invoice or delivery event. Treasury should specify both functions and the evidence that proves each was performed.
Even where § 4-A-202(2) initially makes an unauthorised order effective, § 4-A-203(1)(b) can prevent enforcement. The customer must exclude direct or indirect causation by a person entrusted at any time with payment-order or security-procedure duties, a person who accessed its transmitting facilities, or a person who obtained security-breach information from a customer-controlled source without bank authority. An ERP operator entrusted with those duties, or a compromise meeting those access conditions, can defeat that showing even without customer fault. Evidence that the bank alone caused the unauthorised change can change the result. A bank may also expressly assume more of this risk under § 4-A-203(1)(a).
For an accepted erroneous customer order, § 4-A-205 has a separate test. The order must have been transmitted under an agreed error-detection procedure. The sender must prove its own compliance, or that of a transmitter acting for it under § 4-A-206, and that bank compliance would have detected the covered error. If the transfer completes on that order, a qualifying wrong-beneficiary or duplicate-transmission error excuses payment; an excess-amount error excuses only the excess. Successful authentication alone does not satisfy those requirements.
Allocate the three failures
- A genuine delivery is recorded twice. Liability decision: Two releases may be authorised under a rule that acts on each ERP event. A duplicate transmission must meet § 4-A-205's additional conditions. A bank that creates a second downstream order from one customer order faces § 4-A-303(1). Remedy and decisive evidence: Compare delivery references, event and order identifiers, both payloads and the agreed duplicate check. Seek return of the excess payment; claim the statutory refund where its conditions are met.
- The recipient changes without the treasurer's authority. Liability decision: Test company authority first, then §§ 4-A-202–203. If the bank substitutes a different beneficiary in its downstream order and the transfer completes on that error, § 4-A-303(3) excuses payment. A name-account mismatch also requires § 4-A-207. Remedy and decisive evidence: Preserve the old and new supplier details, amendment signatures, credential and access history, accepted order and bank-generated order. Demand refund if the order is unenforceable or the bank's execution creates the statutory refund right.
- Payment follows a rule the company intended to switch off. Liability decision: Internal intent leaves an otherwise valid mandate effective. A verified, timely cancellation of an issued order can prevent acceptance. A prospective rule suspension must be tested against the mandate and received notice. Remedy and decisive evidence: Preserve suspension instructions, bank receipt and acknowledgment, the active rule version and order-acceptance times. Seek cancellation while effective; after acceptance, pursue the applicable return, refund or contract route.
For the first event, compare what the mandate actually authorises. A rule authorising one payment per delivery reference differs from a rule authorising a payment for every incoming ERP event. If two separate orders accurately implement the latter rule, the company's duplicate corporate payment generally remains its business-data loss. Section 4-A-205 does not create a general bank duty to discover that two genuine-looking events describe one delivery. If the bank ignores an agreed check capable of detecting the covered error, the statutory analysis changes. §§ 4-A-202, 4-A-205, 4-A-402.
For a bank-created duplicate downstream order, the bank can charge the sender only the amount of the sender's order, subject to § 4-A-402. If the bank's implementing order names a different beneficiary and the transfer completes on that error, § 4-A-303(3) excuses the affected sender and preceding senders. The bank's right to recover from the recipient is subject to mistake and restitution law. For an on-us ledger error, determine whether the bank accepted a qualifying order and what the sender owes under § 4-A-402(2). An excess debit not owed is refundable under § 4-A-402(4). Acceptance of a proper order may leave its original amount payable while the bank must correct its beneficiary-side performance under §§ 4-A-404, 4-A-405 and the mandate. Section 4-A-303 requires a downstream order issued by the receiving bank. §§ 4-A-302, 4-A-303, 4-A-402(4).
For a changed recipient, determine whether the instruction names one person but gives another person's account number. Under § 4-A-207(2)–(4), a beneficiary's bank without knowledge of the discrepancy can generally rely on the number. If the original order contains that mismatch and the beneficiary's bank permissibly pays by number, a non-bank originator must prove the numbered recipient was not entitled to payment. It then owes nothing unless its bank proves that the manufacturer had notice, before that bank accepted the manufacturer's order, that the number could control despite the name. If the beneficiary's bank knows of the mismatch, only the person it pays can have beneficiary rights, and only if that person was entitled to payment; otherwise acceptance cannot occur. If both name and number identify the same wrong recipient, the mismatch rule does not resolve the authority question.
For the rule the company wanted to disable, distinguish stopping future generation from cancelling an order already issued. The first concerns the standing mandate and the agreed suspension process. The second invokes § 4-A-211. The manufacturer must establish bank receipt and effectiveness under the mandate; a draft request, internal ticket or ERP-only change leaves that step unproved. A suspension communicated to the bank must also be tested as a restriction on acceptance under § 4-A-202(2), including its timing and consistency with the recorded agreement. §§ 4-A-202(2), 4-A-211.
Separate a stop request from a right to recover
Before acceptance, a cancellation or amendment is effective if the receiving bank receives it in time and in a manner giving a reasonable opportunity to act. An agreed security procedure must be satisfied, unless the bank agrees to the cancellation or amendment. Under § 4-A-106, the bank's cut-off may defer receipt to its next funds-transfer business day. The legal stop point can therefore precede a later debit or customer notification. § 4-A-211(1)–(2); Fischer & Mandell LLP v Citibank, N.A., 632 F3d 793, 801–802 (2d Cir 2011), slip opinion pages 18–21.
After acceptance, cancellation requires the receiving bank's agreement or an applicable system rule permitting it. If that bank has issued a downstream order, a conforming cancellation must also occur downstream. After the beneficiary's bank accepts, § 4-A-211(3)(b) adds specific grounds: an order executing an unauthorised order, or a sender's mistake producing a duplicate, payment to someone not entitled to payment, or an excessive payment. A customer's change of mind about paying a supplier legitimately owed the amount does not satisfy those grounds. § 4-A-211(3), (8).
The bank can request a voluntary return even where those cancellation conditions are unavailable. Record the request, the response and any money actually returned. Confirm reversal through evidence of effective cancellation or funds actually returned. Where statutory cancellation succeeds, acceptance is nullified, but recovery from the recipient remains subject to restitution law. Recipient entitlement and notice of the mistake matter, as Golden Door V & I, Inc. v TD Bank, 123 AD3d 976, 977–979 (2d Dept 2014) demonstrates.
If the bank agrees to cancellation after acceptance, or is bound by a system rule allowing it, § 4-A-211(6) generally makes the sender bear the bank's resulting loss and expenses, including reasonable attorney's fees, even if the attempt fails. The parties or system rule can provide a different allocation. A refund claim against the manufacturer's own bank must be pursued separately. Section 4-A-204 requires refund for an unauthorised order that is ineffective under § 4-A-202 or unenforceable under § 4-A-203. Section 4-A-402(4) requires refund of payment the sender was not obliged to make. Neither provision makes the customer's qualifying refund depend on successful recovery from the recipient.
Preserve the evidence at the feasible stop point
Treasury operations should use the bank's agreed emergency channel as soon as the discrepancy is identified. Send the notice to the bank unit designated to receive cancellations and disputes. Notify the ERP incident owner in parallel. Preserve the original records before changing the configuration; restrict further releases while retaining the versions needed to establish what happened.
- Detection and containment. Owner and action: Treasury identifies affected orders and requests suspension of future releases. Information technology (IT) restricts compromised access. Evidence to retain: Delivery and invoice references; event identifiers; active and previous rule versions; approvals and signatures; access logs.
- Before acceptance, if still possible. Owner and action: An authorised treasury operator sends a verified cancellation or amendment to the receiving bank. Evidence to retain: Exact notice and payload; sender identity; authentication result; bank receipt time and channel; stated execution or payment date.
- Establish each bank's position. Owner and action: Bank operations confirms receipt, execution, acceptance and downstream status separately. Evidence to retain: Customer order; implementing bank order; bank acknowledgments; rail and branch identifiers; timestamps with time zones and clock-offset information.
- After acceptance. Owner and action: Treasury requests the permitted cancellation or voluntary return and states any independent refund claim. Evidence to retain: Recall or return reference; bank agreement or refusal; downstream cancellation result; supplier-bank response; fees or indemnity demanded.
- Confirm credit and recovery. Owner and action: Treasury reconciles with the supplier and bank. Counsel evaluates recipient entitlement and the correct recovery claimant. Evidence to retain: Beneficiary credit and availability evidence; actual return credit; underlying invoice or debt; communications about the mistake.
- Preserve notice rights. Owner and action: Controller records when the company received each bank notification and sends an express objection promptly. Counsel calendars the applicable periods. Evidence to retain: Statement or electronic notification actually received; delivery logs; objection text and proof of receipt; chronology linking all versions and orders.
These are proposed operational steps. Their legal purpose is to establish the elements of acceptance, cancellation, authority, error and notice. Sections 4-A-209, 4-A-211 and 4-A-405 identify different events. Maintain that chronology alongside any dashboard status.
Report promptly and preserve the correct remedy
The reporting provisions have different consequences:
- Under § 4-A-204(1), failure to use ordinary care and report an unauthorised order within a reasonable time, no longer than 90 days after the relevant notification, can forfeit interest. The section does not make that failure an independent ground to recover damages from the customer.
- Under § 4-A-205(2), failure to exercise ordinary care to report a qualifying erroneous customer order within a reasonable time, at most 90 days after bank notification, can make the sender liable for the bank's proved resulting loss, capped at the order amount.
- Under § 4-A-304, failure to exercise ordinary care to report erroneous execution within a reasonable time, at most 90 days after notification of execution or debit, can remove interest for the period before the bank learns of the error. The provision bars additional recovery from the sender for that reporting failure.
- Under § 4-A-505, a customer who paid an accepted order must object within one year after receiving notification reasonably identifying it, or lose the right to challenge the bank's retention of payment. This sets the objection period; counsel must identify any litigation filing deadline separately.
In Regatos v North Fork Bank, 5 NY3d 395, 398–405 (2005), the Court of Appeals held that the one-year period could not be shortened by contract. It also rejected constructive notice through a hold-mail arrangement for starting the relevant periods. The case concerned unauthorised transfers and the bank's failure to follow agreed security procedures. It does not supply a general refund for a valid authorised payment based on bad ERP data. Preserve actual receipt of an identifying notification; do not wait until a particular officer later recognises the fraud.
The Court of Appeals preserved the distinction between Article 4-A and the separate cheque rules in Clemente Bros. Contracting Corp. v Hafner-Milazzo, 23 NY3d 277, 288–289 (2014). Contractual notice language therefore needs analysis against the applicable provision. Prompt reporting remains necessary even where a clause cannot remove the statutory principal refund.
Negotiate the bank mandate and ERP contract separately
The following proposed terms require bank agreement. Counsel should place them in the operative mandate and security schedules before activation, with precedence over inconsistent standard terms. Treasury and IT must implement the corresponding controls.
Rule amendments and supplier changes
Require approval by two named company roles for changes to the supplier, account, amount formula, event source or release conditions. The bank must verify approvals through the agreed procedure before activating a new version. Each activation must produce a timestamped acknowledgment identifying the previous and replacement versions. Specify which company personnel and vendors have no amendment authority. Record these restrictions as acceptance restrictions where applicable under § 4-A-201 and § 4-A-202.
Duplicate detection
Agree which business identifiers and payment identifiers must remain unique, how retries retain those identifiers, and how partial deliveries are handled. Require the bank to reject or hold a repeated covered instruction and notify treasury. Define the check as an agreed error-detection procedure, with evidence of performance. If the company wants protection against two distinct orders generated from one duplicated business event, obtain an express allocation of that loss as well. The scope of § 4-A-205 makes that distinction consequential.
Revocation and emergency suspension
Specify the authenticated channel and bank unit that receive a rule suspension. Require a defined effective time, a halt on subsequent releases, and identification of orders already generated. Address queued instructions, retries, restored system states and any backup rule. Give an authorised emergency operator power to suspend, while requiring fresh approval to reactivate. For issued orders, preserve the statutory pre-acceptance cancellation route and specify the bank's agreed assistance after acceptance. Provide that an otherwise effective cancellation under § 4-A-211 takes effect without awaiting a bank acknowledgment.
Bank acknowledgments and remedy records
Require separate records for rule activation, suspension receipt, payment-order receipt, acceptance, cancellation outcome and beneficiary credit. Each record must identify the rule version and relevant order. Agree access to the underlying logs and their retention. Require the bank to identify the contractual and statutory basis for any refusal to refund, and keep the refund decision separate from its recovery efforts against a recipient. Obtain any desired consequential-loss coverage expressly: § 4-A-305(3)–(4) generally requires an express agreement evidenced by a record for those additional damages.
Bank agreement can improve protection, but mandatory rules constrain its terms. Sections 4-A-202(6), 4-A-204(2) and 4-A-402(6) restrict variation of the identified rights and duties. Section 1-302(b) also preserves prescribed good faith, diligence, reasonableness and care. A supplier's rights against its own bank require separate consideration under § 4-A-404(3).
The ERP contract should allocate responsibility for unique delivery records, supplier-master changes, event authentication, retries, revocation propagation and incident evidence. Obtain its liability cap, loss exclusions, indemnity, subcontractor allocation and claim-notice clauses. If the vendor promised a control and its breach caused the loss, those terms determine the available contract claim. If the company retained responsibility for the incorrect input and the vendor performed its promised service, that claim may fail. A third-party transmission system can also be treated as the sender's agent under § 4-A-206; the provision's Federal Reserve exception must be respected.
Where the bank undertakes a separate programming or suspension duty, identify that promise and the conduct that breached it. Common-law claims cannot impose liability inconsistent with Article 4-A's allocation. Golden Door, 123 AD3d at 979, and Fischer & Mandell, slip opinion pages 8–9, explain the boundary.
Licentium's analysis of treasury-tool payment authority in Ireland addresses the upstream delegation decision. The New York decision requires the accepted order, the applicable security and error controls, and the available remedy. Consumer remittance complaints require their own customer and rail analysis; see US remittance errors when a Philippine payout partner fails.
Before activation, the controller should obtain the signed bank schedules, the ERP allocation of duties, and a test record demonstrating amendment, duplicate-event handling and suspension. Treasury should approve the residual loss it will bear when a valid rule receives incorrect business information.