API Connect Individual Product Guide (EAandECA) v.1.33

Equifax Apply &
Equifax Commercial
Apply
API Connect Product Guide v1.33
API Connect Individual Product Guide – Equifax Apply & Equifax Commercial Apply
Revision Number: 1.33
Issue Date: 14/09/2023
Revision control
Revision Date Description

0.1 16/12/2013 Initial Draft
1.0 28/02/2014 Updated to include:
- Differentiation between VedaScore Apply® and Commercial Credit Assess –
Individual
- Permission type controlled using additional request data element instead of
using dedicated services resulting in a reduced number of services
- Optional provision of current negative score (as in VedaScore 1.1 product) in
the VedaScore Apply® response
- Additional data elements in the account structure:
o Transfer date
o Transfer reason
- Schema modification for summary characteristics:
o Renamed data block
o Additional data elements: data block name and variable name
- Updated code and description for Comprehensive data level (instead of Full
Comprehensive) according to new wording in ARCA Data Standard v1.0
- Additional loan payment method value according to ARCA Data Standard
v1.0
- List of Key Contributing Factors included
- List of Summary Characteristics removed and replaced by a separate detailed
document: Genesis Data BlockTM Guide.
- Additional samples
1.1 05/05/2014 Revised during product development:
- Account data level table (section 3.2.2) corrected
- Section regarding name validation (4.7) deleted and validation rules included
in section 0
- Customer Test Environment section updated and end point added
- Request Message Body Content tables corrected and updated:
o Additional validation rules included throughout section 6.2.2
o permission-type-code (Seq No 1.4) mandatory and variable in length
o family-name (Seq No 2.2.1.2, 2.2.2.1.2 and 2.2.3.1.2) and first-name
(Seq No 2.2.1.3, 2.2.2.1.3 and 2.2.3.1.3) mandatory
o Length extended for client-reference (Seq No 1.1), title (Seq No
2.2.1.1, Seq No 2.2.1.1.1, Seq No 2.2.3.1.1), family-name (Seq No
2.2.1.2), first-given-name (Seq No 2.2.1.3) and other-given-name
(Seq No 2.2.1.4), property (Seq No 2.2.4.1.3), street-name (Seq No
2.2.4.1.6) and suburb (Seq No 2.2.4.1.8).
o Length corrected for the address type (Seq No 2.2.4.1.1),
co-borrower (Seq No 2.3.7) and enquiry-client-reference (Seq No
2.3.8)
- Response Message Body Content tables corrected and updated:
2
o Match type (Seq No 2.1.1.2) is optional.
o Length extended for title (Seq No 2.1.1.7.4), family-name (Seq No
2.1.1.7.5), first-given-name (Seq No 2.1.1.7.6) and other-given-name
(Seq No 2.1.1.7.7)
o Length corrected for address type (Seq No 2.1.3.1.6), property (Seq
No 2.1.3.1.8), street-name (Seq No 2.1.3.1.11), suburb (Seq No
2.1.3.1.13), directorship type (Seq No 2.1.7.3.1.4)
o Additional credit enquiry type
o Additional elements in the default structure: original
reason-to-report and latest reason-to-report and their associated
code (Seq No 2.1.5.3.1.25.1.6.3 and 2.1.5.3.1.25.1.7.3)
- Consumer account type AO –All other account types not valid in the request
- New Default reason to report code table (Section 8.7)
- Additional default status value (Section 8.8)
- Key Contributing Factors updated and enriched (Section 8.11)
- New tables for Special Score Values (Section 0)
- Section 3.2.2 revised as account data Level 1 is not applicable to consumer
accounts anymore
- Section 3.7 updated to include more information about handling future use
fields
- Sections 4.9.3 and 5.2 updated to include more details about dynamic data
testing
- Additional note in relation to optional fields in section 6.2.1
- Request structure (section 6.2.2):
o Updated validation rule on address element to enforce a choice
between formatted address or unformatted address.
o Added new element in request is-credit-review (Seq No 2.3.4)
- Response structure (section 6.2.3):
o Corrected error cardinality and updated error/fault-code,
fault-string, fault-actor and detail as optional in the response
o Updated description for account/open-date, closed-date,
original-maximum-amount-credit, latest-maximum-amount-credit
and date-last-changed
o Added new elements in the account structure:
▪ account/account-reopen-date (2.1.5.3.1.15)
▪ account/defaults/default/is-accelerated-debt (Seq No
2.1.5.3.1.26.1.6) for future use only
o List of valid values for court action type (2.1.7.1.1.4) modified
o Updated business-name/business-name-id (2.1.7.4.1.10.5) as future
use only
o Updated sole-trader/ABN as optional in the response
o Updated length of characteristic/@key-characteristic
o Updated file-ban-report/reported-date attribute optional in the
response
- Appendix B updated to include an initial list of error codes and descriptions
- Corrected cardinality for request elements (section 6.2.2):
o Corrected product-data-level (Seq No 1.5) to mandatory in the
request.
3
o Corrected enquiry-amount (Seq No 2.2.3) to mandatory in the
request.
- Corrected format for date elements (section 6.2.3):
o Updated length of datetime-requested (1.2) and datetime-generated
(1.3) from 19 to 30 and format to
CCYY-MM-DDThh:mm:ss.sss(+|-)hh:mm.
o Updated length of @last-extract-time (2.1.7.2.1.5, 2.1.7.3.1.6,
2.1.7.4.1.5) and @last-update-time (2.1.7.2.1.7, 2.1.7.3.1.8,
2.1.7.4.1.7) from 15 to 20 and format to hh:mm:ss.sss(+|-)hh:mm.
- Updated descriptions for special scores -903 and -902 in section 8.21.1.
- Updated section ‘7.2 Appendix B: Product error codes and descriptions’ and
replaced with error code categorisations, cause and action table.
- Added section ‘7.2.1 Error samples’ table.
- Updated section 8.11.1 and 8.11.2 with two new special scores each
(KCF-029, KCF-031 and KCF-129, KCF-131 respectively)
- Changes to the data returned for possible match identity
o Updated format and validation rule to return @first-reported-date
for a possible match identity (section 6.2.3.2) – permissible. This is
applicable to Seq No 2.1.1.7.1, 2.1.3.1.1, 2.1.4.1.1.
o Updated format and validation rule to not return certain fields for a
possible match identity (section 6.2.3.2) – not permissible. This is
applicable to Seq No 2.1.1.11, 2.1.1.11.1, 2.1.1.12, 2.1.1.12.1.
- Updated section 1.7 to include XML report style sheet and guides for the
transition from VedaScore 1.0/1.1 to VedaScore Apply® and Commercial
Credit Assess – Individual
- Added section 3.111 – XML report style sheet as a new feature available for
customers
- Updated section 5.2 Endpoint URLs with the production endpoint
- Removed section and endpoint in relation to static data testing (stub). The
dynamic data test service is now fully functional, so the temporary static
data testing service is no longer required.
- Added Key Contributing Factors for VedaScore Apply® (KCF-040 in section
8.11.1)
- Removed KCF-111 and modified the name and description of KCF-106 (Lack
of Adverse Information) for Commercial Credit Assess – Individual
1.7 23/01/2015 Updated the examples in section 9 to align with new schema v2.0.4 changes.
1.7.1 27/01/2015 Updated the field attributes of certain elements in the product response:
- 2.3.1.2.2 ‘name’ to 50 (previously 20)
- 2.3.1.4.1.2 ‘name’ to 60 (previously 40)
- 3.1 ‘message’ to 300 (previously 150)
- Reference to the VedaConnect Previous Enquiry API documentation.
- Notes in relation to the Access Seeker product.
- Format and validation rules for 2.2.8 employer to clarify that only one
employer record can be submitted in the request.
4
1.8.1 23/02/2015 Updated the field attributes of certain elements in the product response:
- 1.2 ‘datetime-requested’ to 29 (previously 30)
- 1.3 ‘datetime-generated’ to 29 (previously 30)
- 2.1.5.2.1.7 ‘account-type’ to 35 (previously 30)
- 2.1.5.3.1.10.1 ‘@code’ to V (previously F)
- 2.1.5.2.1.7.1 ‘@code’ to V (previously F)
- 2.3.1.4.1.1 ‘@id’ to 10 (previously 6)
- 2.1.5.3.1.15 ‘loan-payment-method’ to 60
(previously 50)
- 2.1.7.3.1.13.5 ‘status’ to 60 (previously 20)
- 2.1.7.5.1.5 ‘type’ to 60 (previously 40)
- 2.1.7.5.1.11 ‘relationship’ to 30 (previously 25)
- 2.3.1.3 ‘risk-odds‘ to 18 (previously 10)
Updated the description of ‘is-unlimited-credit’ field as a
result of ACRDS update.
1.9 05/03/2015 Updated the descriptions of last-extract-date/time, last-update-date/time response fields to

clearly state that the data was sourced from ASIC systems.
- 2.1.7.2.1.4 @last-extract-date
- 2.1.7.2.1.5 @last-extract-time
- 2.1.7.2.1.6 @last-update-date
- 2.1.7.2.1.7 @last-update-time
1.10 16/04/2015 Corrected 1.1 enquiry-id under section 6.2.3.1.1 Product-header from Attribute to Element in
the response.
1.11 30/06/2015 Updated 2.2.1.3 first-given-name field validation from min of 2 char to min of 1 char.
Added a second Customer Test Environment end point to ‘5.2 Endpoint URLs’ and included
‘7.3 Appendix C’ to explain how customers can test hybrid & asynchronous ticket responses.
1.12.1 19/10/2015 Updated the descriptions for classification at the following positions in the product response.
- 2.1.5.2.1.13.2 classification
Added section 8.26 for Industry Classification Codes and description
1.13 30/11/2015 Commercial Credit Assess – Individual Commercial only variant is now available for
customers. This document has been updated with details of the new variant.
1.14 24/02/2016 ● Updated format & validation rules in section 6.2.2.1 (Seq No 1.1), section
6.2.2.2 (Seq No 2.2.8.2), section 6.2.2.3 (Seq Nos 2.3.8 & 2.3.9)
● XML elements account-type-code (section 6.2.2.3 (Seq No 2.3.2)),
enquiry-amount (section 6.2.2.3 (Seq No 2.3.2)) and relationship-code
(section 6.2.2.3 (Seq No 2.3.7)) have been made optional.
5
1.15 01/05/2016 ● Added notes and comments around VedaScore Apply® (Telco) and VedaScore
Apply® (Utility) products.
● Updated section 3.3 to include additional scores for Telcos and Utility
products
● Added section 8.11.2 for KCFs for Telcos and Utilities
● Added section 8.21 for court types
● Added section 8.22.2 for special scores for Telcos & Utilities
1.15.1 01/06/2016 ● Added notes and comments for VedaScore Apply® (Alternative Lending)
product.
● Updated section 3.3 to include additional scores for Alternative lending
product.
● Combined section 8.11.2 with 8.11.1 and section 8.22.2 with 8.22.1
1.16 01/12/2016 ● Clarified the scenarios when possible matches are returned in section
6.2.3.5.
● Removed Files notes section (previously 6.2.3.2.5.1) as it is no longer
returned in the VedaScore Apply® response.
● Added section 3.8 for custom data blocks
● Updated section 3.2.2 to extend the possible fields for account data level 1.
● Updated XML sample list in section 9 with segment specific request and
response sample descriptions.
1.17 11/03/2017 Product names and channels names updated as part of Equifax rebranding
● ‘VedaScore Apply’ renamed to ‘Equifax Apply’
● ‘Commercial Credit Assess – Individual’ renamed to ‘Equifax Commercial
Apply’
● ‘VedaCheck’ renamed to ‘IQ Connect’
● ‘VedaConnect’ renamed to ‘API Connect’
1.18 7/12/2017 Amended:
● Hybrid, Synchronous and Asynchronous diagrams to show as API Connect
● A number of references to “Veda” which is now known in Australia as
“Equifax”.
● Additional text under street type
● Updated the format and validation rules for Seq. No 2.2.8.2 & 2.2.8.6
● Additional explanation on the Enquiry-Client-Reference in the request
(2.3.9).
● Updated the End Points URL - 5.2 & Added the IP Address
1.19 11/05/2018 ⮚ Individual Trading History Option added to the product:
● Section 2.5 – Individual Trading History Information product variation
description
● Section 3.9 – Key product features for Individual Trading History information,
and how to request
● Section 9.1 – Sample ITH variant request
● Section 9.2 – Sample ITH variant response
⮚ Appendix A –Appendix A –Tips for Matching to Individual Bureau Files
1.19.1 27/10/2018 ⮚ New Telco Negative Scorecards – EA_2.1_X_NR_TC, EA_2.1_XY_NR_TC - these
are recommended for Telcos.
⮚ Correction of 2.1.5.3.1.9.5 Transfer Reason was incorrectly previously marked for
“Future Use” but this field is being supplied. Document now includes
transfer-reason and @code
6
⮚ Section 8.28 – Transfer Reason Code Table added
⮚ Section 4.9 – Updates made on testing environment
⮚ Minor changes in wordings
1.20 10/12/2018 ⮚ Equifax Apply Partial product for Telcos added. Document reflects the necessary
changes.
⮚ Section 6.2.3.2.7.3 - Directorships had Individual Trading History fields incorrectly
greyed out, but the fields are being supplied. Document now includes these
fields.
⮚ Section 6.2.3.2.7.4 - Business-names had Individual Trading History fields
incorrectly greyed out, but the fields are being supplied. Document now includes
these fields.
⮚ Section 6.2.3.2.7.4 - Business-names had Proprietorships field incorrectly
labelled as Proprietors. Document now stands corrected.
⮚ Section 6.2.3.2.7.4 - Business-names had incorrectly not mentioned fields
current-directors and previous-directors, although these fields were being
provided. Document now stands corrected.
⮚ Section 8.2 - Consumer Account Type updated to explain Account Type ‘CC’ in
detail.
⮚ Section 8.18 - Relationship table updated to reflect relationship code 1 correctly.
⮚ Section 8.18.1 - Account Relationship mapping table added
1.21 15/04/2019 ⮚ Equifax Commercial Apply Telco New Score Card (recommended)
ECA_2.1_YX_NR_TC
⮚ Section 6.2.3.2.5.2 Accounts, 2.1.5.3.1.21.2 date-last-changed corrected to be an
attribute as defined in the schema
⮚ Section 8.19 Repayment History Status, definitions for statuses ‘O’ (other) and ‘P’
(pending) corrected
⮚ Section 6.2.2.2 Bureau-reference and Individual, 2.2.8.2 Name of Employer
validation rule updated
⮚ Section 8.8 Default Status, table updated, ‘S’ (settled) no longer a valid default
status
1.22 13/02/2020 ⮚ Section 8.8 Paid default definition updated
⮚ Section 8.8 Current no longer a valid default status
⮚ Section 8.8 Disputed Defaults no longer available on Equifax Consumer Bureau
⮚ Section 8.27 Industry Classification ‘Serv’ added
⮚ Added Appendix B – tips for entering Driver Licence Number
⮚ Section 2.1.5.3.1.13 account-open-date definition updated
⮚ 6.2.3.2.7.1 Court-actions note added on privacy credit reporting code 2014, that came
into effect from 14th February 2020
1.23 15/09/2020 ⮚ Section 8.27 Industry Classification ‘BNPL’ added for Buy Now Pay Later
Additionally added some other possible but less common Industry codes: for
completeness
FGOV – Federal Government, SGOV – State Government, LGOV – Local Government,
INDU – Industries, MISC – Miscellaneous, and OTHA - Other
1.24 14/12/2020 ⮚ Inclusion of new Comprehensive Score for Consumer lending: Equifax One Score (see 3.3
Scores, ONE_1.0_XY_CR & ONE_1.0_X_CR)
⮚ Addition of Section 8.11.5 New KCFs for Equifax One Score
⮚ The product name will appear as “Equifax Apply One Score” where one of the new
Equifax One Score scorecards has been requested.
⮚ Changes to the Alternative Lending Data Block to incorporate new Buy Now Pay Later
characteristics (see 3.8 Alternative Lending Data Block and Customer Data Block)
⮚ Section 8.11.4 – Table of KCFs for Telco, Utility and Alternative Lending Models
7
⮚ Authorised Agent enquiries have been updated to be for Commercial only (2.1.5.2,
2.1.5.2.1.4, 2.1.5.2.1.7 & 2.1.6.2 and table 8.5)
⮚ Some minor wording changes to reflect that EA and ECA are no longer “new” products
⮚ Minor revision of scorecard ordering in section 3.3 Scores.
⮚ Move of Appendix C Hybrid & Asynchronous Ticket Response Testing to end of document
⮚ Additional note on removing leading zero for 10 digit Victorian Driver’s Licences in
Appendix A.
⮚ Change in timeout to 45 seconds in section 4.4 to reflect current situation
1.25 15/02/2021 ⮚ Comparison sites – addition of One Score (B2C) scorecard id –Equifax One Score with
consumer facing Key Contributing Factors
⮚ New Buy Now Pay Later (BNPL) Consumer Account Types. BNPL Facility (BF) and BNPL
Transaction (BT)
⮚ How to access the new optional units of time for Term of Loan – ACRDS v2.1 allows Term
of Loan to be reported for an account in days, weeks, or years in addition to months.
Refer to section 3.11 Comprehensive Credit Reporting Term of Loan Unit Type
1.27 24/09/2021 Minor wording changes to the below One Score Key Contributing Factor (KCF) names and
descriptions. Note that the KCF codes have not changed.
⮚ KCF for Equifax One Score KCF-301, KCF-302, KCF-304, KCF-324, KCF-337 & KCF-338
⮚ KCF for Equifax One Score B2C for Comparison Sites KCF-301, KCF-302, KCF-324, KCF-326,
KCF-327, KCF-337 & KCF-338
1.28 14/02/2022 Updated for changes to the Australian Credit Reporting Data Standard (ACRDS) V3.0
DRAFT including:
⮚ Financial Hardship Information (FHI) will now be returned alongside repayment history
information. Refer to the Accounts section for details.
⮚ A new FHI data block with summary characteristics. Refer also to the Genesis Data Block
GuideTM v1.21 DRAFT. Refer to the Summary Data section for details.
⮚ Addition of a separate field for default new arrangement information. Refer to the
Defaults section within Accounts for details.
Removal of the CTEAU test environment endpoints. These are no longer in use and all testing
can be conducted via the CTA endpoint here.
1.28 01/04/2022 v1.28 is now final

THIS VERSION IS RELEASED AHEAD OF THE FINANCIAL HARDSHIP INFORMATION CHANGES
DOCUMENTED WITHIN IT TO ALLOW PLANNING FOR THOSE CHANGES. THE CHANGES WILL
BE AVAILABLE IN THE TEST ENVIRONMENT (CTA) ETA 1 MAY 2022 AND IN PRODUCTION
FROM 1 JULY 2022. ALL CHANGES ARE HIGHLIGHTED YELLOW. DATA IS EXPECTED TO BE
RETURNED IN THE AMENDED FIELDS FROM LATE JULY AS SUPPLIED BY CREDIT PROVIDERS.
- There are no changes to this version from the previous draft version.
1.29 28/04/2022 Update - Equifax Apply ACRDS v3.0 changes production release date moved by one day to
Saturday 2nd July (weekend release).
1.30 23/05/2022 Updated for the release of the new One Score for Telco scorecards which are leveraged via
Equifax Apply (Telco).
➢ Section 2 - updated the scorecard id’s and recommended scorecards.
➢ Section 3.3 - Inclusion of new partial and negative Telco score for Telecommunication
providers: Equifax Apply (Telco) - One Score for Telco (see 3.3 Scores).
➢ Added - Section 8.12.7 KCF for One Score for Telco.
8
1.31 1/09/2022 Updated for the release of the new Equifax Commercial Apply (Telco) - scorecards
➢ Section 2 - updated the scorecard ids and recommended scorecards.
➢ Section 3.3 - Inclusion of new commercial partial and negative Telco score for
Telecommunication providers.
1.32 17/04/2023 Updated for the release of Consumer Credit Liability Information (CCLI) changes:
➢ Section: 2.1.5.3.1.20 Original Maximum Amount of Credit Available field will no longer
be returned in the API response and PDF report. However, Latest Maximum Amount
Credit will not change
1.33 14/09/2023 Update of Special Score Value table:
➢ Section: 8.24.1 Special Score Values - Equifax Apply, Equifax One Score and Equifax
Commercial Apply
9
COPYRIGHT NOTICE
Copyright © 2023 Equifax Pty Ltd., a wholly owned subsidiary of Equifax Inc. All rights reserved. Equifax and
EFX are registered trademarks of Equifax Inc.
CONFIDENTIALITY WARNING
This document is confidential, and its contents must not be disclosed or disseminated to any unauthorised party,
used or reproduced in any way without the prior written permission of Equifax Australia Information Services and
Solutions Ltd.
10
Table of Contents
Introduction 13
Individual consumer credit versus individual commercial credit 14
About individual enquiry products 15
Audience 15
Scope 16
Pre-requisites 16
Terminology 16
References 16
Product Variations 18
Product version 20
Permission type 20
Data level 21
Scorecard ID 22
Individual Trading History Information 23
Key Product Features 24

Full Identity Reporting 24
Accounts and defaults 25
Account structure 25
Account data level 25
Scores 26
Key Contributing Factors 29
Additional scores 29
Genesis Data BlockTM 30
Financial Hardship Information Data Block 30
Alternative Lending Block & Custom Data Blocks 31
3.8 Individual Trading History Information 31
Future use fields 31
Comprehensive Credit Reporting Term of Loan Unit Type 31
XML report style sheet 32
PDF retrieval over API Connect 32
Key Technical Features 32

System Integration 32
API Connect SOAP Overview 32
Hybrid, Synchronous/Asynchronous Transmission Model 32
Asynchronous Transmission Model 33
Recommended Guidelines for Asynchronous Processing 34
Using Hybrid or Asynchronous Integration 36
Typical Synchronous/Hybrid Use-cases 36
Typical Asynchronous Use-cases 36
11
Possible response types 36
Enquiry ID 36
Timeouts 37
Supported SOAP Bindings 37
Reserved XML characters 37
Request Validation 38
Overview 38
Validating addresses 38
Formatted addresses 38
Unformatted addresses 39
Validating dates 39
Error-handling 39
Testing Environment for Customers 39
Web Services 41
Operations 41
Endpoint URLs 41
Request & Response Message Specifications 42

Conventions 42
Data Types, Constraints and Attributes 42
Schema representations explained 42
Message Body Content table explained 42
Submit Enquiry 43
Business Overview 43
Request Overview 43
Enquiry-header 44
Bureau-reference and Individual 47
Enquiry 54
Response Overview 57
Ticket Response 57
Product-header 59
General-messages 61
Errors 62
Report Response 63
Primary-match 66
Other-identities 69
Addresses 71
Employment 73
Consumer-credit-file 74
Credit-enquiries 75
Accounts 78
Messages 89
12
Commercial-credit-file 89
File-notes 90
Public-record or consumer-credit-information 91
Court-actions 93
Disqualified-directorships 95
Directorships 96
Business-names 99
Personal-insolvencies 103
Sole-trader 105
Summary-data 106
Score-data 108
Possible-matches 110
File-ban-report 110
Retrieve Enquiry by ID 111
Business Overview 111
Request Overview 111
Request-by-enquiry-id 112
Response Overview 112
Other Response Considerations 113

Responses to matching of identification data from the request 113
Product error codes and descriptions 114
Error samples 114
Code Tables 115

Address Type 115
Consumer Account Type 115
Commercial Account Type 115
Court action status 116
Credit enquiry type 116
Data Level 116
Default Reason to Report (commercial defaults only) 116
Default Status 117
Default New Arrangement 117
Employment Type 117
Gender 117
Key Contributing Factors (KCF) 118
KCF for Equifax Apply scores 118
KCF for Equifax Commercial Apply scores 119
KCF for VedaScore 1.1 scores 120
KCF for Telco, Utility and Alternative Lending Scores 121
KCF for Equifax One Score 122
KCF for Equifax One Score – B2C – for Comparison Sites 124
13
Loan Payment Method 126
Organisation Status 127
Organisation Type 127
Permission type 127
Personal Insolvency Status 127
Personal Insolvency Type 127
Relationship 128
8.18.1 Account Relationship Mapping 128
Repayment History Status 128
Financial Hardship Information 129
Score Impactors 129
Equifax Apply and Equifax Commercial Apply Score Impactors 129
Court Type 129
Special Score Values 129
Equifax Apply, Equifax One Score and Equifax Commercial Apply 129
VedaScore 1.1 129
Secured Credit 130
State 130
Street Type 130
Term type 131
Industry Classification 131
Transfer Reason 132
Term of Loan Unit Type 132
Examples 133
Request 133
Response 134
Appendix A –Tips for Matching to Individual Bureau Files 137
Appendix B –Tips for entering Driver Licence Number 139
Appendix C –Hybrid & Asynchronous Ticket Response Testing 141
14
1 Introduction
1.1 Individual consumer credit versus individual commercial credit

Australian law distinguishes between Consumer and Commercial credit in relation to an Individual.
The term Consumer Credit refers to any loan intended wholly or primarily for personal, family or household
purposes (as well as to acquire, refinance, renovate or improve residential investment properties). Consumer
credit is governed by Part IIIA of the Privacy Act 1988 (the Act) and credit information is defined in Section 6N of
the Act.
The term Commercial Credit is defined as credit (other than consumer credit) that is applied for by or provided to
an individual. Personal information relating to commercial credit is governed by the Australian Privacy Principles
of the Act.
As a direct consequence of this legal separation Equifax holds its individual credit information in two databases
(consumer and commercial). The footprints of consumer credit enquiries (a record of the information supplied in
service request) are recorded on the consumer database, while the footprints of commercial credit enquiries are
recorded on the commercial database.
Regardless of which type of credit is being provided or assessed, Credit Providers and Access Seekers can choose
to retrieve combined* credit information for the applicant and in this case the Equifax enquiry response includes
information from both the consumer and the commercial databases. The response also includes information from
the Equifax public record database.
Such enquiries are referred to as “Consumer + Commercial” or “Commercial + Consumer” enquiries depending on
the credit purpose as defined above. The underlying information is the same for both enquiries – they differ with
respect to the footprint they leave on the record, the treatment of publicly available information and the product
they utilise (with its related functionality and features).
This Guide covers the following products:
● Equifax Apply (previously known as VedaScore Apply®) suite1 – which is intended for consumer credit
application assessment and includes the Consumer and Consumer + Commercial service.
● Equifax Commercial Apply (previously known as Commercial Credit Assess – Individual) suite2 – which is
intended for commercial credit application assessment and includes the Commercial only and Commercial
+ Consumer service.
*appropriate consents and permissions must be obtained from the applicant by the Credit Provider
1
All references to Equifax Apply include Equifax Apply® (Telco), Equifax Apply® (Utility) and Equifax Apply®
(Alternative Lending), unless specified otherwise.
2
All references to Equifax Commercial Apply include Equifax Commercial Apply (Telco) and Equifax Commercial
Apply (Utility), unless specified otherwise.
15
1.2 About individual enquiry products
Equifax Apply and Equifax Commercial Apply represent the latest generation in the Equifax credit origination
product suite leveraging comprehensive data. Equifax Apply is dedicated to individual consumer credit origination
whereas Equifax Commercial Apply focuses on individual commercial credit origination.
Equifax Apply and Equifax Commercial Apply both offer the option of including comprehensive credit data and
use the latest version of Equifax bureau scorecards designed to allow subscribers to obtain bureau-based risk
profiles (scores) on new credit applicants and to help subscribers make more informed credit assessment
decisions. Equifax Apply and Equifax Commercial Apply provide the solid base for Equifax Individual enquiries
with a flexible scoring solution to all Equifax customers.
Equifax Apply and Equifax Commercial Apply scorecards measure an applicant’s potential credit risk based on
Equifax data at the point of application and is a risk ranking tool to help credit providers assess an applicant’s
willingness to make payments.
Equifax Apply and Equifax Commercial Apply also offer customers currently using the older versions of Equifax
scored origination products the opportunity to upgrade to the next generation of products.
Equifax Apply (Telco), Equifax Apply (Utility) and Equifax Apply (Alternative Lending) are the credit origination
products built specifically for Telecommunication (Telco), Utility and Alternative Lending segments respectively.
These products offer additional features and capability to Telecommunications, Utility and Alternative Lending
companies over the standard Equifax Apply® product and use a new, improved scorecard specific to the segment.
Please note that Equifax Commercial Apply (Telco) and Equifax Commercial Apply (Utility) are also available.
Equifax Apply (Telco) product includes Negative and Partial data, Equifax Apply (Utility) and Equifax Apply
(Alternative Lending) products currently include only Negative data. Partial (for Utility) and Comprehensive (for
Alternative Lenders) versions of these products may be available in a future release (to be determined).
Equifax Apply and Equifax Commercial Apply are not backward compatible with previous versions of
VedaScore products. VedaScore 1.1 and VedaScore 1.0 products cannot be accessed using Equifax
Apply web services and vice versa.
1.3 Audience
The audience for this document is primarily:
● Those wishing to develop software to interface with API Connect Web Services for Equifax Apply and
Equifax Commercial Apply products
● Those wishing to understand the business rules related to Equifax Apply and Equifax Commercial Apply
products
This guide is suitable for Credit Providers and Agents of Credit Providers, as well as Agents of an Individual/Access
Seekers. As Access Seekers are acting on behalf of an Individual and are entitled to see all comprehensive data
held and there are some differences in the product. Access Seekers should specifically review the Notes for Access
Seekers (an example is shown below).
Note for Access Seekers
16
Description of note.
Telecommunication and Utility segment customers should specifically review the Notes for Telcos and Utilities (an
example is shown below).
Note for Telcos and Utilities

