The postal Record provides standard functionality for managing single and group money transactions in an acceptable combination with the appropriate type of money transaction. Additionally, the way of providing the service - by cash or cashless (bank account) can be specified. The System allows to be configured with different types of postal money transactions, and for each type the payment method can be specified (single, group, cash, cashless). This configuration is performed as a result of analysis of the business processes that are taking place in your organization and the technological capabilities that BINETIX can provide.
The current version of BINETIX PTM is provided pre-configured with the following types of postal transactions:
❖Regular Postal Transaction (RPT) - intended to provide a standard postal money transaction service;
❖Express Postal Transaction (EPT) - intended to provide an express postal money transaction service;
❖Official money transaction - intended to provide an internal-branch or specialized postal money transaction services;
❖Cash on delivery (COD) - intended for making money transactions as a result of another implemented postal service on "cash on delivery" base.
The configuration allows the indicated postal money transactions to be paid on bank account and/or as group transactions. An exception to this rule is the Express transaction, which is limited to cash payments only.
Herein are discussed in more detail the following operating scenarios that illustrate key capabilities of the System in practice:
1)Sending cash payment by single postal express transaction, at the post office;
2)Sending cashless Postal COD transaction, at the post office;
3)Receiving of a Group postal money transaction;
4)Receiving of Postal money transaction in cash payment at the post office;
5)Receiving Postal money transaction in cashless payment at the post office;
6)Management of invitations of receiving Postal money transactions;
7)Centralized management of changes and cancellations of Postal money transactions.
Note: The access to illustrated above functionality depends on the user rights that are given to you in the System. You may see more or less screen elements according to the role you have in your organization. For more information, contact your System administrator or your coordinator responsible for implementing the System.
|