LIXI Credit Application (CAL 2.4.2) Standard


Version Superseded

Please note that this version (CAL 2.4.2) was superseded on 18th April 2016 by the release CAL 2.5.0 Standard.
The latest version of all LIXI Standards are always available here.


LIXI issued this CAL 2.4.2 release of the LIXI Credit Application Schema on 25th February 2016. This Transaction Schema was derived from the LIXI Master Schema v2.0.0. A short video outlining our new methodology for deriving the Transaction Schema from the LIXI Master Schema can be found here.

This release supersedes all previous versions of CAL 2.x Schema and is a non-breaking update to the most recent LIXI CAL 2.4.1 Package that was released on the 19th October 2015.

Artefacts in this release include:

Overview

This page describes the business requirements and corresponding solutions at the high level that required a change in the LIXI Master Schema v2.0.0 (or associated definitions that are embedded as annotations) and caused a resulting change in the derived CAL Schema between the CAL 2.4.1 and CAL 2.4.2 releases.

Index of Changes

Type of Change: Create New Simple Type with Enumerated List and Add to New Attributes

Capture Details for Liabilities Paid Out using funds from Third Party Institution
Explictly Express Payment Timing (In Advance or In Arrears)

Type of Change: Add New Elements and Attributes

Enable Conversion from LIXI 1.x to LIXI 2.x and back without Loss of Fidelity

Type of Change: Add New Attributes

Uniquely Identify Elements for Cross Reference Purposes
GST & Stamp Duty on Regular Repayments and Structured Payments
Add Various Identifiers of Software, Guidebook and TransactionType
Allow Parenting Payment as an option under Government Benefits
Allow Sequence Number within Broker Business System to be Identified
Base Frequency for Structured Payments
Different Accountants used in Different Periods
Identify LIXI Customised Schema

Type of Change: Add New Enumerations

Uniquely Identify Equipment Finance Transaction Types
Enable Macquarie as a Funder of Loans

Type of Change: Definition Updates Only

Improve Definition of Dealing Number under Power of Attorney
Improve Definition of Enumerations of Valuation Types
Improve Definition of Vendor Tax Invoice Type
Update Missing Definitions for simpleType restrictions of standard xml types
Update Incorrect Definition of "Loan Documents Re-Issued" Enumeration in Application Instructions List


Details of Changes

Capture Details for Liabilities Paid Out using funds from Third Party Institution

Problem / Requirement Statement

Applicants need the ability to express whether or not an existing liability will be paid out (either in full or partially) using funds from a third party institution.

Solution Overview

Add New Simple Type:

  • clearingFromOtherSourceList

Add New Enumerations

  • clearingFromOtherSourceList.No
  • clearingFromOtherSourceList.Partial
  • clearingFromOtherSourceList.Yes

Add Attribute

  • Package.Content.Application.Liability.ClearingFromOtherSource (type="clearingFromOtherSourceList" use="optional")

Return To Index


Explictly Express Payment Timing (In Advance or In Arrears)

Problem / Requirement Statement

In Equipment Finance transactions, payments (either regular or structured) may be made in advance (at the start of the period) or in arrears (at the end of the period). The standard needs to offer the ability to explicitly specify one of these payment timing options.

Solution Overview

Add New Simple Type:

  • paymentTimingList

Add Enumerations:

  • paymentTimingList.In Advance
  • paymentTimingList.In Arrears

Add Attribute:

  • Package.Content.Application.LoanDetails.ProposedRepayment.PaymentTiming (type="paymentTimingList" use="optional")

Return To Index


Enable Conversion from LIXI 1.x to LIXI 2.x and back without Loss of Fidelity

Problem / Requirement Statement

The immediate business requirement is to be able to convert a CAL 1.x message to a CAL 2.x message and return it to a CAL 1.x, completing the round trip. As such the LIXI 2.x schema needs to cater for storing identifier metadata in order to be able to execute such round-trip transformations. Relevant identifiers are those that were associated with elements in the CAL 1.x schema but have been changed to attributes in LIXI 2.x and therefore cannot have a unique ID associated with that attribute. It is important to note that these identifiers carry no meaning other than uniquely identifying the element in the LIXI 2.x schema.

