To use the Hub Testing Integration System (HITS), you'll need the following:
You'll also need a basic knowledge of SIF REST:
You need to know how to work with a use case in HITS and access the HITS API
If you get stuck: drop us a line at
Schools need to be able to lodge Financial Questionnaire (FQ) data to the Australian Government efficiently, with use of automation both in compiling the submissions and in submitting them.
NOTE: this is a preliminary version of the technical use case, which realises only the initial submission of FQ data. A future iteration of this use case will cover the validation of FQ submissions, and the declaration accompanying the finalised FQ submission. The details of batch processing, and the object level at which receipts will be issued, has also not yet been finalised.
A 3rd Party finance application connects to HITS as a proxy for the Australian Government Service Entry Point. The application submits FQ data to the centralised system, consisting of a record per school/authority that it represents, and receives back a receipt number corresponding to each record.
In a future version of the use case:
A full FQ conceptual model diagram will be published with the complete technical use case. In the current version of the use case, there are only two objects involved, the Financial Questionnaire Submission, and the associated School.
A full diagram of interacting SIF objects will be published with the complete technical use case. In the current version of the use case, there are only two objects involved, FQReportingObject, and SchoolInfo.
Here is the XSD schema for SIF 3.4.3.
3rd party application connects to Schools Entry Point endpoint
3rd party application authenticates
3rd party client provides financial submission data in SIF/XML:
In this iteration of the use case, the response for each object is a normal SIF response:
In this iteration of the use case, the HTTP status code will be HTTP 201 "Created", so long as the submitted FQReportingObject is syntactically valid.
In the future complete version of the use case, the response will be a full AGCollectionsStatusObject object, indicating the validation status of the submitted object against the business rules in place for the Financial Questionnaire collection.
The processes around declaring object submission (i.e. having an authorised party asset that the objects submitted are finalised, and are an accurate report of school finances) is currently undertaken out-of-band, and does not involve the SIF API.
The Financial Questionnaire (FQ) is an annual collection of income, expenditure, assets and liabilities from all non-government schools, It is lodged at the end of the calendar year, based on information from the system or school's audited financial statements; for example for 2016 calendar year FQ must be completed before 30 June 2017.
The Financial Questionnaire currently allows school systems to submit using an XML schema specific to the Australian Government business unit. For individual non-systemic schools, the Financial Questionnaire is an intensive manual process, involving filling out spreadsheets. Schools have reported that this is onerous for them, as there is no integration between the spreadsheet and any existing computer systems they have for managing their finances. The process is all the more onerous as schools have had poor and late visibility of the validation rules that the submissions are subject to.
Moving Financial Questionnaire submissions to SIF will enable submissions for non-systemic schools, as well as school systems, will allow significant efficiency gains in schools compiling the required data automatically, in applying validation rules as QA locally before submission, and in more timely and less error-prone submission procedures.
In this iteration of the use case, a new FQReportingObject object is well-formed if it adheres to the SIF schema. The complete version of the use case will further apply the detailed business rules particular to the Financial Questionnaire, including whether particular classes of income or expenditure should be reported by that school based on other information, and rules about the relative values of particular values, and whether an override comment has been provided for the application of particular rules.
N/A. No Service Paths are supported for this use case.
N/A. No Queries By Example are supported for this use case.