DC1 Help Centre 12.0

Payment and settlement interface

The purpose of the Payment and Settlement Interface is to create a gateway through which payments and settlements that need to be created in the DC1 Financial system can be loaded.

The interface consists of a number of mutually related files into which the payment and the settlement definitions should be entered before the loading process is started.

Unlike for the old DC1 pre-system, the new interface-based transactions are loaded into the system through an always created open batch environment that not only gives much better preview and correction possibilities, but also creates an integrated transaction entry facility, that is independent of the transaction entry stream (be it a WORKSTN or a database file record).

The Payment and Settlement Interface consists of the following files:

SROKBPP	A/R Payment interface	This is the main payment interface file.
SROKBPS	A/R Settlement interface	This is the main settlement interface file, where the settlement option should be indicated.
SROKBSP	A/R settlement interface file – documents list	This file should contain the list of the documents to be settled, if it is required by the used settlement option. If one of the following settlement options DOC_LIST, DOC_LIST3 or DOC_LISTE is used then this file is mandatory.
SROKBVH	Voucher additional info interface	If any additional information to control the voucher amount is required then this file should be loaded.
SROKBCB	Cash book header interface	If the transferred payment is a Cash book payment, then this file should be loaded with the required bank information.
SROKBSN	Sundry information interface	If the transferred payment belongs to a sundry debtor then this file should hold the address information.
SROKBTX	Text interface	If any text should be attached to the transferred payment then it should be loaded into this file.

The interface file diagrams are presented in the next sections. For more detail information, see About DC1 Financials interface environment.

Interface – diagrams

SROKBPP – A/R payment

SROKBPS – A/R settlement

SROKBSP – A/R settlement; documents list

Interface file relations

Note: Payment, voucher and liquid entry external reference numbers share one common External reference number series.

Note: The External reference number series and External reference number fields of SROKBPS are foreseen to handle settlements of a payment that already exists in the system. Currently, such settlements are not supported and the field values should equally correspond to the payment external reference number series and payment external reference number of the transferred payment (of the main settlement document).

Settlement interface file relations

If a transferred payment should be settled then the main settlement interface file SROKBPS (A/R settlement interface file) must be loaded and indicate the settlement option, according to which the settlement is to be created. If the settlement option *DOC_LIST (or a settlement option having the *DOC_LIST as its base settlement option) is indicated, then the required list of the documents to be settled must be loaded into the dedicated file, SROKBSP; A/R settlement interface file – documents list.

Batch loading

Native files – diagrams

Native files these are the files based on which transactions of the given type are automatically created. At pre-loading the interface data is organised into the native files first, then the validation process is run. If the validation is not passed the interface data remains in the native files. The native file consists of the transaction data along with the validation and status information. The native file structure is a mirror image of the corresponding detail registration panel structure. It enables viewing and validating interface data the same way as at manual registration. Each registration panel has its dedicated native file.