A more generically worded version of this requirement is: To enable an instance of a data model other than a LIXI 2.x message (for example CAL 1.x) and convert it into a message that conforms to this schema. There are often data elements in the external data model that have identifiers. If that instance of an external data model is needed to be converted to a LIXI 2.x message, whilst the data is not needed in the LIXI 2.x message, some data elements may be needed to convert the message back to the format of the external data model without loss of fidelity.

Solution Overview

Add Elements

  • Package.TransformMetadata (minOccurs="0" maxOccurs="1")
  • Package.TransformMetadata.Identifier(minOccurs="0" maxOccurs="unbounded")

Add Attributes

  • Package.TransformMetadata.Identifier.AttributeName (type="stringType" use="optional")
  • Package.TransformMetadata.Identifier.ExternalID (type="stringType" use="optional")
  • Package.TransformMetadata.Identifier.UniqueID (type="stringType" use="optional")
  • Package.TransformMetadata.Identifier.x_Context (type="stringType" use="optional")

Return To Index


Uniquely Identify Elements for Cross Reference Purposes

Problem / Requirement Statement

The schema allows for XML instances to contain repeating elements that have no identifier that can be used to refer to that element uniquely from elsewhere in the message. A unique identifier for each repeating element is required where it does not already exist.

Solution Overview

Add Attributes

  • Package.Content.Application.PersonApplicant.CreditHistory.UniqueID  (type="uniqueIDType" use="optional")
  • Package.Content.Application.PersonApplicant.ResponsibleLending.SignificantChange.UniqueID  (type="uniqueIDType" use="optional")
  • Package.Content.Application.PersonApplicant.ResponsibleLending.Mitigant.UniqueID  (type="uniqueIDType" use="optional")
  • Package.Content.Application.PersonApplicant.Contact.EmailAddress.UniqueID  (type="uniqueIDType" use="optional")
  • Package.Content.Application.CompanyApplicant.CreditHistory.UniqueID  (type="uniqueIDType" use="optional")
  • Package.Content.Application.CompanyApplicant.ResponsibleLending.SignificantChange.UniqueID  (type="uniqueIDType" use="optional")
  • Package.Content.Application.CompanyApplicant.ResponsibleLending.Mitigant.UniqueID  (type="uniqueIDType" use="optional")
  • Package.Content.Application.TrustApplicant.TrustDeedVariation.UniqueID  (type="uniqueIDType" use="optional")
  • Package.Content.Application.RealEstateAsset.Encumbrance.UniqueID  (type="uniqueIDType" use="optional")
  • Package.Content.Application.RealEstateAsset.ConstructionDetails.ConstructionStage.UniqueID  (type="uniqueIDType" use="optional")
  • Package.Content.Application.NonRealEstateAsset.Encumbrance.UniqueID  (type="uniqueIDType" use="optional")
  • Package.Content.Application.LoanDetails.ProposedRepayment.StructuredPayments.Payment.UniqueID  (type="uniqueIDType" use="optional")
  • Package.Content.Application.LoanDetails.LendingPurpose.UniqueID  (type="uniqueIDType" use="optional")
  • Package.Content.Application.LoanDetails.FeaturesSelected.ExtraFeature.UniqueID  (type="uniqueIDType" use="optional")
  • Package.Content.Application.LoanDetails.FeaturesSelected.OffsetAccount.UniqueID  (type="uniqueIDType" use="optional")
  • Package.Content.Application.LoanDetails.FundsDisbursement.UniqueID  (type="uniqueIDType" use="optional")
  • Package.Content.Application.Household.Dependant.UniqueID  (type="uniqueIDType" use="optional")
  • Package.Content.Application.Summary.Fee.UniqueID  (type="uniqueIDType" use="optional")
  • dealingNumberType.UniqueID  (type="uniqueIDType" use="optional")

Return To Index


GST & Stamp Duty on Regular Repayments and Structured Payments

Problem / Requirement Statement

In Equipment Finance Transactions, both Regular Repayments and Structured Payments may have GST and Stamp Duty and the dollar values need to be explicitly defined for each and every repayment. At the moment only the total amount is described.

Solution Overview

