Payment

Payment Data Model

Payment - Main

The following data model illustrates the payment object.

graphics11

Payment - FT

The following data model illustrates the FT that must be associated with a payment segment.

graphics12

Payment Table Names

*Data Model Name*	*Table Name*	*Generated Keys*	*Referential Integrity Validation Batch Control*	*Key Assignment Batch Control*	*Insertion Batch Control*
Payment	CI_PAY	YesCI_PAY_K	CIPVPAYV	CIPVPAYK Has dependencies	CIPVPAYI
Payment Characteristic	CI_PAY_CHAR	No. The key is PAY_ID, plus a sequence number and a char type	CIPVPYCV		CIPVPYCI
Payment Event	CI_PAY_EVENT	YesCI_PAY_EVENT_K		CIPVPYEK Has dependencies	CIPVPYEI
Payment Tender	CI_PAY_TNDR	YesCI_PAY_TNDR_K	CIPVTNDV	CIPVTNDK Has dependencies	CIPVTNDI
Payment Tender Characteristic	CI_PAY_TNDR_CHAR	No. The key is PAY_TENDER_ID, plus a sequence number and a char type	CIPVTNCV		CIPVTNCI
Payment Segment	CI_PAY_SEG	Yes CI_PAY_SEG_K	CIPVPSGV	CIPVPSGK Has dependencies	CIPVPSGI
FT (financial transaction)	CI_FT	Yes CI_FT_K	CIPVFTFV	CIPVFTXK Has dependencies	CIPVFTFI See Optional FK Note below.
FT Characteristic	CI_FT_CHAR	No. The key is FT id, char type code and a sequence number	CIPVFTCV		CIPVFTCI
FT GL (FT general ledger)	CI_FT_GL	No. The key is FT id and a GL sequence number	CIPVFTGV		CIPVFTGI

Payment Suggestions

The SEQ_NUM field on the payment should be left blank. This is part of the primary key for the Payment Event Distribution Details, which are not part of the conversion process.

We recommend that you use the system to create a single deposit control and link to it a single tender control using the PRODUCTION tables. The tender control should reference a tender source of "conversion". Use the prime key of the tender control as the foreign key on the tenders that you insert into the STAGING tables. This means you will have an invalid foreign key relationship on CI_PAY_TNDR (it will reference a tender control that doesn't exist).

After converting the payments:

Re-access the tender control in production and enter the appropriate amounts (per tender type) to balance the tender control.
Re-access the deposit control in production and enter the appropriate amounts to balance the deposit control.

Please populate the columns on the FT that's associated with the payment segment as follows:

CUR_AMT should be set equal to the payment segment amount
PAY_AMT should be set equal to the payment segment amount
CRE_DTTM should be set equal to the payment segment date / time
FREEZE_SW should be "Y"
FREEZE_DTTM should be set equal to the payment segment date / time
ARS_DT should be set equal to the payment segment date
CORRECTION_SW should be "N"
REDUNDANT_SW should be "N"
NEW_DEBIT_SW should be "N"
NOT_IN_ARS_SW should be set to "N"
SHOW_ON_BILL_SW should be set to "N" on all payments other than payments that have been received since the last bill. For recent payments that you want to show on the next bill, this switch must be "Y"
ACCOUNTING_DT should be set to the current date
SCHED_DISTRIB_DT should be left blank
CURRENCY_CD should be the currency on the installation record
BAL_CTL_GRP_ID should be left blank
XFERRED_OUT_SW should be set to "Y"
PARENT_ID should be set to the payment ID
SIBLING_ID should be set to the payment segment ID
Do NOT create any GL details for the FT. If GL details are converted, ensure they are populated with the EXACT information the system would use to create them. This information is used to create the reversing GL entry when the payment segment is canceled.

Optional FK Note

FTs for adjustments have an optional foreign key BILL_ID to the Bill (CI_BILL) table. If your implementation is planning to convert financial transactions for adjustments, but does not plan to convert bills, the key generation program for Bill must still be run. Refer to The Big Picture of Key Assignment for more information.