Alternative Lending customers should specifically review the Notes for Alternative Lending Customers (an example
is shown below).
Note for Alternative Lending Customers

1.4 Scope
The scope of the document is primarily:
● Defining and describing the interfaces to Equifax’s web service methods to Equifax Apply services, which
are used to serve Equifax Apply and Equifax Commercial Apply products
● Defining the business rules related to the Equifax Apply services
1.5 Pre-requisites
There are three prerequisites before a client can use API Connect web services operations.
● Prerequisite 1 – Get Equifax Digital Certificates.
Why - You need Equifax Digital Certificates to establish a secure connection to API Connect over an HTTPS
channel. Please refer API Connect Getting Started Guide on how to establish a secure connection to API
Connect over HTTPS channel
● Prerequisite 2 –Get Username and Password.
Why - Once a secure channel is established, all SOAP messages sent over it need to be authenticated. This
authentication information is sent using SOAP headers.
● Prerequisite 3 –Get WSDL.
Why – The WSDL (Web Services Description Language) describes the location of the service and the
operations the service exposes. It is recommended to use the latest version of the WSDL to create your
client programs.
If you do not meet the above three prerequisites, please contact your Equifax account manager or Equifax
Technical Support.
1.6 Terminology
API Connect is the new brand name used for products offered over secure HTTPS channel using SOAP or VedaXML
protocol.
If you are not familiar with the API Connect products, VedaXML or SOAP interfaces, please refer to the API
Connect Getting Started Guide.
17
1.7 References
This product guide belongs to a package which also includes:
1. API Connect Channel Documentation - Equifax recommends prior reading of the following documents,
also published by Equifax to get a better understanding of the concepts and systems described in this
product guide
o API Connect Connectivity Guide
o API Connect Getting Started Guide
2. Equifax Apply – Individual Product Information Guide
3. Genesis Data BlockTM Guide: Equifax Apply and Equifax Commercial Apply product include a set of
hundreds of summary characteristics referred to as the Genesis Data BlockTM.
4. Genesis Data BlockTM Guide for Telcos and Utilities: Equifax Apply (Telco) and Equifax Apply (Utility)
products includes details on the additional 30+characteristics available as part of the Telco Data Block and
Utility Data Block delivered as part of these new services, as well as the extensive. Genesis Data Block.
5. vedascore-apply-v2.0 interface documents (which is shared between Equifax Apply and Equifax
Commercial Apply) and samples
o WSDL
o XSD
o XML sample requests and responses as defined in 9 - Examples.
o XML report style sheet
6. Test documentation - Equifax Apply and Equifax Commercial Apply – Customer Test Guide
7. Release notes
8. For customers transitioning from VedaScore 1.0 or 1.1 over API Connect, also refer to the following
documents:
o Equifax Apply and Equifax Commercial Apply Schema Migration Guide
o VedaScore 1.0 to Equifax Apply Schema Transition (spreadsheet)
o VedaScore 1.1 to Equifax Apply Schema Transition (spreadsheet)
9. For customers planning to use the previous enquiries API to retrieve PDF reports over API Connect, refer
to:
o API Connect Previous Enquiry – Application Programming Interface
This Product Guide is based on version 1.0 of the Australian Credit Reporting Data Standard (ACRDS) issued by
ARCA in January 2014. A copy of this data standard can be obtained from:
http://www.arca.asn.au/focus/australian-credit-reporting-data-standard.html

Interface documents such as WSDL, XSL, transitional documents & guides, and API Connect Channel
Documentation remains the same as that of standard Equifax Apply product.
Note for Alternative Lending customers

Interface documents such as WSDL, XSL, transitional documents & guides, and API Connect Channel
Documentation remains the same as that of standard Equifax Apply product.
18
2 Product Variations
The product response is conditioned by:
● A product version
● A permission type
● A data level
● One or more scorecard IDs
● The type of Equifax customer submitting the enquiry
The following tables detail the scorecards that are available to API users. A maximum of 3 scorecard ids can be
requested in a product. It is recommended that the choice of scorecard be discussed with Equifax, please
reach out to your Equifax account manager for assistance.
Product name Equifax Apply Controlled via

Product version 2.0 End point
Permission type Consumer Consumer + Commercial Request data
Data Level Negative* Comprehensive** Negative* Comprehensive** Request data
Scorecard IDs VSA_2.0_X_NR ONE_1.0_X_CR~ VSA_2.0_XY_NR ONE_1.0_XY_CR~ Request data
VS_1.1_X_NR VSA_2.0_X_CR VS_1.1_XY_NR VSA_2.0_XY_CR

VSA_2.0_X_NR VSA_2.0_XY_NR
VS_1.1_X_NR VS_1.1_XY_NR
ONE_1.0_XY_CR_B2C#
Product name Equifax Commercial Apply Controlled via

Permission type Commercial + Consumer Commercial Request data
Data Level Negative* Comprehensive** Negative* Request data
Scorecard IDs CCAI_2.0_YX_NR CCAI_2.0_YX_CR CCAI_2.0_Y_NR Request data
VS_1.1_YX_NR CCAI_2.0_YX_NR VS_1.1_Y_NR

VS_1.1_YX_NR
19
Product Equifax Apply (Telco)
name
Product version 2.0

Permission Consumer Consumer + Commercial
type
Data Level Negative* Partial*** Negative Partial
Scorecard IDs TOS_1.0_X _NR_TC~ TOS_1.0_X_PR_TC~ TOS_1.0_XY_NR_TC~ TOS_1.0_XY_PR_TC
~
EA_2.1_X_NR_TC~ EA_2.0_X_PR_TC~ EA_2.1_XY_NR_TC~
VSA_2.0_X_NR_TC^ EA_2.1_X_NR_TC VSA_2.0_XY_NR_TC^
VS_1.1_X_NR_TC^ VS_1.1_X_NR_TC^ VS_1.1_XY_NR_TC^
Product Equifax Commercial Apply (Telco) Controlled via

name
Product 2.0 2.0 End point

version
Permission Commercial +Consumer Commercial+Consumer Request data
type
Data Level Negative Partial Request data
Scorecard IDs TOS_1.0_YX_NR_TC~ TOS_1.0_YX_PR_TC~ Request data
ECA_2.1_YX_NR_TC^
CCAI_2.0_YX_NR_TC^
VS_1.1_YX_NR_TC
Product name Equifax Apply (Utility) Equifax Commercial Controlled via

Apply (Utility)
Product version 2.0 2.0 End point

Permission type Consumer Consumer + Commercial +Consumer Request data
Commercial
Data Level Negative Negative Negative Request data
Scorecard IDs VSA_2.0_X_NR_UT VSA_2.0_XY_NR_UT CCAI_2.0_YX_NR_UT Request data
VS_1.1_X_NR VS_1.1_XY_NR VS_1.1_YX_NR
Product name Equifax Apply (Alternative Lending) Controlled via
Permission type Consumer Consumer + Commercial Request data
20
Product name Equifax Apply (Alternative Lending) Controlled via
Data Level Negative Negative Request data

Scorecard IDs VSA_2.0_X_NR_ALT VSA_2.0_XY_NR_ALT Request data
VS_1.1_X_NR VS_1.1_XY_NR
* For use by Credit Provider subscribers.

** For use by Credit Provider and Access Seeker subscribers.
*** For use by Telcos
~ Recommended. Not to be used in conjunction with ONE_1.0_XY_CR_B2C
^ Not recommended – customers are requested to move to new recommended scorecard id.
# For use by Comparison Sites. Not to be used in conjunction with ONE_1.0_XY_CR
Explanation of Scorecard Id:

● VSA: VedaScore Apply®
● EA: Equifax Apply
● ONE: Equifax One Score (Introduced December 2020)
● CCAI: Commercial Credit Assess – Individual
● VS: VedaScore (for VedaScore 1.1 scores)
● X: Indicates Consumer
● Y: Indicates Commercial
● NR/CR/PR: Indicates Negative / Comprehensive/Partial
● TC: Telco
● UT: Utility
● ALT: Alternative Lending
● B2C: indicates that consumer facing KCFs (Key Contributing Factors) are returned

The Access Seeker product only supports Comprehensive data level; Negative/Partial data level is not
supported for this subscriber group.
Note for Comparison Sites
One Score offers two versions of the Key Contributing Factor descriptions. The B2C scorecard
(ONE_1.0_XY_CR_B2C) provides meaningful descriptions for consumers, while the B2B
(ONE_1.0_XY_CR ) descriptions are more concise. Comparison sites can request either one of these
versions, however it is recommended to use B2C scorecard id. They should not be requested
together.
Only one Genesis Data BlockTM will be provided in the Equifax Apply product response regardless of
the number of scorecards requested. See note below for Telcos and Utilities. The characteristics in
this block will always reflect the maximum data level of the product selected by the customer. Refer
to section 3.6 Genesis Data BlockTM for more details.

An additional data block (Telco Data Block or Utility Data Block) will be provided in the Equifax Apply
(Telco) and Equifax Apply (Utility) product response.
21
An additional data block (Alternative Lending Data Block) will be provided in the Equifax Apply (Alternative
Lending) product response.
2.1 Product version

The product version is driven by the end point. Refer to 5.2 - Endpoint URLs for more information.
This version of the product guide relates to version 2.0 of Equifax Apply and Equifax Commercial Apply. When a
new product version is available, an updated version of this product guide will be released and include any
additional features and product variations
2.2 Permission type

The permission type is defined in the request using the element <permission-type>.
Permission type Description
Consumer Used in the context of consumer credit applications where only access to the individual's consumer
credit information is required.
Equifax searches its individual consumer and public record databases for the response and the Equifax
Apply product is returned.
The information you supply in your request is written to the consumer database.
Consumer + Used in the context of consumer credit applications where access to the individual's consumer and the
Commercial individual’s commercial credit information is required.
Equifax searches its individual consumer, individual commercial and public record databases for the
response and the Equifax Apply product is returned
The information you supply in your request is written to the consumer database.
Commercial + Used in the context of commercial credit enquiries where access to the individual’s commercial and the
Consumer individual’s consumer credit information is required.
Equifax searches its individual commercial, individual consumer, and public record databases for the
response and the Equifax Commercial Apply product is returned.
The information you supply in your request is written to the individual commercial database.
Commercial Used in the context of commercial credit enquiries where only access to the individual’s commercial
credit information is required.
Equifax searches its individual commercial and public record databases for the response and the
Equifax Commercial Apply product is returned.
The information you supply in your request is written to the individual commercial database.
Definitions:
● Individual Consumer credit is intended wholly or partly for personal, family or household purposes or to
acquire, re-finance, maintain or improve a residential property for investment purposes. This includes
credit applications such as credit cards, mortgages, and personal loans.
● Individual Commercial credit is credit for commercial purposes, e.g. a sole trader, partner, director or
guarantor of a company or other investment properties such as shops and factories.
Depending upon the enquiry being made consent of the individual or notice to the individual is required prior to
accessing the relevant report.
22
Individual consumer credit is governed by Part IIIA of the Privacy Act 1988 (the Act) and credit information is
defined in Section 6N.
Personal information relating to individual commercial enquiries is governed by the Australian Privacy Principles of
the Act.

Equifax Apply (Telco) and Equifax Apply (Utility) services are available in Consumer and Consumer +
Commercial permission types.
Equifax Commercial Apply (Telco) and Equifax Commercial Apply (Utility) Services are also available
in Commercial + Consumer permission type only.

Equifax Apply (Alternative Lending) services are available in two permission types - Consumer and
Consumer + Commercial.
2.3 Data level

The data level is defined in the request using the element <product-data-level>.
The data level defines whether additional data introduced with Comprehensive Reporting is included in the
product.
As part of version 2.0 negative and comprehensive data levels are supported. Partial is supported for Equifax
(Telco) only. A partial reporting product includes account details and account holder information but no
repayment history information or financial hardship information.
Subject to market demand and as a placeholder for future product release, Equifax will introduce more partial
reporting products.
In addition to the requirements of the Privacy Act 1988, rules of reciprocity apply to Equifax Apply and Equifax
Commercial Apply. The contribution level defines the maximum data level allowed. Only a comprehensive data
contributor has access to comprehensive data and comprehensive scores.
The credit provider’s data contribution level is controlled by Equifax internal configuration.
To facilitate the transition to comprehensive data, credit providers who are entitled to comprehensive data level
have the option of using negative services instead. The negative product structure is identical to the
comprehensive product structure to help ensure ease of transition from negative to comprehensive reporting.

Rules of reciprocity do not apply to access seekers. The Access Seeker product only supports
Comprehensive data level; Negative data level is not supported for this subscriber group.

Rules of Reciprocity also apply to Telco and Utility customers. Currently Equifax Apply (Utility)
services only support Negative data level while Equifax Apply (Telco) services support negative and
partial data levels.
23
Rules of Reciprocity also apply to Alternative Lending customers. Currently Equifax Apply
(Alternative Lending) supports Negative data level. Comprehensive data level is currently
unsupported and will be available in the future. Any Alternative Lender looking to supply and
receive Comprehensive data is advised to use the main Equifax Apply product at this time.
2.4 Scorecard ID
Multiple scores can be included in the response based on the request element <scorecard-id>. Refer to 3.3 -
Scores for the list of scorecard IDs.
If no scorecard ID is specified in the request, the system uses the latest scorecard based on permission type and
data level.
Configuring scorecard ID in the request helps ensure score stability when a new version of the score is released.
Over time, subscribers can remain on their current version of the score and transition gradually to the latest
version when ready.
Note that the choice of scorecard ID is limited depending on permission type and account data level. The product
data level needs to be higher or equal to the scorecard data level, e.g. a comprehensive score can only be
returned if the product data level is comprehensive (and subscriber is a comprehensive data contributor).
Note for Comparison Sites

One Score offers two versions of the Key Contributing Factor descriptions. The B2C scorecard
(ONE_1.0_XY_CR_B2C) provides meaningful descriptions for consumers, while the B2B
(ONE_1.0_XY_CR ) descriptions are more concise. Comparison sites can request either one of these
versions, however it is recommended to use B2C scorecard id. They should not be requested
together.
To obtain Equifax Apply (Telco) and Equifax Apply (Utility) product response, a Telco or Utility
scorecard ID is mandatory as part of the request. If no scorecard ID is mentioned, the standard
Equifax Apply product response would be returned.

To obtain Equifax Apply (Alternative Lending) product response, an alternative lending scorecard ID
is mandatory in the request. If no scorecard ID is mentioned, the standard Equifax Apply product
response is returned.
2.5 Individual Trading History Information

The Individual Trading History variant of the Equifax Apply and Equifax Commercial Apply reports provides
optional extra summary information about the companies that the individual holds a current or previous
directorship with and the businesses that they hold a proprietorship for. This information provides summary credit
risk information about those entities to gain further insight into the credit risk of the individual.
24
3 Key Product Features
This section only includes product features introduced in this version of the product. For a full view of the
response content, please refer to 6.2.3.2 - Report Response.
3.1 Full Identity Reporting

Equifax currently has around 1.5 million cross-references on Consumer files. Cross references occur where an
individual’s identity details change due to a name change (e.g.: maiden name to married name) or an individual
has an alias for some other reason. Cross references are expected to increase with Comprehensive Reporting as
individuals may have multiple accounts over multiple identities (e.g. accounts still active opened under maiden
name). Equifax is therefore introducing Full Identity Reporting to provide richer data and matching to our
customers.
Full Identity Reporting (FIR) naturally extends previous functionality called Multiple Identity Reporting (MIR).
While MIR consolidated and removed duplicates of credit information across all the cross-referenced files for an
individual, it only displayed identity information of the Primary Matched Identity. FIR provides more insight into
the information Equifax holds on other Identities for that individual, such as:
● While a maximum number of 3 Addresses are returned for an individual, these are sourced from all the
cross-referenced files and tagged accordingly.
● Aliases /alternate names are shown for cross-referenced records.
● Date of birth, driver’s licence, gender and employer are shown. Where available these will be sourced
from the primary record, otherwise cross-referenced identities may be used as a source.
● Credit data such as credit enquiries and defaults will be sourced from all the cross-referenced files and
tagged accordingly.
FIR also introduces additional metadata date fields associated with the individual's personal information -
specifically their name, DOB, driver's licence, address and employment details. This data provides insight into
when that data item was first reported and last reported to Equifax. Although in the first instance such fields may
be empty in the responses that will be returned, they will be populated more frequently over time as our
consumer credit database gradually becomes enriched with this data.
In the API Connect schema, FIR functionality is implemented using:

- An identity index (attribute id-index) appended to each identity associated to the subject.
- An identity reference (element <id-reference>) appended to credit information to associate the source of
this information to the identity defined in the identity index. In some instances, a list of identity references
can be returned if this information is associated to multiple identities (e.g. address).
- First Reported Date and Last Reported Date attributes (attribute first-reported-date, last-reported-date)
appended to each relevant personal information data item.
For Access Seekers, all identity data stored in the Bureau will be returned. Date of birth, driver’s
licence and gender will be returned as found on the primary identity and all cross-referenced identity
files. It is therefore possible for the same piece of identity data to have different values in the report.

Equifax Apply (Telco) and Equifax Apply (Utility) services would also have Full Identity Reporting
feature enabled.
25
Equifax Apply (Alternative Lending) services also have Full Identity Reporting feature enabled.
3.2 Accounts and defaults
3.2.1 Account structure

Equifax Apply and Equifax Commercial Apply use an account structure like the account structure introduced in
ARCA data standard. It includes:
- Elements of Consumer Credit Liability Information
- Account association details
- Repayment History Information and Financial Hardship Information
- Default Information
Note that the account information included in Equifax Apply and Equifax Commercial Apply product is only in
relation to the account holder who is the subject of the enquiry. For example, only defaults which are associated
to the subject will be included and repayment history will only include repayment data for periods where the
subject was active on the account.
3.2.2 Account data level

Depending on the level of underlying data available for an account, account information can be presented via five
different variations. In the API Connect schema for Equifax Apply and Equifax Commercial Apply, an account data
level (attribute account-data-level) is appended to each account element. It represents the maximum amount of
data that can be included for that account:
- Data level 1 includes only basic account details and account holder start date. This category replaces what
used to be reported as ‘Current Credit Provider’ (Note that only commercial Current Credit Provider
accounts are included in the credit provider report).
- Data level 2 includes basic account details and default data. This category typically includes default loaded
via all Equifax channels except for Data Load Services (which is the channel used for monthly data loads).
- Data level 3 includes basic account details, account holder association dates and default data. This
category typically includes defaults loaded by negative contributors via Data Load Services.
- Data level 4 includes CCLI details, account holder association dates and default data. This category
typically includes accounts loaded by partial contributors via Data Load Services.
- Data level 5 includes CCLI details, account holder association dates, default data, repayment history and
financial hardship information. This category typically includes accounts loaded by comprehensive
contributors via Data Load Services.
Account data level

Account data element 1 2 3 4 5
Original Credit Provider ✔ ✔ ✔ ✔ ✔
Latest Credit Provider ✔ ✔ ✔ ✔ ✔
Transfer Date ✔ ✔ ✔ ✔ ✔
Account Identifier ✔ ✔ ✔ ✔ ✔
26
Type of Account ✔ ✔ ✔ ✔ ✔
Account Holder Count 🗶 🗶 🗶 ✔ ✔
Account Holder Latest Start Date ✔ 🗶 ✔ ✔ ✔
Account Holder Latest Cease Date 🗶 🗶 ✔ ✔ ✔
Relationship ✔ ✔ ✔ ✔ ✔
Account Holder Default Association Start Date 🗶 🗶 ✔ ✔ ✔
Account Holder Default Association Cease Date 🗶 🗶 ✔ ✔ ✔
Serious Credit Infringement Indicator 🗶 ✔ ✔ ✔ ✔
Serious Credit Infringement Date 🗶 ✔ ✔ ✔ ✔
Open Date 🗶 🗶 🗶 ✔ ✔
Closed Date 🗶 🗶 🗶 ✔ ✔
Reopen Date 🗶 🗶 🗶 ✔ ✔
Loan Payment Method 🗶 🗶 🗶 ✔ ✔
Term Type 🗶 🗶 🗶 ✔ ✔
Secured Credit 🗶 🗶 🗶 ✔ ✔
Term of Loan 🗶 🗶 🗶 ✔ ✔
Original Maximum Amount of Credit Available 🗶 🗶 🗶 🗶 🗶
Latest Maximum Amount of Credit Available 🗶 🗶 🗶 ✔ ✔
No Fixed Limit Credit 🗶 🗶 🗶 ✔ ✔

Repayment History Information and Financial
Hardship Information 🗶 🗶 🗶 🗶 ✔
Default Information 🗶 ✔ ✔ ✔ ✔
Account History Information ✔ ✔ ✔ ✔ ✔
The symbol ✔ indicates that a data element will be included for this account data level if available.
Note that only account data levels 1 and 2 are available for individual commercial accounts.
For consumer accounts, account data level 4 is available to partial and comprehensive contributors and account
data level 5 is only available to comprehensive contributors only.
3.3 Scores
Equifax introduced a new scorecard to its range of scores in December 2020 – Equifax One Score. The new
scorecard is for Consumer Credit Providers and Access Seekers who have access to Comprehensive Data and is the
best Equifax scorecard built to date. Equifax has been able to include a much larger pool of Credit Provider
Comprehensive Credit Reporting (CCR) data than was available in the pilot, unleashed the full power of the
Comprehensive Data, included the superior Equifax Negative Consumer and Commercial bureau data, removed
the incoming origination enquiry, minimised any unintended bias and possible discriminatory factors, added new
27
BNPL and Geodemographic factors, maximised stability through Covid-19 and used some patented Equifax Neuro
DecisionTM Technology to produce a scorecard that is vastly more predictive that Equifax Apply Comprehensive and
all previous Equifax (and Veda) Australian scorecards.
Financial Hardship Information is not considered for scoring. Hence, no changes to any of Equifax Scores.
Equifax Apply and Equifax Commercial Apply previously introduced the VedaScore 2.0 suite which was built on
the highly successful Comprehensive Credit Reporting Pilot in 2011/12, and provided a greatly improved scoring
solution to Equifax customers as it incorporated not only Enquiry, Demographic and Default information but also
the Consumer Comprehensive Reporting Data (where applicable).
There are a total of 13 scorecards available in the suite now (plus 15 specialist scorecards – see over) depending
on the credit providers Data Level (access to Comprehensive Credit Reporting data or Negative data) and the
purpose (Consumer or Commercial) and permission type of the enquiry. Provided that the individual has given
appropriate consent, the scores available include Consumer, Consumer + Commercial and for individual
commercial purposes - Commercial + Consumer and Commercial only. Equifax One Score is now available in
Comprehensive Data Level only, for Consumer purpose only (not for Commercial borrowing).
Up to 3 scorecard ids can be ordered. Equifax recommends using scorecards as high up in this table as possible, i.e.
Equifax One Score over Equifax Apply, Consumer + Commercial over Consumer only and Comprehensive over
negative (where applicable). Account Managers can help engage Equifax Analytics and Advisory consultants to
help choose the right scorecard ids for each customers situation, via either a simple score comparison exercise or
something more in-depth.
Four VedaScore 1.1 scorecards remain available to facilitate the transition from 1.1 and are not recommended as a
sole scorecard at this time.
Score name Score Version Score Data level Permission type Scorecard ID
ONE_1.0_XY_CR or
Consumer + Commercial
Equifax One Score 1.0 Comprehensive ONE_1.0_XY_CR_B2C
Consumer ONE_1.0_X_CR
Consumer + Commercial VSA_2.0_XY_CR
Comprehensive
Consumer VSA_2.0_X_CR
Equifax Apply 2.0
Consumer + Commercial VSA_2.0_XY_NR
Negative
Consumer VSA_2.0_X_NR
Comprehensive Commercial + Consumer CCAI_2.0_YX_CR
Equifax
2.0 Commercial + Consumer CCAI_2.0_YX_NR
Commercial Apply Negative
Commercial CCAI_2.0_Y_NR
Consumer + Commercial VS_1.1_XY_NR
Consumer VS_1.1_X_NR
VedaScore 1.1 Negative
Commercial + Consumer VS_1.1_YX_NR
Commercial VS_1.1_Y_NR
28
Ten additional scorecards are available for Equifax Apply (Telco) and Equifax Apply (Utility) products and cover
Consumer, Consumer + Commercial and Commercial + Consumer type.
For Telcos the new Equifax One Score for Telco scorecards utilising both Partial and Negative data sets have been
added. It is recommended that Telcos use the new scorecard/s in preference to the existing scorecard.
Score name Score Version Score Data level Permission type

Consumer + Commercial TOS_1.0_XY_PR_TC~
Partial
Consumer TOS_1.0_X_PR_TC~
Equifax One Score for Telco 1.0
Consumer + Commercial TOS_1.0_XY_NR_TC~
Negative
Consumer TOS_1.0_X _NR_TC~
Consumer + Commercial EA_2.1_XY_NR_TC
2.1 Negative
Consumer EA_2.1_X_NR_TC
Equifax Apply (Telco) Consumer + Commercial VSA_2.0_XY_NR_TC^
2.0 Negative
Consumer VSA_2.0_X_NR_TC^
2.0 Partial Consumer EA_2.0_X_PR_TC
TOS_1.0_YX_PR_TC~
Equifax Commercial Apply 2.0 Negative Commercial + Consumer
ECA_2.1_YX_NR_TC^
(Telco)
2.0 Partial Commercial + Consumer TOS_1.0_YX_PR_TC~
Consumer + Commercial VS_1.1_XY_NR_TC^
VedaScore 1.1 Negative Consumer VS_1.1_X_NR_TC^
Commercial + Consumer VS_1.1_YX_NR^
~ Recommended.
^ Not recommended – customers are requested to move to the new recommended scorecard id.
Consumer + Commercial VSA_2.0_XY_NR_UT
Equifax Apply (Utility) 2.0 Negative
Consumer VSA_2.0_X_NR_UT
Equifax Commercial Apply

2.0 Negative Commercial + Consumer CCAI_2.0_YX_NR_UT
(Utility)

VedaScore 1.1 Negative Consumer VS_1.1_X_NR
Commercial + Consumer VS_1.1_YX_NR
Two scorecards are developed for Equifax Apply (Alternative Lending) and cover Consumer and Consumer +
Commercial permission type.
29
Equifax Apply (Alternative Consumer + Commercial VSA_2.0_XY_NR_ALT
2.0 Negative
Lending) Consumer VSA_2.0_X_NR_ALT
VedaScore 1.1 Negative
Consumer VS_1.1_X_NR
When new versions of the score are introduced in the future, new scorecard IDs will be available in Equifax Apply.
Credit Providers who are loading Comprehensive data onto the Equifax consumer credit database (including
repayment history information) are eligible to use all models.
Telco Companies who are loading partial data (i.e. CCR data excluding Repayment History Information) are eligible
to see partial and negative scoring models only. Over time, partial services may be developed for Utility
Companies and Credit providers based on the demand. All other users and contributors of default information are
only able to use negative scoring models.
All Scorecard models used in Equifax Apply and Equifax Commercial Apply deploy the Masterscale in line with the
VedaScore 1.1 product suite (previously reported as veda-score in the VedaScore 1.1 XML response). This
Masterscale returns an integer value between -200 and 1200 and so offers customers a number of advantages
including simplicity and consistency of meaning across different Equifax products.
Equifax Apply and Equifax Commercial Apply do not include relative risk, percentile and VedaScore 1.1 index.
Population odds and applicant odds have also been removed; the latter being displaced by the new
risk odds value.
Access Seekers have access to all scorecards (excluding Equifax Apply (Telco) and Equifax Apply
(Utility)) within any given report permission type context and just need to specify which ones they
require in the request.

To obtain Equifax Apply (Telco) and Equifax Apply (Utility) product response, a Telco or Utility
scorecard ID is mandatory as part of the request. If no scorecard ID is mentioned, the standard
Equifax Apply product response would be returned.

To obtain Equifax Apply (Alternative Lending) product response, the Alternative Lending scorecard
ID is mandatory as part of the request. If no scorecard ID is mentioned, the standard Equifax Apply
product response would be returned.
3.4 Key Contributing Factors

The key contributing factors (KCFs) are dynamically generated with each enquiry to provide insight into the
information that had the largest impact on the calculated score. Various scorecard parameters may be aggregated
under one Key Contributing Factor if they relate to similar behaviour / attributes. Each KCF has an associated text
descriptor. The aggregate relative score weights for each KCF are evaluated for the purpose of risk impact
calculations and have a corresponding “Impact on Risk” measure to depict a severity and direction of impact. This
could be a “marginal”, “moderate” or “great” impact on increasing / decreasing risk.
30
Four KCFs are associated with a score for individuals with no insolvency on file. Only one KCF will be generated for
individuals with insolvency on file. Refer to 8.11 - Key Contributing Factors (KCF) for a complete list of key
contributing factors.
3.5 Additional scores

