pub:ach_installation
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
pub:ach_installation [2025/05/22 20:53] – [Work with Database Map Fields] kkramer | pub:ach_installation [2025/05/27 18:28] (current) – [Work with Spool Map Fields] kkramer | ||
---|---|---|---|
Line 30: | Line 30: | ||
|BEFDATE | |BEFDATE | ||
|BORGDFI | |BORGDFI | ||
- | |BSECCODE |Standard Entry Class Code. Identifies the entries in the batch. Common standard entry class codes are PPD (Prearranged Payments and Deposit entries) for consumer items, CCD (Cash Concentration and Disbursement entries), CTX (Corporate Trade Exchange entries) for corporate transactions, | + | |BSECCODE |Standard Entry Class Code. Identifies the entries in the batch. Common standard entry class codes are **PPD** (Prearranged Payments and Deposit entries) for consumer items, |
|BSRVCLS | |BSRVCLS | ||
|DCHECKAMT | |DCHECKAMT | ||
Line 44: | Line 44: | ||
|DPAYTYPE | |DPAYTYPE | ||
|DPAYTYPE* |Payment type code. Input ‘R’ for recurring payments, and ‘S’ for a single-entry payment. This field is used for a multiple lines of spool text (block text)| | |DPAYTYPE* |Payment type code. Input ‘R’ for recurring payments, and ‘S’ for a single-entry payment. This field is used for a multiple lines of spool text (block text)| | ||
- | |DTRNCODE | + | |DTRNCODE |
|DTRNCODE* |Same as DTRNCODE but it is used for multiple lines of block text| | |DTRNCODE* |Same as DTRNCODE but it is used for multiple lines of block text| | ||
|HBANKNAME |Your company’s bank name| | |HBANKNAME |Your company’s bank name| | ||
Line 71: | Line 71: | ||
To enroll more payees, press F8=Enroll Payees, you will see the list of defined payees who are not enrolled, select option 1 on the payees from list you want to enroll and press Enter | To enroll more payees, press F8=Enroll Payees, you will see the list of defined payees who are not enrolled, select option 1 on the payees from list you want to enroll and press Enter | ||
{{: | {{: | ||
+ | |||
+ | ====== Work with ACH Applications | ||
+ | < | ||
+ | [[start# | ||
+ | |||
+ | ===== Work with ACH Applications ===== | ||
+ | |||
+ | This screen allows users to view, edit, copy, delete, or rename Automated Clearing House (ACH) payment applications. Each row represents a configured ACH Application that can be managed. | ||
+ | {{pub: | ||
+ | **Main Columns:** | ||
+ | | **Column** | **Description** | | ||
+ | |Option | Enter an action option (e.g., 2, 3, 4, 7) for the respective ACH Application| | ||
+ | |ACH Application |Application Name – unique identifier for the ACH configuration| | ||
+ | |Description | ||
+ | |Creation/ | ||
+ | **Available Actions:** | ||
+ | | **Option** | **Function** | **Description** | | ||
+ | |2 | Edit |Modify an existing ACH application| | ||
+ | |3 | Copy |Duplicate an existing application with a new name| | ||
+ | |4 | Delete |Remove the application from the system| | ||
+ | |7 | Rename |Change the name of an existing application| | ||
+ | | **Column** | **Description** | | ||
+ | **Function Keys:** | ||
+ | | **Key** | **Action** | **Description** | | ||
+ | |F3 | Exit |Return to the previous menu| | ||
+ | |F5 | Refresh |Reload the screen data| | ||
+ | |F6 | Add |Create a new ACH application entry| | ||
+ | ===== Maintain an ACH Application ===== | ||
+ | This screen allows users to configure or maintain the ACH file definitions for a given ACH Application. The structure follows the standard NACHA file format, including: | ||
+ | * File Header Record | ||
+ | * Batch Header Record | ||
+ | * Entry Detail (not shown here but linked via F18) | ||
+ | {{pub: | ||
+ | **Section 1: ACH File Header** | ||
+ | | **Field** | **Description** | **NACHA Reference** | | ||
+ | | Payor Company ID |10-digit unique identifier of the originating company |File Header Record, Field 1 | | ||
+ | | Payor Company Name |Legal name of the originating company (e.g., Performance Contractors)|File Header Record, Field 2 | | ||
+ | | Payor Bank Transit# |Bank’s routing transit number (RTN)|File Header Record, Field 3 | | ||
+ | | Payor Bank Name |Optional field for audit tracking |File Header Record, Field 4 | | ||
+ | | Bank Trace Number|10-digit unique identifier of the originating company |Optional | | ||
+ | | File ID Modifier |1-character code to differentiate multiple files per day (e.g., A, B, C)|File Header Record, Field 11| | ||
+ | | File Creation Date / Time |Date & Time when the file is generated (YYMMDD, HHMM)|File Header Record, Field 5 | | ||
+ | **Section 2: ACH Batch Header** | ||
+ | | **Field** | **Description** | **NACHA Reference** | | ||
+ | | **Company Entry** | ||
+ | |** Originating DFI ID** |First 8 digits of the ODFI’s RTN (DFI = Depository Financial Institution)|File Header Record, Field 9 | | ||
+ | | **Standard Entry Class** |Code representing the type of transactions, | ||
+ | | **Transaction Code** |Code for transaction type: **22** Deposit destined for a Checking Account **23** Prenotification for a checking credit **24** Zero dollar with remittance into Checking Account **27** Debit destined for a Checking Account **28** Prenotification for a checking debit **29** Zero dollar with remittance into Checking Account **32** Deposit destined for a Savings Account **33** Prenotification for a savings credit **34** Zero dollar with remittance into Savings Account **37** Debit destined for a Savings Account **38** Prenotification for a Savings debit **39** Zero dollar with remittance into Savings Account | ||
+ | | **No. records of batch** | Number of entry detail records included in a batch |Batch Control Record | | ||
+ | **Section 3: Processing Control** | ||
+ | | **Field** | **Description** | | ||
+ | |**Descriptive Date** | Text description of the file creation date (for reference)| | ||
+ | |**Service Class Code** |Classifies transaction: | ||
+ | |**Effective Entry Date** |Date when entries are intended to post (YYMMDD)| | ||
+ | |**Prefix of ACH Files** |Prefix character (e.g., Z) used when naming the file in IFS| | ||
+ | |**Hold Processing** |Set to Y to hold processing (i.e., prevent file from transmitting), | ||
+ | **Navigation & Function Keys** | ||
+ | | **Key** | **Function** | | ||
+ | |F3 | Exit to previous menu| | ||
+ | |F4 |Prompt field values (help)| | ||
+ | |F10 |Save current ACH definition| | ||
+ | |F12 |Cancel without saving| | ||
+ | |F18 |Go to transaction records (Entry Detail)| | ||
+ | |F20 |View generated ACH files| | ||
+ | |||
+ | |||
====== Work with ACH Files Option 3 ====== | ====== Work with ACH Files Option 3 ====== | ||
Line 76: | Line 142: | ||
[[start# | [[start# | ||
- | ===== Work with ACH Files ===== | ||
From iPayment menu, select item 3. Work with ACH Files. | From iPayment menu, select item 3. Work with ACH Files. | ||
{{pub: | {{pub: | ||
Line 166: | Line 231: | ||
====== Merge ACH Definition with Database | ====== Merge ACH Definition with Database | ||
- | When a DB connection was defined in ACH Definition, you can merge it by select option 19=Merge with Database, or you also can merge with some external database by selecting Opt 11 or API command IMRGACHDB. | + | When a DB connection was defined in ACH Definition, you can merge it by select option 19=Merge with Database, or you also can merge with some external database by selecting Opt 10 or API command IMRGACHDB. |
{{: | {{: | ||
Line 181: | Line 246: | ||
* In order to see what spool file a transaction is created from, select option 9=Mrg Spool Files. If Mrg Spool Files is empty, it means the transaction is created by merge ACH definition with an external database. | * In order to see what spool file a transaction is created from, select option 9=Mrg Spool Files. If Mrg Spool Files is empty, it means the transaction is created by merge ACH definition with an external database. | ||
+ | ====== Work with Selected Access Groups Option 15 ====== | ||
+ | You can assign the authority to some users or some groups to have permissions on some function by set up Selected Access Authorization. By default, users with *SECOFR permission can access this menu. | ||
+ | There are 04 permissions mainly: Read, Update, Write and Execute in respectively. The permission Write will override Read and Update, and the permission Update will override Read. | ||
+ | |||
+ | Firstly, you need to define a Selected Access Groups. From iPayment menu, select item 15. Work with Selected Access Groups | ||
+ | |||
+ | {{: | ||
+ | {{: | ||
+ | Press F6=Add to add a new group. | ||
+ | |||
+ | Select option 12=Work with Users to add or remove some user from group. | ||
+ | |||
+ | ====== Work with Selected Access Groups Option 20 ====== | ||
+ | After defining a group, you will assign the permissions for the group by select menu item 20. Selected Access Authorization. | ||
+ | {{: | ||
+ | There are 08 modules you can set the access authorization. Select one of the modules by option 1, then hit Enter | ||
+ | {{: | ||
+ | In the screen Work with Selected Access User/Group, you can add a Group or a particular user. | ||
+ | To add a Group, press F8=Add a Group. | ||
+ | {{: | ||
+ | Enter the group name and assign the permissions on Group | ||
+ | |||
+ | To add a user profile, press F6=Add a User | ||
+ | |||
+ | {{: | ||
+ | Enter the user ID and assign the permissions on User | ||
+ | |||
+ | |||
+ | < | ||
+ | [[start# | ||
\\ | \\ | ||
\\ | \\ |
pub/ach_installation.1747972422.txt.gz · Last modified: 2025/05/22 20:53 by kkramer