Add new attributes to carry additional data:

  • Package.Content.Application.LoanDetails.ProposedRepayment.RegularRepayment.GSTAmount (type="currencyType" use="optional")
  • Package.Content.Application.LoanDetails.ProposedRepayment.RegularRepayment.StampDutyAmount (type="currencyType" use="optional")
  • Package.Content.Application.LoanDetails.ProposedRepayment.StructuredPayments.Payment.GSTAmount (type="currencyType" use="optional")
  • Package.Content.Application.LoanDetails.ProposedRepayment.StructuredPayments.Payment.StampDutyAmount (type="currencyType" use="optional")

Update existing definitions to make it clearer that these are total or gross payment amounts:

  • Package.Content.Application.LoanDetails.ProposedRepayment.RegularRepayment.Amount
  • Package.Content.Application.LoanDetails.ProposedRepayment.StructuredPayments.Payment.Amount

Return To Index


Add Various Identifiers of Software, Guidebook and TransactionType

Problem / Requirement Statement
  • Licensees need to be able to communicate the Name and Version of the software used to publish the LIXI message.
  • Licensees need to be able to communicate the name of the Electronic Guidebook used to create the LIXI message along with the GuidebookVersion.
  • Licensees need to be able to specify the LIXI Transaction Type (CAL, DAS etc) along with the LIXIVersion.
Solution Overview

Add Attributes:

  • Package.Publisher.Software.Name (type="stringType" use="optional")
  • Package.Publisher.Software.Version (type="stringType" use="optional")
  • Package.SchemaVersion.GuidebookName (type="stringType" use="optional")
  • Package.SchemaVersion.LIXITransactionType (type="stringType" use="optional")

Return To Index


Allow Parenting Payment as an option under Government Benefits

Problem / Requirement Statement

When expressing Other Income (Government Benefits), there is no options to explicitly specify a Parenting Payment.

Solution Overview

Create new enumeration:
governmentBenefitsTypeList.Parenting Payment

Return To Index


Allow Sequence Number within Broker Business System to be Identified

Problem / Requirement Statement

There is a scenario where messages are exchanged between the Broker Business System (CRM) and the Point of Sale provider system (E-Lodgement Application). In the case of submissions followed by resubmissions, there is the ability to uniquely identify the sequence for the POS system, but not within the Broker Business System. This ability to uniquely identify the sequence within the Broker Business System is required.

Solution Overview

Add Attribute:

Package.Content.Application.Overview.BrokerApplicationSequenceNumber (type="integerType" use="optional")

Return To Index


Base Frequency for Structured Payments

Problem / Requirement Statement

With structured repayments (frequently used for Equipment Finance Transactions), there exists a Base Frequency that is used for interest calculations and needs to be specified. It is usually the minimum period between all structured payments, but it would be much clearer to allow it to be explicitly specified.

Solution Overview

Add new attribute to carry additional data:

  • Package.Content.Application.LoanDetails.ProposedRepayment.StructuredPayments.BaseFrequency (type="frequencyFullList" use="optional")

Return To Index


Different Accountants used in Different Periods

Problem / Requirement Statement

There are occasions where an applicant's current accountant differs from the accountant used for this years reported income and from that used in other years (notated as 'previous', 'prior' and 'recent' within the schema). In such cases, the applicant needs to describe the accountant for each year independently of the current accountant.

Solution Overview

Add Attributes:

  • Package.Content.Application.PersonApplicant.Employment.SelfEmployed.BusinessIncomeRecent.x_Accountant (type="referenceType" use="optional")
  • Package.Content.Application.PersonApplicant.Employment.SelfEmployed.BusinessIncomePrevious.x_Accountant (type="referenceType" use="optional")
  • Package.Content.Application.PersonApplicant.Employment.SelfEmployed.BusinessIncomePrior.x_Accountant (type="referenceType" use="optional")
  • Package.Content.Application.CompanyApplicant.IncomeRecent.x_Accountant (type="referenceType" use="optional")
  • Package.Content.Application.CompanyApplicant.IncomePrevious.x_Accountant (type="referenceType" use="optional")
  • Package.Content.Application.CompanyApplicant.IncomePrior.x_Accountant (type="referenceType" use="optional")
  • Package.Content.Application.TrustApplicant.IncomeRecent.x_Accountant (type="referenceType" use="optional")
  • Package.Content.Application.TrustApplicant.IncomePrevious.x_Accountant (type="referenceType" use="optional")
  • Package.Content.Application.TrustApplicant.IncomePrior.x_Accountant (type="referenceType" use="optional")

