| Table of Contents | ||||
|---|---|---|---|---|
|
PCR-360 allows for reporting and tracking Payment activity against GLA balances. Once entered 'Payments' cannot be deleted only Voided or Reversed.
...
Reverse Selected
Click thebutton to trigger Payment Reversal. This button allows multiple Payments to be selected.
...
Click thebutton voids all selected Pending payments.
View Receipt
Click thebutton generates a Payment Receipt. All the Invoices that the Payment is applied to will be listed on the 'Payment Receipt' in a comma separated list.
...
Form
...
The 'Manage Payment' form allows the User to create and edit any existing Payments and attach these Payments to 'Payment Batches'.
...
A single Payment can be applied to multiple Invoices. The 'Invoice' tab on the Payment form has a grid of the Invoices that allows the User to manually specify which Invoices are to be paid with a Payment. Thebutton on this grid can be used to select Invoices and will open the 'Existing Invoices' form. An Invoice can only be associated with a Payment once. The 'Existing Invoices' form only displays Billed or Partial Payment Invoices that are not already associated with the Payment and only Invoices from the GLA specified on the Payment.
...
The Primary Contact is the person responsible for a given GLA and is required on GLAs. If the GLA is created without a Primary Contact, then when a Payment is created, the resulting Charge will not have an owner and cannot be billed. Primary Contacts are required for Service Fees. The Primary Contact is also used as the "Bill to" person on Invoices (although the address is actually the Billing address on the GLA). Setting this will route Billing to that Contact as well as aid in quick identification of the primary point of contact. Simply select the Contact that should be Primary and click the
button. The Contact will now be set as 'Primary'.
...
The last step of Payment Reversal is to trigger the 'Update Accounts' event to recalculate the account balances for the GLAs involved.
| Include Page | ||||
|---|---|---|---|---|
|
Payment Events
Payment Events allow hooks for Escalations and Notifications. There are three hooks.
Payment Created: This Event is triggered whenever a Payment is created.
Available Data:
RECID
PAYMENT_BATCH
GLA
PAYMENT_STATUS
PAYMENT_METHOD
DESCRIPTION
PAYMENT_DATE
AMOUNT
IMPORT_FILES_FILENAME
Payment Updated: This Event is triggered whenever a Payment is updated. This includes status updates.
Available Data:
RECID
PAYMENT_BATCH
GLA
PAYMENT_STATUS
PAYMENT_METHOD
DESCRIPTION
PAYMENT_DATE
AMOUNT
IMPORT_FILES_FILENAME
Payment Status Changed: This Event is triggered whenever a Payment status is changed.
Available Data:
RECID
PAYMENT_BATCH
GLA
PAYMENT_STATUS
OLD_PAYMENT_STATUS
PAYMENT_METHOD
DESCRIPTION
PAYMENT_DATE
AMOUNT
IMPORT_FILES_FILENAME
Payment Import
'Payment Imports' provide the capability to Import Payments in bulk. Only Pending payments can be Imported. Payment statuses CANNOT be updated via the Import. Payment Imports CANNOT be deleted or reprocessed.
The following columns can be written with the Payment Import:
Account Number (GLA) - Required
Method of Payment (custom list) - Required
Description - Optional
Payment Date - Required
Amount (decimal) - Required
Batch Number – Optional
Must be a preexisting Payment Batch
Remarks (CLOB) – Optional
Added to Payment Remarks
UDFs
Payment API
Payments cannot currently be accessed via the API. This will be added in a future version.