Customer's Deposit is Memo Posted Twice, Thirty Minutes Apart.

Customer's Deposit is Memo Posted Twice, Thirty Minutes Apart.

The teller processed a deposit at 10:05 AM. The customer's account shows a memo post at 10:05 AM, and a second memo post for the same transaction at 10:35 AM. Why?


Workaround:

This double memo post occurred because the teller did not follow suggested procedures.


Follow these steps to research this issue:

  1. Open Superview, and select the teller's branch as your working group.
  2. Go to EZTeller Roles > Journal Scan, and configure a query to view teller's journal.
  3. Highlight the transaction in question and click on View Record
  4. The Status box shows a P (Host timed-out, teller chose to repost.)

 

Note: In this example, the P tells us that the teller was online when processing the transaction. She clicked Proceed to send the transaction to the host. EZTeller did not receive a reply from the host.  As a result, the teller was given the option to Click Q to quit. EZTeller went online-inactive.
 

  1. Later in the day when the teller reconnected to the host, the following Information Box appeared on the EZTeller screen: There is a total of <1> backlogged transactions. Press -0- to send to the host.
  2.  The teller pressed -0-.

 

Note: EZTeller would have displayed a message indicating that the transaction had previously been sent to the host and would have given the teller the option to Inquire.  If the inquiry had been done, the host display would have shown that the transaction had already memo posted. The teller could have chosen to continue without reposting.
 

  1. In this case the teller did not do the inquiry and chose to repost.  EZTeller sent the memo post again to the host and the customer had two memo posts for the same transaction.

ArticleNumber:

000066750