Update Definitions:

  • Package.Content.Application.PersonApplicant.x_Accountant
  • Package.Content.Application.CompanyApplicant.x_Accountant
  • Package.Content.Application.TrustApplicant.x_Accountant

Return To Index


Identify LIXI Customised Schema

Problem / Requirement Statement

Create a way for LIXI Customised Schema Versions to be uniquely identified. This is specific to LIXI Customisation by Restriction Methodology only.

Solution Overview

Add attribute:
Package.SchemaVersion.LIXICustomVersion (type="stringType" use="optional")

Return To Index


Uniquely Identify Equipment Finance Transaction Types

Problem / Requirement Statement

There is no way to explicitly identify the most common forms of equipment finance transactions at the loan level:

  • Chattel Mortgage
  • Commercial Hire Purchase
  • Operating Lease
  • Finance Lease

This explicit identification of the type of transaction for that specific loan under the credit application is required.

Solution Overview

Add Enumerations:

  • loanTypeList.Chattel Mortgage
  • loanTypeList.Commercial Hire Purchase
  • loanTypeList.Operating Lease
  • loanTypeList Finance Lease

Return To Index


Enable Macquarie as a Funder of Loans

Problem / Requirement Statement

Macquarie needs to be available as a funder of loans.

Solution Overview

Add enumeration:
funderList.Macquarie

Return To Index


Improve Definition of Dealing Number under Power of Attorney

Problem / Requirement Statement

Definition of Dealing Number element for a PersonApplicant's PowerOfAttorney is unclear. Update the definition to be more explicit.

Solution Overview

Update Definition:

  • Package.Content.Application.PersonApplicant.PowerOfAttorney.DealingNumber

Return To Index


Improve Definition of Enumerations of Valuation Types

Problem / Requirement Statement

The definitions of the valuation types (enumerations under valuationProgramList) are not provided.

Solution Overview

Update Definitions:

  • valuationProgramList.Full Registered
  • valuationProgramList.Kerb Side
  • valuationProgramList.Desktop
  • valuationProgramList.Progress Inspection
  • valuationProgramList.Costing
  • valuationProgramList.AVM

Return To Index


Improve Definition of Vendor Tax Invoice Type

Problem / Requirement Statement

The definitions of the vendor tax invoice type was not previously provided.

Solution Overview

Update Definitions:

  • vendorTaxInvoiceType.ItemName
  • vendorTaxInvoiceType.TaxInvoiceDate
  • vendorTaxInvoiceType.Asset
  • vendorTaxInvoiceType.Asset.AssetDescription
  • vendorTaxInvoiceType.Asset.UniqueAssetIdentifier
  • vendorTaxInvoiceType.Asset.GSTComponent
  • vendorTaxInvoiceType.Asset.TotalCostOfAsset
  • vendorTaxInvoiceType.Asset.TradeIn
  • vendorTaxInvoiceType.Asset.DepositPaid
  • vendorTaxInvoiceType.Asset.Payout
  • vendorTaxInvoiceType.Asset.Refund
  • vendorTaxInvoiceType.Asset.FinalPosition

Return To Index


Update Missing Definitions for simpleType restrictions of standard xml types

Problem / Requirement Statement

Update Missing Definitions for simpleType restrictions of standard xml types

Solution Overview

Insert Definitions:

  • base64BinaryType
  • currencyType
  • dateTimeType
  • dateType
  • decimalType
  • gYearType
  • percentType
  • stringType

Return To Index


Update Incorrect Definition of "Loan Documents Re-Issued" Enumeration in Application Instructions List

Problem / Requirement Statement

Definition of "Loan Documents Re-Issued" was updated from: "A request to follow up the Loan Document production has been received." to "The Loan Documents have been re-issued."

Solution Overview

Update Definition:
eventNameApplicationInstructionsList.Loan Documents Re-Issued

Return To Index

Statement of Proprietary Information
This standard is confidential to LIXI Limited and may not be disclosed, duplicated, or used, for any purpose, in whole or in part, without the prior consent of LIXI Limited. Both the XML Schema Definition files and associated documentation are licensed under the LIXI End User Licence Agreement (EULA) that can be found here: LIXI-End-User-Licence-Agreement-v4-2015-08 . An introduction to this EULA is available here: Introduction to EULA 2013 10 V.2.pdf .

Updated: 18th April 2016