Tuition Fees - Duplicate Fee Detection

Share

Duplicate fee detection is a simple tool that identifies possible duplicate tuition fees. The final decision of whether or not the tuition fee is posted is made by you. Note: This function does not replace the necessity for you to review the tuition fees that are about to be posted.

By default, Duplicate fee detection will search for other transactions with a Transaction Type:Tuition Fee for a specific date range, however, you can select more criteria to filter your search with using the Also match on the same criteria.  

The Previewed Transaction Batch page, generated when the Preview Tuition Fee button is selected, identifies detected duplicate tuition fees by highlighting them in yellow and sorting them to the top of the report results. The reason for the fee being determined a duplicate is also shown.  

The Post  check box is selected by default; this will include the fee in the batch. If you determine the fee is a duplicate and you do not want to post it, clear the Post check box and the fee will be omitted from the batch. You can also use the Check All Duplicates and Un-check All Duplicates buttons for convenience.

Duplicate Fee Detection Fields Defined

Use Duplicate Tuition Fee Detection

To use Duplicate fee detection select the Use duplicate tuition fee detection check box.

Check Dates From / Through

Jackrabbit searches for any tuition fee {Transaction Type: Tuition Fee (Debit)} that has already been posted to a family account during that time frame.

Transaction Type

This is preset to Tuition Fee and can't be changed.

Also match on the same

The Also match on the same field is optional and has several drop down choices. Each is described below.

Student and Class

Both the existing (already posted) tuition fee and the tuition fee about to be posted must have the same Student and Class and a Transaction Type: Tuition Fee (Debit). When these match, the fee is highlighted as a duplicate. If either the Student or the Class is missing on the existing tuition fee, the new fee will not be detected as a possible duplicate.

Student and Category1

Both the existing (already posted) tuition fee and the tuition fee about to be posted must have the same Student and Category1 and a Transaction Type: Tuition Fee. When these match, the fee is highlighted as a duplicate. If either the Student or the Category1 is missing on the existing tuition fee, the new fee will not be detected as a possible duplicate.

Student

Both the existing (already posted) tuition fee and the tuition fee about to be posted must have the same Student and a Transaction Type: Tuition Fee. When these match, the fee is highlighted as a duplicate. 

Category1

Both the existing (already posted) tuition fee and the tuition fee about to be posted must have the same Category1 and a Transaction Type: Tuition Fee. When these match, the fee is highlighted as a duplicate. 

Transaction SubType

Both the existing (already posted) tuition fee and the tuition fee about to be posted must have the same Transaction SubType and a Transaction Type: Tuition Fee. When these match, the fee is highlighted as a duplicate.