Purpose

To report any inconsistencies found between invoices and invoice summaries.

Initially, after each run of the invoice master job, INTJ0021, and then as required

INTR1120 lists information about discrepancies between invoice and invoice summary data for fee type calendar instance records that have not been finalised (for information about finalising fee periods, see Finalise Fees ). It also details expected revenue amounts (invoices) and aggregate expected export revenue amounts (invoice summary).

Run Details

This report can be run in immediate or batch mode.

Refer to Job Control & Scheduling Subsystem for details on scheduling and running batch jobs.

Timing

The report would normally be run after running the summary job, (INTJ0060) that creates summary records for export to the external HEP Finance System.

It would normally be run before end of financial year processing.

Report Parameters

For information about system (or control) parameters, see Parameter Forms .

A comment can be added to appear on the cover page of the report.

Invoice Summary Exception Report Block

Parameters tab

• Comment

Rules/Notes:

INTR1120 lists details of the summarised amounts from I_INVOICE_TRANS_V (Invoice Tax Amount and Invoice Fee Amount columns in the report output) that do not equal the I_INVOICE_SUMMARY fee and/or tax amounts (Summary Tax Amount and Summary Fee Amount columns in the report output).

Records are grouped by fee period (Fee Assessment Calendar), with the most recent period first. Within fee period, they are sorted in ascending order of Batch Date and iis_sequence_number.

Invoice Summary Exception Report Module

This module summarises fee amounts and tax amounts for invoice data in I_INVOICE_TRANS.

Before summarising, invoice data is grouped by iis_sequence_number.

The report then compares this summary data to data held in the Callista interface table, I_INVOICE_SUMMARY, giving details of any inconsistencies found.

The report only compares fee type calendar instance records not finalised. Debit memos that are not older than the number of days specified in I_INT_CONTROL (INVSUM_DEBMEM_CHK_DAYS) are also compared.

Rules/Notes:

It should not be possible to introduce inconsistent data through normal running of the system. If any is found, it suggests either that jobs are not functioning correctly, or that there has been intervention directly at database table level, rather than through supplied Callista forms.

If discrepancies are found, their origin will need to be tracked by information systems/programming staff with responsibility for Callista.