Equifax has designed the Equifax Apply and Equifax Commercial Apply products so that subscribers are able to
request multiple scores in one transaction. This functionality has a number of benefits including:
- Enabling Equifax over time to build or incorporate new scoring services for credit origination e.g. Fraud
models, Propensity models etc.
- Enabling subscribers to receive old and new models concurrently as the Comprehensive Credit Reporting
landscape matures and subscribers assimilate all the new information. New score variants will be available
as additional scores, facilitating score champion challenger analytics and soft deployments/monitoring.
This means that score versions 1.1, 2.0 and future score versions will be accessible through this product.
Note that even when additional scores are requested, only one Genesis Data BlockTM is returned in the response.
Exclusions apply to Telcos and Utilities (see note below).

An additional data block (Telco Data Block or Utility Data Block) is provided in the Equifax Apply
(Telco) and Equifax Apply (Utility) product response. Hence a total of two data blocks would be
returned as part of these product responses.

An additional Alternative Lending data block is provided in the Equifax Apply (Alternative Lending)
product response. Hence a total of two data blocks would be returned as part of this product
response.
3.6 Genesis Data BlockTM

Enhanced credit reporting information is also provided in the Equifax Genesis Data BlockTM which is available with
every product request. The Genesis Data BlockTM allows subscribers to include additional business rules in the
decisioning process.
The Genesis Data BlockTM is made up of:
o The negative data summarised by 120+ characteristics and, where Consumer + Commercial or
Commercial + Consumer information is requested, incorporates Consumer and Commercial data.
o The CR data incorporates 320+ new Consumer characteristics.
o Partial data items are included within the CR set and are currently available for Telcos.
o As per international best practice, the set includes 10+ “own” variables – for example “Own Worst
Account Payment Status”. “Own” variables will be derived based on the Credit Provider’s subscriber
setup with Equifax.
The characteristics included in the Genesis Data BlockTM for each transaction will be based on the product data
level (Negative or Comprehensive) specified in the request. CR characteristics will only be included if data level is
Comprehensive.
31
Refer to the Genesis Data BlockTM Guide for a complete list of characteristics included in the Genesis Data
BlockTM.

A separate Genesis Data BlockTM guide is available for Equifax Apply (Telco) and Equifax Apply
(Utility) services. It contains all the Negative characteristics that are returned as part of the Genesis
Data BlockTM, Telco Data Block and Utility Data Block. For Telcos onboarding to Partial product please
refer to the Genesis Data BlockTM guide Partial (Telcos)
3.7 Financial Hardship Information Data Block

From July 1 2022 Financial Hardship Information (FHI) is reported alongside Repayment History Information. To
facilitate use of this data in customer decisioning processes a new FHI data block is introduced. The FHI data block
is returned automatically with Comprehensive data level reports as permitted by the customer tier level.
3.8 Alternative Lending Block & Custom Data Blocks

Subscribers can further customise the reports they receive by opting to receive a data block that a service does
not normally receive. For example, an Equifax Apply subscriber may opt to receive the Alternate Lending data
block in addition to the Genesis Data BlockTM. From December 2020 Equifax has released an enhanced Alternative
Lending Data Block that contains a number of additional “Buy Now Pay Later” characteristics to look more deeply
into this sector of Alternative Lending. For more information on the new characteristics please refer to the
Genesis Data Block Guide on the Developer Centre. To request the Alternative Lending Data Block be returned in
the response please refer to an Equifax Account Manager.
A subscriber can also request to have a fully customised data block if the existing data blocks do not meet their
needs. Please contact your Equifax account manager to discuss what options are available to you.
o 3.8 Individual Trading History Information
For each of the companies and businesses that the individual holds a current or previous directorship or
proprietorship for the trading history variant returned information about the number of enquiries, defaults,
mercantile enquiries, court writs and actions, directorships and proprietorships/proprietors.
In order to request the trading history information for an individual, in the request to API Connect specify a
custom input parameter key “ITH” with the value “true” (Refer to 6.2.2.1 Enquiry Header Seq no 1.8.1.1 and Seq
no 1.8.1.2).
3.1 Future use fields

The API Connect schema for Equifax Apply and Equifax Commercial Apply includes multiple future use fields in
the request and response messages. The intent is to provide some extra flexibility in regard to dealing with future
additions to data structures. This approach allows for incremental changes to the product to be rolled out with
minimal impact to subscribers, by alleviating the need to integrate with a new schema in most cases.
Whilst a field is marked as future use, such fields should not be submitted in the request to avoid additional and
unnecessary validation. Future use fields have no bearing on the report until they are enabled.
32
However, Equifax recommends that subscribers build their client systems in readiness to accept and ingest, where
possible, fields marked as “future use” in the response. This will help reduce the transition effort once Equifax
starts to return future use fields in the response.
3.2 Comprehensive Credit Reporting Term of Loan Unit Type

For CCR customers the term field supplied with accounts was originally supplied only in months – so a term of 60
was always 60 months. In version 2.1 of the Australian Credit Reporting Data Standard (ACRDS), customers can
provide the term in Days, Weeks, Months or Years, so a 5-year term could be supplied as 5 (years), 60 (months) or
260 (weeks). To determine if a term of 60 is in Days, Weeks, Months or Years, it is important to refer to the new
optional Term Unit Type field. If the field is missing, then the default term remains in months.
To avoid a schema change this has been incorporated into one of the future use fields.
The additional data fields section is designed as an array of key-value pairs so it will look like this:
<additional-data-fields>
<data-field>
<key>term-unit-type</key>
<value>years</value>
</data-field>
</additional-data-fields>
Refer to section 6.2.3.2.5.2 Accounts Seq 2.1.5.3.1.23 additional data fields and 8.29 Term of Loan Unit Type code
table for a list of valid values.
3.3 XML report style sheet

Equifax has developed an XSL style sheet that allows API Connect customers to render the product XML response
into a HTML report. This provides customers an easy and reliable way of displaying the report in their systems in a
user-friendly format with minimal development effort.
3.4 PDF retrieval over API Connect

The Equifax Apply and Equifax Commercial Apply product allow API Connect customers to retrieve reports in PDF
format via the Previous Enquiry API. Initially, the customer must submit an enquiry request. They then use the
enquiry ID value returned in the response product header as the input to the Previous Enquiry service, to retrieve
the report as a PDF.
Refer to the API Connect Previous Enquiry – Application Programming Interface document for guidance.
4 Key Technical Features

4.1 System Integration
4.1.1 API Connect SOAP Overview

Equifax Apply and Equifax Commercial Apply are delivered over the API Connect SOAP channel, which
implements the standards-based SOAP protocol for transmitting data over a secure HTTP transport. This
document assumes the reader has knowledge and understanding of the SOAP (1.1/1.2) protocol, as well as of
other API Connect concepts detailed in the API Connect Connectivity and API Connect Getting Started guides.
33
The following areas will be of particular interest to users of previous VedaScore XML-based products:
● Authentication: API Connect SOAP relies on the WS-Security protocol for handling user credentials as part
of the transaction.
● Dedicated SOAP Endpoint: The API Connect SOAP channel provides separate, dedicated SOAP/HTTP
endpoints for each product suite, including one shared between Equifax Apply and Equifax Commercial
Apply.
Whereas previous VedaScore products supported only a synchronous transmission model, Equifax Apply and
Equifax Commercial Apply are typically invoked using a hybrid mode of operation, which aims to provide a
complete response in real-time but with the possibility to switch to an asynchronous model if required. A fully
asynchronous mode of operation is also supported by this specific product. Both modes of operations are
described in the sections below.
4.1.2 Hybrid, Synchronous/Asynchronous Transmission Model

Most typical Equifax Apply and Equifax Commercial Apply transactions are completed by sending a single HTTP
POST request to the API Connect server and receiving a completed response as part of the same SOAP transaction.
Where this is not possible, the service will endeavour to complete the response and make it available for
collection in asynchronous fashion.
By default, each transaction starts with the aim of completing the request in real-time but switches automatically
to asynchronous alternative mode under circumstances where the system is unable to fulfil the request within the
service response window.
When switching to this alternative mode, the initial transaction will return a ticket response rather than a product
report. This ticket will provide a unique enquiry identifier which can be used to retrieve the completed product
report at a later time from the API Connect server. The diagram in Figure 1 provides a high-level view of the
semi-asynchronous transmission model.
34
Figure 1 – Hybrid Sync/Async Transmission Model
4.1.3 Asynchronous Transmission Model

The web service API for Equifax Apply and Equifax Commercial Apply also supports a full asynchronous model (via
separate operations dedicated to asynchronous processing). In this model, the initial POST transaction always
return a ticket response to the caller and the product report can only be retrieved (once generated and ready for
collection) via a separate POST transaction, which uses the enquiry ID returned in the ticket to identify the report.
Note that the API does not at this stage support a PUSH delivery model and the caller must therefore explicitly
initiate the subsequent transaction with the API Connect server to PULL the completed report (NB: client polling
mechanisms should follow Equifax recommendations when checking for completed reports). The diagram in
Figure 2 describes a typical sequence of events when requesting an Equifax Apply or an Equifax Commercial
Apply report using the asynchronous API.
35
Figure 2 - Asynchronous Transmission Model
4.1.4 Recommended Guidelines for Asynchronous Processing

As noted in previous sections, semi-asynchronous or fully asynchronous processing requires the caller to poll the
API Connect server to retrieve the completed product report. Equifax recommends the following implementation
guidelines to ensure sustainable performance and stability in the integration between the client and server
systems:
● Client timeout configuration should be set in line with indicative guidelines specified in the API Connect
Connectivity Guide. Equifax currently recommends a minimum of 45 seconds.
● Subsequent HTTP POST requests related to a pending enquiry should be sent at an interval no shorter
than FIVE seconds from the initial POST.
● In the unlikely event that additional polling requests are required to retrieve a completed enquiry, these
should be sent at increasing intervals, starting from the minimum 5-second period specified above.
Figure 3 describes a possible scenario where two polling requests are required in order to retrieve the completed
report.
36
Figure 3 - Polling for a completed report
4.1.5 Using Hybrid or Asynchronous Integration

The decision to use either of the two models is typically driven by a variety of factors, including:
● Integration capabilities of the client system
● Requirement for real-time decisioning capability
● Business and operational workflow constraints
● User behaviour and expectations
The following guidelines may be used to assist in the decision of which integration API to use.
37
4.1.5.1 Typical Synchronous/Hybrid Use-cases
● End users require or expect a response in near-real-time, as part of the credit origination process
● The client system has limited or no capability to integrate with a ticketing system (in which case ticketing
scenarios made possible by the hybrid API may be treated as exceptions)
● There is a need or preference for keeping the number of HTTP POST calls per enquiry to a minimum (most
hybrid transactions will typically only require a single POST)
4.1.5.2 Typical Asynchronous Use-cases
● The user consuming the report is not the same person who submitted the enquiry
● The credit origination workflow does not require an immediate response to the initial enquiry
● The client system has built-in capabilities for integration which lend themselves to asynchronous
processing
● There is a need to submit enquiries in small batches and do not require to return an immediate response
for each to a user
4.2 Possible response types

The following matrix describes which response elements will be included in the payload, depending on the
integration method and associated use-cases.
Wrapper element response product- product- general- errors

-type header data messages
Successful synchronous request (full response ‘report’ Yes Yes Optional No
response)
Successful synchronous request (file response ‘file-ban’ Yes Yes Optional No
ban)
Deferred synchronous request (ticket response ‘ticket’ Yes No Optional No
response)
Synchronous request with errors response ‘error’ Yes No Optional Yes
Successful asynchronous request ticket-response ‘ticket’ Yes No Optional No
Asynchronous request with errors ticket-response ‘error’ Yes No Optional Yes
4.3 Enquiry ID
The enquiry ID is used to uniquely identify a particular business transaction, such as an Equifax Apply enquiry or
an Equifax Commercial Apply enquiry. It is always returned in the response (as part of the product-header) in both
synchronous or asynchronous models and can thereafter be used to retrieve the corresponding report, using the
web service operations dedicated to that purpose (see section 5.1 - Operations).
It is also of value within the context of troubleshooting and support queries, where Equifax support personnel can
use this number to rapidly identify and isolate events pertaining to a particular enquiry.
4.4 Timeouts
The recommended HTTP timeout for Equifax Apply and Equifax Commercial Apply will be specified in a later
iteration of this document. In general terms, Equifax typically recommends a minimum value of 45 seconds for
connection timeouts.
38
4.5 Supported SOAP Bindings
The Equifax Apply WSDL may show bindings for SOAP version 1.1 and 1.2. It should be noted that only SOAP 1.1 is
currently supported. Support for SOAP 1.2 may be introduced in a later release (based on demand).
4.6 Reserved XML characters

Some characters are specifically reserved for use in XML mark up. Consequently, these characters must be
translated into character references in requests. Table 1 lists the reserved characters and their XML references.
Character XML Reference
Left angle bracket < <
Right angle bracket > >
Ampersand & &
Apostrophe ' '
Quotation mark " "
Table 1 - Reserved XML Characters
For example, the following element will be rejected by the schema:

<employer>O’Toole & Murphy</employer>
Instead, enter the above example as:
<employer>O'Toole & Murphy</employer>
or
<employer>O’Toole & Murphy</employer>
An XML character reference counts as a single character.

Some XML builder tools can perform these translations automatically.
API Connect responses return apostrophes and quotation marks as their original characters; they are not
transformed to XML references. Angle brackets and the ampersand character are transformed to their
XML reference.
4.7 Request Validation
4.7.1 Overview
Requests are validated in two stages:
● Initial validation takes place when the request is parsed by the schema. This validation focuses on the
structure and the request message, with some basic type-checking. Errors encountered during schema
validation will typically abort the transaction and return a SOAP fault.
● Further validation takes place after Equifax has received the request and has successfully validated it
against the schema. This validation checks the items that the schema was unable to validate, for instance,
validating field data against known product business rules. Errors will be returned as product errors.
Refer to section 4.8 - Error-handling for more information on error-handling for this product.
39
4.7.2 Validating addresses
Formatted addresses divide the address into specific items, such as the street name and the suburb name. Equifax
recommends the use of formatted addresses wherever possible for optimum matching.
4.7.2.1 Formatted addresses
In the case of formatted addresses, different elements may be mandatory, depending on the composition of the
address.
For example, this address uses a street number/street name combination:
<street-number>8</street-number>
<street-name>Taree</street-name>
<street-type >AVE</street-type >
This address uses a property name only:
<property>The Gables</property>
The rules covering address elements may be summarised as follows:

● A street type cannot be entered without a street name.
● If a street number consists of a range of numbers (e.g., 1-8), enter only the first number.
● If a street name consists of a street type (such as “The Avenue” or “The Boulevard”), enter the whole
string into the <street-name> element and leave out the <street-type> element.
For example, the following is correct.
<street-name>The Avenue</street-name>
The example below, on the other hand, is incorrect.
<street-name>The</street-name>
<street-type >AVE</street-type >
If a street type does not match any of the street-type codes listed in the Product Guide, do not enter it.
Australian addresses require a suburb/state combination in an address.
4.7.2.2 Unformatted addresses
Where a fully fielded address is not available, the Equifax Apply schema also provides support for unformatted
addresses. Where possible and applicable (i.e. for addresses in Australia), unformatted addresses should be
entered using a structure in line, as per the following example:
<unformatted-address>The Gables 8 Taree AVE North Balgowlah NSW 2093</ unformatted-address >
4.7.3 Validating dates

All dates, in both requests and responses, have the same 10-character format using International ISO Standard
8601: YYYY-MM-DD
40
4.8 Error-handling
Equifax Apply implements error-handling in a manner that is consistent with the approach described in the API
Connect Connectivity Guide. Error message formats will vary, depending on the type and cause of the error.
System-level or transport-level errors, such as protocol or authentication errors, are returned to the caller as SOAP
Faults and should be handled accordingly by the client. The following is an example of a failed authentication
attempt to use the service.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>Policy Falsified</faultstring>
<faultactor>http://127.0.0.1:8080/sys2/ping-v1</faultactor>
<detail>
<l7:policyResult status="Authentication Failed"
xmlns:l7="http://www.layer7tech.com/ws/policy/fault"/>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
For more information on this type of error, including more examples, please refer to the API Connect Connectivity
Guide.
Product-type errors, which for instance result from an incorrect or invalid use of the product, are returned to the
caller as error messages inside a valid SOAP response body.
Refer to 7.2 Product error codes and descriptions for a categorisation of error codes and recommended action(s)
relevant to this product.
4.9 Testing Environment for Customers

The section below only includes high level information around the testing environment for customers. Please refer
to the Equifax Apply and Equifax Commercial Apply – Customer Test Guide for more information and detailed
test coverage.
Equifax provides a dedicated test environment to subscribers to enable them to test their solution prior to
deployment in a production environment. This environment offers a test service endpoint for both connectivity
and functional testing to assist software developers in integrating with Equifax Apply. The test service endpoint
enables subscribers to test the full array of functionality by submitting enquiries against a test system and receive
dynamically generated responses in return.
Refer to the Equifax Apply and Equifax Commercial Apply – Customer Test Guide for an understanding of which
features, and test cases are available in this environment
Refer to section 5.2 - Endpoint URLs for more information on how to connect to the product endpoint in CTE.
41
5 Web Services
5.1 Operations
The table below contains a list of services specific to the Equifax Apply and Equifax Commercial Apply products
and a brief description for each service. Detailed description for each service can be found in subsequent
chapters.
Service Description
submitEnquiry
This web-service operation allows users to perform a credit application enquiry by
using either an Equifax reference (identified as bureau-reference in the schema) or
searching using the applicant's personal details and details of the credit for which
the applicant has applied for.
This operation is expected to return the applicant's credit information within the
agreed response time. If that is not possible, it will instead only return the Enquiry
ID for the requester to use to retrieve the credit information at a later time.
submitEnquiryAsync Same as submitEnquiry; however, the interaction is asynchronously fulfilled.
This web-service operation will return an EnquiryID for which the user will be able
to retrieve the applicant's individual Consumer credit information later by using the
Enquiry ID as input into the retrieveEnquiryByID operation.
retrieveEnquiryByID This web service allows the user to retrieve a previously requested enquiry.
To use this operation, the serviced consumer must provide an Enquiry ID that is
typically acquired from calling one of the previous operations.
Details of each operation are provided in the next sections by way of request and response message
specifications. The intent is to explain the semantics of the data being exchanged in each message and associated
business rules, over and above to the information available in the WSDL files.
The message specifications include the schemas, represented diagrammatically (one high level diagram followed
by the low-level diagrams for complex elements), and the list of elements for each message.
5.2 Endpoint URLs

The user must establish a connection to the appropriate endpoint using the standard port 443.
Environment URL IP Address
Production https://apiconnect.equifax.com.au/sys2/soap11/vedascore-apply-v2-0 103.23.218.113
Test URL 1 https://ctaau.apiconnect.equifax.com.au/cta/sys2/soap11/vedascore-a

103.23.218.114
(Recommended) pply-v2-0
42
6 Request & Response Message Specifications
6.1 Conventions
6.1.1 Data Types, Constraints and Attributes

Descriptions given in this manual should always be used in conjunction with the WSDL and associated XML schemas provided for the product.
6.1.2 Schema representations explained

Optional elements: Indicated by a broken line.
Mandatory elements: Indicated by a continuous line.
: indicates a choice.
: indicates a sequence of elements which must be provided as per their optionality.
6.1.3 Message Body Content table explained

Each message specification contains a table which is used to list and define the XML element contained in the XML schema.
● Seq No: This is a sequential number used to indicate where the XML element appears within the schema document tree. To represent nested
elements the sequence number breaks into the next numbering level.
● XML Element: Name of the XML element.
● Type: Container, Element or Attribute (attribute elements are preceded with an @ symbol in this document).
● O/C (Optionality/Cardinality): Indicates if the XML element is optional and the number of possible occurrences of the element (assuming the
parent element is present).
o 0-1 indicates that the element is optional and its maximum occurrence is 1
o 1 indicates that the element is mandatory (assuming the parent element is present)
o 0-M indicates that the element is optional and can occur multiple times
o 1-M indicates that the element is mandatory (assuming the parent element is present) and can occur multiple times
o 1-50 indicates that the element is mandatory (assuming the parent element is present) and can occur up to 50 times
● Description: Description or business meaning of the XML element.
● Len: Indicates the max length of the XML element.
● V/F (Variable/Fixed): Indicates whether the value of the XML element will be variable or fixed.
43
● Format and Validation Rules: Describes the format and or validation rule applicable to the data element.
6.2 Submit Enquiry
6.2.1 Business Overview

A new enquiry can be submitted by using the following operations:
1. submitEnquiry
2. submitEnquiryAsync
These web service operations allow the user to search the Equifax database(s) for an individual’s (i.e. the credit applicant’s) credit information.
The requestor can identify the applicant in one of two ways:

● By Personal Details; Details of the applicant’s name, address and other personal information to search the individual Consumer and/or individual
Commercial and Public record databases for records that best match the supplied details.
● By Bureau Reference Number; The Bureau Reference Number is a unique identifier for that individual. Bureau Reference Numbers can change over
time and storing these is not advisable. However, this type of request is useful when an initial enquiry using identity details did not return the
applicant’s file but the applicant is listed as a possible match with a Bureau Reference Number. The Bureau Reference Number can then be used for
the subsequent enquiry and will guarantee that the appropriate match is returned.
To increase the possibility that the database finds the correct individual, ensure that as much information about the individual is supplied as possible.
If a field is optional and the intention is to not supply a value, then do not submit the element tags at all. <element></element> or
<element/> are interpreted as a zero length string and will be subject to field and cross field validation rules if supplied.
This principle is applicable to future use fields also. Whilst a field is marked as future use, such fields should not be submitted in the request
to avoid additional and unnecessary validation. Future use fields have no bearing on the report until they are enabled.
6.2.2 Request Overview

Request includes:
● Enquiry header information
o Client reference and operator details; ID and name.
44
o Product Data level; Data level must be compatible with the requestor subscriber’s Comprehensive Reporting data contribution level.
o Requested scores; can include more than one score. Scorecard ID(s) must be compatible with the requested product data level.
● Enquiry data information
o Credit applicant’s identification details; Bureau reference or personal details.
o Details of the line of credit for which the applicant is applying for.
The following illustration depicts the general structure of the request.
Figure 4: Submit Enquiry - Request Overview

6.2.2.1 Enquiry-header
Schema location: request>enquiry-header
Figure 5: Enquiry-header
45
Message Body Content Table
Seq XML Element Type O/C Description Len V/F Format and Validation Rules
No
1 enquiry-header Container 1 Container for control information related to the
request.
1.1 client-reference Element 0-1 Client reference ID provided associated with this 64 V Valid characters are Alphanumeric,
request transaction – this value will be returned Blanks, and the following characters:
back in response for traceability. @#$%&*()-_+=!\}{“‘?/.,:;
1.2 operator-id Element 0-1 Operator (or system) identifier submitting this 20 V
request transaction N
1.3 operator-name Element 0-1 Operator name submitting this request 20 V
transaction – this value will be returned back in
response for traceability.
1.4 permission-type-code Element 1 Indicates the permission type. Used to 2 V Refer to 2.2 - Permission type for
determine whether consumer and/or more information about permission
commercial data is included in the report. type.
1.5 product-data-level-code Element 1 Indicates the product data level used to 1 F Refer to 8.6 - Data Level code table (p.)
construct the report. for valid values
For Credit Providers, this value must be less than
or equal to the Credit Provider's data
contribution level with Equifax.
For Access Seekers, this value must be set to C
(Comprehensive).
For Telcos, this value must be less than or equal
to the data contribution level with Equifax
(Negative/ Partial).
For Utility and Alternative Lending customers,
this value must be set to N (Negative). Partial (for
Utilities) and Comprehensive (for Alternative
Lending) data level is not currently available.
1.6 requested-scores Container 0-1 Contains the scorecard ID of the primary score
and additional scores if requested.
1.6.1 scorecard-id Element 0-M Scorecard Identifier -Indicates the scorecard to 20 V Note: When no scorecard ID is
return in the product response. Must be a specified, the system uses the latest
46
compatible scorecard to the product and product scorecard based on permission type
data level. and data level.
Telco, Utility, or Alternative Lending
Scorecard ID is mandatory for Equifax
Apply (Telco), Equifax Apply (Utility)
and Equifax Apply (Alternative Lending)
products.
1.7 possible-matches Container 0-1 Future use only
1.7.1 maximum-matches Element 1 Future use only
1.7.2 match-criteria Container 1-M Future use only
1.7.2.1 match-criterion Element 1 Future use only
1.8 custom-input-parameters Container 0-1 List of custom input parameters to specify
additional product variations.
1.8.1 custom-input-parameter Element 1-M Contains a key/value pair for a custom
parameter.
1.8.1.1 Key Element 1 The custom input parameter key. V String,
To order Individual Trading History
Summary add “ITH” here.
Note: There is no validation of this field.
If the key matches to a known custom
input parameter then it is processed,
else it is ignored.
1.8.1.2 value Element 1 The custom input parameter value. V String.
To order Individual Trading History
Summary add “true” here.
47
6.2.2.2 Bureau-reference and Individual
Schema location: request>enquiry-data>individual
request>enquiry-data>bureau-reference
Figure 6: Bureau-reference and Individual

Seq No XML Element Type O/C Description Len V/F Format and Validation Rules
2 enquiry-data Container 1 Container for request information related - -
to the enquiry.
2.1 bureau-reference Element 0-1 Bureau reference; this is a unique identifier 10 V Maximum length of 10 chars.
for that individual. Use this option if the
individual can be explicitly identified by If bureau-reference is entered, then details in
Bureau reference value. individual container must not be supplied.
48
2.2 individual Container 0-1 Contains personal detail elements for If details in individual container are entered, then
identifying an individual. Use this option if bureau-reference must not be supplied.
searching by identification data of that
individual.
To increase the possibility that the search
finds the correct individual, submit as much
personal information about that individual
as possible.
2.2.1 current-name Container 1 Contains the individual's name elements. Mandatory if individual is present.
2.2.1.1 title Element 0-1 Future use only 25 V
2.2.1.2 family-name Element 1 Family Name. Also referred to as Surname. 50 V Max 50 chars.
Min 1 char.
If the applicant only has a single name Valid characters are Alpha, Blanks, Hyphens and
being their first-given-name, then Apostrophes. Exception for forward slash in the
family-name is to be reported as ‘N/A’ to case of ‘N/A’ (not case sensitive).
indicate not applicable. First character must be Alpha or Apostrophe.
Blanks, Hyphens and Apostrophes must not be
adjacent.
If family-name is 1 character, that character must
be Alpha.
family-name and first-given-name cannot both be
‘N/A’.
Refer to 4.6 Reserved XML characters for more
details.
2.2.1.3 first-given-name Element 1 First Name. 40 V Max 40 chars.
Min 1 chars
If the applicant only has a single name Valid characters are Alpha, Blanks, Hyphens and
being their family-name, then Apostrophes. Exception for forward slash in the
first-given-name is to be reported as ‘N/A’ case of ‘N/A’ (not case sensitive).
to indicate not applicable. First character must be Alpha.
adjacent.
first-given-name and family-name cannot both be
‘N/A’.
details.
49
2.2.1.4 other-given-name Element 0-1 Also referred to as middle names. 80 V Max 80 chars.
Although optional this information is Min 1 char.
recommended for better file matching. Valid characters are Alpha, Blanks, Hyphens and
Apostrophes.
First character must be Alpha.
adjacent.
Refer to Appendix A –Tips for Matching to
Individual Bureau Files
details.
2.2.2 known-as-names Container 0-1 Future use only
2.2.2.1 known-as Container 1-M Future use only
2.2.1.1.1 title Element 0-1 Future use only 25 V
2.2.2.1.2 family-name Element 1 Future use only 50 V
2.2.2.1.3 first-given-name Element 1 Future use only 40 V
2.2.2.1.4 other-given-name Element 0-1 Future use only 80 V
2.2.3 previous-names Container 0-1 Future use only
2.2.3.1 previous-name Container 1-M Future use only
2.2.3.1.2 family-name Element 1 Future use only 50 V
2.2.3.1.3 first-given-name Element 1 Future use only 40 V
2.2.3.1.4 other-given-name Element 0-1 Future use only 80 V
2.2.4 addresses Container 1 Contains information about the individual's
address.
2.2.4.1 address Container 1-M Contains information about an instance of There can be up to two addresses: one for the
the individual's address. current and one for the previous address. Note
that previous address is optional but
recommended - refer to Appendix A –Tips for
Matching to Individual Bureau Files
Customers have the choice of submitting a
formatted address or unformatted address.
2.2.4.1.1 @type Attribute 1 Address type. 1 F Refer to 8.1 - Address Type code table (p.) for valid
values.
2.2.4.1.2 @time-at-address Attribute 0-1 Future use only
50
2.2.4.1.3 property Element 0-1 Property Name 40 V Max 40 chars.
Min 3 chars.
This field is required if street-name is not entered.
Valid characters are Alpha, Numeric, Blanks,
Hyphen, Apostrophe, Slash and Back Slash.
Blank, Hyphen, Apostrophe, Slash and Back Slash
cannot be adjacent.
details.
2.2.4.1.4 unit-number Element 0-1 Unit or Flat Number 5 V Noise words such as ‘UNIT’, ‘FLAT’, ‘NO.’ etc.
should not be included in this field when supplied.
Max 5 chars.
Min 1 char.
Valid characters are Alpha, Numeric, Blanks,
Hyphen, Slash and Back Slash.
Blank, Hyphen, Slash and Back Slash cannot be
adjacent.
2.2.4.1.5 street-number Element 0-1 Street/House Number 8 V If the address legitimately does not have a street
number and Street Name has been input then
‘N/A’ must be input for Street Number to indicate
not applicable
If this field is entered, then there must also be a
street-name. Should start with a numeric value.
e.g.: ’56 Lot’
Max 8 chars.
Min 1 char.
Valid characters are Alpha, Numeric, Blank,
Hyphen, Slash and Back Slash.
Blanks, Hyphen, Slash and Back Slash cannot be
adjacent.
51
2.2.4.1.6 street-name Element 0-1 Street Name 40 V This field is required if property is not entered.
If this field is entered, then there must also be a
street-number.
Max 40 chars.
Min1 char.
Valid characters are Alpha, Numeric Blanks,
Hyphen, Apostrophe, Slash and Back Slash.
Blanks, Hyphen, Slash and Back Slash cannot be
adjacent.
details.
2.2.4.1.7 street-type Element 0-1 Street Type 4 V If this field is entered, then there must also be a
street-name.
Refer to 8.25 - Street Type code table for valid

