ACH payments enable business users to send or collect funds to/from third parties without requiring pre-verified external accounts. Businesses can leverage this functionality for various purposes, including distributing employee payroll, making vendor payments for services rendered, or collecting subscription payments. Narmi Banking supports one-time and recurring payment scheduling, allowing users to set specific send dates. When initiating payments, users have the flexibility to create new recipients or select from their existing contact list, with the option to supplement any missing banking details as needed for that rail. For more information on ACH payments, go to About ACH Payments.
Narmi Banking supports both individual and bulk payments. The following instructions cover individual payments. For bulk payment instructions, go to Make a Bulk ACH Payment.
To send or collect a single ACH payment:
From the web or mobile app, select Transfer > Payments > Make a payment.
On the page that appears, select Send payment to send an ACH payment to a recipient or Collect payment to collect an ACH payment from someone.
Select a Recipient. To add a new recipient, select Add a new recipient from the Recipient dropdown. Go to Add an ACH Payment Recipient for more information.Select Continue.
Once you select the recipient, you can choose Edit to update the recipient’s details.
Under Payment details:
Select From account to choose the source account for the sending a payment or To account to choose the destination account for collecting a payment.
Enter the Amount of the payment.
Add an optional note in the Memo field. This will be posted with the transaction. To enable the Memo field, please contact your Narmi Relationship Manager.
Select View your ACH limits and disclosures to view the ACH payment disclosure text and limits. To update the disclosure text for your institution, go to Narmi Command under Configurations > Institution settings and edit the following settings:
Institution Ach Payment Disclosure – For sending payments
Institution Ach Collect Payment Disclosure – For collecting payments
For information on setting limits, go to Transfer Limits.
Select Date to open a calendar and choose when you would like the payment sent.
If you would like this to be a recurring payment, select Repeat this payment. Select the Frequency—Daily, Weekly, Every two weeks, 1st and 15th, Monthly, or Yearly. Then configure when the recurring payment should end—Never, on a specific date, or after a specific number of payments. If you select a specific number of payments, the total amount of the payments is shown.
Select Next.Select a Transaction type and an Entry description (both required) that goes into the NACHA file. To customize the list of entry descriptions, please contact your Narmi Relationship Manager. Default entry descriptions are:
Ext Transf – General external transfers
Payroll – Employee salary and wage payments
Bill Pmt – General bill payments
Refund – Reimbursements or returned funds
Loan Pmt – Loan repayments
You can also enter optional Internal details.
If your institution has Elevated Authentication enabled for ACH payments, the next page requires identity verification by entering a two-factor authentication (2FA) code. Select a verification method and select Continue. Follow the prompt on the next page to enter the code that appears on the trusted device.
To enable or disable Elevated Authentication for ACH payments, go to Narmi Command under Institution Settings > Features Requiring Elevated Authentication > ach_payments. After a user completes the 2FA step, they remain in Elevated Authentication Mode for the length of time in seconds that is specified by Elevated Authentication Mode Duration institution setting. To ensure a user has sufficient time to receive and enter their authentication code, the default is 600 seconds (10 minutes).
For users who have biometrics set up on their mobile device, Elevated Authentication uses biometric verification instead of 2FA. Please contact your Narmi Relationship Manager to enable sudo mode biometrics for your institution.
For more information, go to Elevated Authentication.
Review payment details and select Make payment.
A payment receipt appears. Select Done to be directed to the Payment Activity page or select Make another payment.
If the business has dual approvals enabled, payments are submitted for approval to all Org users with permissions to approve payments on the web app and mobile app. For more information, go to Using Dual Approvals for ACH Payments.
Once the payment passes risk evaluation, whether automatically or manually, we send the user an email confirming the initiation of the payment. To learn about the individual ACH payment communications we send, go to End-User Communications - Individual ACH Payments.
For more information on manually approving payments that your institution's risk settings have flagged, go to Use DB ACH Manager for Review.
Transaction Type SEC Codes
Transaction Type SEC Codes (Standard Entry Class codes) are three-letter codes used in the U.S. ACH network. They describe the type of ACH transaction, specify how the payment information was collected, and state the purpose of the transaction. These codes are crucial for accurate processing, compliance with authorization requirements, and effective risk management. To update the SEC Codes that users select in the payment flow, please contact your Narmi Relationship Manager.
The following codes are available to select in the Transaction type field (for individual ACH payments) or the Payment type field (for bulk ACH payments) in Narmi Banking:
CCD Payment (Cash Concentration or Disbursement) – A CCD entry can be either a buyer-initiated or seller-initiated transaction used to move funds between the buyer’s and seller’s financial institution accounts. Companies also use it to move funds from outlying depository locations to a central bank account. A CCD entry supports including one addenda and is typically used when paying for one item.
PPD Payment (Prearranged Payment and Deposits) – A PPD entry is a credit or debit entry originated by an organization to a consumer’s account based on standing or single-entry authorization from that consumer. A PPD entry supports including one addendum.
