Ensenta Workflow

This article covers two workflows for Ensenta—the Standard workflow and Narmi's real-time posting workflow.

Standard Workflow

When a user is in the mobile app and completing a mobile check deposit, the following steps always occur for a client with Ensenta.

1. Narmi sends the following information to Ensenta when the mobile deposit session is initiated:
   • Account holder Names (primary and secondary)
   • Email address
   • IP address
   • AccountHolderAttribute with AttributeName = Tier
   • AttributeValue = [Name of mapped segment]
2. The user completes the check image capture on their mobile device and submits the deposit.
3. Ensenta's Risk Mitigation Engine validates the check information:
   • Uploaded image is a check (via OCR)
   • Check date
   • Deposit amount
   • MICR line (routing number, account number, check number)
   • Restricted endorsement
4. The remote deposit is accepted and moves into review queues based on FI's determined risk rules/routing (e.g., back signature not detected → Needs Review Queue).
5. Your institution's staff logs in to EZAdmin to review queues and hold, approve, or adjust (up/down) amounts.
6. Every day after your institution's selected cut-off time, Ensenta generates an X9 file (or "cash letter file") for manual or automated transmission to the Item Processor Vendor or FRB.
7. Item Processor Vendor submits the X9 file to the Federal Reserve Bank or presentment point for settlement.
8. Your institution’s segment-specific $ limits and hold days apply for fund availability.
9. Your institution can opt to send email notifications to users with copies of checks and subsequent notifications for changes in deposit status.

Note: Narmi posts RDC transactions directly to the core banking system. Narmi is not dependent on the Ensenta system to do so. 

Add-on Services

The following steps occur for add-on services that can be purchased.

Integrated Fraud Check

1. Upon remote deposit acceptance, deposits that meet your institution's set dollar threshold will be sent from Ensenta to EWS:
   • Routing number
   • Account number
   • Check number
2. EWS returns risk factors in categories that route deposits to a client's defined Ensenta review queues (see table below).
3. Checks are reviewed in EZAdmin for approval, adjustments, or decline.
4. Your institution's determined segment $ limits and global hold days apply for fund availability.
5. Your institution's staff can view a monthly EWS report to review all items sent to EWS during the prior month.
   
   

*High-risk queue is only available with Integrated Fraud Check.

Smart Alerts (Real-Time Fraud Monitoring)

• Upon remote deposit acceptance, a 'Deposit Submitted' alert is sent to Verafin.
• Verafin runs deposit fraud analytics and sends an alert email to your institution if a deposit is potentially fraudulent.
• Your staff uses the Verafin online portal to assist in investigating the deposit.
• Your staff makes the final decision in EZAdmin; the final status "alert" is sent to Verafin.
• Your institution's determined segment $ limits and global hold days apply for fund availability.

Narmi Real-Time Posting Workflow

1. The user submits their remote deposit via the Mitek image capture component in the mobile app.
2. The deposit is reviewed against your institution's defined risk rules and is pushed to:
   • Review queue(s) - managed by your staff in Ensenta EZAdmin
   • Reject status - uncommon; only caused by OCR fail or client-determined fraud rule
3. Narmi does not know the exact queue a deposit is in, so Narmi posts all deposits in manual review queues to the user's account
4. Manual reconciliation in the core is required for any adjustments (e.g., corrected amounts, reversals) made in the EZAdmin Portal during manual review via:
   • Direct change in the core system (e.g., reversal, amount adjustment)
   • A batch process using an X9 file that contains all rejections within the EZAdmin Portal
5. Your institution's determined holds and limits apply for fund availability.