Navigation: Deposit Reports > Deposit Reports - Numerical Order >
Availability
This report should be run daily in the afterhours.
Purpose
The Outbound ACH Report (FPSDR147) lists all outbound ACH batches for an institution. This would include such transactions as automatic loan payments, customer-directed transfers, ACH returns, etc.
The files are transmitted to the Federal Reserve Bank (FRB) four times each day at 6:00 a.m., 12:00 p.m., 6:00 p.m., and 12:00 a.m.(MT).
Batch Heading Information (Summary)
See FPSDR147 Example for an example of this report.
Column Heading |
Description |
---|---|
Originating Company Name |
This is the name of the company originating the batch. |
Company ID # |
This is the ID number for the company originating the batch. |
Transaction Description |
This tells what type of transactions are in this batch. |
Standard Entry Class |
This is the standard entry class (PPD, LOC, MTE, etc.). |
Effective Date |
This is the effective date of the batch. |
Batch # |
This is the batch number. |
Posted |
This is the date on which the batch was transmitted to the FRB. (These batches will appear on this report for three days after this date.) |
Batch Line Item Information (Detail)
See FPSDR147 Example for an example of this report.
Column Heading |
Description |
---|---|
TC |
This is the ACH transaction code. |
Description |
This is the description of the transaction being originated. |
Destination Name |
This is the name of the institution that will be receiving the transactions. |
Routing # |
This is the routing number of the receiving institution. |
Phone # |
This is the phone number of the receiving institution. |
Original Trace # |
This is the trace number found on the original rejected item that was returned. |
ACH Name |
This is generally the customer name. |
Account # |
This is the account number the ACH item is being sent to. |
Trans. Amount |
This is the transaction amount, debit or credit. |
Trace # |
This is the trace number of this transaction. |
ACH ID # |
This is the customer/ACH identification number. |
Original Return Code |
This is the original return code of the rejected item that was returned. |
Totals and Subtotals Provided
See FPSDR147 Example for an example of this report.
Column Heading |
Description |
---|---|
Total Entries |
This is the number of transactions in this batch. |
Total Credits |
This is the total amount of credits in this batch. |
Total Debits |
This is the total amount of debits in this batch. |
Sort Options
This report has two levels of sorting that can be used. The primary level is the batch sort. This type will sort the batches within the report.
The second-level sort is the transaction sort. This allows each transaction within a batch to be sorted. The following list displays the sort keys and what they are sorted by.
Primary (Batch) Sort Keys |
Sorted By |
80 |
Originating Company |
81 |
Company ID Number |
82 |
Batch Description |
83 |
Effective Date (value of 8 for totaling) |
84 |
Batch Number |
91 |
Posted Date (value of 3 for totaling) |
Secondary (Transaction) Sort Keys |
Sorted By |
86 |
Destination Routing Number |
87 |
Trace Number |
88 |
Transaction Code |
89 |
ACH ID Number |
90 |
ACH Name |
To balance back to the Federal Reserve Bank Settlement Statement, set up the following Sort fields and Criticals:
Set the first Sort field to “91” and the second Sort field to “83.” Then set the Critical From field and the To field to “1” and “15.” This will subtotal the Effective Date amounts within the Posted Date and create a subtotal for transaction amounts at each Posted Date.
GOLDPoint Systems Only: Criticals Needed:
If sort=80, 1 to 20 If sort=81, 1 to 14 If sort=82, 1 to 14 If sort=83, 1 to 12 If sort=84, 1 to 11 |
---|
Institution Totals and Subtotals
If needed, the report can be broken up to display subtotals along with the institution totals. The report will subtotal according to any changes in the first primary sort.
GOLDPoint Systems Only: The way the report is sorted depends on what sort keys are used in the report setup. Below is a list of rules that need to be followed when setting up the report.
•The primary sort key needs to be the first sort key in the report setup. •The secondary sort key needs to be the third sort key in the report setup. •If you decide to use the secondary sort, the second sort key defined in the report needs to be 85. This is required to keep the transactions in their correct batches. •The critical fields in the report setup need to be set to the criticals listed above in the primary sort options for the subtotaling to work correctly. (For example, if subtotaling by Company ID number, put 1 to 14 in the criticals.) •It is possible to sort the report by one primary level and then by another primary level. When doing this, only the first two sort keys are needed. Put the two primary sorts you want to use in these boxes in the order you want them done.
Note: When using two primary sorts, you lose the ability to do a second-level sort. (For example, if you sort by the effective date and then by the company name, you can’t sort the transactions in any specific order.) |
---|