Defining the Master Data for Teller module

To define the master data:

  • Use the Teller Module Constants (lptur1100m000) session to specify the data for the teller module. You can use this session to define this data:
    • Main Company: The main company that we use in transactions
    • Currency: The local currency of the transactions.
    • Country: The country where the transaction occurs
    • Transfer on Approval: The transactions posted in cash management are transferred to finance when the transaction is approved.
    • Automatic Argument ID: Select this check box to assign an automated queue number to verify each new check data in the system
    • Reeskont Rate: The rate of the re-discount
    • Warning Defined Holidays: Select this check box for important holidays.
  • Use the Companies (lptur1101m000) session to define the company code and name for the transactions. If the transactions are posted to finance then accounting option is selected.
  • Use the Entities (lptur1102m000) session to define the 'entities groups' for the cash management. Entity is the predefined parameter that is used to define characteristics of the planned transaction. Entities are defined in debit/credit parameter of the transaction types of Cash Management module. Ledger integration for each entity transaction type couple is defined in this session. You can define this data:
    • Entity: This is to define entities by domain.
    • Entity name: By using “References” on the menu, Ledger Accounts can be accessed that are defined for this company as debit/credit. For instance, the Bank entity, transaction types are specified, and ledger mapping is defined.
  • Use the Transaction Rules (lptur1115m000) session to define the transaction rules at the transaction type level for all cash transaction type. Transaction rules are defined by defining debit and credit and entity type, argument type, argument status (before transaction), new argument status after transaction is approved, integration type (voucher, argument) Transaction types are pre-defined in Transaction Types (tfgld0511m000) session. In this session you can define this data:
    • Transaction Types: The transaction type that is defined.
    • Description: The name of the transaction type.
    • Debit Entity Type: The transaction type for the debit transaction
    • Debit Entity Number: The default ledger account where the transaction is posted. This is based on the account type.
    • Credit Entity Type: The transaction type for the credit transaction
    • Credit Entity Number: The default ledger account where the transaction is posted. This is based on the account type.
    • Argument Type: The argument type that is selected for the transaction
    • Argument Status: In check and bill transactions, this is the place of the definition of status of checks and bills before the transactions
    • VAT needed: Indicates if a VAT must be used or not for the defined transaction type
    • Integration Type: The type of integration applicable for the transaction. The two possible values are:
      • By Voucher: When a transaction is posted to customer and supplier tables in Finance, related with the defined transaction type, it creates one posting for the entire payroll.
      • By Argument: When a transaction is posted to customer and supplier tables in Finance, related with the defined transaction type, it creates a detailed posting for the entire payroll.
    • Transfer to teller: It is possible to collect all the check transactions in one teller. In this parameter, when a transaction is posted with the related transaction type, the entity type of KK that would be transferred is specified in this field. The possible status for general argument are:
      • Free in portfolio : Check is in portfolio of the company and open for any transaction for endorsing to supplier or sending to bank, or sending back to customer.
      • Allocated in portfolio: Means check is allocated for a reason, mostly sending to bank.
      • Dishonored in portfolio: Check is received back from supplier or bank
      • Unknown in portfolio: Check does not have any status yet in portfolio, the first status before receiving check from customer.
      • Given out: Check that is endorsed to supplier
      • Unusable: The status when dishonored check is returned to the customer of the company
      • Cashed: The status when the check is paid
  • Use the Banks (lptur1116m000) session to define the bank or branch that is used for recording the cash and note transactions. By using the References Menu of bank session bank branches can be defined.
  • Use the Banks Branch (lptur1117m000) session to define the branch details for the bank such as branch name, city, province and so on.
  • Use the Our Checks (lptur1121m000) session to create the company’s own check. You can define data such as bank information, company, teller id who creates company check, starting argument id and ending argument ID.
  • Use the General Arguments (lptur1521m000) session to update the general arguments in the system. This session displays all the company or customer checks/notes. By double clicking the selected argument, it is possible to access update session of arguments.
  • Use the Holidays (lptur1130m000) session to define the holidays. You can use the data in this session to track due dates of check both received from customer and companies own checks.