Scribd
Upload
651 views

How To Set EB Mandate Parameter, EB Signatory Groups and Minimum Signatory Requirement For Financial and Non Financial Transactions

This document discusses setting up minimum signatory requirements for financial and non-financial transactions in EB. It provides 4 scenarios that demonstrate: 1) Minimum signatory validation for a teller transaction when the mandate is set for the account 2) Minimum signatory validation for a teller transaction when the mandate is set for the customer 3) Minimum signatory validation using an API attached to the amount field 4) A transaction moves to INAO status when the minimum signatories are not attached

Uploaded by

Tes Tesfu
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
651 views

How To Set EB Mandate Parameter, EB Signatory Groups and Minimum Signatory Requirement For Financial and Non Financial Transactions

This document discusses setting up minimum signatory requirements for financial and non-financial transactions in EB. It provides 4 scenarios that demonstrate: 1) Minimum signatory validation for a teller transaction when the mandate is set for the account 2) Minimum signatory validation for a teller transaction when the mandate is set for the customer 3) Minimum signatory validation using an API attached to the amount field 4) A transaction moves to INAO status when the minimum signatories are not attached

Uploaded by

Tes Tesfu
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 23

How to Set EB Mandate Parameter, EB

Signatory Groups and Minimum Signatory


Requirement for Financial and Non
Financial Transactions
Summary
 set the EB Mandate parameter for Financial and Non Financial transactions

 set the EB Signatory Groups

 check the minimum Signatory requirement during the processing of financial and non
financial transactions

Scenario 1:

To show the Minimum Signatory requirement for a Teller transaction (financial), when the
Mandate is set for the account.

The override ‘Minimum Signatory not reached’ is displayed when the required Signatories
are not attached to the transaction and are subsequently processed upon attaching the them.

Pre-requisite: Mandate to be attached to the Account record.

The following screen shot shows the group of Department Heads who work for Temenos
Quality Systems (Customer Id- 110258). A Signatory group has been created in the system
for the same with the id <Customer id.XXX>, which identifies the list of Dept Heads who
belong to the Company.
The following screen shot shows the group of Managers who work for Temenos Quality
Systems (Customer Id- 110258). A Signatory group has been created in the system for the
same with the id <Customer id.XXX>, which identifies the list of managers who belong to
the company.
The set up done in the EB.MANDATE for Temenos Quality System record.

Amount range Number of Signatories Level of Signatory


Upto 25000 1 Dept head
25001- 50000 2 Dept head
(or) 1 Manager
50001-100000 2 Manager
  1 Director

The system displays an override ‘Minimum Signatory not reached’ when the Teller
transaction does not have any Signatories attached. As per the above setup for any amount
upto 25000, one Dept Head is required for processing the transaction without any override. It
may be noted that the system checks the fields ACCOUNT.1 and AMOUNT.LOCAL.1 for
performing the Signatory validations, which is as per the setup in the
EB.MANDATE.PARAMETER
Once the Signatory is attached, the transaction is processed without the Signatory Override.
Scenario 2:

To show the Minimum Signatory requirement for a Teller transaction, (financial), when the
Mandate is set for the customer.

The Override ‘Minimum Signatory not reached’ is displayed when the required signatories
are not attached to the transaction and are subsequently processed upon attaching the same.

Pre-requisite: Mandate to be attached to the Customer record.


The system displays an override ‘Minimum Signatory not reached’ when the Teller
transaction does not have any signatories attached. As per the above setup for any amount
upto 50000, two Dept Heads or one manager is required for processing the transaction
without any override. It may be noted that system checks the fields CUSTOMER.2 and
AMOUNT.LOCAL.2 for performing the signatory validations, which is as per the setup in
the EB.MANDATE.PARAMETER
Once the signatory is attached, the transaction is processed without the Signatory Override.
Scenario 3:

To show the Minimum Signatory requirement for a Teller transaction (financial), when the
Mandate is set for the account with an API attached to the Amount field.

The override ‘Minimum Signatory not reached’ is displayed when the required signatories are
not attached to the transaction and are subsequently processed upon attaching the same.

Pre-requisite: Mandate to be attached to the Account record.

View of EB.API record:


View of EB.MANDATE.PARAMETER record:

View of EB.MANDATE record:


View of EB.SIGNATORY.GROUP.RECORD:

View of Account
Before attaching signatories, ‘Minimum Signatory not reached’ override is displayed:
After Attaching Signatories, ‘Minimum Signatory not reached’ override is not displayed:
Scenario 4:

To show the Minimum Signatory requirement for a Teller transaction (financial), when the
Mandate is set for account.

The override ‘Minimum Signatory not reached’ is displayed when the required Signatories
are not attached to the transaction and the status of the Teller transaction is moved to INAO.

Pre-requisite: Mandate to be attached to the Account record:


After committing the record without attaching the signatory, the record goes to INAU.
After authorising the record, Status moves to INAO.
 Published on: 25/04/2019

You might also like