values
2.2.4.1.8 suburb Element 1 Suburb or Town 50 V Max 50 chars.
Min 1 char.
Valid characters are Alpha, Blanks, Hyphens,
Apostrophe, Slash and Back Slash.
Blanks, Hyphens, Apostrophe, Slash and Back
Slash cannot be adjacent.
details.
2.2.4.1.9 state Element 1 State Code 3 V Refer to 8.24 - State code table for valid values.
For an overseas address use 'OS' as per State Code
table.
2.2.4.1.1 post-code Element 0-1 Post Code 4 F Postcode should be valid for State
0
Only numeric integers are allowed.
Must be a 4-digit number.
For overseas addresses post-code must not be

entered.
2.2.4.1.1 country-code Element 0-1 Country code of the country. Must conform 3 V Accepted country codes are ‘AUS’ and ‘NZL’ only.
1 to the ISO 3166 standard. Other country codes will not be captured and will
be ignored in the request.
52
For other overseas addresses, use 'OS' in the state
field.
2.2.4.1.1 dpid Element 0-1 Future use only 8 F
2
2.2.4.1.1 unformatted-addres Element 0-1 Free-form Address. 340 V An unformatted address must contain at least a
3 s street name or property name, suburb, state
Must contain a minimum set of Address code.
data elements to identify a valid unique Max 340 chars.
address. Min 10 chars.
If possible enclose the property name within
quotation marks. This will increase the chances of
the system decoding the address.
details.
2.2.5 drivers-licence Container 0-1 Contains information about the individual's Refer to Appendix A –Tips for Matching to
driver's licence. Individual Bureau Files
Refer to Appendix B –Tips for entering Driver
Licence Number
2.2.5.1 country-code Element 0-1 Future use only 3 V
2.2.5.2 number Element 1 Drivers Licence number 9 V Must be a valid Driver’s Licence number as issued
by the relevant State authority.
Max 9 chars.
Min 4 chars.
Refer to Appendix B –Tips for entering Driver

