Written Statement of Unauthorized Debit Copy (WSUD)
To print this page, go to File and select Print.
Case Type Description | Proper Usage
Written Statement of Unauthorized Debit Copy (WSUD) – Used by the originating depository financial institution (ODFI) to request the written statement of unauthorized debit from the receiving depository financial institution (RDFI).
If you need to send a WSUD, submit an exception request to the Federal Reserve Banks.
As stated in the March 20, 2020, ACH Operations Bulletin #3-2020 (Off-site), Nacha is providing temporary relief from deadlines for delivery of certain records required under the Nacha Rules. For the duration of the national emergency surrounding COVID-19, Nacha will allow 20 banking days—doubling the usual 10 banking days allowed—for ODFIs to provide a proof of a Receiver’s authorization following the RDFI’s request and for RDFIs to provide a copy of a consumer Receiver’s Written Statement of Unauthorized Debit after receipt of an ODFI’s request.
The FedACH Exception Resolution Service has been modified to accommodate the extended deadlines for as long as the temporary changes to the Nacha Rules remain in place.
| Federal Reserve Bank Reporting Time Frame | If | Then the Federal Reserve Banks will |
|---|---|---|
| Within two calendar years
of the ACH entry date. |
The Requestor is a Full-Service Participant* and the Responder is a Full-Service Participant or a Partial Service Participant* of the Exception Resolution Service | Send a same day acknowledgement to the Requestor if received by 8:00 p.m. ET Send a new exception case to the Responder |
| Within two calendar years
of the ACH entry date. |
No response is received from the Responder after 20 business days from receipt of the request | Send a cancellation message to the Requestor and close the case |
| Within two calendar years
of the ACH entry date. |
The Requestor receives a response and no action is taken by the Requestor after 20 business days from receipt of the response | Close the case |
| Within two calendar years
of the ACH entry date. |
The Requestor is not a Full-Service Participant of the Exception Resolution Service | Send a cancellation message to the Requestor and close the case |
| Within two calendar years
of the ACH entry date. |
The Responder is not a Participating Bank of the Exception Resolution Service | Send a cancellation message to the Requestor and close the case |
*Refer to the General Notes section for the definitions of the Exception Resolution Service Participant roles.
Required Fields
| Field Name | Field Description |
|---|---|
| Case Type | The investigation type that is being sent - WSUD. |
| Requestor ABA | The nine-digit routing number of the institution that is submitting the exception request to the Federal Reserve Banks. |
| Responder ABA | Auto-populates, after the ACH Transaction History Entry Lookup is performed (see below), with the nine-digit routing number of the institution that will receive the exception request from the Federal Reserve Banks. |
| Contact Name | The name of an individual who could be contacted regarding the submission of the exception request. |
| Telephone Number / Extension | The telephone number of the Requestor; to be used if there was a question regarding the exception request. |
| Reference Number | The reference number assigned to the exception as it is known by the Requestor of the message. |
ACH Transaction History Entry Lookup
| Field Name | Field Description |
|---|---|
| Settlement Date | The date an ACH transaction was settled in batch. If the Settlement date is keyed, the processing start and end date range will be automatically populated. |
| Processing Start Date | The date an ACH transaction was processed. Required if the settlement date is not entered as search criteria. If only the processing start date is keyed, a search will occur only on that date. To search using a date range, enter a Processing End Date as well. |
| Processing End Date | Required for a date range search. Enter the Processing Start and End date. |
| Trace Number | The trace number assigned to the item, by the originator of the entry, involved in the exception request. |
| Account Number | The account number from the ACH entry. |
| Amount | The amount of the item that is the subject of the exception request. |
| Originator Name | The Originator’s name from the batch header. |
| Originating ID | The Originator’s ID from the batch header. |
Transaction Information
| Field Name | Field Description |
|---|---|
| Settlement Date | The date an ACH transaction was settled in batch. |
| Effective Entry Date | The date the transaction was settled through the Federal Reserve Bank. |
| Originating DFI | The nine-digit routing number of the institution that originated the ACH entry. |
| Receiving DFI | The nine-digit routing number of the institution that received the ACH entry. |
| Trace Number | The trace number assigned to the item, by the originator of the entry, involved in the exception request. |
| Entry Amount | The amount of the item that is the subject of the exception request. |
| Account Number | The account number from the ACH entry. |
| Individual or Company Name | The account holder’s name (individual or company name) from the ACH entry. |
| Check Serial Number | Serial number of the check from a Converted Check Copy (not populated if the case type is not CCC). |
| Transaction Code | The National Automated Clearing House Association (NACHA) transaction code. |
| Transaction Type | Identifies the transaction type as a debit or credit entry. |
| Originator ID | The Originator’s ID from the batch header. |
| Originator Name | The Originator’s name from the batch header. |
| Processing Date | The date the ACH transaction was processed. |
| Sec Code | The NACHA Standard Entry Class (SEC) code. |