Your institution can use the ACH Manager for Account Opening (AO) in Narmi Command to view and manage your Narmi AO ACH Service transactions, including approving or rejecting ACH transactions in manual review and manually processing ACH transactions.
Note: For rejected transactions, your institution is responsible for reversing the transaction and removing any holds from the core. Narmi cannot reverse transactions. Go to Handling Manual Core Reversals for Rejected Funding Transactions to learn more.
In this article:
View AO ACH Transactions
Monitor your applicants’ transactions by viewing them in ACH Manager for AO.
To view ACH transactions:
From the Narmi Command sidebar, select Transactions > ACH manager > Account opening.
The ACH Manager page appears, displaying your Account Opening ACH transactions in review.
Tabs across the top correspond to ACH transaction status. Select a tab to view the applicants for that status. Some tabs only show when there are transactions for that status. For descriptions of each status, go to Account Opening ACH Statuses.
Each transaction row displays the following information:Applicant – Name of the user initiating the transaction
Created – Date the transaction was created
Account Number – The destination account that funds are moving to
Issue (For Review tab only) – The Microbilt result associated with the transaction. If there are multiple issues, select the transaction row to open a panel with details.
Assignee (For Review tab only) – The staff member assigned to the transaction. For more information, go to Assign Transactions.
Posting Status – If your institution has Real-Time Posting (RTP) enabled, “Posted” indicates that the ACH transaction was posted successfully to the core—funds have been moved to and from the General Ledger (GL) account designated for ACH RTP, and any relevant holds have been applied. “Not posted” indicates the ACH transaction was not successfully posted to the core.
Funding – The transaction amount
Select an applicant row to open a panel where you can view transaction details.
The following details display:
Status – The ACH status
Amount – The dollar amount of the transaction
Transaction type – Incoming
Created date – Date and time the transaction was created
Source sender – The name of the applicant
Source account number – Account number and account type from which funds are transferred. Account type displays for checking, savings, money market, or certificate of deposit.
Source routing number – Routing number of the institution from which funds are transferred
Destination recipient – The name of the applicant
Destination account numbers – The account number(s) and account type(s) receiving funds. If the account has not yet been opened on the core, the first part of the application ID is displayed. Account type displays for checking, savings, money market, or certificate of deposit.
Destination routing number – Routing number of the receiving institution
Transaction history – The timeline of events associated with the transaction, including:
When it was initiated
If in review, who and when it was approved or rejected by
When it was moved to a different state
If approved, when it was queued for processing
When it was processed
If it failed
If the transaction does not go into review and is auto-approved, the timeline shows:
When it was initiated
When it was moved to a different state
When it was queued for processing
When it was processed
Select View details in the timeline to see details, including:
Account selection method – Response from the validation partner: either IAV (instant account verification) or Manual (for manual only). Go to Account Validation for more information.
Status – Microbilt's status that prompted the review; some examples are: "Accept," "Warning (Insufficient history)," and "Decline (Account number is invalid)."
Name validation – Microbilt's validation of an applicant's first name, last name, and the organization name.
Related application – Select the link to open the application view.
If your institution has enabled hard reject of applications, you can select the 3 dots menu and choose Approve transaction or Reject transaction. Please contact your Narmi Relationship Manager to enable this option. See Review AO ACH Transactions for complete details.
To close the panel, select the “X.”
Search AO ACH Transactions
In AO ACH Manager, you can search for transactions using the search bar. Enter the applicant name (consumer or business name), source account number, or destination account number, and the search begins automatically.
To clear the search, select the "X" in the search bar.
Filter AO ACH Transactions
To filter the list of transactions:
In ACH Manager, select the filter icon.
Select from the following filters:
Applicant – Filter by applicant name
Created – Filter by the start date and end date range of when the transaction was created. Enter a date in MM/DD/YYYY format or select the calendar icon to choose from a calendar.
Funding account number – Filter by funding account number.
Amount – Filter by minimum and maximum transaction amounts.
Assignee – Filter by the staff member(s) assigned to the transaction by selecting one or more assignee names from the list, or enter a name in the Search field.
Posting status – Filter by whether the transaction was Posted or Not posted.
Select Apply.
Once you apply a filter, an indicator shows at the top of the list. Select the filter indicator to refine it further, or clear it by selecting Clear filter.
Review AO ACH Transactions
If there are transactions in the Review tab, you’ll need to manually approve or reject them. Select one or more boxes next to the transaction(s) and select Approve or Reject.
A dialog appears asking you to provide an optional reason for the approval or rejection. If more than one transaction was selected, a banner indicates how many transactions will be approved or rejected. Select Submit.
Approved transactions automatically move to the Pending tab, and the account will be opened on the core. Rejected transactions move to the Rejected tab, and the application moves to “Funding Failed” status. If you reject the transaction, the applicant receives either one of two notifications, depending on the maximum number of funding attempts allowed per application set by your institution:
If the user has funding attempts remaining, then they would be sent an email (automatically) asking them to re-fill out their transaction information and resubmit. This would create a new transaction.
If the user does NOT have funding attempts remaining, they receive an email notification of the rejection.
The number of attempts can be set in Narmi Command under Institution Settings > Maximum Funding Attempts Per Application. The default is 20 attempts. Each funding attempt gets added to a single total, even if the applicant switches between ACH and debit/credit card.
You can also reject the transaction in the Pending tab if the account does not need to be funded. Since the account is already open when it’s moved to “Pending” status, no email notification is sent to the applicant when a transaction is rejected from the Pending tab. Select one or more boxes next to the transaction(s) you would like to reject and select Reject.
Note: Rejecting the pending transaction does not update the application or account status. You cannot resubmit the application once it is rejected.
If you try to approve a transaction while the NACHA file is actively processing, you receive an error message instructing you to try again later.
Hard Reject of Application
You can also approve or reject the application from the transaction details, including a hard rejection.
To do this, select the applicant row, and in the panel that opens, select the 3 dots > Approve transaction or Reject transaction.
If you select Approve transaction, a dialog appears in which you can provide an optional reason for approval. Select Submit. A confirmation message appears indicating the transaction was processed.
If you select Reject transaction, a dialog appears for you to choose how to reject:
If the applicant has funding attempts remaining, you can choose to Allow applicant to retry funding or Reject application to perform a hard reject that rejects the transaction and application.
If the applicant does not have funding attempts remaining, the only option is Reject application.
You can also provide an optional reason for the rejection. Select Submit to finish. Once rejected, the applicant receives an email notification.
Manually Process AO ACH Transactions
Your staff may need to manually process AO ACH transactions if your institution does not have automatic ACH processing set up with Narmi, or if it has automatic processing but chooses to process transactions manually. When processing a transaction manually, we ensure it is not included in the end-of-day to prevent duplicates.
To manually process AO ACH transactions:
Approved transactions show in the Pending tab. Select one or more boxes next to the transaction(s) you would like to process and select Manually Process. The transaction(s) automatically move to the Processing tab.
You can also bulk-process all transactions in the list. Select the top checkbox next to "Applicant" (which selects all transactions on the current page) or choose Select all eligible transactions if there are multiple pages. Then select Manually Process.
In the Processing tab, select one or more transactions, then select Download file to download the NACHA file. If you’d like to reject the selected transaction(s) instead, select Reject.
Once the *.txt file is downloaded, submit the NACHA file in accordance with your existing ACH process so it gets processed by your operator.
Select Mark as processed to mark the transaction(s) as processed. The transaction(s) automatically move to the Processed tab.
Download AO ACH Transaction History
To review historical files, you can download your processed ACH transaction history. To download the transaction history:
In the Processed tab, select Download.
In the dialog that appears, select the specific batch file, then select Download.
Handling Manual Core Reversals for Rejected Funding Transactions
In some instances, an account opening transaction may be rejected by FI staff after a posted entry has already been recorded on the core. Because ACH returns are processed through the Fed (external to the Narmi platform), these reversals cannot be automated within the Narmi platform and require manual intervention on your core system.
Why does this happen?
When an applicant funds a new account, Narmi initiates the transaction and places an ACH hold on the funding amount. This hold is a protective measure to ensure the transaction clears before the funds are fully accessible.
If the transaction is ultimately rejected — most commonly due to insufficient funds in the source account rather than fraud — the following manual steps must be taken to reconcile your ledgers.
Action Steps for FI Staff
If you identify a rejected transaction that has already been posted, please follow your internal standard operating procedures to complete the following:
Manual Core Reversal: Reverse the deposit entry to the new account and the corresponding offsetting General Ledger (GL) entry.
Manage Holds: Delete the existing ACH funding hold.
If the account is to remain open while awaiting alternate funding, determine if a full balance hold is required per your FI's risk policy.
Account Status: Decide whether to close the account immediately or keep it active.
Member/Customer Outreach: Reach out to the individual to:
Notify them of the rejected funding.
Request they visit a branch or send an alternate funding method by a specific date/timeframe to keep the account active.
Note: While these rejections require manual work, the majority of these cases are caused by simple insufficient funds in the external account, not malicious intent.