Licence Number
2.2.5.3 date-of-expiry Element 0-1 Future use only
2.2.5.4 card-number Element 0-1 Future use only 10 V
2.2.5.5 state Element 0-1 Future use only 3 V
2.2.6 gender-code Element 1 Gender code associated with the gender of 1 F Refer to 8.10 - Gender code table for valid values
individual. Refer to Appendix A –Tips for Matching to
2.2.7 date-of-birth Element 0-1 Date of birth of individual. 10 F YYYY-MM-DD format.
Individual must be at least 18 years before the
current date.
53
2.2.8 employment Container 0-1 Contains information about the individual's Refer to Appendix A –Tips for Matching to
employment. Individual Bureau Files
2.2.8 employer Container 1-M Contains information about the individual's Only one employer record can be submitted in the
employer. request; current employer record. Previous
employer is not currently supported.
2.2.8.1 @type Attribute 1 Employment type 1 F Refer to 8.9 Employment Type code table for valid
values
2.2.8.2 name Element 1 Name of Employer 100 V Minimum length of 2 chars.
Valid characters are Alphanumeric, Blanks, and
the following characters: @ # $ % & * ( ) - _ + = ! \
}{“‘?/.,:;
Blanks, hyphens, commas and semicolons cannot
be adjacent. Apostrophe cannot be the ending
value.
Note: For Self-employed individuals use ‘SELF
EMPLOYED’ or ‘SELF’.
details.
2.2.8.3 country-code Element 0-1 Future use only 3 V
2.2.8.4 ABN Element 0-1 Future use only 11 F
2.2.8.5 organisation-numbe Element 0-1 Future use only 9 F
r
2.2.8.6 occupation Element 0-1 Free-form occupation description. 22 V Max 22 chars.
Applicable only if the credit purpose is for Min 1 char.
individual Commercial Credit. Valid characters are Alpha, Numeric, Blanks,
Commas and Semicolons.
Blanks, commas and semicolons cannot be
adjacent.
Note: For Self-employed individuals leave this
field blank
details.
2.2.8.7 is-self-employed Element 0-1 Future use only 5 V
54
6.2.2.3 Enquiry
Schema location: request>enquiry-data>enquiry
Figure 7: Enquiry

Seq No XML Element Type O/ Description Le V/ Format and Validation Rules
C n F
2.3 enquiry Containe 0-1 Contains information about the credit enquiry.
r
2.3.1 permitted-disclosure Element 0-1 Future use only 1 F
2.3.2 account-type-code Element 0-1 Type of credit account 2 V Refer to 8.2 - Consumer Account Type
code tables for valid values.
Please note the exception to 'AO' in
the Consumer code table.
55
Please note this field remains
mandatory for all Credit Provider,
Telco, Utility, Alternative Lending and
Access Seeker enquiries.
2.3.3 enquiry-amount Element 0-1 Amount of credit applied for. 9 V Maximum length of 9 chars. Enter
whole dollars only, without a decimal
place or separators.
Telco, Utility, Alternative Lending and
Access Seeker enquiries.
2.3.3.1 @currency-code Attribute 0-1 Indicates the type of currency. Currency code must 3 F The only currency supported at this
conform to the ISO 4217 standard. stage is AUD.
Defaults to AUD if not supplied.
2.3.4 is-credit-review Element 0-1 Indicates whether the enquiry is in relation to a review 5 V Valid values are ‘true’ or ‘false’.
of an existing commercial account or a credit limit
increase. Note: This element is ignored if the
permission type is Consumer (X) or
If the enquiry is a Commercial or Consumer+Commercial (XY).
Commercial+Consumer enquiry, then the purpose of
the enquiry can be a credit review rather than a new
credit application. If this is the case submit a value of
‘true’ in this element.
This element is not applicable to Consumer or

Consumer+Commercial enquiries.
2.3.5 is-unlimited-credit Element 0-1 Future use only. 5 V
Note: This field is equivalent in meaning and use to the

ACRDS no-fixed-limit field.
2.3.6 secured-credit-code Element 0-1 Future use only. 1 F
2.3.7 relationship-code Element 0-1 Relationship code corresponding to the individual’s 1 F Refer to 8.18 - Relationship code table
association with the enquiry. for valid values
Telco, Utility and Access Seeker
enquiries.
56
2.3.8 co-borrower Element 0-1 Name of co-borrower if the individual is not a single 20 V
Max 20 chars.
borrower (in free-form text).
Applicable only if the credit purpose is individual Min 2 chars.
Commercial Credit.
Valid characters are Alphanumeric,
Blanks, and the following characters:
@#$%&*()-_+=!\}{“‘?/.,:;
Blanks, hyphens, commas and
semicolons cannot be adjacent.
Ampersand must be suffixed by Blank.
2.3.9 enquiry-client-reference Element 0-1 Client enquiry reference associated to this credit 15 V
Max 15 chars.
enquiry application such as a client number or account
number. This enquiry client reference is stored on the Min 1 char.
Equifax bureau and is returned to all subsequent
Valid characters are Alphanumeric,
enquirers on the individuals file.
Blanks, and the following characters:
@#$%&*()-_+=!\}{“‘?/,.:;
Must contain at least one numeric
character.
2.3.10 other-enquiry-attribute Containe 0-1 Future use only - -
s r
2.3.10.1 enquiry-attribute Element 1- Future use only
M
2.3.10.1. key Element 1 Future use only
1
2.3.10.1. value Element 1 Future use only
2
2.3.10.1. @unit Attribute 0-1 Future use only
3
57
6.2.3 Response Overview
The response returned to a new enquiry request depends on the transmission mode chosen (synchronous/asynchronous) as well as the system’s capacity to
fulfil the request within the service response window.
The system will return a response to the one described in 6.2.3.1 Ticket Response in the following scenarios:
● The request was submitted using the asynchronous operation
● The request was submitted using the synchronous operation but was not fulfilled within the service response window.
The system will return a response to the one described in 6.2.3.2 Report Response in all other cases, where no system errors occurred.
6.2.3.1 Ticket Response

Response includes:
● Product header information; contains the unique enquiry ID and a range of other report metadata. The data in this message component sets the
parameters that conditioned the report. This could be from the requested or configuration driven.
● General messages; relate to the response in general as opposed to a specific element or file. E.g. a statutory disclaimer to qualify circumstances
under which the report was generated.
● Errors; such errors are not system errors but report build errors. They are valid use case scenarios. The information returned in this message
component can help describe and locate the root of the report build error for investigation.
The following illustration depicts the general structure of the ticket response.
58
Figure 8: Ticket Response Overview
Seq No XML Element Type O/C Description
0 @response-type Attribute 0-1 Describes the nature of the response. For a ticket response, possible values are “ticket” or “error”.
1 product-header Container 0-1 Container for control information related to the response.
Child XML elements of this container element are defined under 6.2.3.1.1 Product-header
3 general-messages Container 0-1 Container for general messages related to the response. It does not relate to a specific element or file.
Child XML elements of this container element are defined under 6.2.3.1.2 General Messages
4 errors Container 0-1 Container for errors related to the response.
Child XML elements of this container element are defined under 6.2.3.1.3 Errors
59
6.2.3.1.1 Product-header
Schema location: ticket-response>product -header
response>product -header
Figure 9: Product-header
Seq No XML Element Type O/C Description Len V/F Format and
Validation Rules
1.1 enquiry-id Element 1 System generated unique ID related to this response 20 V
transaction. This ID can be used to retrieve this response at a
later time.
1.2 datetime-requested Element 1 Date and time of request. 29 F CCYY-MM-DDThh:m
m:ss.sss(+|-)hh:mm
60
1.3 datetime-generated Element 0-1 Date and time of response 29 F CCYY-MM-DDThh:m
m:ss.sss(+|-)hh:mm
1.4 client-reference Element 0-1 Client reference ID supplied in the request message. 64 V
1.5 operator-id Element 0-1 Operator (or system) identifier who submitted this request 20 V
transaction supplied in the request message.
1.6 operator-name Element 0-1 Operator name who submitted this request transaction 20 V
supplied in the request message.
1.7 product-name Element 1 Product Name. 50 V Defined by service
end-point and
If permission type is X (Consumer) or XY permission type.
(Consumer+Commercial), the product name will be .
VedaScore Apply®, unless Equifax One Score has been
requested, then it will show: “Equifax Apply One Score”
If permission type YX (Commercial + Consumer) or
Y(Commercial), the product name will be Commercial Credit
Assess - Individual.
1.8 permission-type Element 1 Permission Type. Defined by the permission-type code 40 V
supplied in the request message.
1.8.1 @code Attribute 0-1 Code associated with the permission type 2 F Refer to 8.15
Permission Type code
table for valid values
1.9 product-data-level Element 0-1 Indicates the product data level used to construct the report. 20 V
This value was selected from the request.
1.9.1 @code Attribute 0-1 Code associated with the product data level 1 F Refer to 8.6 Data
Level table for valid
values
1.10 product-version Element 0-1 Product Version. Defined by service end-point. 5 V
1.11 possible-matches Container 0-1 Future use only
1.11.1 maximum-matches Element 0-1 Future use only 2 V
1.11.2 match-criteria Container 0-1 Future use only
1.11.2.1 match-criterion Element 1- Future use only 2 V
M
1.12 custom-input-parameters Container 0-1 Future use only
1.12.1 custom-input-parameter Container 1- Future use only 20 V
M
1.12.1.1 key Element 1 Future use only 20 V
1.12.1.2 value Element 1 Future use only 20 V
61
1.12.1.2.1 @unit Attribute 0-1 Future use only 20 V
1.13 configuration-data-attributes Container 0-1 Contains client configuration as key and value pairs - Sourced
from configuration for that client.
1.13.1 configuration-data-attribute Container 1- Configuration parameter that has been applied to the
M requested product.
1.13.1.1 key Element 1 The key associated with the configuration parameter. 20 V
1.13.1.2 value Element 1 The value associated with the configuration parameter. 20 V
1.13.1.2.1 @unit Attribute 0-1 Unit of measurement associated with the value. 20 V
6.2.3.1.2 General-messages
Schema location: ticket-response>general-messages
response>general-messages
Figure 10: General-messages

Seq XML Element Type O/C Description Len V/F Format and
No Validation Rules
3 general-messages Container 0-1 Container for general messages related to the response. It does not relate to
a specific element or file.
3.1 message Element 1 This is an instance of a general message. 300 V
3.1.1 @code Attribute 1 Message code related to the message. 10 V
62
6.2.3.1.3 Errors
Schema location: ticket-response>errors
response>errors
Figure 11: Errors

4.1 error Container 1-M This is an instance of an error.
4.1.1 fault-code Element 0-1 Code identifying the error or condition. 10 V
4.1.2 fault-string Element 0-1 Human readable explanation of the error or condition 100 V
4.1.3 fault-actor Element 0-1 Information on the system responsible for the error or condition 30 V
4.1.4 detail Element 0-1 Application specific, detailed information on the error or condition 200 V
63
6.2.3.2 Report Response
Schema location: response>product-data
If the request enquiry was performed by Bureau Reference, the system will return the individual explicitly identified by this reference. Otherwise, if the
request was performed by searching by identity details, the system will find the best match to that information. See 7.1 Responses to matching of
identification data from the request (p. 111) for more information.
Possible matches may be returned if the information partially matches the request identity details.
If a File Ban is active on that individual’s records, then a file ban report is returned rather than an enquiry report.
Response includes:
● Product header information; contains the unique enquiry ID and a range of other report metadata. The data in this message component sets the
parameters that conditioned the report. This could be from the requested or configuration driven.
● Product data information
o File ban report; this is returned when the individual’s records are under a File Ban.
o Enquiry report
▪ Identity data and aliases; discloses the individual’s personal details from the primary match and alias identity files with FIR
● Consumer credit file; sourced from the individual Consumer database and contains credit enquiry data, account data
including default, repayment history data, financial hardship information and messages.
● Commercial credit file; sourced from the individual Commercial database and contains credit enquiry data, account data
including default and repayment history data, messages and file notes.
● Public record or Consumer credit information; sourced from public sources, contains court actions, directorships, business
names, insolvencies and messages. Notwithstanding the fact that this data is sourced from the Public domain, this
information is Consumer credit information under the Act when the credit purpose is for Consumer credit and should be
treated as such.
▪ Summary data; derived summary data about the individual’s credit file across the data across the individual Consumer, individual
Commercial (if applicable) and Public sources. This data can be used in the Decisioning process in addition to scores.
▪ Score data; depending on the request, multiple scores can be returned. All scores are accompanied by key contributing factors.
o Possible matches; can be returned if the information partially matches the request identity details. A search on the possible match identity
can be performed by a subsequent enquiry using the Bureau reference as input.
● General messages; relate to the response in general as opposed to a specific element or file. E.g. a statutory disclaimer to qualify circumstances
under which the report was generated.
64
● Errors; such errors are not system errors but report build errors. They are valid use case scenarios. The information returned in this message
component can help describe and locate the root of the report build error for investigation.
The following illustration depicts the general structure of the report response.
Figure 12: Report Response Overview

Seq XML Element Type O/C Description
No
65
0 @response-type Attribute 0-1 Describes the nature of the response. For a report response, possible values are “ticket”, “report”,
“file-ban” or “error”.
Child XML elements of this container element are defined under 6.2.3.1.1 Product-header.
2 product-data Container 0-1 Container for response information related to the enquiry.
2.1 enquiry-report Container 0-1 Contains information about the individual's personal information, credit and public data found in the
Equifax databases.
2.1.1 primary-match Container 1 Contains the individual's personal information from the primary match record.
Child XML elements of this container element are defined under 6.2.3.2.1-Primary-match.
2.1.2 other-identities Container 0-1 Contains the individual's personal information from any alias identity files. An individual may have
many aliases.
Child XML elements of this container element are defined under 6.2.3.2.2-Other-identities.
2.1.3 addresses Container 0-1 Contains information about the individual's addresses.
Child XML elements of this container element are defined under 6.2.3.2.3 Addresses.
2.1.4 employment Container 0-1 Contains information about the individual's employment.
Child XML elements of this container element are defined under 6.2.3.2.4-Employment
2.1.5 consumer-credit-file Container 0-1 Child XML elements of this container element are defined under 6.2.3.2.5-Consumer-credit-file
2.1.6 commercial-credit-file Container 0-1 Commercial data is included only if the permission type specified in the request includes commercial
data
Child XML elements of this container element are defined under 6.2.3.2.6 - Commercial-credit-file
2.1.7 public-record-or-consumer-c Container 0-1 In the context of a consumer enquiry, this section includes consumer credit information.
redit-information In the context of a commercial enquiry, this section includes public records.
Child XML elements of this container element are defined under 6.2.3.2.7 - Public-record or
consumer-credit-information
2.2 file-ban-report Container 0-1 Indicates whether the individual is under a Ban. If the individual is under a Ban then the
enquiry-report element will not be returned. Mutually exclusive. Ban Flags are a requirement under
the Privacy Act.
Child XML elements of this container element are defined under 6.2.3.6 -File-ban-report
2.3 summary-data Container 0-1 Contains summarised information about the individual's credit file data which are called
characteristics.
Child XML elements of this container element are defined under 6.2.3.3-Summary-data
2.4 score-data Container 0-1 Contains information about the individual's scores. The response may include multiple scores if
additional score cards were requested.
Child XML elements of this container element are defined under 6.2.3.4-Score-data
2.5 possible-matches Container 0-1 Contains personal information of possible match files to the individual. An individual may have many
possible matches.
Child XML elements of this container element are defined under 6.2.3.5-Possible-matches
3 general-messages Container 0-1 Container for general messages related to the response. It does not relate to a specific element or file.
66
Child XML elements of this container element are defined under 6.2.3.1.2 General Messages
Child XML elements of this container element are defined under 6.2.3.1.3 Errors
6.2.3.2.1 Primary-match
Schema location: response>product-data>enquiry-report>primary-match
Figure 13: Primary-match

Seq No XML Element Type O/C Description Len V/F Format and Validation
Rules
2.1.1 primary-match Container 1 Contains the individual's personal information from the primary
match record.
2.1.1.1 @id-index Attribute 0-1 An identifier appended to each known identity of the individual. 3 V
Information relating to the individual (credit enquiry, account,
67
bankruptcy…) can include a reference to this identity index
value to associate which identity the information was sourced
from. This feature is called Full Identity Reporting (FIR).
2.1.1.2 @type Attribute 0-1 For the primary match record, this value indicates if it is a 10 V
'strong' or 'create' match.
‘strong’ – the database finds a record in which the data closely

resembles the identification data in the request.
‘create’ – the database cannot find a record resembling the data

in the file. In this case, a new file is created.
For the possible match record, this value will return ‘possible’.
2.1.1.3 @is-disputed Attribute 0-1 Future use only 5 V
2.1.1.4 @dispute-reported-date Attribute 0-1 Future use only 10 F Format ccyy-mm-dd
2.1.1.5 @dispute-code Attribute 0-1 Future use only 1 V
2.1.1.6 bureau-reference Element 0-1 Bureau reference; this is a unique identifier for that individual. 10 V Bureau reference will
only be returned in the
case for a
primary-match record
and possible-matches
records.
Bureau reference is not

returned for
other-identities
2.1.1.7 individual-name Container 0-1 Contains information about the individual's name.
2.1.1.7.1 @first-reported-date Attribute 0-1 First reported date of name in the Bureau. 10 F Format ccyy-mm-dd
2.1.1.7.2 @last-reported-date Attribute 0-1 Last reported date of name in the Bureau. 10 F Format ccyy-mm-dd
(Not returned for
possible matches.)
2.1.1.7.3 @last-credit-enquiry-date Attribute 0-1 Last credit enquiry date submitted against this identity. 10 F Format ccyy-mm-dd
Depending on the credit purpose it will return the date of the (Not returned for
last consumer credit enquiry or the last commercial credit possible matches.)
enquiry.
2.1.1.7.5 family-name Element 0-1 Family Name. Also referred to as Surname 50 V
68
2.1.1.7.6 first-given-name Element 0-1 First Name 40 V
2.1.1.7.7 other-given-name Element 0- Other given name. Also referred to as middle name. 80 V
M
2.1.1.8 gender Element 0-1 Gender of individual 7 V
2.1.1.8.1 code Attribute 0-1 Code associated with the gender 1 F Refer to 8.10 - Gender
code table for valid
values
2.1.1.9 date-of-birth Element 0-1 Date of birth of individual 10 F Format ccyy-mm-dd
2.1.1.9.1 @first-reported-date Attribute 0-1 First reported date of DOB to Equifax 10 F Format ccyy-mm-dd
(Not returned for
possible matches.)
2.1.1.9.2 @last-reported-date Attribute 0-1 Last reported date of DOB to Equifax. 10 F Format ccyy-mm-dd
(Not returned for
possible matches.)
2.1.1.10 drivers-licence Container 0-1 Includes driver licence details
2.1.1.10.1 @first-reported-date Attribute 0-1 First reported date of Driver’s Licence number to Equifax. 10 F Format ccyy-mm-dd
(Not returned for
possible matches.)
2.1.1.10.2 @last-reported-date Attribute 0-1 Last reported date of Driver’s Licence number to Equifax. 10 F Format ccyy-mm-dd
(Not returned for
possible matches.)
2.1.1.10.3 country-code Element 0-1 Future use only 3 V
2.1.1.10.4 state Element 0-1 Future use only 3 V
2.1.1.10.5 number Element 0-1 Drivers Licence number 9 V
2.1.1.10.6 date-of-expiry Element 0-1 Future use only 10 F Format ccyy-mm-dd
2.1.1.10.7 card-number Element 0-1 Future use only 10 V
2.1.1.11 lodged-complaint Element 0-1 Indicates whether the individual has lodged a complaint about 5 V (Not returned for
Equifax acts or practices that may be a breach of the Amending possible matches.)
Act or Credit Reporting Code.
2.1.1.11.1 @reported-date Attribute 0-1 Reported date of the Complaint. 10 F Format ccyy-mm-dd
(Not returned for
possible matches.)
2.1.1.12 is-deceased Element 0-1 5 V (Not returned for
possible matches.)
2.1.1.12.1 @reported-date Attribute 0-1 Reported date of the deceased status 10 F Format ccyy-mm-dd
(Not returned for
possible matches.)
69
2.1.1.13 do-not-provide-credit Element 0-1 Future use only 5 V
2.1.1.13.1 @reported-date Attribute 0-1 Future use only 10 F Format ccyy-mm-dd
2.1.1.14 other-indicators Container 0-1 Future use only.
2.1.1.14.1 indicator Container 1- Future use only
M
2.1.1.14.1.1 @reported-date Attribute 0-1 Future use only 10 F Format ccyy-mm-dd
2.1.1.14.1.2 key Element 1 Future use only 20 V
2.1.1.14.1.3 value Element 1 Future use only 20 V
2.1.1.14.1.3. @unit Attribute 0-1 Future use only. 20 V
1
6.2.3.2.2 Other-identities
Schema location: response>product-data>enquiry-report>other-identities
Figure 14: Other-identities
70
Seq XML Element Type O/C Description Le V/F Format and
No n Validation Rules
2.1.2 other-identities Container 0-1 Contains the individual's personal information from any alias identity files. An
individual may have many aliases.
2.1.2.1 other-identity Container 1-50 Contains the individual's personal information an instance of an alias identity
record.
Child XML elements of this container element are defined under 6.2.3.2.1 -
Primary-match
71
6.2.3.2.3 Addresses
Schema location: response>product-data>enquiry-report>addresses
Figure 15: Addresses

2.1.3 addresses Container 0-1 Contains information about the individual's For a Consumer product only a
addresses. maximum of 3 addresses can be
returned.
2.1.3.1 address Container 1-M Contains information about an instance of the
individual's address.
72
2.1.3.1.1 @first-reported-date Attribute 0-1 First reported date of this address from this 10 F Format ccyy-mm-dd
individual to Equifax. Not applicable to possible matches.
2.1.3.1.2 @last-reported-date Attribute 0-1 Last reported date of this address from this 10 F Format ccyy-mm-dd
individual to Equifax. Not applicable to possible matches.
2.1.3.1.3 @is-disputed Attribute 0-1 Future use only 5 V
2.1.3.1.4 @dispute-reported-date Attribute 0-1 Future use only 10 F Format ccyy-mm-dd
2.1.3.1.5 @dispute-code Attribute 0-1 Future use only 1 V
2.1.3.1.6 @type Attribute 0-1 Address type. 1 F Refer to 8.1 - Address Type code table
for valid values
2.1.3.1.7 id-references Container 0-1 Contains a list of id-references
2.1.3.1.7. id-reference Element 1-M Reference to associate the source of this 3 V
1 information to the identity defined by identity
index.
2.1.3.1.8 property Element 0-1 Property Name 40 V
2.1.3.1.9 unit-number Element 0-1 Unit or Flat Number 5 V
2.1.3.1.10 street-number Element 0-1 Street/House Number 8 V
2.1.3.1.11 street-name Element 0-1 Street Name 40 V
2.1.3.1.12 street-type Element 0-1 Street Type 4 V Refer to 8.25 -Street Type code table
for valid values
2.1.3.1.13 suburb Element 0-1 Suburb or Town 50 V
2.1.3.1.14 state Element 0-1 State Code 3 V Refer to 8.24 - State code table for
valid values.
2.1.3.1.15 postcode Element 0-1 Post Code 4 F
2.1.3.1.16 dpid Element 0-1 Future use only 8 F
2.1.3.1.17 country-code Element 0-1 Country code of the country. Must conform to the 3 V
ISO 3166 standard.
73
6.2.3.2.4 Employment
Schema location: response>product-data>enquiry-report>employment
Figure 16: Employment

2.1.4 employment Container 0-1 Contains information about the individual's
employment.
2.1.4.1 employer Container 1-M
2.1.4.1.1 @first-reported-date Attribute 0-1 First reported date of this employment record from 10 F Format ccyy-mm-dd
this individual to Equifax. Not applicable to possible
matches.
2.1.4.1.2 @last-reported-date Attribute 0-1 Last reported date of this employment record from 10 F Format ccyy-mm-dd
this individual to Equifax. Not applicable to possible
matches.
2.1.4.1.3 @is-disputed Attribute 0-1 Future use only 5 V
2.1.4.1.4 @dispute-reported-d Attribute 0-1 Future use only 10 F Format ccyy-mm-dd
ate
74
2.1.4.1.5 @dispute-code Attribute 0-1 Future use only 1 V
2.1.4.1.6 @type Attribute 0-1 Employment type 1 F Refer to 8.9 - Employment Type
code table for valid values
2.1.4.1.7 id-references Container 0-1 Includes a list of id-references
2.1.4.1.7.1 id-reference Element 1-M Reference to associate the source of this information 3 V
to the identity defined by identity index.
2.1.4.1.8 name Element 0-1 Name of Employer V
100
0-1 3 V
2.1.4.1.9 country-code Element Future use only
2.1.4.1.10 ABN Element 0-1 Future use only 11 F
2.1.4.1.11 organisation-number Element 0-1 Future use only 9 F
2.1.4.1.12 occupation Element 0-1 Occupation description. 22 V
2.1.4.1.13 is-self-employed Element 0-1 Future use only 5 v
6.2.3.2.5 Consumer-credit-file
Schema location: response>product-data>enquiry-report>consumer-credit-file
Figure 17: consumer-credit-file overview

No
2.1.5 consumer-credit-fil Container 0-1 This section includes elements of consumer credit information.
e
2.1.5.1 file-notes Container 0-1 File notes are no longer a part of an individual’s consumer credit file and are not returned in the report.
2.1.5.2 credit-enquiries Container 0-1 Includes information about credit-enquiries (commercial only), credit applications (consumer only) and authorised
agent enquiries (commercial only).
Child XML elements of this container element are defined under 6.2.3.2.5.1 - Credit-enquiries
75
2.1.5.3 accounts Container 0-1 Includes information about the subject's accounts.
Child XML elements of this container element are defined under 6.2.3.2.5.2- Accounts
2.1.5.4 messages Container 0-1 Includes messages in relation to this section of the report.
Child XML elements of this container element are defined under 6.2.3.2.5.3- Messages
6.2.3.2.5.1 Credit-enquiries
Schema location: response>product-data>enquiry-report>consumer-credit-file>credit-enquiries
response>product-data>enquiry-report>commercial-credit-file>credit-enquiries
Figure 18: Credit-enquiries
76
2.1.5.2 credit-enquiries Container 0-1 Includes information about credit-enquiries
(commercial only), credit applications
(consumer only) and authorised agent
enquiries (commercial only)
2.1.5.2.1 credit-enquiry Container 1-5 Includes details of one enquiry
0
2.1.5.2.1.1 @is-disputed Attribute 0-1 Future use only 5 V
2.1.5.2.1.2 @dispute-reported-date Attribute 0-1 Future use only 10 F Format ccyy-mm-dd
2.1.5.2.1.3 @dispute-code Attribute 0-1 Future use only 1 V
2.1.5.2.1.4 @type Attribute 0-1 Type of enquiry: credit-enquiry (commercial 24 V Refer to 8.5 - Credit enquiry type
only), credit-review (commercial only), table for valid values
credit-application (consumer only) or
authorised-agent-enquiry (commercial only)
2.1.5.2.1.5 @enquiry-date Attribute 0-1 Date the credit enquiry was recorded 10 F Format ccyy-mm-dd
2.1.5.2.1.6 id-references Container 0-1 Includes a list of id-references
2.1.5.2.1.6.1 id-reference Element 1- Reference to associate the source of this 3 V
M information to the identity defined by
identity index.
2.1.5.2.1.7 account-type Element 0-1 Type of account (descriptor) 35 V Refer to 8.2 - Consumer Account
Type for credit applications
(consumer) and consumer
authorised agent enquiries
(commercial only).
2.1.5.2.1.7.1 @code Attribute 0-1 Type of account (code) 2 V

2.1.5.2.1.8 enquiry-amount Element 0-1 Enquiry amount 9 V Not applicable if credit has no fixed
limit.
2.1.5.2.1.8.1 @currency-code Attribute 0-1 Currency code 3 F The only currency supported at this
stage is AUD
2.1.5.2.1.9 is-unlimited-credit Element 0-1 Future use only 5 V
Note: This field is equivalent in meaning and

use to the ACRDS no-fixed-limit field.
2.1.5.2.1.10 secured-credit Element 0-1 Future use only 40 V
2.1.5.2.1.10.1 @code Attribute 0-1 Future use only 1 F
77
2.1.5.2.1.11 relationship Element 0-1 Indicates whether the subject was a single 30 V
borrower or a guarantor. Replaces the field
"role" in VedaScore 1.1.
2.1.5.2.1.11.1 @code Attribute 0-1 Type of relationship (code) 1 F Refer to 8.18 - Relationship code
2.1.5.2.1.12 co-borrower Element 0-1 Name of the co-borrower if the subject was 40 V Not included for consumer enquiries.
part of an association. Not applicable to commercial
enquiries if relationship is Principal
2.1.5.2.1.13 credit-enquirer Container 0-1 Includes details about who recorded the
enquiry
2.1.5.2.1.13.1 name Element 0-1 Credit enquirer name 28 V
2.1.5.2.1.13.2 classification Element 0-1 Credit enquirer’s industry type code 50 V Refer to 8.27 - Industry Classification
code table for list of codes and
description
2.1.5.2.1.14 enquiry-client-reference Element 0-1 The reference provided by the credit enquirer 15 V
2.1.5.2.1.15 additional-data-fields Container 0-1 Contains additional data fields. Will be used
in the future to report additional
information.
2.1.5.2.1.15.1 data-field Container 1- Future use only V
M
2.1.5.2.1.15.1.1 key Element 1 Future use only 20 V
2.1.5.2.1.15.1.2 value Element 1 Future use only 20 V
2.1.5.2.1.15.1.2. @unit Attribute 0-1 Future use only 20 V
1
78
6.2.3.2.5.2 Accounts
Schema location: response>product-data>enquiry-report>consumer-credit-file>accounts
response>product-data>enquiry-report>commercial-credit-file>accounts
Figure 19: Accounts
79
2.1.5.3 accounts Container 0-1 Includes information about the
subject's accounts.
2.1.5.3.1 account Container 1-10 Contains information about an instance
0 of the individual's accounts
2.1.5.3.1.4 @latest-update-date Attribute 0-1 Date the account was last updated 10 F Format ccyy-mm-dd
2.1.5.3.1.5 @account-data-level Attribute 0-1 Indicates the maximum data level that 1 F Refer to 3.2.2 - Account data level
can be returned for this account. for more details and valid values
2.1.5.3.1.6.1 id-reference Element 1-M Reference to associate the source of 3 V
this information to the identity defined
by identity index.
2.1.5.3.1.7 account-id Element 0-1 Account identifier 45 V
2.1.5.3.1.8 original-credit-provider Container 0-1 Includes details about the original
credit provider
2.1.5.3.1.8.1 name Element 0-1 Original credit provider name 28 V
2.1.5.3.1.8.2 classification Element 0-1 Original credit provider’s industry type 50 V Refer to 8.27 - Industry
code Classification code table for list
of codes and description
2.1.5.3.1.8.3 is-licensee Element 0-1 Indicates whether the original credit 5 V Boolean (true/false)
provider is a licensee
2.1.5.3.1.9 latest-credit-provider Container 0-1 Includes details about the latest credit
provider
2.1.5.3.1.9.1 name Element 0-1 Latest credit provider name 28 V
2.1.5.3.1.9.2 classification Element 0-1 Latest credit provider ‘s industry type 50 V Refer to 8.27 - Industry
code Classification code table for list
of codes and description
2.1.5.3.1.9.3 is-licensee Element 0-1 Indicates whether the original credit 5 V
provider is a licensee
2.1.5.3.1.9.4 transfer-date Element 0-1 Date Account ownership was 10 F Format ccyy-mm-dd
transferred. Start of effective ownership
of account.
80
2.1.5.3.1.9.5 transfer-reason Element 0-1 Reason Account ownership was 50 V
transferred.
2.1.5.3.1.9.5.1 @code Attribute 0-1 Reason code for Account ownership 1 F Refer to 8.28 Transfer Reason
transfer code table for valid values.
2.1.5.3.1.10 account-type Element 0-1 Type of account (descriptor) 35 V

2.1.5.3.1.10.1 @code Attribute 0-1 Type of account (code) 2 V Refer to 8.2 - Consumer Account
Type for consumer accounts.
2.1.5.3.1.11 relationship Element 0-1 The relation of the individual to the 30 V

account
2.1.5.3.1.11.1 @code Attribute 0-1 Relationship (code) 1 F Refer to 8.18 - Relationship code
2.1.5.3.1.12 account-holder-count Element 0-1 The number of account holders 2 V
recorded for the account.
2.1.5.3.1.13 account-open-date Element 0-1 Date that the credit was unconditionally 10 F Format ccyy-mm-dd
approved and the account has been
generated by the CP within its credit
management system.
2.1.5.3.1.14 account-closed-date Element 0-1 Date credit was last terminated or 10 F Format ccyy-mm-dd
otherwise ceased to be in force when
the credit was no longer available to
the individual.
2.1.5.3.1.15 account-reopen-date Element 0-1 Date account was last reopened after 10 F Format ccyy-mm-dd
being terminated.
If reopen date is later than closed date,
the account is currently active.
If closed date is later than reopen date,
the account was closed again after
being reopened.
2.1.5.3.1.15 loan-payment-method Element 0-1 Type of loan repayment arrangement 60 V
2.1.5.3.1.16.1 @code Attribute 0-1 Code used for the loan payment 1 F Refer to 8.11.4 KCF for Telco,
method Utility and Alternate Lending
2.1.5.3.1.17 term-type Element 0-1 Term arrangement type for the account 40 V
2.1.5.3.1.17.1 @code Attribute 0-1 Code used for term type 1 F Refer to 8.26 - Term type code
81
2.1.5.3.1.18 secured-credit Element 0-1 Indicates whether a secured or 40 V
unsecured line of credit
2.1.5.3.1.18.1 @code Attribute 0-1 Code used for secured credit 1 F Refer to 8.23 - Secured Credit
2.1.5.3.1.19 term-of-loan Element 0-1 The time period of the original 3 V Format NNN
contracted term of the loan Must be between 001 and 999 or
else ‘XXX’ if Ongoing or
Unspecified
Default in Months subject to
optional value supplied in
term-unit-type-value
2.1.5.3.1.23.1.2
2.1.5.3.1.20 original-maximum-amount-cre Element 0-1 Original maximum amount of credit 9 V Positive, whole-dollar value
dit available as first reported to Equifax. Minimum value $0
Important Note: With the release of Maximum value $999,999,999
the Credit Reporting Code in Not applicable to Telco’s or
September 2022, the Office of the Utilities.
Australian Information Commissioner Not applicable if maximum
(OAIC) has determined that current amount of credit available has no
Consumer Credit Liability Information fixed limit. e.g. certain Charge
(CCLI) only should be disclosed to Cards
ensure consistency across Credit Note: This field will no longer be
Reporting Bodies. Hence, Original returned
Maximum Amount of Credit Available
field will no longer be returned.
2.1.5.3.1.20.1 @currency-code Attribute 0-1 Currency code 3 F The only currency supported at
this stage is AUD
2.1.5.3.1.21 latest-maximum-amount-credi Element 0-1 Latest maximum amount of credit 9 V Positive, whole-dollar value
t available reported to Equifax Minimum value $0
Maximum value $999,999,999
Not applicable to Telco’s or
Utilities.
Not applicable if maximum
amount of credit available has no
fixed limit. e.g. certain Charge
Cards
this stage is AUD
82
2.1.5.3.1.21.2 date-last-changed 0-1 The date a change in the maximum 10 F Format ccyy-mm-dd
Attribute amount of credit was last reported to
Equifax. Included in the response only if
a change in credit limit was recorded.
2.1.5.3.1.22 is-unlimited-credit Element 0-1 Indicates whether credit amount 5 V
available is unlimited.
Note: This field is equivalent in meaning
and use to the ACRDS no-fixed-limit
field.
2.1.5.3.1.23 additional-data-fields Container 0-1 Contains additional data fields.
2.1.5.3.1.23.1 data-field Container 1-M Contains a key/value pair for a custom
parameter.
2.1.5.3.1.23.1.1 key Element 1 The custom input parameter key. 20 V term-unit-type will be returned
here when an account has an
associated optional unit of time
field. See 3.11 CCR Term of Loan
2.1.5.3.1.23.1.2 value Element 1 The custom input parameter value. 20 V The term unit type will be
returned here. Refer to 8.29 Term
of Loan Unit Type code table for
valid values.
The term-of-loan value (e.g. 60)
will be returned in term-of-loan
see 2.1.5.3.1.19
2.1.5.3.1.23.1.2.1 @unit Attribute 0-1 Future use only 20 V
2.1.5.3.1.24 association-information Container 0-1 Includes account association data Child XML elements of this
specific to the subject of the enquiry container element are defined
under 6.2.3.2.5.2.1 -
Association-information.
2.1.5.3.1.25 repayment-history Container 0-1 Includes repayment history information Child XML elements of this
for this account. container element are defined
under 6.2.3.2.5.2.2 -
Repayment-history .
2.1.5.3.1.26 defaults Container 0-1 Includes default information for this Child XML elements of this
account. container element are defined
under 6.2.3.2.5.2.3 -Defaults.
2.1.5.3.1.27 account-history Container 0-1 Includes historical information for this Child XML elements of this
account. container element are defined
83
under 6.2.3.2.5.2.4 -
Account-history
84
6.2.3.2.5.2.1 Association-information
Schema location: response>product-data>enquiry-report>consumer-credit-file> accounts>account >association-information
Figure 20: association-information

Validation
Rules
2.1.5.3.1.24 association-information Container 0-1 Includes account association data specific to the
subject of the enquiry
2.1.5.3.1.24.1 @is-disputed Attribute 0-1 Future use only 5 V
2.1.5.3.1.24.2 @dispute-reported-date Attribute 0-1 Future use only 10 F Format
ccyy-mm-dd
2.1.5.3.1.24.3 @dispute-code Attribute 0-1 Future use only 1 V
2.1.5.3.1.24.4 latest-start-date Element 0-1 Date account holder commenced his last 10 F Format
involvement with account ccyy-mm-dd
2.1.5.3.1.24.5 latest-ceased-date Element 0-1 Date account holder last ceased involvement with 10 F Format
account ccyy-mm-dd
2.1.5.3.1.24.6 is-serious-credit-infringement Element 0-1 Indicates that the subject of the enquiry has 5 V True/False
committed a serious credit infringement
2.1.5.3.1.24.7 sci-date Element 0-1 Date serious credit infringement was determined 10 F Format
ccyy-mm-dd
85
2.1.5.3.1.24.8 default-association-start-date Element 0-1 Date account holder started association with the 10 F Format
default state of the account ccyy-mm-dd
2.1.5.3.1.24.9 default-association-cease-date Element 0-1 Date account holder ceased association with the 10 F Format
default state of the account ccyy-mm-dd
2.1.5.3.1.24.10 additional-data-fields Container 0-1 Contains additional data fields. Will be used in the
future to report additional information.
2.1.5.3.1.24.10.1 data-field Container 1-M Future use only
2.1.5.3.1.24.10.1.1 key Element 1 Future use only 20 V
2.1.5.3.1.24.10.1.2 value Element 1 Future use only 20 V
2.1.5.3.1.24.10.1.2.1 @unit Attribute 0-1 Future use only 20 V
6.2.3.2.5.2.2 Repayment-history
Schema location: response>product-data>enquiry-report>consumer-credit-file> accounts>account >repayment-history
Figure 21: repayment-history

86
2.1.5.3.1.25 repayment-history Container 0-1 Includes repayment history and financial
hardship information for this account.
2.1.5.3.1.25.1 payment Container 1-M Includes repayment history and financial
hardship information for one repayment
period
2.1.5.3.1.25.1.1 @is-disputed Attribute 0-1 Future use only 5 V
2.1.5.3.1.25.1.2 @dispute-reported-date Attribute 0-1 Future use only 10 F Format ccyy-mm-dd
2.1.5.3.1.25.1.3 @dispute-code Attribute 0-1 Future use only 1 V
2.1.5.3.1.25.1.4 period Element 0-1 Repayment and financial hardship 7 F Format ccyy-mm
period year and month
2.1.5.3.1.25.1.5 status Element 0-1 The repayment history status of the 1 F Refer to 8.19 - Repayment History
account for the specified monthly period Status for valid values.
2.1.5.3.1.25.1.6 balance Element 0-1 Future use only 9 V
2.1.5.3.1.25.1.6.1 @currency-code Attribute 0-2 Future use only 3 F The only currency supported at
this stage is AUD
2.1.5.3.1.25.1.7 utilisation Element 0-1 Future use only 5 V
2.1.5.3.1.25.1.8 additional-data-fields Container 0-1 Contains additional data fields.
2.1.5.3.1.25.1.8.1 data-field Container 1-M Contains a key/value pair for a custom
parameter
2.1.5.3.1.25.1.8.1.1 key Element 1 fin-hardship-ind will be returned here 20 V
when the payment period has an
associated financial hardship indicator.
2.1.5.3.1.25.1.8.1.2 value Element 1 The type of financial hardship indicator 20 V Refer to 8.21 Financial Hardship
will be returned here. Information for valid values.
2.1.5.3.1.25.1.8.1.2.1 @unit Attribute 0-1 Future use only 20 V
87
6.2.3.2.5.2.3 Defaults
Schema location: response>product-data>enquiry-report>consumer-credit-file> accounts>account >defaults
response>product-data>enquiry-report>commercial-credit-file> accounts>account >defaults
Figure 22: defaults

2.1.5.3.1.26 defaults Container 0-1 Includes default information for this
account
88
2.1.5.3.1.26.1 default Container 1-M Includes information for one default
2.1.5.3.1.26.1.2 @dispute-reported-d Attribute 0-1 Future use only 10 F Format ccyy-mm-dd
ate
2.1.5.3.1.26.1.4 status Element 0-1 The payment status of the debt 25 V Refer to 8.7 - Default Status code table
for valid values
2.1.5.3.1.26.1.4.1 @code Attribute 0-1 Code used for default status 1 F
2.1.5.3.1.26.1.5 status-date Element 0-1 Date of last status update on default 10 F Format ccyy-mm-dd
2.1.5.3.1.26.1.6 is-accelerated-debt Element 0-1 Future use only 5 V Set to true if present.
2.1.5.3.1.26.1.7 original-default Container 0-1 Includes default information as
originally reported
2.1.5.3.1.26.1.7.1 date-recorded Element 0-1 Date the account was originally 10 F Format ccyy-mm-dd
reported as in default.
2.1.5.3.1.26.1.7.2 default-amount Element 0-1 Original default amount 9 V
2.1.5.3.1.26.1.7.2.1 @currency-code Attribute 0-1 Currency code 3 F The only currency supported at this
stage is AUD
2.1.5.3.1.26.1.7.3 reason-to-report Element 0-1 For commercial defaults only. 70 V Refer to 8.7 - Default Reason to Report
Reason the default was originally (commercial defaults only) code table
reported. for valid values
2.1.5.3.1.26.1.7.3.1 @code Attribute 0-1 For commercial defaults only. 2 V
Code used for reason to report
2.1.5.3.1.26.1.8 current-default Container 0-1 Includes current default information
2.1.5.3.1.26.1.8.1 date-recorded Element 0-1 Date the default information was last 10 F Format ccyy-mm-dd
updated.
2.1.5.3.1.26.1.8.2 default-amount Element 0-1 Current default amount 9 V
2.1.5.3.1.26.1.8.2.1 @currency-code Attribute 0-1 Currency code 3 F The only currency supported at this
stage is AUD
2.1.5.3.1.26.1.8.3 reason-to-report Element 0-1 For commercial defaults only. 70 V Refer to 8.7 - Default Reason to Report
Reason the default was last reported. (commercial defaults only) code table
for valid values
2.1.5.3.1.26.1.8.3.1 @code Attribute 0-1 Code used for reason to report 2 V
2.1.5.3.1.26.1.9 additional-data-fields Container 0-1 Contains additional data fields.
2.1.5.3.1.26.1.9.1 data-field Container 1-M Contains a key/value pair for a custom
parameter
89
2.1.5.3.1.26.1.9.1.1 key Element 1 new-arrangement-flag will be returned 20 V
here when a new arrangement applies
to the default
2.1.5.3.1.26.1.9.1.2 value Element 1 The type of new arrangement will be 20 V Refer to 8.9 Default New Arrangement
returned here. code table for valid values.
2.1.5.3.1.26.1.9.1.2.1 @unit Attribute 0-1 Future use only 20 V
6.2.3.2.5.2.4 Account-history
Schema location: response>product-data>enquiry-report>consumer-credit-file>accounts>account>account-history
Figure 23: account-history

2.1.5.3.1.27 account-history Container 0-1 Future use only
2.1.5.3.1.27.1 event Container 1-M Future use only
2.1.5.3.1.27.1.2 @dispute-reported-date Attribute 0-1 Future use only 10 F Format ccyy-mm-dd
2.1.5.3.1.27.1.4 @event-date Attribute 0-1 Future use only 10 F Format ccyy-mm-dd
2.1.5.3.1.27.1.5 @event-code Attribute 0-1 Future use only 10 V?
2.1.5.3.1.27.1.6 event-description Element 0-1 Future use only 50 V
2.1.5.3.1.27.1.7 event-details Container 0-1 Future use only
2.1.5.3.1.27.1.7.1 property Container 1-M Future use only
90
2.1.5.3.1.27.1.7.1.1 @unit Attribute 0-1 Future use only 20 V
2.1.5.3.1.27.1.7.1.2 name Element 0-1 Future use only 30 V
2.1.5.3.1.27.1.7.1.3 prior-value Element 0-1 Future use only 40 V
2.1.5.3.1.27.1.7.1.3.1 @code Attribute 0-1 Future use only 4 V
2.1.5.3.1.27.1.7.1.4 updated-value Element 0-1 Future use only 40 V
2.1.5.3.1.27.1.7.1.4.1 @code Attribute 0-1 Future use only 4 V
6.2.3.2.5.3 Messages
Schema location: response>product-data>enquiry-report>consumer-credit-file> messages
response>product-data>enquiry-report>commercial-credit-file> messages
response>product-data>enquiry-report>public-record-or-consumer-credit-information > messages
Figure 24 - messages
2.1.5.4 messages Container 0-1 Includes messages in relation to this section the report
2.1.5.4.1 message Element 1-9 Message (renamed, was file-message in VedaScore 1.1) 20 V
9 0
2.1.5.4.1.1 @code Attribute 0-1 The code assigned to this product message 10 V
6.2.3.2.6 Commercial-credit-file
Schema location: response>product-data>enquiry-report>commercial-credit-file
91
Figure 25 - commercial-credit-file overview
No
2.1.6 commercial-credi Container 0-1 Commercial data is included only if the permission type specified in the request includes commercial data
t-file
2.1.6.1 file-notes Container 0-1 Contains notes appended to the individual's credit file. Notes can include important information and it is highly
recommended to implement the capability to read and display these.
Child XML elements of this container element are defined under 6.2.3.2.6.1-File-notes.
2.1.6.2 credit-enquiries Container 0-1 Includes information about credit-enquiries (commercial only), credit applications (consumer only) and authorised
agent enquiries (commercial only).
Child XML elements of this container element are defined under 6.2.3.2.5.1 - Credit-enquiries.
2.1.6.3 accounts Container 0-1 Includes information about the subject's accounts.
Child XML elements of this container element are defined under 6.2.3.2.5.2-Accounts.
2.1.6.4 messages Container 0-1 Includes messages in relation to this section the report.
Child XML elements of this container element are defined under 6.2.3.2.5.3- Messages.
6.2.3.2.6.1 File-notes
Schema location:
response>product-data>enquiry-report>commercial-credit-file>file-notes
92
Figure 26: File-notes
Validation Rules
2.1.5.1 file-notes Container 0-1 Contains notes appended to the individual's credit file. Notes can include
important information and it is highly recommended to implement the
capability to read and display these.
2.1.5.1.1 file-note Container 1-15 File note
2.1.5.1.1.1 @code Attribute 0-1 Future use only 10 V
2.1.5.1.1.2 @date-recorded Attribute 0-1 Date the file note was recorded 10 F Format
ccyy-mm-dd
2.1.5.1.1.3. id-reference Element 1-M Reference to associate the source of this information to the identity defined 3 V
1 by identity index.
2.1.5.1.1.4 note Element 0-1 The file note content 63 V
6.2.3.2.7 Public-record or consumer-credit-information

Schema location: response>product-data>enquiry-report>public-record-or-consumer-credit-information
93
Figure 27: public-record-or-consumer-credit-information
No
2.1.7 public-record-or-consumer-c Container 0-1 In the context of a consumer enquiry, this section includes consumer credit information.
redit-information In the context of a commercial enquiry, this section includes public records.
2.1.7.1 court-actions Container 0-1 Includes information about default judgements, writs, summonses and claims.
Child XML elements of this container element are defined under 6.2.3.2.7.1 Court Actions.
2.1.7.2 disqualified-directorships Container 0-1 Includes periods for which the subject has been disqualified by the ASIC from holding executive office.
Child XML elements of this container element are defined under 6.2.3.2.7.2-Disqualified-directorships.
2.1.7.3 directorships Container 0-1 Includes current and previous directorships held by the subject.
Child XML elements of this container element are defined under 6.2.3.2.7.3-Directorships.
2.1.7.4 business-names Container 0-1 Includes the list of business names held by the subject.
Child XML elements of this container element are defined under 6.2.3.2.7.4-Business-names.
2.1.7.5 personal-insolvencies Container 0-1 Includes information about personal insolvencies.
Child XML elements of this container element are defined 6.2.3.2.7.5 Personal-insolvencies.
2.1.7.6 sole-trader Container 0-1 Future use only
Child XML elements of this container element are defined under 6.2.3.2.7.6-Sole-trader (p.).
2.1.7.7 messages Container 0-1 Includes messages in relation to this section of the report.
Child XML elements of this container element are defined under 6.2.3.2.5.3- Messages.
94
6.2.3.2.7.1 Court-actions
Schema location: response>product-data>enquiry-report>public-record-or-consumer-credit-information>court-actions
Note: Due to changes to the Privacy (Credit Reporting) Code 2014 that came into effect on 14 February 2020, Writs and Summons data is no longer
considered publicly available information and will no longer be collected for disclosure in consumer credit reports.
Figure 28: court-actions
95
2.1.7.1 court-actions Containe 0-1 Includes information about default judgements
r and other court actions (such as writs and
summons).
2.1.7.1.1 court-action Containe 1-2 Includes details of one court action
r 0
2.1.7.1.1.2 @dispute-reported-dat Attribute 0-1 Future use only 10 F Format ccyy-mm-dd
e
2.1.7.1.1.4 @type Attribute 0-1 The type of court action: default-judgement or 20 V
other-court-action (such as writs and summons).
2.1.7.1.1.5 id-references Containe 0-1 Includes a list of id-references
r
2.1.7.1.1.5.1 id-reference Element 1-M Reference to associate the source of this 3 V
information to the identity defined by identity
index.
2.1.7.1.1.6 action-date Element 0-1 The date when a court judgement was signed or a 10 F Format ccyy-mm-dd
writ, summons or claim was issued
2.1.7.1.1.7 creditor Element 0-1 Name of the creditor 40 V
2.1.7.1.1.8 court-action-amount Element 0-1 Dollar amount of Court Action 9 V
this stage is AUD
2.1.7.1.1.9 plaint-number Element 0-1 Identification of the action as supplied by the 40 V
court
2.1.7.1.1.10 court-type Element 0-1 Type of court in which the action took place 30 V
2.1.7.1.1.11 relationship Element 0-1 Indicates whether the subject was a single 30 V
borrower or part of an association
2.1.7.1.1.11.1 @code Attribute 0-1 Type of relationship (code) 1 F Refer to 8.18 - Relationship code
2.1.7.1.1.12 co-borrower Element 0-1 Name of the co-borrower if the subject was part 40 V
of an association
2.1.7.1.1.13 court-action-status Element 0-1 Current status of the court action 30 V
2.1.7.1.1.13.1 @date Attribute 0-1 Status date 10 F Format ccyy-mm-dd
2.1.7.1.1.13.2 @code Attribute 0-1 Status code 1 F Refer to 8.4 - Court action status
96
2.1.7.1.1.14 additional-data-fields Containe 0-1 Contains additional data fields. Will be used in the
r future to report additional information.
2.1.7.1.1.14.1 data-field Containe 1-M Future use only
r
2.1.7.1.1.14.1.2. @unit Attribute 0-1 Future use only 20 V
1
6.2.3.2.7.2 Disqualified-directorships
Schema location: response>product-data>enquiry-report>public-record-or-consumer-credit-information>disqualified-directorships
Figure 29: disqualified-directorships

Validation Rules
2.1.7.2 disqualified-directorships Container 0-1 Includes periods for which the subject has been
disqualified by the ASIC from holding executive office
2.1.7.2.1 disqualified-directorship Container 1-50 Includes details of one disqualification period
97
2.1.7.2.1.4 @last-extract-date Attribute 0-1 Date of when the disqualified directorship details were 10 F Format ccyy-mm-dd
last extracted from ASIC.
2.1.7.2.1.5 @last-extract-time Attribute 0-1 Time of when the disqualified directorship details were 20 V Format
last extracted from ASIC. hh:mm:ss.sss(+|-)hh:
mm
2.1.7.2.1.6 @last-update-date Attribute 0-1 Date of when the disqualified directorship details were 10 F Format ccyy-mm-dd
last updated from ASIC.
As opposed to an extract, an update might only refresh a
subset of the data.
2.1.7.2.1.7 @last-update-time Attribute 0-1 Time of when the disqualified directorship details were 20 V Format
last updated from ASIC. hh:mm:ss.sss(+|-)hh:
mm
2.1.7.2.1.8.1 id-reference Element 1-M Reference to associate the source of this information to 3 V
the identity defined by identity index.
2.1.7.2.1.9 date-disqualified Element 0-1 Date of disqualification 10 F Format ccyy-mm-dd
2.1.7.2.1.10 date-disqualified-until Element 0-1 Date disqualification will be lifted 10 F Format ccyy-mm-dd
2.1.7.2.1.11 additional-data-fields Container 0-1 Contains additional data fields. Will be used in the future
to report additional information.
2.1.7.2.1.11.1 data-field Container 1-M Future use only
6.2.3.2.7.3 Directorships
Schema location: response>product-data>enquiry-report>public-record-or-consumer-credit-information>directorships
98
Figure 30: directorships
2.1.7.3 directorships Container 0-1 Includes current and previous
directorships held by the subject
2.1.7.3.1 directorship Container 1-100 Includes details of one current or
previous directorship
2.1.7.3.1.4 @type Attribute 0-1 Determines whether the directorship 1 F
is current (C) or previous (P)
2.1.7.3.1.5 @last-extract-date Attribute 0-1 Date of when the directorship details 10 F Format ccyy-mm-dd
were last extracted from ASIC.
2.1.7.3.1.6 @last-extract-time Attribute 0-1 Time of when the directorship details 20 V Format hh:mm:ss.sss(+|-)hh:mm
2.1.7.3.1.7 @last-update-date Attribute 0-1 Date of when the directorship details 10 F Format ccyy-mm-dd
were last updated from ASIC.
99
As opposed to an extract, an update
might only refresh a subset of the
data.
2.1.7.3.1.8 @last-update-time Attribute 0-1 Time of when the directorship details 20 V Format hh:mm:ss.sss(+|-)hh:mm
2.1.7.2.1.9.1 id-reference Element 1-M Reference to associate the source of 3 V
this information to the identity
defined by identity index.
2.1.7.3.1.10 date-appointed Element 0-1 Date when the subject was 10 F Format ccyy-mm-dd
appointed director of the
organisation
2.1.7.3.1.11 date-ceased Element 0-1 Date when the subject ceased to be 10 F Format ccyy-mm-dd
a director of the organisation
2.1.7.3.1.12 date-last-known-as-director Element 0-1 Date when the subject was last 10 F Format ccyy-mm-dd
recorded as a director
2.1.7.3.1.13 organisation Container 0-1 Includes the organisation details
2.1.7.3.1.13.1 bureau-reference Element 0-1 Equifax internal unique reference for 10 V
this organisation
2.1.7.3.1.13.2 name Element 0-1 Name of the organisation 200 V
2.1.7.3.1.13.3 name-start-date Element 0-1 Date the name was registered or 10 F Format ccyy-mm-dd
reserved with ASIC
2.1.7.3.1.13.4 type Element 0-1 Type of organisation 30 V
2.1.7.3.1.13.4.1 @code Attribute 0-1 Associated code 3 F Refer to 8.14 - Organisation Type
2.1.7.3.1.13.5 status Element 0-1 Status of the organisation (returned 60 V
only when @type = current (C))
2.1.7.3.1.13.5.1 @code Attribute 0-1 Associated code 4 V Refer to 8.13 - Organisation Status
2.1.7.3.1.13.6 organisation-number Element 0-1 The organisation number. 9 F
2.1.7.3.1.13.7 ABN Element 0-1 The organisation's Australian 11 F
Business Number
2.1.7.3.1.14 additional-data-fields Container 0-1 Contains additional data fields. Will
be used in the future to report
additional information.
100
2.1.7.3.1.15 organisation-summary Container 0-1 Contains a trading history summary This section is only returned for a
of the organisation the individual directorship or previous directorship
is/was a director of. if the trading history variant was
requested.
2.1.7.3.1.15.1 enquiries Element 1 The number of enquiries found for 2 V Returns a maximum count of 50.
the organisation.
2.1.7.3.1.15.2 payment-defaults Element 1 The number of payment defaults 2 V Returns a maximum count of 25.
found for the organisation.
2.1.7.3.1.15.3 Mercantile Element 1 The number of mercantile enquiries 2 V Returns a maximum count of 10.
2.1.7.3.1.15.4 court-writs Element 1 The number of court writs found for 2 V Returns a maximum count of 10.
the organisation.
2.1.7.3.1.15.5 court-actions Element 1 The number of court actions found 2 V Returns a maximum count of 10.
for the organisation.
2.1.7.3.1.15.6 current-directors Element 1 The number of current directors 2 V Returns a maximum count of 50.
2.1.7.3.1.15.7 previous-directors Element 1 The number of previous directors 2 V Returns a maximum count of 50.
2.1.7.3.1.15.8 proprietorships Element 1 The number of proprietorships found 2 V Returns a maximum count of 50.
for the organisation.
6.2.3.2.7.4 Business-names
Schema location: response>product-data>enquiry-report>public-record-or-consumer-credit-information>business-names
101
Figure 31: business-names
2.1.7.4 business-names Container 0-1 Includes the list of business names held
by the subject
2.1.7.4.1 business-name Container 1-50 Includes details about one business
name held by the subject (previously
referred to as proprietorship)
2.1.7.4.1.4 @last-extract-date Attribute 0-1 Date of when the business name details 10 F Format ccyy-mm-dd
2.1.7.4.1.5 @last-extract-time Attribute 0-1 Time of when the business name details 20 V Format
were last extracted from ASIC. hh:mm:ss.sss(+|-)hh:mm
2.1.7.4.1.6 @last-update-date Attribute 0-1 Date of when the business name details 10 F Format ccyy-mm-dd
As opposed to an extract, an update
might only refresh a subset of the data.
102
2.1.7.4.1.7 @last-update-time Attribute 0-1 Time of when the business name details 20 V Format
were last updated from ASIC. hh:mm:ss.sss(+|-)hh:mm
information to the identity defined by
identity index.
2.1.7.4.1.9 start-date Element 0-1 Date when the individual became the 10 F Format ccyy-mm-dd
owner of the business name
2.1.7.4.1.10 business Container 0-1 Includes the business details
2.1.7.4.1.10.1 bureau-reference Element 0-1 Equifax internal unique reference for this 10 V
organisation
2.1.7.4.1.10.2 name Element 0-1 Business name 200 V
2.1.7.4.1.10.3 previous-state-or-territory-regist Container 0-1 State registration details. Only available
ration for business names registered prior to
National Business Names reform in May
2012.
2.1.7.4.1.10.3.1 state Element 0-1 The code of the state or territory where 3 V Refer to 8.24 - State code
the business name was registered table for valid values.
2.1.7.4.1.10.3.2 number Element 0-1 The number assigned by the state for 15 V
registration of the business
2.1.7.4.1.10.4 ABN Element 0-1 Australian Business Number 11 F
business-name-id Element 0-1 Future use only
2.1.7.4.1.10.5 10 V
2.1.7.4.1.10.6 business-summary Container 0-1 Contains a trading history summary of This section is only returned
the business name. for a directorship or previous
directorship if the trading
history variant was
requested.
2.1.7.4.1.10.6.1 enquiries Element 1 The number of enquiries found for the Returns a maximum count of
2 V
business name. 50.
2.1.7.4.1.10.6.2 payment-defaults Element 1 The number of payment defaults found Returns a maximum count of
2 V
for the business name. 25.
2.1.7.4.1.10.6.3 mercantile Element 1 The number of mercantile enquiries Returns a maximum count of
2 V
found for the business name. 10.
2.1.7.4.1.10.6.4 proprietorships Element 1 The number of Returns a maximum count of
2 V
proprietorships/proprietors found for 50.
the business name.
103
2.1.7.4.1.10.6.5 court-writs Element 1 The number of court writs found for the Returns a maximum count of
2 V
business name. 10.
2.1.7.4.1.10.6.6 court-actions Element 1 The number of court actions found for Returns a maximum count of
2 V
the business name. 10.
2.1.7.4.1.10.6.7 current-directors Element 1 The number of current directors found Returns a maximum count of
2 V
for the organisation. (Please disregard 50.
the field for Business Names
2.1.7.4.1.10.6.8 previous-directors Element 1 The number of previous directors found Returns a maximum count of
2 V
for the organisation. 50.
additional-data-fields Container 0-1 Contains additional data fields. Will be
2.1.7.4.1.11
used in the future to report additional
information.
data-field Container 1-M Future use only
2.1.7.4.1.11.1
key Element 1 Future use only 20 V
2.1.7.4.1.11.1.1
value Element 1 Future use only 20 V
2.1.7.4.1.11.1.2
@unit Attribute 0-1 Future use only 20 V
2.1.7.4.1.11.1.2.1
104
6.2.3.2.7.5 Personal-insolvencies
Schema location: response>product-data>enquiry-report>public-record-or-consumer-credit-information>personal-insolvencies
Figure 32: personal-insolvencies

2.1.7.5 personal-insolvencies Container 0-1 Includes information about personal
insolvencies
2.1.7.5.1 personal-insolvency Container 1-2 Includes details of up to two personal
insolvencies (previously referred to as
bankruptcy)
2.1.7.5.1.2 @dispute-reported-dat Attribute 0-1 Future use only 10 F Format ccyy-mm-dd
e
105
information to the identity defined by identity
index.
2.1.7.5.1.5 type Element 0-1 Full description of the type of insolvency 60 V
(previously named bankruptcy-type)
2.1.7.5.1.5 @code Attribute 0-1 Associated code 1 F Refer to 8.17- Personal
Insolvency Type code table for
valid values
2.1.7.5.1.6 date-declared Element 0-1 Date the bankruptcy was declared 10 F Format ccyy-mm-dd
2.1.7.5.1.7 text Element 0-1 The type of administration or petition 50 V
2.1.7.5.1.8 administration-id Container 0-1 Administration identifier (previously called
proceedings)
2.1.7.5.1.8.1 district Element 0-1 The district the matter was commenced in 3 V Refer to 8.24 - State code table
(previously called state). for valid values.
2.1.7.5.1.8.2 year Element 0-1 The year in which the application/estate 4 F
commenced.
2.1.7.5.1.8.3 number Element 0-1 The number from the source system 8 V
2.1.7.5.1.8.4 proceedings-status Element 0-1 Either Part 9 or Part 10. 7 V
2.1.7.5.1.9 status Element 0-1 Current status of the personal insolvency 28 V
2.1.7.5.1.9.1 @code Attribute 0-1 Associated code 1 F Refer to 8.16 - Personal
Insolvency Status code table for
valid values
2.1.7.5.1.10 status-date Element 0-1 Date the personal insolvency was discharged, 10 F Format ccyy-mm-dd
terminated or completed
2.1.7.5.1.11 relationship Element 0-1 Indicates if other persons are part of the same 30 V
application/joint estate (previously called role).
2.1.7.5.1.11.1 @code Attribute 0-1 Type of relationship (code) 1 F
Refer to 8.18 - Relationship code
2.1.7.5.1.12 co-borrower Element 0-1 Name of other person who is part of the same 40 V
application/joint estate
2.1.7.5.1.13 trustee Container 0-1 Future use only
2.1.7.5.1.13.1 name Element 0-1 Future use only 60 V
2.1.7.5.1.13.2 business-name Element 0-1 Future use only 30 V
2.1.7.5.1.13.3 business-address Element 0-1 Future use only 400 V
2.1.7.5.1.13.4 phone-number Element 0-1 Future use only 20 V
106
2.1.7.5.1.14 additional-data-fields Container 0-1 Contains additional data fields. Will be used in
the future to report additional information.
6.2.3.2.7.6 Sole-trader
Schema location: response>product-data>enquiry-report>public-record-or-consumer-credit-information>sole-trader
Figure 33: sole-trader

Validation Rules
2.1.7.6 sole-trader Containe 0-1 Future use only
r
2.1.7.6.1 sole-trader-registrati Containe 1-M
on r
2.1.7.6.1.1 id-references Containe 0-1 Includes a list of id-references
r
2.1.7.6.1.1.1 id-reference Element 1-M Reference to associate the source of this information to the 3 V
identity defined by identity index.
2.1.7.6.1.2 ABN Element 0-1 Future use only 11 F
2.1.7.6.1.3 additional-fields Containe 0-1 Future use only
r
2.1.7.6.1.3.1 data-field Containe 1-M Future use only
r
2.1.7.6.1.3.1.1 Key Element 1 Future use only 20 V
107
6.2.3.3 Summary-data
Schema location: response>product-data> summary-data
Figure 34: Summary-data

2.2 summary-data Container 0-1 Contains summarised information about the
individual's credit file data which are called
characteristics.
2.2.1 data-block Container 1-M Contains characteristics. Refer to the Genesis Data BlockTM
guide for all details about the
summary characteristics.
In addition to the Genesis Data

BlockTM the Financial Hardship
Information data block will also be
returned for all Comprehensive data
level customers where permitted. The
block will be named fin_hardship.
In addition to the Genesis Data

BlockTM, Equifax Apply (Telco), Equifax
108
Apply (Utility) and Equifax Apply
(Alternative Lending) return an
additional (Telco, Utility or
Alternative Lending) data block.
2.2.1.1 @type Attribute 1 Indicates whether this list of characteristics is a 8 F
standard set or a custom set list. Custom
characteristic lists are a future product feature and
will be configuration driven.
2.2.1.2 @name Attribute 1 Name associated with the data block. The standard 50 V
data block name is Genesis.
2.2.1.3 characteristic Container 1-M Contains information about a characteristic data
item.
2.2.1.3.1 @id Attribute 1 Characteristic ID which uniquely identifies the 6 V
characteristic.
2.2.1.3.2 @key-characteristic Attribute 0-1 Indicates whether the characteristic returned is a 5 V
key characteristic. Key characteristics are flagged
so that they can be easily identified to render on a
screen or a report.
2.2.1.3.3 variable-name Element 1 Name of the variable 40 V
2.2.1.3.4 description Element 1 Description of the characteristic 150 V
2.2.1.3.5 value Element 1 Value of the characteristic. 20 V
2.2.1.3.5.1 @unit Attribute 0-1 Use of measure associated with the value. 20 V
2.2.1.3.6 data-level Element 0-1 Indicates the data level type of the characteristic. A 20 V
characteristic can be derived based on Negative,
Partial or Comprehensive data.
2.2.1.3.6.1 @code Attribute 0-1 Code associated with the data level 1 F Refer to 8.6 - Data Level code table for
valid values
109
6.2.3.4 Score-data
Schema location: response>product-data> score-data
Figure 35: Score-data

Seq No XML Element Type O/C Description Len V/F Format and Validation
Rules
2.3 score-data Container 0-1 Contains information about the individual's scores. The
response may include multiple scores if additional score cards
was requested.
2.3.1 score Container 1-M Contains information about the scorecards returned.
2.3.1.1 @is-gated Attribute 0-1 Future use only 5 V
2.3.1.2 scorecard Container 1 Contains information about the scorecard use and the
calculated score value.
2.3.1.2.1 @id Attribute 1 Scorecard ID which uniquely identifies the scorecard. 15 V Refer to 2.4 - Scorecard
ID for a list of available
scorecard ids
110
2.3.1.2.2 name Element 1 Name of the scorecard used to calculate the score. 50 V
2.3.1.2.3 version Element 1 Version of the scorecard. 4 V
2.3.1.2.4 type Element 0-1 Indicates the type of scorecard. e.g. Consumer, Consumer + 40 V
Commercial
2.3.1.2.5 data-level Element 0-1 Indicates the data level type of the scorecard. A scorecard 20 V
developed for Negative, Partial or Comprehensive data.
2.3.1.2.5.1 @code Attribute 0-1 Code associated with the data level 1 F Refer to 8.6 - Data Level
code table for valid
values
2.3.1.3 risk-odds Element 0-1 Odds of adverse information in the next 12 months calculated 18 V Note: Risk-odds is
against the full population. returned as a decimal
Risk odds returns the Good Bad odds of the given applicants value. e.g.: 117.78
score band. For example, odds of 14 (i.e. 14:1) mean that of all (117.78:1)
the individuals with the same score as this particular applicant,
on average 14 applicants exhibit good credit behaviour while 1
applicant exhibits bad credit behaviour.
2.3.1.4 key-contributing-fact Container 0-1 Contains the key contributing factors which can impact risk. Refer to 8.11 - Key
ors Contributing Factors
(KCF) code tables for
valid values
2.3.1.4.1 contributing-factor Container 1-M Contains information about one of the contributing factors.
2.3.1.4.1.1 @id Attribute 0-1 Contributing factor ID which uniquely identifies the contributing 10 V
factor.
2.3.1.4.1.2 name Element 1 Name of the contributing factor. 60 V
2.3.1.4.1.3 description Element 0-1 Description of the contributing factor. 200 V
2.3.1.4.1.4 score-impactor Element 1 Describes the level of risk. e.g. Greatly increases risk. 40 V Refer to 8.20 - Score
Impactors code table for
valid values
2.3.1.4.1.4. @code Attribute 0-1 Future use only 2 F
1
2.3.1.5 score-masterscale Element 1 Score. 6 V Refer 8.22 - Special
Score Values for a list
of special values.
2.3.1.6 additional-fields Container 0-1 Future use only
2.3.1.6.1 data-field Container 1-M Future use only
2.3.1.6.1.1 Key Element 1 Future use only 20 V
2.3.1.6.1.2 value Element 1 Future use only 20 V
111
2.3.1.6.1.2. @unit Attribute 0-1 Future use only 20 V
1
6.2.3.5 Possible-matches
Schema location: response>product-data> possible-matches
Figure 36: possible-matches

No
2.5
possible-matches Container 0-1 Contains personal information of a possible match file to the individual.
Note: Possible matches are returned where the additional information may affect the individual’s credit risk
profile.
2.5.1 possible-match Container 1 Contains personal information of a possible match to the individual.
2.5.1.1 Identity Container 1 Contains the individual's personal information for an instance of a possible match identity record.
Child XML elements of this container element are defined under 6.2.3.2.1-Primary-match
2.5.1.2 Addresses Container 0-1 Contains information about the individual's addresses.
Child XML elements of this container element are defined under 6.2.3.2.3 Addresses.
2.5.1.3 Employment Container 0-1 Contains information about the individual's employment.
Child XML elements of this container element are defined under 6.2.3.2.4-Employment.
6.2.3.6 File-ban-report
Schema location: response>product-data> file-ban-report
112
Figure 37: File-ban-report
Seq XML Element Type O/C Description Len V/F Format and
No Validation Rules
2.4 file-ban-report Contain 0-1 Indicates whether the individual is under a Ban. If the individual is under a Ban then
er the enquiry-report element will not be returned. Mutually exclusive. Ban Flags are a
requirement under the Privacy Act.
2.4.1 reported-date Element 0-1 Reported date of the Ban. 10 F Format
ccyy-mm-dd
2.4.2 is-extended Element 0-1 Indicates whether the Ban is an extension. 5 V
2.4.3 end-date Element 1 End date of the Ban. 10 F Format
ccyy-mm-dd
6.3 Retrieve Enquiry by ID
6.3.1 Business Overview

An enquiry response can be retrieved by using the following operation:
1. retrieveEnquiryByID
This web service operation allows the user to retrieve an enquiry report which has been generated previously using the new enquiry operation or to pick-up
an enquiry response that was originally requested in asynchronous mode.
6.3.2 Request Overview

Request includes:
● Enquiry ID; unique ID issued by the system and related to a particular request operation.
113
The following illustration depicts the general structure of the ticket response.
Figure 38: Retrieve Consumer Enquiry - Request Overview
6.3.2.1 Request-by-enquiry-id
Seq XML Type O/C Description Len V/ Format and Validation
No Element F Rules
1 enquiry-id Element 1 System generated unique ID related to a particular response 20 V
transaction.
6.3.3 Response Overview

The response for Retrieve Enquiry by ID is the same as that described in section 6.2.3 Response Overview.
114
7 Other Response Considerations
7.1 Responses to matching of identification data from the request
The table below lays out the possible responses of matching to identification data from the request.
Condition Result Response
Request by Identity Details
No match for a Credit The system creates a new file and For the created file, a primary match element with a
Provider records a credit enquiry based on the bureau number and details from the request.
data supplied in your request.
No match for an The system returns a general message A general message element.
Access Seeker indicating that the subject of your
enquiry was not found
One strong match and The information in your request is A primary-match element with details from the
no possible matches added to the individual Consumer or individual Consumer and/or individual Commercial file
individual Commercial file. and the Public record file.
One strong and one The information in your request is For the strong match, a primary-match element with
possible matches added to the individual Consumer or details from the individual Consumer and/or
individual Commercial file for the individual Commercial file and the Public record file.
strong match. For the possible match(es), a possible-match element
with the file number and identity details.
No strong match and The system creates a new file based on For the created file, a primary match element with a
one or more possible the data supplied in your request. bureau number and details from the request.
matches for a credit For the possible match(es), a possible-match element
provider with the file number and identity details.
No strong match and The system returns a general message A general message element.
one or more possible indicating that the subject of your
matches for an Access enquiry was not found
Seeker
Request by Bureau Reference Number

File found on database The information in your request is A primary-match element with details from the
added to the individual’s consumer or individual Consumer and /or individual Commercial
individual’s commercial file. file and the Public record file.
Table 2 Responses to matching to identification data from the request

Note: Current default settings provide a maximum of one possible match returned in response. Existing customer
configurations allowing variations will continue to apply. The ability to customize possible matches at runtime is
not yet supported.

Equifax Apply (Telco) and Equifax Apply (Utility) products use the same matching conditions as those
used for Credit Providers (listed above).
115
Equifax Apply (Alternative Lending) product also uses the same matching conditions as those used
for Credit Providers (listed above).
7.2 Product error codes and descriptions

Below is a categorisation of error codes for Equifax Apply and Equifax Commercial Apply with a brief description
of cause and recommended action(s). API Connect generic errors are described in section 4.5 of API Connect
Connectivity Guide.
Code Range Cause Action

010000-019999 Product cannot be fulfilled because a critical Primary: Resubmit original request.
product component is not available. Secondary: Contact Equifax for resolution.
020000-029999 Product cannot be fulfilled because an external Primary: Resubmit original request.
product dependency is not available.
030000-039999 User has attempted to submit a request with Primary: Correct original request and resubmit
incompatible parameters. The root cause may be as a new request.
because of the user’s configuration settings or Secondary: Contact Equifax for investigation.
product rules.
040000-049999 User has attempted to submit a request which Primary: Correct original request and resubmit
fails minimum request validation rules. as a new request.
7.2.1 Error samples

Fault-code Fault-string Fault-actor Detail Explanation
010001 Service An unrecoverable error A system error has occurred which has
unavailable has occurred. Please disrupted the delivery of your report.
re-try again later or The request can be resubmitted to overcome
contact Equifax quoting transient issues but if the error persists then
the enquiry-id for contact Equifax for resolution.
resolution
[000000-00000-00001].
030001 Product User profile The requested product Requested product data level exceeds the
data level data level exceeds your user’s data supply level.
conflict supply level of N. Please To overcome this error, resubmit the request
correct and try again. with a lower product data level.
040002 Individual is Validation REQUEST REJECTED Applicant’s date of birth in the request
under 18 engine BECAUSE INDIVIDUAL IS indicates that the individual is less than 18
error UNDER 18 years of age.
Equifax is not permitted to collect or disclose
consumer credit information for individuals
under the age of 18.
040005 Request Validation FILE NUMBER IS User has submitted a request by bureau
validation engine INVALID reference number which was not found or no
error longer exists.
The individual’s credit report can still be
returned by using the applicant’s identity
details instead.
116
8 Code Tables
NOTE
The following tables are provided for indicative purposes and may be subject to further changes. It is therefore
recommended for client systems to be designed in such a way as to cater for other values being returned in
addition to those listed in these tables.
8.1 Address Type

Address Type Code Table
Code Description
C Current or Last Known Residential
Address
P Previous Residential Address
8.2 Consumer Account Type

Consumer Account Type Code Table
Code Description
AL Auto Loan
BF Buy Now Pay Later Facility
BT Buy Now Pay Later Transaction
CC Credit Card (also maybe Continuing Credit Contract) *
CA Charge Card
OD Overdraft
PF Personal Loan (fixed term)
PR Personal Loan (revolving)
RE Equipment Hire or Rental
RM Real Property Mortgage
TC Telecommunications Services
UA Utilities
AO All Other Account Types
This account type is only valid for accounts in the response and will not be accepted as a valid account type for
credit enquiries in the request.
*In CCR Data Supply, a Consumer Account Type of CC means Credit Card, however in the legacy Equifax Consumer Enquiries,
CC means Continuing Credit Contract. Throughout the Equifax Apply report CC will be treated as Credit Card, however please
be aware that it may also mean Continuing Credit Contract for some enquiries. For a revolving line of credit enquiry or Data
Supply it is recommended that an Account Type of OD (Overdraft) or PR (Personal Loan (Revolving)) is used for revolving
continuing credit accounts, and that CC is solely used for Credit Card
8.3 Commercial Account Type

Commercial Account Type Code Table
Code Description
BF Bridging Finance
BS Bill of Sale
CD Cash on Delivery
CH Cheque
CP Credit Card
CR Commercial Rental
D Dealership
DB Deferred Payment Debit Card
F Factored Account
117
HC Hire Purchase
L Leasing
LP Lending Proposal
OD Bank Overdraft
PF Premium Finance
PL Personal Loan
RM Real Estate Mortgage
SR Search Request
TF Trade Finance
TC Telecommunication services
UA Utilities
WF Wholesale Finance
7 7-Day Account
30 30-Day Account
60 60-Day Account
90 90-Day Account
8.4 Court action status

Court Action Status Code
Table
Code Description
D Discontinued
P Paid
S Settled
8.5 Credit enquiry type

Credit Enquiry Type Table
Value Context
credit-application Consumer only
credit-enquiry Commercial only
credit-review Commercial only
authorised-agent-enquiry Commercial only
8.6 Data Level

Data Level Code Table
Code Description
N Negative
P Partial
C Comprehensive
8.7 Default Reason to Report (commercial defaults only)

Commercial Default Reason to Report Code Table
Code Description
C Clearout (Watched)
CX Clearout (Not watched)
DC Dishonoured Cheque
II Account opened on incorrect information supplied by customer
IS Insurance Shortfall
JD Judgement Debt Outstanding
L Legal (Where court action commenced)
OA Overdrawn Account
PD Payment Default
118
R Repossession (Loss not yet established)
RC Referred to Collection or Collection Agency
RL Repossession Loss (After sale of the item)
SA Scheme of Arrangement
VS Voluntary Surrender
WO Bad Debt Written Off
WX Write Off (Monitoring Complete)
8.8 Default Status

Default Status Code Table
Code Description
O Outstanding
Means that the payment is still outstanding, and the account remains in Default.
P Paid
Default associated with this account has been paid on the date supplied.
*Note: The Office of the Australian Information Commissioner (OAIC) has recently provided a view that the only lawful
disclosure of payment information is that a default has been paid (‘P’ code). Prior to this, the industry practice was for
payment of defaults to be disclosed as either paid in full (‘P’ code) or settled for a lesser amount (‘S’ code). From 15 February
2019, all existing ‘S’ codes were converted to ‘P’ codes on the Equifax consumer bureau. Hence ‘S’ is no longer a valid Default
status.
To bring the CR Code in line with the views previously expressed by the OAIC.As of 14th February 2020, all existing ‘C’ codes
will be converted to ‘P’ codes on the Equifax consumer bureau. Hence ‘C’ is no longer a valid default status.
The Disputed status is no longer available oin the Equifax Consumer bureau for both consumer and commercial defaults.
8.9 Default New Arrangement

Default New Arrangement Code Table
Code Description
N New Arrangement - New consumer credit provided that relates, wholly or in part, to this amount of credit.
V New Arrangement - Terms or conditions of the original consumer credit that relate to the repayment of the
amount of the credit are varied.
8.10 Employment Type

Employment Type Code Table
Code Description
C Current or Last Known Employment
P Previous Employment
8.11 Gender
Gender Code Table
Code Description
M Male
F Female
U Unknown
119
8.12 Key Contributing Factors (KCF)
8.12.1 KCF for Equifax Apply scores

Key Contributing Factors for Equifax Apply scores
ID Name Description Minimum score
data level
KCF-001 Length of Credit History The time since credit activity is first recorded on file can be an Negative
indicator of risk.
KCF-002 Applicant Information Details of an applicant (such as age, employment and address Negative
details) can have an impact on risk.
KCF-003 Consumer Credit The type and frequency of credit applications can impact risk. Negative
Application Pattern Research shows that applicants with a higher risk typically
apply for credit more often.
KCF-004 Current Consumer Credit The type and amount of credit being applied for can have an Negative
Application Information impact on risk.
KCF-005 Recent Consumer Credit Recent credit applications made can have an impact on risk. Negative
Application Information
KCF-006 Historical Consumer Credit The type and frequency of historical credit applications can be Negative
Application Information an indicator of risk.
KCF-007 Consumer Default The existence of consumer default information can be a Negative
Information powerful indicator of risk.
KCF-008 Lack of Consumer Adverse Having no consumer adverse information can have an impact Negative
Information on risk.
KCF-009 Commercial Credit Commercial credit application history relating to number, Negative
Application Information frequency and type of credit sought can have an impact on risk.
Applicable only when permission type is XY
(Consumer+Commercial)
KCF-010 Commercial Default The existence of commercial default information can be a Negative
KCF-011 Public Adverse Information The existence of public adverse information such as court Negative
judgements and writs can have a powerful impact on risk.
KCF-040 Lack of Public Adverse Having no public adverse information can have an impact on Negative
Information risk.
KCF-012 Directorship Information Information on an applicant’s director’s file can impact risk. Negative
KCF-032 Consumer Credit Telco The Telco type and frequency of credit applications can impact Negative
Application Pattern risk.
KCF-033 Commercial Credit Commercial credit application history relating to number, Negative
Application and Default frequency and type of credit sought can have an impact on risk
Information as well as existence of commercial default information.

KCF-013 Current Payment Status Current repayment status can be a powerful indicator of risk. Comprehensive
KCF-014 Account Repayment History Repayment history information can have an impact on risk. Comprehensive
KCF-015 Time Since Observed The length of time since the last late payment made can be an Comprehensive
Delinquency indicator of risk.
KCF-016 Credit Exposure in An applicant’s credit exposure in arrears can be a powerful Comprehensive
KCF-017 Limit Changes Increases in credit limits can have an impact on risk. Partial
The following Key Contributing Factors can be returned in the case of a special score scenario
120
KCF-018 Bankrupt Bankrupt (excluding Discharged, Part X, Part IX) as at time of Negative
enquiry
KCF-019 Part X Personal Insolvency Part X Personal Insolvency Agreement (excluding Discharged Negative
Agreement and Terminated) as at time of enquiry
KCF-020 Part IX Debt Agreement Part IX Debt Agreement (excluding Discharged and Terminated) Negative
as at time of enquiry
KCF-021 Discharged Bankrupt Discharged Bankrupt (excluding Part X, and Part IX) as at time Negative
of enquiry
KCF-022 Part X Personal Insolvency Part X Personal Insolvency Agreement Discharged as at time of Negative
Agreement Discharged enquiry
KCF-023 Part IX Debt Agreement Part IX Debt Agreement Discharged as at time of enquiry Negative
Discharged
KCF-024 Part X Personal Insolvency Part X Personal Insolvency Agreement Terminated as at time of Negative
Agreement Terminated enquiry
KCF-025 Part IX Debt Agreement Part IX Debt Agreement Terminated as at time of enquiry Negative
Terminated
KCF-029 Deceased At least 1 report has flagged the individual as deceased at time Negative
of enquiry
KCF-030 Under 18 Individual is under 18 on their primary file. Negative
Applicable only to Access Seekers
KCF-031 Current Worst Repayment At least 1 open account with repayment status 4+ at time of Comprehensive
Status 4+ enquiry (excludes guarantor accounts)
8.12.2 KCF for Equifax Commercial Apply scores

Key Contributing Factors for Equifax Commercial Apply scores
ID Name Description Minimum
score data
level
KCF-101 Length of Credit History The time since credit activity is first recorded on file can be an Negative
indicator of risk.
KCF-103 Historical Commercial Credit Commercial credit application history relating to number, Negative
Application Information frequency and type of credit sought can have an impact on risk.
KCF-104 Current application The type and amount of credit being applied for can have an Negative
information impact on risk.
KCF-105 Commercial Default The existence of commercial default information can be a Negative
KCF-106 Lack of Adverse Information The lack of consumer, commercial or public adverse Negative
information such as defaults, court judgements and writs can
have an impact on risk.
Application Pattern Research shows that applicants with a higher risk typically
apply for credit more often.
Applicable only when permission type is YX
(Commercial+Consumer)
KCF-108 Recent Consumer Credit Recent credit application activity can have an impact on risk. Negative
Application Information Applicable only when permission type is YX
KCF-109 Historical Consumer Credit The type and frequency of historical credit applications can be Negative
Application Information an indicator of risk.
KCF-110 Consumer Default The existence of consumer default information can be a Negative
121
KCF-112 Public adverse information The existence of public adverse information such as court Negative
judgements and writs can have a powerful impact on risk.
KCF-113 Directorship or Directorship and Proprietor information can have an impact on Negative
Proprietorship Information risk
KCF-114 Current Payment Status Current repayment status can be a powerful indicator of risk. Comprehensive
KCF-115 Account Repayment History Repayment history information can have an impact on risk. Comprehensive
KCF-116 Time Since Observed The length of time since the last late payment made can be an Comprehensive
KCF-118 Bankrupt Bankrupt (excluding Discharged, Part X, Part IX) as at time of Negative
enquiry
KCF-119 Part X Personal Insolvency Part X Personal Insolvency Agreement (excluding Discharged Negative
Agreement and Terminated) as at time of enquiry
KCF-120 Part IX Debt Agreement Part IX Debt Agreement (excluding Discharged and Terminated) Negative
as at time of enquiry
KCF-121 Discharged Bankrupt Discharged Bankrupt (excluding Part X, and Part IX) as at time Negative
of enquiry
KCF-122 Part X Personal Insolvency Part X Personal Insolvency Agreement Discharged as at time of Negative
Agreement Discharged enquiry
KCF-123 Part IX Debt Agreement Part IX Debt Agreement Discharged as at time of enquiry Negative
Discharged
KCF-124 Part X Personal Insolvency Part X Personal Insolvency Agreement Terminated as at time of Negative
Agreement Terminated enquiry
KCF-125 Part IX Debt Agreement Part IX Debt Agreement Terminated as at time of enquiry Negative
Terminated
KCF-129 Deceased At least 1 report has flagged the individual as deceased at time Negative
of enquiry
KCF-130 Under 18 Individual is under 18 on their primary file. Negative
Applicable only to Access Seekers
KCF-131 Current Worst Repayment At least 1 open account with repayment status 4+ at time of Comprehensive
Status 4+ enquiry (excludes guarantor accounts)
8.12.3 KCF for VedaScore 1.1 scores

Key Contributing Factors for VedaScore 1.1 scores
score data
level
KCF-201 Applications from Research shows that risk is related to the type of credit provider Negative
Particular Industry Groups being approached.
KCF-202 Current and Historic Credit The type of credit currently and historically applied for can impact Negative
Type Sought risk.
KCF-203 Individual Shopping The type and frequency of credit applications can impact risk. Negative
Pattern Research shows that applicants with a higher risk typically apply for
credit more often.
KCF-204 Number of Consumer The number of consumer credit applications by an individual can be Negative
Credit Applications an indicator of risk.
122
KCF-205 Current and Historic Credit The amount of credit an applicant has applied for can be an Negative
Amount Sought indicator of risk.
KCF-206 Authorised Agent Enquiries to authorised agents can impact risk. Negative
Information
KCF-207 Directorship Information Information on an applicant’s director’s file can impact risk. Negative
KCF-208 Age of File The age of an applicant’s file can be an indicator of risk. Negative
KCF-209 Age of File & Pattern of The spread of credit activity as it relates to the age of the applicant's Negative
Credit Applications file can impact risk.
KCF-211 Application Information Information included as part of the current application for credit can Negative
have an impact on risk.
KCF-212 Default Information The existence of default information on the consumer file can be a Negative
Recorded very powerful indicator of risk.
KCF-213 Court Writ Recorded The existence of court writ information on the file is a powerful Negative
indicator of increased risk.
KCF-214 Specific Default Data Specific default information has been shown to have an impact on Negative
the risk.
KCF-215 Default Judgement The existence of default judgement information on the applicant’s Negative
Information Recorded file can have a powerful impact on risk.
KCF-216 Proprietorship Information Proprietorship information on an applicant’s file can impact risk. Negative
KCF-217 Credit Provider Research shows that risk can be related to the type of credit Negative
Information provider being approached.
KCF-218 Specific Default Specific default judgement information can have an impact on risk. Negative
Judgement Data
KCF-220 Lack of Consumer Adverse No consumer adverse information: i.e. No defaults, default Negative
Information judgments, court writs and bankruptcies on file can have an impact
on risk.
KCF-221 Commercial Default The existence of commercial default information can be a very Negative
Applicable only when permission type is XY (Consumer+Commercial)
KCF-222 Commercial Address Details of commercial address can have an impact on risk. Negative
Information Applicable only when permission type is XY (Consumer+Commercial)
8.12.4 KCF for Telco, Utility and Alternative Lending Scores

Key Contributing Factors for Equifax Apply Telco, Utility and Alternative Lending Scores
score data
level
Application Pattern Research shows that applicants with a higher risk typically apply for
credit more often.
KCF-006 Historical Consumer The type and frequency of historical credit applications can be an Negative
Credit Application indicator of risk.
Information
KCF-007 Consumer Default The existence of consumer default information can be a powerful Negative
Information indicator of risk.
KCF-008 Historical Account The age, limits, number of credit accounts held is an indicator of risk Negative
Information
KCF-011 Public Adverse The existence of public adverse information such as court Negative
Information judgements and writs can have a powerful impact on risk.
KCF-032 Consumer Credit Telco The Telco type and frequency of credit applications can impact risk. Negative
Application Pattern
123
KCF-033 Commercial Credit Commercial credit application history relating to number, frequency Negative
Application and Default and type of credit sought can have an impact on risk as well as
Information existence of commercial default information.
8.12.5 KCF for Equifax One Score

Key Contributing Factors for One Score
ID Name Description
KCF-301 Accounts in arrears by 30 days or more show previous payment difficulties
Late Payments of 30+ Days
and are an indicator of higher credit risk.
Late Payments of 15-29 Days Early arrears over a period of time can be an indicator of higher credit risk.
KCF-302
Over Several Months
Number of Accounts with Arrears across multiple accounts can be an indicator of higher credit risk.
KCF-303
Overdue Payments
Having Accounts with Overdue Accounts in arrears can indicate higher credit risk.
KCF-304
Payments
KCF-305 Credit Cards Closed Closure of Credit Card accounts may show more responsible use of credit.
Existing Mortgages or Having Residential Mortgage accounts and/or enquiries is an indicator of
KCF-306
Applications stability and responsible use of credit.
KCF-307 Unsecured Personal Loans Use of unsecured personal loans may be an indicator of higher credit risk.
Consumer Defaults or Default Defaults or Court Judgements demonstrate previous non-payment of debt
KCF-308
Judgements and are an indicator of higher credit risk.
Use of shorter term low value credit facilities is often an indicator of higher
KCF-309 Short Term Credit Enquiries
credit risk.
Buy Now Pay Later Credit Use of Buy Now Pay Later facilities may be an indicator of higher credit risk.
KCF-310
Enquiries
Infrequent applications for credit is an indicator of stability and may indicate
KCF-311 Infrequent Credit Enquiries
lower credit risk.
The nature and frequency of applications for credit may be an indicator of
KCF-312 Frequent Applications for Credit
higher credit risk.
The lenders and type of credit applied for show more responsible use of
KCF-313 Better Type of Credit Enquiries
credit.
The lenders and type of credit enquiries may be an indicator of higher credit
KCF-314 Lesser Type of Credit Enquiries
risk.
Longer experience with credit and lender relationships shows more
KCF-315 Longer Credit History
responsible use of credit.
KCF-316 Shorter Credit History Shorter credit history can be an indicator of higher credit risk.
Lower Credit Profile of The credit risk profile of the residential locality is associated with higher
KCF-317
Residential Area credit risk.
Higher Credit Profile of The credit risk profile of the residential locality is associated with lower
KCF-318
Residential Area credit risk.
Infrequent applications for commercial credit is an indicator of stability and
Infrequent Commercial Credit
KCF-319 responsible use of credit.
Enquiries
Applicable only when permission type is XY (Consumer+Commercial
The nature and frequency of commercial credit enquiries may indicate
Frequent Commercial Credit
KCF-320 higher credit risk.
Enquiries
Long and Stable Company Having long term directorships is an indicator of stability.
KCF-321
Directorship
New or Changes to Company New or changes to directorships may indicate higher credit risk.
KCF-322
Directorship
Commercial Defaults demonstrate previous non-payment of debt and are
KCF-323 Commercial Credit Defaults an indicator of higher credit risk.
124
Commercial credit defaults and disqualified directorships or a directorship
Commercial Default & Disq
of a company in external administration demonstrates previous
KCF-324 Director or Company in Ext
non-payment of debt and may indicate a higher level of credit risk.
Admin
Disqualified Directorship or Director of Company in External Administration
KCF-325 Disqualified Directorship
can be an indicator of higher credit risk.
Stability of Residence and Residential and employment history are indicators of stability
KCF-326
Employment
Instability of Residence or Recent residential or employment changes may indicate higher credit risk.
KCF-327
Employment
KCF-328 Strong Credit History Having no arrears or defaults demonstrates better credit risk
The number and frequency of unsecured credit enquiries may indicate
KCF-329 More Unsecured Enquiries
higher credit risk.
Infrequent application for unsecured credit is an indicator of stability and
KCF-330 Fewer Unsecured Enquiries
responsible use of credit.
Type of facility applied for and lack of credit history are not indicative of
KCF-331 Better First Type of Credit Sought
higher credit risk.
Type of facility applied for and lack of credit history may indicate higher
KCF-332 Lesser First Type of Credit Sought
credit risk.
KCF-333 Few Telco Credit Enquiries Infrequent applications for telco facilities is an indicator of lower credit risk.
KCF-334 More Telco Credit Enquiries More frequent telco enquiries may indicate higher credit risk.
Infrequent enquiries for credit is an indicator of stability and responsible
KCF-335 Infrequent Enquiries
use of credit.
KCF-336 Frequent Enquiries The frequency and diversity of enquiries may indicate higher credit risk.
Stability of Residence and Residential and employment history are indicators of stability.
KCF-337
Employment
Instability of Residence or Recent residential or employment changes may indicate higher credit risk.
KCF-338
Employment
KCF-339 Changing Name Multiple Times Use of multiple aliases may indicate higher credit risk.
KCF-340 Long Credit History Longer credit history demonstrates experience with use of credit.
KCF-341 Lack of Credit History Available Short credit history may indicate a higher credit risk.
The nature and type of default information is not associated with significant
KCF-342 Less Serious Default
credit issues.
The nature and type of default information may indicate significant
KCF-343 More Serious Default
non-payment of debt and is associated with higher credit risk.
Having Residential Mortgage enquiries is an indicator of being in a good
KCF-344 Mortgage Applications
credit position and is associated with lower credit risk.
The geodemographic profile of the residential locality is associated with
KCF-345 Better Area Profile
lower credit risk.
The geodemographic profile of the residential locality is associated with
KCF-346 Lesser Area Profile
higher credit risk.
KCF-351 Exclusion - Bankruptcy Bankrupt (excluding Discharged, Part X, Part IX) as at time of enquiry.
KCF-352 Exclusion - Part X Personal Part X Personal Insolvency Agreement (excluding Discharged and
Insolvency Agreement Terminated) as at time of enquiry.
KCF-353 Exclusion - Part IX Debt Part IX Debt Agreement (excluding Discharged and Terminated) as at time of
Agreement enquiry.
KCF-354 Exclusion - Discharged Discharged Bankrupt (excluding Part X, and Part IX) as at time of enquiry.
Bankruptcy
KCF-355 Exclusion - Part X Personal Part X Personal Insolvency Agreement Discharged as at time of enquiry.
Insolvency Agreement
Discharged
KCF-356 Exclusion - Part IX Debt Part IX Debt Agreement Discharged as at time of enquiry.
Agreement Discharged
125
KCF-357 Exclusion - Part X Personal Part X Personal Insolvency Agreement Terminated as at time of enquiry.
Terminated
KCF-358 Exclusion - Part IX Debt Part IX Debt Agreement Terminated as at time of enquiry.
Agreement Terminated
KCF-359 Exclusion - Deceased At least 1 report has flagged the individual as deceased at time of enquiry.
KCF-360 Exclusion - Individual is under 18 Individual is under 18 on their primary file.
KCF-361 Exclusion - Lack of Credit There is not enough Credit Information to provide an Equifax One Score at
Information this time.
8.12.6 KCF for Equifax One Score – B2C – for Comparison Sites
Key Contributing Factors for One Score – B2C – for Comparison Sites
ID Name Description
KCF-301 Late payments of 30+ days Payments 30 days or more overdue drive down your credit score
considerably, so keep your payments up to date and on time.
KCF-302 Late payments of 15-29 days over Being 15-29 days late with repayments over a few months will hurt your
several months credit score. Regularly make your minimum repayments on time each
month to demonstrate good credit behaviour.
KCF-303 Number of loans and credit Having a number of loans or credit accounts with overdue repayments is a
accounts with overdue payments warning sign to lenders. Try not to miss payments on multiple accounts.
KCF-304 Loans and credit accounts in Having loan or credit accounts in arrears will drive down your credit score.
arrears Try to catch up on any late repayments within 14 days so you won’t be
reported as being in arrears.
KCF-305 Credit cards that have been Closing your credit cards can show you are responsible when it comes to
closed credit, which can help your credit score, rather than hurt it.
KCF-306 Existing home loans or home You have a home loan, or have applied for one, which is good for your credit
loan applications score, it makes you a more eligible applicant.
KCF-307 Unsecured personal loans Because unsecured personal loans are not secured by an asset, they are
considered higher risk for lenders and can negatively impact your credit
score. Try to limit your unsecured personal loans.
KCF-308 Consumer payment defaults A credit provider has report you have a consumer payment default debt of
at least $150 that is overdue by 60 days or more. To avoid defaults, make
payments as soon as your credit provider asks.
KCF-309 Applying for short-term credit Applying for short-term low value credit and loans, can be an indicator that
and loans you may be in financial stress and lower your credit score. Avoid applying
for short-term loans and credit.
KCF-310 Applying for Buy Now Pay Later When applying to Buy Now Pay Later’ (BNPL) services, an ‘enquiry’ can be
services made on your account, leaving a mark on your credit file. Frequent use of
BNPL could suggest you may be in financial stress.
KCF-311 Rare or infrequent credit or loan When you apply for credit, an ‘enquiry’ is carried out and an enquiry is left
applications on your credit file. Having fewer enquiries over a longer period, makes you
appear as a more responsible borrower.
KCF-312 Multiple applications for loans or You have made lots of applications in a short period through several lenders
credit in a short period which negatively impacts your score as you look more desperate for credit.
Try limiting your credit applications.
KCF-313 Applying for better types of The types of credit and lenders are important to your score. Continue to
credit or lenders apply for secured credit applications (where you offer up an asset as
collateral) and from large banks or auto financers
KCF-314 Applying for lesser types of credit The types of credit and lenders are important to your score. Avoid applying
or lenders for too many unsecured credit accounts and using non-bank lenders, as
these can lower your credit score.
126
KCF-315 Long credit history The longer your credit history, the better it is for your score. Aim for a long
track record of credit accounts, such as long-held credit cards and long
lender relationships, without major slip-ups.
KCF-316 Short credit history Lenders want to see if you can handle debt before they give you any. Having
a shorter than average credit history doesn't provide enough evidence. Try
to gradually build up a credit file.
KCF-317 Lower credit profile of your The credit profile of the area you live in can influence your score. Your area
residential area has a lower credit profile, this could mean you are more likely to miss
repayments and are a higher risk to lenders.
KCF-318 Good credit profile of your The credit profile of the area you live in can influence your score. As your
residential area area has a good credit profile, it could mean you are more likely to make
repayments and are less of a risk to lenders.
KCF-319 Infrequent applications for You rarely or infrequently make credit or loan applications for business
commercial credit or loans purposes. This indicates you are a lower risk to lenders, which can help your
credit score.
KCF-320 Frequent applications for You've made loan applications for business purposes with multiple lenders
commercial credit or loans or within a short period, this suggests you're a higher risk. Aim to reduce
the number or spread out applications over time.
KCF-321 Long and stable company You have been a company director for a long period, which is viewed
directorship positively and can help your credit score.
KCF-322 New or changes to Company New or changes to directorships can indicate you are a risk to lenders and
Directorship drive down your credit score. Previous directorship information will stay on
your file for up to 10 years.
KCF-323 Commercial credit payment You have defaults on your credit file from business credit, which has driven
defaults down your credit score. Aim to pay the defaults as soon as possible.
KCF-324 Commercial default & disq You have a commercial credit default and have a disqualified directorship or
director or company in ext admin directorship of a company in external administration.
KCF-325 Your Directorship status You were disqualified as a company director, or are a director of a company
in external administration which negatively impacts your credit score.
KCF-326 Stable employment and Stable employment and residence can indicate you are more reliable. If
residence you've been living and working in one place for a long time, it's better for
your credit score.
KCF-327 Recent household or Moving homes or jobs can indicate that you are a higher risk, impacting
employment changes your score.
KCF-328 Strong credit history You have a long credit history with up to date payments and no defaults,
demonstrating to lenders that you’re likely to be able to repay debts over
the long haul. This is great for your credit score.
KCF-329 Frequent or recent unsecured More frequent or recent unsecured loan applications (not secured by an
loan applications asset) can negatively impact your credit score. Try to spread out your
unsecured loan enquiries.
KCF-330 Fewer unsecured loan Fewer than average unsecured loan applications is a positive for your credit
applications score, as it indicates that you are more responsible with credit and
therefore a lower risk.
KCF-333 Few credit applications to When you apply for a post-paid mobile phone or internet contract, you are
phone/internet providers applying for credit. Fewer than average credit applications to
telecommunication providers can help your credit score.
KCF-334 Frequent credit applications to When you apply for a post-paid mobile phone or internet contract, you are
phone/internet providers applying for credit. Frequent applications to these providers can hurt your
credit score. Aim to spread these out over time.
KCF-335 Few or infrequent applications Every time you apply for credit cards, loans, etc, the lender puts an enquiry
for credit or loans on your credit file. If you have fewer enquiries, it indicates you are more
responsible with debt and helps your score.
KCF-336 Frequent applications for credit Every time you apply for credit, the provider puts an enquiry on your credit
or loans file. Frequent enquiries or from more than 3 different lenders can hurt your
score. Aim to spread out applications.
127
KCF-337 Stable employment and You have been at your residence for a long period of time and have been in
residence stable employment. Lenders consider this as an indicator of lower risk.
KCF-338 Recent household or Moving homes or jobs can indicate that you are a higher risk, impacting
employment changes your score.
KCF-339 Change of name multiple times Changing your name if you marry (for example) will not impact your credit
score. However, if you have 3 or more names on your credit file, it can
indicate that you are a higher risk to creditors.
KCF-340 Long credit history The longer your credit history, the better it is for your score. Aim for a long
track record of credit accounts, such as long-held credit cards and long
lender relationships, without major slip-ups.
KCF-341 Lack of credit history available Lenders want to see your credit history. As you don’t have any credit
accounts or applications, this may negatively impact your score. Try to
gradually build up your credit file.
KCF-342 Less serious default, including Some defaults are less serious than others, including paid defaults, older
paid and smaller amounts defaults and for smaller amounts. If paid, your credit report will still list the
default, but it will show you've paid it.
KCF-343 More serious default, including Some defaults are more serious than others, including unpaid defaults,
unpaid and larger amounts more recent defaults and those for larger amounts. Aim to pay off overdue
debts as soon as possible.
KCF-344 Mortgage Applications Applying for residential property loans is an indicator of being in a good
credit position which is good for your credit score.
KCF-345 Better Area Profile The profile of the area you live in can make a difference to your score. If it
has a better demographic profile, it indicates you are more likely to make on
time repayments and are a lower risk.
KCF-346 Lesser Area Profile The profile of the area you live in can make a difference to your score. If it
has a lower demographic profile, it indicates you are more likely to miss
repayments and are a higher risk to lenders.
KCF-351 Exclusion - Bankruptcy Bankrupt (excluding Discharged, Part X, Part IX) as at time of enquiry.
KCF-352 Exclusion - Part X Personal Part X Personal Insolvency Agreement (excluding Discharged and
Insolvency Agreement Terminated) as at time of enquiry.
KCF-353 Exclusion - Part IX Debt Part IX Debt Agreement (excluding Discharged and Terminated) as at time of
Agreement enquiry.
KCF-354 Exclusion - Discharged Discharged Bankrupt (excluding Part X, and Part IX) as at time of enquiry.
Bankruptcy
KCF-355 Exclusion - Part X Personal Part X Personal Insolvency Agreement Discharged as at time of enquiry.
Discharged
KCF-356 Exclusion - Part IX Debt Part IX Debt Agreement Discharged as at time of enquiry.
Agreement Discharged
KCF-357 Exclusion - Part X Personal Part X Personal Insolvency Agreement Terminated as at time of enquiry.
Terminated
KCF-358 Exclusion - Part IX Debt Part IX Debt Agreement Terminated as at time of enquiry.
KCF-359 Exclusion - Deceased At least 1 report has flagged the individual as deceased at time of enquiry.
KCF-360 Exclusion - Individual is under 18 Individual is under 18 on their primary file.
KCF-361 Exclusion - Lack of Credit There is not enough Credit Information to provide an Equifax One Score at
Information this time.
128
8.12.7 KCF for One Score for Telco
Key Contributing Factors for One Score for Telco

Minimum
score data
ID Name Description level
Consumer Defaults or Default Defaults or Court Judgements demonstrate previous non-payment of Negative
KCF-400 Judgements debt and may indicate higher credit risk.
The default information demonstrates significant debt non-payment Negative
KCF-402 More Serious Default and may indicate higher credit risk.
No significant credit issues are associated with this default Negative
KCF-403 Less Serious Default information.
A higher volume and frequency of defaults may indicate higher credit Negative
KCF-404 More Frequent Defaults risk.
KCF-405 Less Frequent Defaults Fewer and less frequent defaults may indicate lower credit risk. Negative
Higher Credit Profile of The geodemographic profile of the residential locality is associated Negative
KCF-407 Residential Area with lower credit risk.
KCF-408 Default Judgements Prior or current default judgements may indicate higher credit risk. Negative
The use of short-term low-value credit facilities may indicate higher Negative
KCF-410 Short Term Credit Enquiries credit risk.
No use of short-term low-value credit facilities may indicate lower Negative
KCF-411 No Short Term Enquiry credit risk.
KCF-412 More Telco Credit Enquiries A higher volume of Telco enquiries may indicate higher credit risk. Negative
KCF-413 Few Telco Credit Enquiries A lower volume of Telco enquiries may indicate lower credit risk. Negative
KCF-414 Recent Adverse Recent adverse events may indicate higher credit risk. Negative
Lower credit risk is associated with adverse events that did not occur Negative
KCF-415 Recent Adverse recently.
The lenders and type of credit enquiries may be an indicator of higher Negative
KCF-416 Lesser Type of Credit Enquiries credit risk
The lenders and type of credit enquiries may be an indicator of lower Negative
KCF-417 Better Type of Credit Enquiries credit risk
KCF-418 More Diverse Enquiries The diversity of enquiries may indicate higher credit risk. Negative
KCF-419 Less Diverse Enquiries Less diversity of enquiries may indicate lower credit risk. Negative
KCF-421 Presence of a clean credit history A clean credit history is an indicator of lower credit risk. Negative
Applying for a residential property loan/s is an indicator of being in a Negative
KCF-423 Existing Mortgages or Enquiries good credit position.
Lower Credit Profile of Higher credit risk is associated with the geodemographic profile of Negative
KCF-424 Residential Area this residential locality.
Higher Credit Profile of Lower credit risk is associated with the geodemographic profile of this Negative
KCF-425 Residential Area residential locality.
KCF-426 Recent Credit Card Enquiries Recent credit card enquiries may indicate higher credit risk Negative
129
KCF-427 Recent Credit Card Enquiries No recent credit card enquiries may indicate lower credit risk. Negative
KCF-428 Recent Telco Enquiries Recent Telco enquiries may indicate higher credit risk Negative
KCF-429 Recent Telco Enquiries No recent Telco enquiries may indicate lower credit risk. Negative
Low Ratio of Secured Credit A lower ratio of secured to unsecured credit enquiries may indicate Negative
KCF-430 Enquiry higher credit risk.
High Ratio of Secured Credit A higher ratio of secured to unsecured credit enquiries may indicate Negative
KCF-431 Enquiry lower credit risk.
The use of short-term low-value credit facilities may indicate higher Negative
KCF-432 Short Term Credit Enquiries credit risk.
No use of short-term low-value credit facilities may indicate lower Negative
KCF-433 No Short Term Enquiry credit risk.
A higher volume of small-amount credit enquiries may indicate higher Negative
KCF-434 More Small Amount Enquiry credit risk.
Less or No Small Amount A low volume of small-amount credit enquiries may indicate lower Negative
KCF-435 Enquiry credit risk.
KCF-436 More recent residence A recent change of residence may indicate higher credit risk. Negative
KCF-437 Longer residence Stability of residence can indicate lower credit risk. Negative
KCF-438 More Telco Credit Enquiries A higher volume of Telco enquiries may indicate higher credit risk. Negative
KCF-439 Few Telco Credit Enquiries A low volume of Telco enquiries may indicate lower credit risk. Negative
The type of lenders and type of credit enquiries may be an indicator of Negative
KCF-440 Lesser Type of Credit Enquiries higher credit risk
The type of lenders and type of credit enquiries may be an indicator of Negative
KCF-441 Better Type of Credit Enquiries lower credit risk
More Frequent Unsecured The amount and volume of unsecured credit enquiries may indicate Negative
KCF-442 Enquiries higher credit risk.
Less Frequent Unsecured The amount and volume of unsecured credit enquiries may indicate Negative
KCF-443 Enquiries lower credit risk.
Applicant details contain information which may indicate lower credit Negative
KCF-445 Applicant Details risk.
Application details contain information which may indicate lower Negative
KCF-447 Application Details credit risk.
Lower Credit Profile of Higher credit risk is associated with the geodemographic profile of Negative
KCF-448 Residential Area this residential locality.
KCF-450 More recent residence A recent change of residence may indicate higher credit risk. Negative
KCF-451 Longer residence A stable residence may indicate lower credit risk. Negative
KCF-453 Strong Credit History No arrears or defaults may indicate lower credit risk. Negative
Applicant details contain information which may indicate lower credit Negative
KCF-455 Applicant Details risk.
KCF-456 Lower Credit Profile of Higher credit risk is associated with the geodemographic profile of Negative
130
Residential Area this residential locality.
KCF-458 Lack of Credit History Available Limited credit history may indicate higher credit risk. Negative
Frequent Commercial Credit Negative
KCF-460 Enquiries Frequent commercial credit enquiries may indicate higher credit risk.
Infrequent Commercial Credit Negative
KCF-461 Enquiries Infrequent commercial credit enquiries may indicate lower credit risk.
External administration or Director of a company in External Administration or disqualified Negative
KCF-462 disqualified directorships directorships may indicate higher credit risk.
KCF-466 Previous Directorships Previous directorships can have an impact on credit risk. Negative
KCF-468 Recent Commercial Default Recent commercial default may indicate higher credit risk. Negative
KCF-469 Early Commercial Default No recent commercial default is an indication of lower credit risk. Negative
The age of a current or previous credit account may indicate a lower Partial
KCF-471 Age of Credit Account credit risk.
The age of a current or previous Telco account may indicate a lower Partial
KCF-473 Age of Telco Account credit risk.
Occurence of non-mortgage Occurence of non-mortgage credit limit increase may indicate a higher Partial
KCF-474 credit limit increase credit risk.
Occurence of non-mortgage Occurence of non-mortgage credit limit decrease may indicate a lower Partial
KCF-475 credit limit decrease credit risk.
The conversion of past credit applications to opened loans may have Partial
KCF-478 Credit Enquiry Conversion an impact on credit risk.
The conversion of past credit applications to opened loans may have Partial
KCF-479 Better Credit Enquiry Conversion an impact on credit risk.
KCF-351 Exclusion - Bankruptcy Bankrupt (excluding Discharged, Part X, Part IX) as at time of enquiry. Negative
Exclusion - Part X Personal Part X Personal Insolvency Agreement (excluding Discharged and Negative
KCF-352 Insolvency Agreement Terminated) as at time of enquiry.
Exclusion - Part IX Debt Part IX Debt Agreement (excluding Discharged and Terminated) as at Negative
KCF-353 Agreement time of enquiry.
Exclusion - Discharged Discharged Bankrupt (excluding Part X, and Part IX) as at time of Negative
KCF-354 Bankruptcy enquiry.
Exclusion - Part X Personal Negative
Insolvency Agreement Part X Personal Insolvency Agreement Discharged as at time of
KCF-355 Discharged enquiry.
Exclusion - Part IX Debt Negative
KCF-356 Agreement Discharged Part IX Debt Agreement Discharged as at time of enquiry.
Exclusion - Part X Personal Negative
Insolvency Agreement Part X Personal Insolvency Agreement Terminated as at time of
KCF-357 Terminated enquiry.
KCF-358 Exclusion - Part IX Debt Part IX Debt Agreement Terminated as at time of enquiry. Negative
131
At least 1 report has flagged the individual as deceased at time of Negative
KCF-359 Exclusion - Deceased enquiry.
KCF-360 Exclusion - Individual is under 18 Individual is under 18 on their primary file. Negative
Exclusion - Lack of Credit There is not enough Credit Information to provide an Equifax One Negative
KCF-361 Information Score at this time.
8.13 Loan Payment Method

Loan Payment Method Code Table
Code Description
I Interest only
N Not applicable for the account
P Principal and Interest in full
Principal and Interest are to be paid in full
R Principal and Interest with residual unpaid amount
Principal and interest are to be paid, leaving a residual unpaid amount of principal and interest at the end of the term
of the consumer credit
8.14 Organisation Status

Organisation Status Code Table
Code Description
APPR Approved (trust organisations only)
DRGD Organisation deregistered
EXAD Under external administration
EXMQ Members voluntarily winding up
NRGD Not registered
PEND Pending
REGD Registered
SOFF Organisation is under strike-off action
[blank] All other cases
8.15 Organisation Type

Organisation Type Code Table
Code Description
PTY Proprietary
P/L Proprietary Limited
N/L No Liability
INC Incorporated
LTD Limited Liability
R/B Registered Body
8.16 Permission type

Permission Type Table
Value Description
X Consumer
XY Consumer+Commercial
132
YX Commercial+Consumer
Y Commercial
8.17 Personal Insolvency Status

Personal Insolvency Status Code Table
Code Description
D Discharged
C Completed
T Terminated
8.18 Personal Insolvency Type

Personal Insolvency Type Code Table
Code Description
A Assignment or Arrangement (Part 10 Deed)
B Bankruptcy (Debtor’s Petition)
C Composition (Part 10 Deed)
D Debt Agreement (Part 9)
P Personal Insolvency Agreement (Part 10 Deed)
Q Bankruptcy
S Bankruptcy (Sequestration Order)
X Arrangement (Part 10 Deed)
8.19 Relationship
Relationship Code Table
Code Description
1 Principal’s Account (sole) or Principal’s Account
(Sole/Joint) *
2 Principal’s Account (joint)
3 Guarantor
4 Director
For commercial credit only
*Account relationship codes loaded via CCR Data Supply do not differentiate between Principal’s Account sole and Principal’s
Account joint, so they are all loaded as Relationship code 1 and therefore should be treated as Principal’s Account (sole/joint).
For Enquiries or Defaults loaded via legacy systems Relationship code 1 means Principal’s Account (sole) and Relationship
code 2 means Principal’s Account (joint) - see mapping table below:
o 8.18.1 Account Relationship Mapping
Enquiries and Defaults via Legacy systems Accounts and Defaults loaded via Data Supply
1 – Principal’s Account (sole) 1 – Principal’s Account (sole or joint borrower)
2 – Principal’s Account (joint) 1 – Principal’s Account (sole or joint borrower)
3 – Guarantor 2 – Guarantor
4 – Director
For commercial credit only
8.20 Repayment History Status

Repayment History Status Table
Code Description
The following codes are as specified by the Australian Credit Reporting Data Standards (ACRDS)
133
0 (zero) The consumer credit is not overdue – Current up to and including the grace period
1 Up to 29 days overdue (after the grace period has been applied)
2 30 – 59 days overdue
X 180 + days overdue
When no repayment data is available for a specific period, Equifax will return a special value depending on the case.
C Closed
The account is closed, was closed during that period or was not opened yet during that period
A Not associated*
The account is open but the subject of the report is not associated to the account
R Not reported
Repayment data was not reported for this period
P Pending
Repayment data has not been reported yet for this period (applies if the repayment period is the current
month or the month preceding the enquiry)
T Transferred
Account transferred to another credit provider
O (letter) Future Use Only
Allowed Repayment History values in the case of a Temporary relief or deferral financial hardship arrangement (code A)
as specified by the Australian Credit Reporting Data Standards (ACRDS)
0 (zero) No amounts due under the temporary relief or deferral FHA remain unpaid for the RHI-FHI Period (regardless
of whether payments due under the terms of the credit contract remain unpaid). No Grace Period applies
1 An amount due under the temporary relief or deferral FHA remains unpaid for the RHI-FHI Period
*Financial Hardship Information is returned separately to Repayment History Status. An “A” value returned in
Repayment History Status will always mean Not Associated.
8.21 Financial Hardship Information

Financial Hardship Information Code Table
Code Description
A Temporary relief or deferral financial hardship
arrangement*
V Variation financial hardship arrangement
8.22 Score Impactors
8.22.1 Equifax Apply and Equifax Commercial Apply Score Impactors

Score Impactor Table
Description
Greatly Increases Risk
Greatly Decreases Risk
Moderately Increases Risk
Moderately Decreases Risk
Marginally Increases Risk
Marginally Decreases Risk
134
8.23 Court Type
Court Type Table
Small Court
County Court
District Court
Local Court
Magistrates Court
Supreme Court
8.24 Special Score Values
8.24.1 Equifax Apply, Equifax One Score and Equifax Commercial Apply
One Score Equifax Apply and Equifax Commercial Apply Special Score Values
Special Score Equifax Apply and Equifax Commercial Apply Equifax One Score Description
Value Description
-903 Customer has a Customer has Bankruptcy or Insolvency on file
1. Bankruptcy or Insolvency on file whether whether discharged or annulled or not
discharged or annulled or not
or
2. 90+ days past due on repayment history in the
current month of scoring
e.g. insolvency, current worst payment status 4+
-902 Deceased/Unknown/ not applicable Deceased/Unknown / not applicable
Not enough information - Credit Inactive with no
Geocodable address
-901 System/internal error (very unlikely) System/internal error (very unlikely)
8.24.2 VedaScore 1.1

VedaScore 1.1 Special Score Values
Special Score Value Description
-999 Bankrupt (excluding Discharged, Part X, Part IX) as at time of enquiry
-998 Part X Personal Insolvency Agreement (excluding Discharged) as at time of enquiry
-997 Part IX Debt Agreement (excluding Discharged) as at time of enquiry
-996 Discharged Bankrupt (excluding Part X, and Part IX) as at time of enquiry
-995 Part X Personal Insolvency Agreement Discharged as at time of enquiry
-994 Part IX Debt Agreement Discharged as at time of enquiry
8.25 Secured Credit

Secured Credit Code Table
Code Description
S Secured or Partially Secured
N Unsecured
U Unspecified
8.26 State
State Code Table
Code Description
ACT Australian Capital Territory
NSW New South Wales
NT Northern Territory
NZ New Zealand
135
OS Overseas (except Other States or Territories of Australia or New Zealand)
OTH Other State or Territory of Australia (Norfolk Island, Australian Antarctic Territory, Jervis Bay, …)
QLD Queensland
SA South Australia
TAS Tasmania
VIC Victoria
WA Western Australia
8.27 Street Type

Street Type Code Table
Code Street type Code Street type Code Street type Code Street type Code Street type
ACCS Access CRST Crest GRA Grange PLAT Plateau SLPE Slope
ALLY Alley CRSS Cross GRN Green PLZA Plaza SND Sound
ALWY Alleyway CRSG Crossing GRND Ground PKT Pocket SPUR Spur
AMBL Amble CRD Crossroad GR Grove PNT Point SQ Square
ANCG Anchorage COWY Crossway GLY Gully PORT Port STRS Stairs
APP Approach CUWY Cruiseway HTS Heights PROM Promenade SHWY State
Highway
ARC Arcade CDS Cul-de-sac HRD Highroad QUAD Quad STPS Steps
ART Artery CTTG Cutting HWY Highway QDGL Quadrangle STRA Strand
AVE Avenue DALE Dale HILL Hill QDRT Quadrant ST Street
BASN Basin DELL Dell INTG Interchange QY Quay STRP Strip
BCH Beach DEVN Deviation INTN Intersection QYS Quays SBWY Subway
BEND Bend DIP Dip JNC Junction RMBL Ramble TARN Tarn
BLK Block DSTR Distributor KEY Key RAMP Ramp TCE Terrace
BVD Boulevard DR Drive LDG Landing RNGE Range THOR Thoroughfare
BRCE Brace DRWY Driveway LANE Lane RCH Reach TLWY Tollway
BRAE Brae EDGE Edge LNWY Laneway RES Reserve TOP Top
BRK Break ELB Elbow LEES Lees REST Rest TOR Tor
BDGE Bridge END End LNE Line RTT Retreat TWRS Towers
BDWY Broadway ENT Entrance LINK Link RIDE Ride TRK Track
BROW Brow ESP Esplanade LT Little RDGE Ridge TRL Trail
BYPA Bypass EST Estate LKT Lookout RGWY Ridgeway TRLR Trailer
BYWY Byway EXP Expressway LOOP Loop ROWY Right of Way TRI Triangle
CAUS Causeway EXTN Extension LWR Lower RING Ring TKY Trunkway
CTR Centre FAWY Fairway MALL Mall RISE Rise TURN TURN
CNWY Centreway FTRK Fire Track MNDR Meander RVR River UPAS Underpass
CH Chase FITR Firetrail MEW Mew RVWY Riverway UPR Upper
CIR Circle FLAT Flat MEWS Mews RVRA Riviera VALE Vale
CLT Circlet FOLW Follow MWY Motorway RD Road VDCT Viaduct
CCT Circuit FTWY Footway MT Mount RDS Roads VIEW View
CRCS Circus FSHR Foreshore NOOK Nook RDSD Roadside VLLS Villas
CL Close FORM Formation OTLK Outlook RDWY Roadway VSTA Vista
CLDE Colonnade FWY Freeway PDE Parade RNDE Ronde WADE Wade
CMMN Common FRNT Front PARK Park RSBL Rosebowl WALK Walk
CON Concourse FRTG Frontage PKLD Parklands RTY Rotary WKWY Walkway
CPS Copse GAP Gap PKWY Parkway RND Round WAY Way
CNR Corner GDN Garden PART Part RTE Route WHRF Wharf
CSO Corso GDNS Gardens PASS Pass ROW Row WYND Wynd
CT Court GTE Gate PATH Path RUE Rue YARD Yard
CTYD Courtyard GTES Gates PHWY Pathway RUN Run
COVE Cove GLD Glade PIAZ Piazza SWY Service Way
136
CRES Crescent GLEN Glen PL Place SDNG Siding
8.28 Term type

Term Type Code Table
Code Description
F Fixed
R Revolving
8.29 Industry Classification

Industry Classification Code Table
Code Description
LBNK Large banks
SBNK Other banks, credit union. & building society.
LATO Large auto companies
SLND Other lenders
CONS Construction
FINC Finance company
APPL Equipment finance and rental
FOOD Food, tobacco and beverage retail
MANU Manufacturing
RECR Retail credit
RETA Consumer retail
INSU Insurance
COLL Collections
MEDA Media
AGBS Agribusiness-food production & wholesale
TELC Telecommunications
GOVE Government
FINA Finance brokers
ACCT Legal, accounting & other prof. services
UTIL Utilities
WHOL Wholesale
DIST Distribution
SERV Service Industry
BNPL Buy Now Pay Later
OTHB Not elsewhere included
FGOV Federal Government
SGOV State Government
LGOV Local Government
INDU Industries
MISC Miscellaneous
OTHA Other
8.30 Transfer Reason

Transfer Reason Code Table
Code Description
M Credit Provider has merged/ been taken over
R Account Transfer Reversal
X Account Sold
137
8.31 Term of Loan Unit Type
Unit Term Type Code Table
Code Description
Days Days
Weeks Weeks
Months Months
Years Years
138
9 Examples
Sample request and response XML messages are included in this documentation package. The intentions of these
samples are to illustrate the interactions and possible data variations when using the Equifax Apply WSDL. Note
that these are samples only and do not contain complete sets of data.
9.1 Request
1. equifax-apply-sample-request-2.0.6
This is a sample request where we have used the applicant’s personal details and requested two scores;
Equifax Apply Consumer+Commercial Negative and Equifax Apply Consumer+Commercial Comprehensive.
2. equifax-commercial-apply-individual-sample-request-2.0.6
This is a sample request where we have used the applicant’s personal details and requested the Equifax
Commercial Apply Commercial+ Consumer Comprehensive score.
3. Sample-request-by-id-2.0.6
This is a sample request by enquiry ID. You must have a valid enquiry ID from a previous transaction in order
to retrieve responses in this way.
4. equifax-apply -sample-request-telco-2.0.6
VedaScore 1.1 Consumer+Commercial and Equifax Apply (Telco) Consumer+Commercial Negative.
5. equifax-apply -sample-request-utility-2.0.6
This is a sample request where we have used the applicant’s personal details and requested the Equifax Apply
(Utility) Consumer+Commercial Negative score.
6. equifax-apply -sample-request-alternative-lender-2.0.6
This is a sample request where we have used the applicant’s personal details and requested the Equifax Apply
(Alternative Lending) Consumer+Commercial Negative score.
7. equifax-apply-sample-request-guarantor-2.0.6
This is a sample request where we have used the guarantor’s personal details and requested two scores;
VedaScore 1.1 Consumer+Commercial and Equifax Apply Consumer+Commercial Comprehensive.
8. equifax-apply-with-trading-history-sample-request-2.0.6
Equifax Apply Consumer+Commercial Negative and Equifax Apply Consumer+Commercial Comprehensive
AND requested trading history information for the businesses and companies related to the individual.
9. equifax-apply-sample-request-with One score-2.0.6
This is a sample request where we have used the applicant’s personal details and requested two scores (One
Score and Equifax Apply Negative Score) for permission type consumer plus commercial.
139
9.2 Response
1. sample-ban-response-2.0.6
This is a sample response in the event that the individual has placed a File Ban on their record in the Bureau.
2. sample-error-response-2.0.6
This is a sample response in the event that some error has occurred during product fulfilment. In this case, the
requestor has requested an invalid product data level associated to their subscriber settings.
3. sample-async-ticket-response-2.0.6
This is a sample response in the event where the requestor had used an asynchronous operation.
4. sample-sync-ticket-response-2.0.6
This is a sample response in the event where the requestor had used a synchronous operation however for
some reason the system was not able to complete the request within the service response window.
5. equifax-apply-sample-full-response-2.0.6
This is a sample response to a request for credit information on an applicant with permission type
Consumer+Commercial (XY). This response illustrates several product features including:
⮚ FIR across identity details
⮚ Consumer credit information with FIR and sample data across all element levels
⮚ Commercial credit information with FIR and sample data across all element levels
⮚ Public credit information with FIR and sample data across all element levels
⮚ Genesis Data BlockTM (only a subset is included in this sample)
⮚ Multiple scores and corresponding Key Contributing Factors

6. equifax-commercial-apply-individual-sample-full-response-2.0.6
This is a sample response to a request for credit information on an applicant with permission type
Commercial+Consumer (YX). This response illustrates several product features including:
⮚ Genesis Data BlockTM (only a subset is included in this sample)

7. equifax-apply-sample-response-special-score-v2.0.6
This is a sample response to a request for credit information on an applicant with a personal insolvency. This
response illustrates special scores.
8. equifax-apply- sample-full-response-telco-2.0.6
140
This is a sample response to an Equifax Apply (Telco) request for credit information on an applicant with
permission type Consumer+Commercial (XY). This response illustrates several product features including:
⮚ Genesis Data BlockTM and Telco Data Block (Negative characteristics)

9. equifax-apply- sample-full-response-utility-2.0.6
This is a sample response to an Equifax Apply (Utility) request for credit information on an applicant with
⮚ Genesis Data BlockTM and Utility Data Block (Negative characteristics)
⮚ Negative score and corresponding Key Contributing Factors

10. equifax-apply- sample-full-response-alternative-lending-2.0.6
This is a sample response to an Equifax Apply (Alternative Lending) request for credit information on an
applicant with permission type Consumer+Commercial (XY). This response illustrates several product features
including:
⮚ Genesis Data BlockTM and Alternative Lending Data Block (Negative characteristics)
⮚ Negative score and corresponding Key Contributing Factors
11. equifax-apply- sample--response-guarantor-2.0.6

This is a sample response to a comprehensive Equifax Apply request for credit information on a guarantor with
⮚ Comprehensive consumer credit information with FIR and sample data across all element levels
141
⮚ Genesis Data BlockTM
12. equifax-apply- sample-no-match-response -2.0.6

This is a sample no-match response to a comprehensive Equifax Apply request for credit information on an
applicant with permission type Consumer+Commercial (XY). This response illustrates several product features
including:
⮚ Applicant’s personal details as supplied
⮚ Score and corresponding Key Contributing Factors
13. equifax-apply-with-trading-history-sample-response-2.0.6
This is a sample response to requesting trading history information. This response illustrates how the
individual trading history information is returned in the report.
14. equifax-apply-sample-full response-with-One Score-2.0.6
This is a sample response with the One Score. This response illustrates how the Equifax One Score is returned
in the report on an applicant with permission type Consumer+Commercial (XY). This response illustrates
several product features including:
⮚ Applicant’s personal details as supplied
⮚ Score and corresponding Key Contributing Factors
⮚ Alternative Lending Block
142
2. Appendix A –Tips for Matching to Individual Bureau Files
The ability to retrieve and match the subject of an enquiry is dependent on the amount and integrity of identity
data provided. Obviously, the better the quality and quantity of identity data provided, the higher the probability
that the bureau is able to retrieve and match the subject of enquiry and the better the credit decision can be.
As Name and Date of Birth are not unique including additional identifiers can ensure the optimal matching results
are obtained. Include previous residential addresses, date of birth, gender, Australian Driver’s Licence number,
middle name and employer name.
Collect and supply as much identity detail as possible:

Seq. No XML Element Notes
2.2.1.2 family-name Always supply a surname
2.2.1.3 first-given-name Ensure the full legal name of the individual is used not the
nickname, contraction or anglicised version
2.2.1.4 other-given-name Supply the middle name, if provided as this also increases match
rate – there are fewer John Michael Smith than John Smith
2.2.4.1 address Only supply Australian residential address/es. Do not supply PO

Box addresses
2.2.4.1.3 property
2.2.4.1.4 unit-number
2.2.4.1.5 street-number
2.2.4.1.6 street-name Ensure the street type does not appear here e.g. “Phillip” not
“Phillip St”
2.2.4.1.7 street-type Valid Street types only
2.2.4.1.8 suburb Ensure the suburb is correct for the postcode
2.2.4.1.9 state
2.2.4.1.10 post-code Ensure the postcode is correct for the suburb
2.2.5 drivers-licence Always include a driver’s licence number, when available, it is very
important for matching
2.2.6 gender-code Gender also increases match rate

2.2.7 date-of-birth Always supply a date of birth – there are often people with the
same name living at the same address e.g. John Smith and John
Smith (father and son)
2.2.8 employer Always supply employer as this can increase your match rate.
If the subject of the enquiry has moved in the last 3 years, it is recommended that both current
and previous addresses are provided. If the subject has resided in another state/territory, enter
this as the previous residential address, regardless of timeframe.
143
Example: An individual moves from Victoria to Queensland and 6 months later applies for credit. They have a
new address and a new driver’s licence, that are not stored on the Equifax Bureau and name and date of birth are
not unique so no definite match can be found. Supplying the previous address in Victoria provides a link to the
existing file and the details are matched and updated.
XML Element Enquiry On the Bureau

family-name Smith = Smith
first-given-name John = John
other-given-name Michael = Michael
address Current Current
property
unit-number 31
street-number 466 45
street-name Ann Edward
street-type Street
≠ Street
suburb Brisbane Brunswick East
state QLD Vic
post-code 4000 3057
drivers-licence 744566A 125688W
gender-code M = M
date-of-birth 1978-10-21 = 1978-10-21
employer Brisbane City Council ≠ Premier Bank
144
3. Appendix B –Tips for entering Driver Licence Number
Australian Driver’s Licence Number is an important identifier when matching to individual bureau files. However,
an incorrectly typed driver licence in an Equifax Apply request results in an error, impacting your completion rates
and match rates.
Equifax highly recommends customers to provide the following restrictions into the Online Form/User Interface
during driver licence’s entry:
● Length of the driver licence is minimum 4, maximum 9 characters
● Valid characters are Alpha and Numeric
● No special characters or blanks/spaces
● Must have at least 4 numeric characters.
● Must have no more than 2 alpha characters.
● The third and fourth characters must be numeric.
Also, Equifax analysed common error patterns and to facilitate correct processing of a request recommends the
following tips for entering Driver’s Licence Numbers.
a) Do not enter card number instead of the licence number for New South Wales Driver Licence
When submitting licence number from an NSW Driver Licence, please do not provide the card number instead of
the licence number. The figure below illustrates where the card number and licence number are placed in the
licence. The card number is 11 digits (XX XXX XXX XXX), placed at the top right corner. The licence number is
placed just below the address and has 9 digits.
b) Do not enter special characters in between the licence number

When submitting licence number care must be taken that they are no special characters in the input. Some
common special characters that have been seen in errored requests include
Character Name
# Number Sign (Hash)
- Hyphen
145
. Full Stop
@ At Sign
( Left Parenthesis
) Right Parenthesis
* Asterix
For example, 123456789 is a valid input but 123-456-789 is an invalid input.
c) Leave field blank in the absence of an Australian Driver’s Licence
If the individual does not have an Australian Driver’s Licence, please leave the driver’s licence field blank. Any
other input in this scenario would lead to an error. Some common inputs that have resulted in errors are:
INPUT
N/A or n/a
Don’t Have One
An Overseas Driver Licence Number
Individual’s Name
Name of another country
d) Do not include spaces in between the driver’s licence number
Do not enter a licence number that has spaces in between the digits, this will result in an error.
For example, ‘129 129 129’ in an incorrect input and ‘129129129’ is the correct input.
e) Do not prefix the state where the licence was issued.
Only the licence number needs to be provided. If you prefix the state before the licence number this becomes a
valid response.
For example, NSW123456 is an invalid input and 123456 is a valid input.
f) Remove leading zeros from 10 digit driver’s licence numbers

