2.7 Teller

This topic provides information about enhancements in the Teller.

Table 2-1 Enhancements in Teller

Summary	Description
Support Third Party Cash Transaction Request for Cash Deposit and Cheque Withdrawal.	This release adds support for Third-Party Cash Transaction requests for Cash Deposit and Cheque Withdrawal by introducing a dynamic transaction-type selector on teller screens. Tellers can now choose between Self, Third Party, and Charge-by-Cash without switching screens, and the system automatically applies the relevant data segments, GL mappings, pricing rules, settlements, and validations. This improvement reduces reliance on custom deployments by allowing banks to set up new transaction variants using parent–child function code mapping. If configuration is unavailable, the system automatically reverts to the base transaction screen without interrupting teller operations.
Reversal configuration for Teller Transactions.	Introduced a new Reversal Configuration capability that allows banks to set the maximum number of days for reversing teller transactions for each function code. The system now determines a Max Reversal Date for every posted transaction and checks each reversal attempt against it. If a transaction exceeds the allowed timeframe, the system displays a clear message to the teller stating that the reversal is not permitted. This improvement gives banks better control, reduces operational risks, and ensures compliance with their reversal policies.
Customer and Account level Memo Handling in Teller Transactions screens.	The Branch Teller application now features improved Memo Alerts that automatically gather and display customer-level and account-level memos during teller transactions. When the teller exits the Account Number field, the system collects all active customer and account memos and combines them in the Memo Alerts widget. If memo verification is enabled for the function code, the teller must verify the displayed memos before proceeding.
Support Structured and Hybrid address format for Payment Requests to OBPM.	This release introduces support for structured and hybrid customer address formats in Branch Teller Payments related screens. Tellers can now view, validate, and capture addresses using the latest SWIFT-compliant formats.
Common-Adoption of Customer address formats	This release introduces support for structured and hybrid customer address formats in Branch Teller screens. Tellers can now view, validate, and capture addresses using the latest SWIFT-compliant formats, with mandatory Town Name and Country enforcement. Addresses for customer accounts auto-populate from common core, while walk-in/external parties benefit from easy manual entry and validation. UI enhancements include an Address Details drawer and improved Address display. All teller transactions now capture and display address data accurately, ensuring regulatory compliance and operational efficiency.
Teller consent for Cash transfer from Till to Till before completion.	A required consent step for cash transfers between tills has been implemented. When this feature is activated, the receiving teller must explicitly approve the transfer request before any cash is moved or recorded. This enhances operational control, stops unauthorized till changes, and increases the auditability of cash handling tasks. The process is smoothly incorporated into current teller operations without affecting the usual transaction screens.
Redesign the Teller Transaction Screens for Redwood Experience.	The Teller Transaction screens have been revamped with Oracle’s Redwood UI standards. The enhancement includes a refreshed layout, new icons, consistent typography, and a modern drawer-based panel for viewing transaction charges. The Customer Panel and Current Till Position widget have also been redesigned for better visibility and ease of use. The update brings the Teller Transaction screens in line with Oracle’s Redwood UI standards. It introduces a new layout, updated icons, consistent font styles, and a modern drawer panel for viewing transaction fees. The update also redesigns the Customer Panel and Current Till Position widget to improve visibility and user-friendliness.
Operational Ledger Cloud Service integration - Phase 2 (GL & Accounts)	Integration with Oracle Banking Operational Ledger Cloud Service (OBOLCS) has been extended to support teller transactions involving both General Ledger (GL) and customer (CASA) accounts. Accounting entries are now automatically routed to the appropriate host system based on account type. This enables centralized, accurate posting, improves reconciliation and reporting, and ensures consistent control across mixed GL and customer account transactions.
Multi BC Issuance against GL	The Multi Bankers Cheque Issuance function has been enhanced to support funding from a General Ledger (GL) account. When the GL issue mode is selected, multiple Bankers Cheques can be issued in a single batch using a designated GL as the funding source. This enables faster bulk issuance, reduces manual effort, and ensures consolidated, auditable accounting for GL-funded cheque operations, while keeping all existing authorization and lifecycle processes unchanged.