Payment event upload Staging

Populating The Payment Event Upload Staging Records

The following diagram illustrates the processes involved in the uploading of payment event distribution details into the system.

Process X refers to the mechanism used by your organization to populate the payment event upload staging table.

You can write your own java code for Process X .

But now I manually insert data into payment event upload staging table.

Go to Main menu->Financial->Payment Event Upload Staging->Add

Payment Event Upload Staging - Main

This page shows the details of a payment event upload staging record.

Open this page using Menu > Financial > Payment Event Upload Staging > Search.

Description of Page

External Source ID corresponds with an external source ID on one of the your tender sources. This should be the unique ID of the source of the interfaced payments. 

External Transmission ID is the unique identifier of the transmission of payments from the external source. This must be a unique value for each transmission from the source.

Sequence is the identifier of the record within the transmission. The C1-PEPL1 process uses this field to organize the parallel threads.

Accounting Date is the payment date that should be used for accounting purposes.

Distribution Rule is the rule by which the payment detail is to be processed. A default distribution rule is displayed if you have set one.

Rule Value is a value associated with the payment and expected by the distribution rule.

Match Type and Match Value are only used if the distribution of the payment should be restricted in some way (i.e., the standard payment distribution algorithm should not be used). Match Type indicates how the payment should be distributed (e.g., only distribute to a specific service agreement), Match Value indicates the ID of the restriction (e.g., the service agreement ID).

Payor Account ID is the tender account. If not populated the C1-PEPL1 process populates this field by calling the Determine Tender Account algorithm defined on the distribution rule.

Tender Amount is the amount tendered (i.e., the payment amount).

Currency Code is the currency of the tendered amount. This should be the same as currency defined on the tender source.

Tender Type defines the form or remittance (e.g., cash, check, etc.). Note that the Tender Type defaults from the installation record.

Check Number is the check number on the payment.

MICR ID is the value of the magnetic ink character recognition (MICR) line on the payment.

External Reference ID may be used to record external information associated with the payment tender.

Customer ID may be used to record additional customer information.

Name may be used to record additional payment tender information.

Tender Control ID is the tender control associated with the payment. This field is should typically be left for the C1-PEPL1 process to populate.

If the Tender Type is associated with an automatic payment the Auto Pay section displays. The system attempts to default automatic payment information from the account's auto-pay option if the tender type is the same as the tender type on the account's auto-pay source and if the auto pay option is effective on the payment date. If the system is unable to default information, you must specify the source of the funds and the customer's account number / credit card number at the financial institution.

• Auto Pay Source Code is the financial institution / credit card company that receives the automatic payment request.
• External Account ID is the customer's account number at the financial institution.
• Expires On is only needed if the Tender Type indicates that an expiration date is necessary (e.g., for a credit card payment).
• Name is the customer's name in the financial institution's system.

Pay Event Process ID is used to group multiple staging records into a single payment event. If not populated, the C1-PEPL1 process sets this field equal to the Payor Account ID.

Pay Event Staging Status shows the state of the staging record.

Payment Event ID is the system-assigned, unique identifier of the related payment event. The C1-PEPL2 process populates this field when it creates a payment event for the upload staging record.

Observe  the status of Pay Event Staging Status ,its in Incomplete state.

Now we will see the next steps of running batches.

The Lifecycle of a Payment Event Upload Staging Record

The following diagram shows the possible lifecycle of a payment event upload staging record.

• Incomplete. A payment event staging record is initially created in incomplete state. The C1-PEPL1 process sets it to pending once it links it to a tender control and determines its tender account.
• Pending. The C1-PEPL2 process sets a pending record to complete once all processing logic is executed and a payment event is linked to it.
• Complete. When processing of the staging record is complete the record is in the complete state. This is a final state.
• Error. A payment event staging record may be set to Error from Incomplete or Pending states by the C1-PEPL1 and C1-PEPL2 processes respectively.

Now we have read all the help from CCB help ...lets proceed to run the batches ..and see what happens..

Click on save.

Now go back to Payment event upload staging page...see the status of Pay Event Staging Status

Its updated to Pending...

Now lets run the next batch ...

Now go back to Payment event upload staging page...see the status of Pay Event Staging Status

Its updated to Complete... and now payment event id is generated.

Go to Payment event Id ...

Now lets run the next batch ...

The batch process C1-PEPL3 refers to the last of three background processes that load the contents of the payment event upload staging records into the various payment tables.

The responsibility of the C1-PEPL3 process is to update the status of the related deposit and tender controls from open to balanced.

Each distinct tender control for which all associated staging records are in complete status is processed as follows:

• The tender deposit is created.
• The tender control is set to balanced.
• The deposit control is set to balanced.