In Victoria 9-digit driver’s licence numbers are being shown as 10 digits. Please remove the leading zero.
e.g. 0123456789 should be shown as 123456789.
146
4. Appendix C –Hybrid & Asynchronous Ticket Response Testing
The Customer Testing Area (CTA) provides a dedicated endpoint for customers to test and validate their
integration against a fully-functional instance of the Equifax Apply web service:
https://ctaau.apiconnect.equifax.com.au/cta/sys2/soap11/vedascore-apply-v2-0
In addition to the standard functionality, this endpoint also enables customers to simulate particular scenarios,
e.g. ticket responses. These scenarios can be triggered by assigning a specific value to the <operator-name>
element in the <enquiry-header> section of the XML request payload.
…
<vs:enquiry-header>
<vs:client-reference>MY-REF-101</vs:client-reference>
<vs:operator-id>101</vs:operator-id>
<vs:operator-name>test-hybrid-success</vs:operator-name>
<vs:permission-type-code>XY</vs:permission-type-code>
<vs:product-data-level-code>C</vs:product-data-level-code>
<vs:requested-scores>
<vs:scorecard-id>VSA_2.0_XY_NR</vs:scorecard-id>
<vs:scorecard-id>VSA_2.0_XY_CR</vs:scorecard-id>
</vs:requested-scores>
</vs:enquiry-header>
…
In the above example, the test-hybrid-success value is used to trigger a “ticket” scenario, where the service returns
an enquiry-id rather than a full report, thus simulating the event of the service switching from synchronous to
asynchronous delivery. The caller should then be able to use the enquiry ID returned in the ticket response to
retrieve the report by calling the retrieveEnquiryByID operation on the same service end point.
The following table describes the test scenarios supported by the CTA endpoint:
Trigger Value Service Operation Description

