The Payment module is integrated into Sage XRT Treasury ERP software.
This module is designed to meet your needs in terms of payment order management, and particularly treasury transfers, in a fully secure environment.
Its modularity enables interfaces between the systems - and hence data exchange -, the dematerialization of flows, the enhanced rapidity and security of your banking exchange. All these possibilities will generate a substantial gain for you company, in terms of performance and productivity.
Fully integrated to the Sage XRT Treasury suite, Payment is in constant communication with the Cash, Sage XRT Signature and Sage XRT Communication modules to ensure a real-time update of flows. Sage XRT Communication can then take over from the Payment module to directly transmit the transfer orders to their beneficiaries. If one of your banks uses the EBICS standard, your files can be encrypted by the Sage XRT Signature application.
To facilitate your usage of Payment, we decided to always use the same working logic, whatever the transaction type.
You will always find the following operating principles:
- Every payment whose type - International, Commercial, Domestic or SEPA Transfers - is not recognized, is identified by the module as a payment request that cannot be fully processed until it is completed.
- Each payment order is associated with a status which represents its place in the remittance process. This status goes from" To Complete", "To Validate" or "To Authorize" to "Validated" or "Authorized" when the payment order is ready to be remitted to the bank.
- Profiles must be set up to associate technical characteristics of the remittance file generation (bank format, protocol, etc.) with each transaction type.
- Constitution Rules must also be created to define, for each transaction type, the way the order remittances will be constituted (multi-currency, multi-date, etc.).
On top of these basic principles, there are some other functions that are common to the various transaction types, such as the selection of the orders to be processed (selection by status, by applicant, by beneficiary, etc.), the type of data to enter, the potential re-use of the order characteristics through the saving of Templates, the import of Payment Orders and Requests, and the generation of Documents.
Eventually, as Payment is integrated into the Sage XRT Treasury application suite, some of the setup must be defined from the Setup, Common Administration and Market Data modules, which are common to every application of the range.
