INTF3053 - Maintain COFI Payments

Purpose This form enables the user to view payments that are currently applied and delete them if required.
Subsystem Callista Open Finance Interface
Normally Run By A Fees Specialist
Anticipated Frequency As required
Structure Blocks Customer
Payments
Payment Application
 

This form displays payment records and the processed payment applications created for those payments.
It allows the deletion of any Payment Application records for a specific payment. Records can be deleted individually or in bulk.
It also displays a Person ID when a sponsor has designated a payment to be applied to a particular student.

Any change made to a payment application (e.g. marked for deletion) is immediately effective for the corresponding invoice and payment, and will not require any finance job to be run. The system marks the invoice for processing, so that when INTJ3021 is next run, it will make any further required adjustments to other payments for that invoice.

This form is accessed directly from the the main menu.

Note: If your institution does not use the COFI Designated Payment Model (DESG_PAYMENT_MODEL_IND is set to N in the I_INT_CONTROL table) then INTF3053 will not be available in your system but INTF0052, which is a simpler, display only' version of this form, is available.

For further information on COFI, see Understanding the Callista Open Finance Interface COFIF1INTR3 or Special Topics COFIF1INTR5.

 

The Customer block contains:

  • Person ID (LOV)
  • Sponsor Code (LOV)
  • Name
  • Include Deleted Records? - check box

The Payments block contains:

  • Receipt Date
  • Receipt Number
  • Currency
  • Person ID
  • Amount
  • Applied Amount
  • Deleted check box
  • Allocate Unapplied button

The Payment Application block contains:

  • Due Date
  • Amount

Spread Table

  • Fee Type
  • Fee Period
  • Fee Category
  • Course
  • Deleted check box
  • Unit Code
  • Period
  • Invoice Number
  • Invoice Line Description

  • Delete Selected button

Rules/Notes:

The Payments block may populate the Person ID if the Customer is a Sponsor.

Payment records are grouped and combined by receipt number, person_id and Deleted Indicator. If a number of records for a single receipt and person exist and are not logically deleted, the total value of those records appears as a single receipt, and all applied payments for those receipts appear in the Payment Application section.

If the 'Include Deleted Records' indicator in the top block is selected, then all logically deleted records are displayed in both the Payment and Payment Application blocks.
Logically deleted records in the Payment block are grouped by receipt number and person_id, regardless of the logical delete date.
When that grouped logically deleted record is selected, all payment applications for those logically deleted payment records appear in the Payment Application block.

The 'Amount' in the Payments block is the total amount for payments for this receipt, the 'Applied Amount' is the total for undeleted payments for this receipt.

For each payment record, a user can click on the Allocate Unapplied button to navigate to a INTF3054 where they can allocate payments to particular invoices for that student.

A blank Fee Type indicates a refund.

 

A lamp will display if a student customer is displayed in the Customer block and they are encumbered or deceased.

Deleting Payment Application Records

  1. Go to INTF3053
  2. Query for student /sponsor for which a payment is to be re-allocated
  3. Select the receipt for which you want to reallocate payments
  4. Select the Delete check box for Payment Application record(s) to be reallocated.
  5. Click on the Allocate Unapplied button, this takes you to INTF3054, with the selected receipt in context or select the Select All check box to select them all.
  6. Click on the Delete Selected button.
  7. The funds from the deleted Payment Application can then be re-allocated. See INTF3054.

Rules/Notes:

  • When a payment application is logically deleted, if the effective date of the payment was before the due date of the invoice it is matched to, then create an invoice todo record to enable INTJ3021 to review the invoice amount (discounts may be affected).
  • Payment Applications cannot be deleted where a loan transaction exists for the fee.
  • Payment Applications cannot be deleted where the record represents a refund.
  • Payment Applications cannot be deleted where the fee period has been finalised.
  • Payment Applications cannot be deleted if the payment has been fully processed.
  • The Person ID value cannot be removed or updated if there are Payment Application records for the payment These payments must be manually removed first.
  • The Person ID value can't be removed or updated when the record has been logically deleted.
  • If the Person ID value is to be changed, a warning message displays advising that the Person ID of all associated payment records will be changed.

Last Modified on 10 November, 2016 4:29 PM

History Information

Release Information Project Changes to Document
18.0.0.2 2146 - VU Payment Matching New Help page.