test-hybrid-success submitEnquiry This returns a ticket with a valid enquiry-id. Any subsequent calls to
retrieveEnquiryByID will return the actual credit report.
test-hybrid-fail submitEnquiry This returns a ticket with a mock enquiry-id. As a result, any subsequent
calls to retrieveEnquiryByID will return a “document not found” error.
test-async-fail submitEnquiryAsync This returns a ticket with a mock enquiry-id. As a result, any subsequent
calls to retrieveEnquiryByID will return a “document not found” error.

The CTA end point for Equifax Apply (Telco) and Equifax Apply (Utility) products is the same as the
standard Equifax Apply product.

The CTA end point for Equifax Apply (Alternative Lending) is the same as the standard Equifax Apply
product.
147

API Connect Individual Product Guide (EAandECA) v.1.33

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

API Connect Individual Product Guide (EAandECA) v.1.33

Uploaded by

Copyright:

Available Formats

Equifax Apply &

Revision Number: 1.33

Issue Date: 14/09/2023

Revision Date Description

1.9 05/03/2015 Updated the descriptions of last-extract-date/time, last-update-date/time response fields to

1.28 01/04/2022 v1.28 is now final

Key Product Features 24

Key Technical Features 32

Request & Response Message Specifications 42

Other Response Considerations 113

Code Tables 115

Appendix A –Tips for Matching to Individual Bureau Files 137

Appendix B –Tips for entering Driver Licence Number 139

Appendix C –Hybrid & Asynchronous Ticket Response Testing 141

1.1 Individual consumer credit versus individual commercial credit

This Guide covers the following products:

Note for Access Seekers

Note for Telcos and Utilities

Note for Alternative Lending Customers

Note for Telcos and Utilities

Note for Alternative Lending customers

Product name Equifax Apply Controlled via

Permission type Consumer Consumer + Commercial Request data

Data Level Negative* Comprehensive** Negative* Comprehensive** Request data

Scorecard IDs VSA_2.0_X_NR ONE_1.0_X_CR~ VSA_2.0_XY_NR ONE_1.0_XY_CR~ Request data

VS_1.1_X_NR VSA_2.0_X_CR VS_1.1_XY_NR VSA_2.0_XY_CR

Product name Equifax Commercial Apply Controlled via

VS_1.1_YX_NR CCAI_2.0_YX_NR VS_1.1_Y_NR

Product version 2.0

Product Equifax Commercial Apply (Telco) Controlled via

Product 2.0 2.0 End point

Product name Equifax Apply (Utility) Equifax Commercial Controlled via

Product version 2.0 2.0 End point

VS_1.1_X_NR VS_1.1_XY_NR VS_1.1_YX_NR

Product name Equifax Apply (Alternative Lending) Controlled via

Product version 2.0 End point

Permission type Consumer Consumer + Commercial Request data

Data Level Negative Negative Request data

* For use by Credit Provider subscribers.

Explanation of Scorecard Id:

Note for Access Seekers

Note for Telcos and Utilities

Note for Alternative Lending customers

2.1 Product version

2.2 Permission type

Note for Telcos and Utilities

Note for Alternative Lending customers

2.3 Data level

Note for Access Seekers

Note for Telcos and Utilities

Note for Comparison Sites

Note for Alternative Lending customers

2.5 Individual Trading History Information

3.1 Full Identity Reporting

In the API Connect schema, FIR functionality is implemented using:

Note for Telcos and Utilities

3.2 Accounts and defaults

3.2.1 Account structure

3.2.2 Account data level

Account data level

Original Credit Provider ✔ ✔ ✔ ✔ ✔

Latest Credit Provider ✔ ✔ ✔ ✔ ✔

Account Holder Count 🗶 🗶 🗶 ✔ ✔