CAIS is our shared database of consumer credit information. CAIS members – organisations who give consumer credit – share their consumers’ credit performance data with us. In return, they benefit from access to the rest of the CAIS database, to the same level as the data they contribute. They can then use this data to improve decision making when consumers apply for credit or other financial services.
Membership is available to companies who give consumer credit or lend to consumers. Members must also:
CAIS membership is available at either ‘default’ or ‘full’ data levels and the member will be entitled to retrieve the same level of data in return. Standard full subscribers provide monthly data on all accounts – positive, delinquent and default. Default-only subscribers provide monthly data on all accounts that are in default.
If you’d like to join CAIS, the first step is to contact your Experian account manager. They’ll confirm whether your business is eligible and provide you with the relevant documents, including copies of the CAIS File Layout Specification, the Principles of Reciprocity and the Principles for the Reporting of Arrears, Arrangements and Defaults at Credit Reference Agencies.
In return the account manager will need copies of credit application forms for Experian to verify that the consent and notification clauses are suitably worded, as required by the Data Protection Act 1998 or, from May 2018, the GDPR (recommended wordings for the clauses may be found on the Experian website under Compliance). You’ll also need to produce confirmation of a consumer credit license and Data Protection registration.
Before becoming a member, you’ll need to compile a test file of data to ensure the data is formatted and submitted correctly and is of acceptable quality. As you’re preparing the test file, you’ll be asked to sign the CAIS agreement and the CAIS control team will allocate a unique source code to identify the portfolio. Once the test data is approved you’ll be granted access to the CAIS database.
Once accepted to CAIS, your portfolio will be held on our database and identified by the source code, which should be included in the header record of each update. CAIS members are obliged to supply updated to their data each month. Each monthly update is validated before it is loaded to the database, building up a clear picture of each customer with the latest balance information and, in the case of full data, accumulating a history of payment performance.
To ensure that CAIS reporting is fair and accurate, as required under the Data Protection Act 1998 (superseded by the GDPR from May 2018), it is essential that each month’s submission is timely, contains a complete file, is an accurate reflection of each customer, and is consistent with the data reported in previous months.
New members gain access to CAIS data on signing the contract and must load their first batch of data within three months. They also agree to follow a number of specific rules – for example, they must provide data files every month and make sure the data meets our quality requirements.
Timing of extracts
The first CAIS extract should be taken at a time when the data will reflect an up to date picture of the accounts most accurately. Future updates will then be expected at the same point in subsequent months.
CAIS membership is governed by the Principles of Reciprocity, administered by the Steering Committee on Reciprocity (SCOR). These principles provide a framework of regulation covering the supply and use of credit account data to credit reference agencies and have been endorsed by all of the appropriate credit industry trade associations.
Members also follow the Principles for the Reporting of Arrears, Arrangements and Defaults at Credit Reference Agencies – industry guidance issued to standardise the way different sectors report data.
We’ll provide copies of both documents when you become a CAIS member.
Under the Data Protection Act 1998 (superseded by the GDPR from May 2018) and the Consumer Credit Act 1974 (CCA) consumers have the right to quickly access the data held on their credit files by credit reference agencies. Under section 159 of the CCA, they also have specific statutory rights to challenge entries they feel are inaccurate. These rights ensure that a necessary balance is maintained between the interests of lenders and the rights of individuals.
If a consumer chooses to challenge a credit file entry with Experian under section 159 of the CCA, we’re required to provide a response to the consumer within 28 days, letting them know whether the entry has been deleted or amended, or whether no action has been taken.
As the vast majority of disputes relate to data provided by lenders, we can only take the relevant action and provide a response if we’ve investigated the record with the relevant lender and been given the necessary information. If the lender does not make a timely response we have to suppress the record in question, even though it may subsequently prove to be accurate.
Upholding consumer rights therefore relies heavily on the cooperation of lenders. In order to ensure that (i) the consumer receives a response within the statutory 28-day period and (ii) correct entries are not supressed from the credit file, we require lenders to respond to us within 14 days of receipt.
Our Data Query Console (DQC) aims to make this process as simple and efficient as possible. The DQC is an easy-to-use, web-based system that will show all queries outstanding and all archived queries that have already been responded to. When clients complete a query, this will be sent back to Experian and removed from the outstanding queries list instantly. Further information on the DQC will be provided when you become a CAIS member.
If an update cannot be supplied on the entire portfolio for one particular month, on loading the next month’s data, a question mark (?) will be inserted on each affected record representing the missing month’s status.
If an update cannot be supplied on an individual account for one month, on loading the next month’s data, a question mark (?) will be inserted on each affected record representing the missing month’s status.
A file of records will contain three types of record, all of which must be 530 bytes in length:
Whether you’re sending test or live data, each file submitted to Experian must contain these three record types in that order. All files must also be complete and consistent. Where files for various portfolios (such as subsidiaries) are drawn from different locations or systems, these should be treated as separate sources, with each having their own identifying source code and update process.
When a file is submitted at full data-sharing level, every month it must contain any new accounts opened since the last extract, together with updates to records previously submitted to CAIS. It must also contain any accounts that have settled (or closed) since the previous update, for example account that are fully repaid. Any account that has moved into default should also be reported with the valid default details where appropriate. Any subsequent changes to the default, such as changes in the current balance, should also be reported.
Where the file is submitted at a default-only level, every month it must contain any new defaults since the last extract, together with any updates to defaults previously reported into CAIS.
The following is the technical overview for data produced in the CAIS2007 file format for submission to Experian. CAIS2007 is the latest format and replaces the CAIS2006, CAIS2004, CAISPlus, Year 2000 and pre-Year 2000 versions.
When preparing data files, please also refer to any other relevant documents such as the latest version of the Principles of Reciprocity, Principles for the Reporting of Arrears, Arrangements and defaults at Credit Reference Agencies, plus any service-level agreement you may have in place with Experian.
Header record
The first record on the file must be a header record as follows:
Description of Item |
Contents and format |
Starting byte |
End |
Field length |
Header identifier |
‘ HEADER’ |
1 |
20 |
20 |
Source code |
‘NNN’ |
21 |
23 |
3 |
Date created |
DDMMCCYY |
24 |
31 |
8 |
Company / portfolio name |
Alphanumeric |
32 |
61 |
30 |
Filler |
Blanks |
62 |
81 |
20 |
CAIS version indicator |
CAIS2007 |
82 |
89 |
8 |
Overdraft reporting cut-off |
££££££ |
90 |
95 |
6 |
Card behavioural sharing flag |
Y or blank |
96 |
96 |
1 |
Filler |
Blanks |
97 |
530 |
434 |
Total bytes |
Account records
After the header record all of the individual customers’ account records must be in the following layout:
Description of Item |
Contents and format |
Starting byte |
End byte |
Field length |
Account number |
Alphanumeric |
1 |
20 |
20 |
Account type |
Numeric |
21 |
22 |
2 |
Start date |
DDMMCCYY |
23 |
30 |
8 |
Close date |
DDMMCCYY |
31 |
38 |
8 |
Monthly payment |
££££££ |
39 |
44 |
6 |
Repayment period |
Numeric |
45 |
47 |
3 |
Current balance |
£££££££ |
48 |
54 |
7 |
Credit balance indicator |
Blank or ‘-’ |
55 |
55 |
1 |
Account status |
0, 1, 2, 3, 4, 5, 6, U, 8, D |
56 |
56 |
1 |
Special instruction indicator |
D, A, L or blank |
57 |
57 |
1 |
Experian block |
Blank |
58 |
207 |
150 |
Payment amount |
££££££ |
208 |
213 |
6 |
Credit payment indicator |
Blank or ‘-’ |
214 |
214 |
1 |
Previous statement balance |
££££££ |
215 |
220 |
6 |
Previous statement balance indicator |
Blank or ‘-’ |
221 |
221 |
1 |
Number of cash advances |
Numeric |
222 |
223 |
2 |
Value of cash advances |
££££££ |
224 |
229 |
6 |
Payment code |
M or blank |
230 |
230 |
1 |
Promotion activity flag |
Y, N or blank |
231 |
231 |
1 |
Filler 1 |
Blank |
232 |
262 |
31 |
Transient association flag |
T or blank |
263 |
263 |
1 |
Air-time flag |
L, B, D or blank |
264 |
264 |
1 |
Flag settings |
D, A, I, V, R, G, Q, M, C, P, S |
265 |
265 |
1 |
Name and address |
Alphanumeric |
266 |
440 |
175 |
Credit limit |
£££££££ |
441 |
447 |
7 |
Date of birth |
DDMMCCYY |
448 |
455 |
8 |
Filler 2 |
Blank |
456 |
456 |
1 |
Transferred to collection account flag |
Y or blank |
457 |
457 |
1 |
Balance type |
A, P or blank |
458 |
458 |
1 |
Credit turnover |
£££££££££ |
459 |
467 |
9 |
Primary account indicator |
Y, N or blank |
468 |
468 |
1 |
Default satisfaction date |
DDMMCCYY |
469 |
476 |
8 |
Transaction flag |
0, 1 or blank |
477 |
477 |
1 |
Filler 3 |
Blank |
478 |
502 |
25 |
Original default balance |
£££££££ |
503 |
509 |
7 |
Payment frequency |
W, F, M, Q, A, P or Blank |
510 |
510 |
1 |
New account number |
Alphanumeric |
511 |
530 |
20 |
Total bytes |
530 |
Trailer record
The last record on the file must be a trailer record as follows:
Description of Item |
Contents and format |
Starting byte |
End byte |
Field length |
Trailer identifier |
‘99999999999999999999’ |
1 |
20 |
20 |
Total records |
Numeric |
21 |
28 |
8 |
Filler |
Blanks |
29 |
530 |
502 |
Total bytes |
530 |
Each of the fields on CAIS records has a set of requirements and constraints. Any errors may result in either data becoming corrupted or an entire file being rejected, so please take time to ensure each field is correctly filled.
Header record
Header identifier
Starting byte: |
1 |
Ending byte: |
20 |
Character type: |
Alpha |
Example: |
‘ HEADER’ |
Position: |
Right justified with leading blanks |
Source code number
Starting byte: |
21 |
Ending byte: |
23 |
Character type: |
Numeric |
Example |
‘012’ |
Position: |
Right justified, filled with leading zero where appropriate |
Date of creation
Starting byte: |
24 |
Ending byte: |
31 |
Character type: |
Numeric |
Example: |
‘24052010’ |
Position: |
Right justified, filled with leading zeros where appropriate |
Company / portfolio name
Starting byte: |
32 |
Ending byte: |
61 |
Character type: |
Alphanumeric |
Example: |
‘ABC Bank Plc ’ |
Position: |
Left justified with following blanks |
Filler
Starting byte: |
62 |
Ending byte: |
81 |
Character type: |
Blanks |
CAIS version indicator
Starting byte: |
82 |
Ending byte: |
89 |
Character type: |
Alphanumeric |
Example: |
CAIS2007 |
Overdraft reporting cut-off
Starting byte: |
90 |
Ending byte: |
95 |
Character type: |
Numeric |
Example: |
001250 |
Position: |
Right justified, filled with leading zeros where appropriate |
Card behavioural sharing flag
Starting byte: |
96 |
Ending byte: |
96 |
Character type: |
Alpha |
Example: |
Y |
Filler
Starting byte: |
97 |
Ending byte: |
530 |
Character type: |
Blanks |
Customer account records
Account number
Starting byte: |
1 |
Ending byte: |
20 |
Character type: |
Alphanumeric |
Example: |
12345B6789B |
Position: |
Left justified with following blanks where appropriate |
Account types
Starting byte: |
21 |
Ending byte: |
22 |
Character type: |
Numeric |
Example: |
02 |
Position: |
Right justified, filled with leading zero where appropriate |
Start date
Starting byte: |
23 |
Ending byte: |
30 |
Character type: |
Numeric |
Example: |
03071999 |
Position: |
Right justified, filled with leading zeros where appropriate |
Close date
Starting byte: |
31 |
Ending byte: |
38 |
Character type: |
Numeric |
Example: |
30072000 |
Position: |
Right justified, filled with leading zeros where appropriate |
a) The date of settlement for records at status U, 0, 1, 2, 3, 4, 5 or 6.
b) The date of default for records at status 8.
Monthly payment
Starting byte: |
39 |
Ending byte: |
44 |
Character type: |
Numeric |
Example: |
000200 |
Position: |
Right justified, filled with leading zeros where appropriate |
Repayment period
Starting byte: |
45 |
Ending byte: |
47 |
Character type: |
Numeric |
Example: |
048 |
Position: |
Right justified, filled with leading zeros where appropriate |
Current balance
Starting byte: |
48 |
Ending byte: |
54 |
Character type: |
Numeric |
Example: |
0003600 |
Position: |
Right justified, fill with leading zeros where appropriate |
Credit balance indicator
Starting byte: |
55 |
Ending byte: |
55 |
Character type: |
Alpha |
Example: |
‘ ’ if in debit, ‘-’ if in credit |
Account status codes
Starting byte: |
56 |
Ending byte: |
56 |
Character type: |
Alphanumeric |
Example: |
0 |
Special instruction indicator
Starting byte: |
57 |
Ending byte: |
57 |
Character type: |
Alpha |
Example: |
L |
Experian block
Starting byte: |
58 |
Ending byte: |
207 |
Character type: |
Blanks |
Payment amount
Starting byte: |
208 |
Ending byte: |
213 |
Character type: |
Numeric |
Example: |
000360 |
Position: |
Right justified, filled with leading zeros where appropriate |
Credit payment indicator
Starting byte: |
214 |
Ending byte: |
214 |
Character type: |
Alpha |
Example: |
Blank if in debit, ‘-’ if in credit |
Previous statement balance
Starting byte: |
215 |
Ending byte: |
220 |
Character type: |
Numeric |
Example: |
001234 |
Position: |
Right justified, filled with leading zeros where appropriate |
Previous statement balance indicator
Starting byte: |
221 |
Ending byte: |
221 |
Character type: |
Alpha |
Example: |
Blank if in debit, ‘-’ if in credit |
Number of cash advances
Starting byte: |
222 |
Ending byte: |
223 |
Character type: |
Numeric |
Example: |
02 |
Position: |
Right justified, filled with leading zeros where appropriate |
Value of cash advances
Starting byte: |
224 |
Ending byte: |
229 |
Character type: |
Numeric |
Example: |
000500 |
Position: |
Right justified, filled with leading zeros where appropriate |
Payment code
Starting byte: |
230 |
Ending byte: |
230 |
Character type: |
Alpha |
Example: |
M |
Promotion activity flag
Starting byte: |
231 |
Ending byte: |
231 |
Character type: |
Alpha |
Example: |
Y |
Filler 1
Starting byte: |
232 |
Ending byte: |
262 |
Character type: |
Blanks |
Transient association flag
Starting byte: |
263 |
Ending byte: |
263 |
Character type: |
Alpha |
Example: |
T |
Air-time retailer flag
Starting byte: |
264 |
Ending byte: |
264 |
Character type: |
Alpha |
Example: |
L |
Flag setting
Starting byte: |
265 |
Ending byte: |
265 |
Character type: |
Alpha |
Example: |
A |
Name and address
Starting byte: |
266 |
Ending byte: |
440 |
Character type: |
Alphanumeric |
Example: |
Mr John W Brown Rose Cottage 5 Main Street Beeston Nottingham, Nottinghamshire NG8 1JD |
Position: |
Left justified with following blanks |
Name 39 characters
Address line 1 32 characters
Address line 2 32 characters
Address line 3 32 characters
Address line 4 32 characters
Postcode 8 characters
Credit limit
Starting byte: |
441 |
Ending byte: |
447 |
Character type: |
Numeric |
Example: |
0005000 |
Position: |
Rights justified, filled with leading zeros as appropriate |
Date of birth
Starting byte: |
448 |
Ending byte: |
455 |
Character type: |
Numeric |
Example: |
13051978 |
Position: |
Right justified, filled with leading zeros as appropriate |
Filler 2
Starting byte: |
456 |
Ending byte: |
456 |
Character type: |
Blanks |
Transferred to collection account flag
Starting byte: |
457 |
Ending byte: |
457 |
Character type: |
Alpha |
Example: |
Y |
Balance type
Starting byte: |
458 |
Ending byte: |
458 |
Character type: |
Alpha |
Example: |
P |
Credit turnover
Starting byte: |
459 |
Ending byte: |
467 |
Character type: |
Numeric |
Example: |
000012345 |
Position: |
Right justified, filled with leading zeros where appropriate |
Primary account indicator
Starting byte: |
468 |
Ending byte: |
468 |
Character type: |
Alpha |
Example: |
Y |
Default satisfaction date
Starting byte: |
469 |
Ending byte: |
476 |
Character type: |
Numeric |
Example: |
14092012 |
Position: |
Right justified, filled with leading zeros where appropriate |
Transactions flag
Starting byte: |
477 |
Ending byte: |
477 |
Character type: |
Numeric |
Example: |
1 |
Filler 3
Starting byte: |
478 |
Ending byte: |
502 |
Character type: |
Blanks |
Original default balance
Starting byte: |
503 |
Ending byte: |
509 |
Character type: |
Numeric |
Example: |
0005000 |
Position: |
Right justified, filled with leading zeros where appropriate |
Payment frequency indicator
Starting byte: |
510 |
Ending byte: |
510 |
Character type: |
Alpha |
Example: |
W |
New account number
Starting byte: |
511 |
Ending byte: |
530 |
Character type: |
Alphanumeric |
Example: |
12345B6789B |
Position: |
Left justified, with following blanks |
Trailer record
Trailer identifier
Starting byte: |
1 |
Ending byte: |
20 |
Character type: |
Numeric |
Example: |
99999999999999999999 |
Total number of records
Starting byte: |
21 |
Ending byte: |
28 |
Character type: |
Numeric |
Example: |
01234567 |
Position: |
Right justified, with leading zeros where appropriate |
Filler
Starting byte: |
29 |
Ending byte: |
530 |
Character type: |
Blanks |
Listed below are the fields that are required and whether or not they are mandatory for either a full or a default CAIS record. These requirements may change from time to time following amendments to the Principles of Reciprocity and mandatory fields are subject to change.
Description of field |
Default CAIS record |
Full CAIS record |
Account number |
Mandatory |
Mandatory |
Account type |
Mandatory |
Mandatory |
Start date |
Mandatory |
Mandatory |
Close date |
Mandatory |
Mandatory when applicable |
Monthly payment |
Not applicable |
Mandatory for certain account types |
Repayment period |
Not applicable |
Mandatory for certain account types |
Current balance |
Mandatory |
Mandatory |
Credit balance indicator |
Not applicable |
Where applicable |
Account status |
Mandatory |
Mandatory |
Special instruction indicator |
Where applicable |
Where applicable |
Experian block |
Not applicable |
Not applicable |
Payment amount |
Where applicable |
Mandatory for certain account types |
Credit payment indicator |
Where applicable |
Mandatory for certain account types |
Last statement balance |
Where applicable |
Mandatory for certain account types |
Last statement balance indicator |
Where applicable |
Mandatory for certain account types |
Number of cash advances |
Where applicable |
Mandatory for certain account types |
Value of cash advances |
Where applicable |
Mandatory for certain account types |
Payment code |
Where applicable |
Mandatory for certain account types |
Promotion activity flag |
Where applicable |
Mandatory for certain account types |
Transient association flag |
Where applicable |
Where applicable |
Air-time flag |
Optional for air-time companies only |
Optional for air-time companies only |
Flag settings |
Mandatory for certain flags when applicable |
Mandatory for certain flags when applicable |
Name & address |
Mandatory |
Mandatory |
Credit limit |
Not applicable |
Mandatory for certain account types |
Date of birth |
Mandatory |
Mandatory |
Transferred to collections account flag |
Where applicable |
Where applicable |
Balance type |
When applicable on certain account types |
When applicable on certain account types |
Credit turnover |
When applicable on certain account types |
When applicable on certain account types |
Primary account indicator |
When applicable on certain account types |
When applicable on certain account types |
Default satisfaction date |
When applicable |
Not applicable |
Transaction flag |
When applicable on certain account types |
When applicable on certain account types |
Payment frequency |
Not applicable |
Optional |
Original default balance |
Mandatory |
Not applicable |
New account number |
Where applicable |
Where applicable |
Type |
Title |
Description |
00 |
Blank |
Normally defaults, but can cover any type of bank account where the product can no longer be identified |
01 |
Hire purchase / conditional sale |
An account where goods remain the property of the lender until all repayments are made |
02 |
Unsecured loan (personal loans) |
An account covering the borrowing of a fixed amount which is not secured |
03 |
Mortgage |
A loan to purchase a property, which is secured by a mortgage deed until the final payment is made |
04 |
Budget (revolving account) |
An account or an agreement for the purchase of goods up to an agreed credit limit. A revolving account may involve numerous draw downs and repayments of a percentage of the balance, while the budget accounts credit facility is repaid by constant regular amounts |
05 |
Credit card / store card |
Where customers are allowed to spend up to an agreed credit limit, making repayments of a minimal value or a percentage of the outstanding balance |
06 |
Charge card |
Where customers can spend up to a credit limit but must pay the balance in full each month |
07 |
Rental – TV, brown or white goods |
Where the customer pays for the use of goods, which remain the property of the lender |
08 |
Mail order |
For all types of mail-order portfolios |
15 |
Current accounts |
For all portfolios operating along the lines of current accounts |
16 |
Second mortgage (secured loan) |
A loan secured against an asset or property, where the security ranks after the prime mortgage |
17 |
Credit sale fixed term |
Where the title to the goods passes to the customer on signing the agreement |
18 |
Communications |
Agreements used by mobile phone, cable or landline communication service providers |
19 |
Fixed-term deferred payment |
‘Buy now pay later’ arrangements. The conditions are similar to hire purchase and credit sale, except that the first payment is deferred for an agreed period of time |
20 |
Variable subscription |
Variable-rate hire purchase, where the monthly payments can vary depending on base rate adjustments |
21 |
Utility |
Covers gas, water and electricity, but not communications |
22 |
Finance lease |
Where the rental covers the total amount of the asset plus charges, meaning the lessor is not at risk |
23 |
Operating lease |
Where the lessee’s rentals do not cover more than 90% of the costs of the goods and charges, meaning the lessor is taking part of the risk |
24 |
Un-presentable cheques |
To be used by cheque guarantee companies for a bounced cheque |
25 |
Flexible mortgages |
An account that is secured by a mortgage deed until the final payment is made, but the account has flexible terms or elements of multiple products (for example, contains a current account in the main mortgage account) |
26 |
Consolidated debt |
Used where a CAIS member transfers multiple accounts into one collection account for the purposes of debt recovery – a process referred to as consolidating debt |
27 |
Combined credit account |
An account with multiple credit elements |
28 |
Payday loans |
Short terms loans, generally secured against salary payments and often no more than one month in length |
29 |
Balloon hire purchase |
An account where the goods remains the property of the lender until all repayments are completed, with a larger final payment |
30 |
Residential mortgage |
A loan for the purchase of the property that is secured by a mortgage deed until the final payment is made. Here, the property must be the primary home of the borrower |
31 |
Buy-to-let mortgage |
A loan for the purchase of a property that is secured by a mortgage deed until the final payment is made. Here, the borrower does not live in the property but leases it to others |
32 |
100+% loan-to-value mortgage |
A loan for the purchase of a property that is secured by a mortgage deed until the final payment is made and is over 100% loan-to-value ratio |
33 |
Current account off-set mortgage |
A loan for the purchase of a property that is secured by a mortgage deed until the final payment is made, where interest is off set with a current account |
34 |
Investment off-set mortgage |
A loan for the purchase of a property that is secured by a mortgage deed until the final payment is made, where interest is off set with an investment |
35 |
Shared-ownership mortgage |
A loan for the shared purchase of a property that is secured by a mortgage deed until the final payment |
36 |
Contingent liability |
Potential liabilities, such as guarantees |
37 |
Store card |
Where customers are allowed to spend up to an agreed credit limit with a specific retailer or group. Repayments are a minimal value or a percentage of the outstanding balance |
38 |
Multi-function card |
A card account with multiple elements |
39 |
Water |
A utility account for water services |
40 |
Gas |
A utility account for gas services |
41 |
Electricity |
A utility account for electricity services |
42 |
Oil |
A utility account for oil services |
43 |
Duel fuel |
An account covering multiple utility services |
44 |
Fuel Card (not motor fuel) |
An account covering utility services issued with a card |
45 |
House insurance |
Credit for house insurance services |
46 |
Car insurance |
Credit for car insurance services |
47 |
Life insurance |
Credit for life insurance services |
48 |
Health insurance |
Credit for health insurance services |
49 |
Card protection |
Credit for payment protection services on cards |
50 |
Mortgage protection |
Credit for payment protection services on mortgages |
51 |
Payment protection |
Credit for general payment protection services |
52 |
Not available in CAIS |
N/A |
53 |
Mobile |
An account for mobile phone services |
54 |
Fixed line |
An account for fixed line telecommunications |
55 |
Cable |
An account for cable entertainment services |
56 |
Satellite |
An account for satellite entertainment services |
57 |
Business line |
An account for business telecommunications |
58 |
Broadband |
An account for broadband services |
59 |
Multi communications |
An account for multiple communication services |
60 |
Student loan |
Loans for education purposes, usually from the Student Loan Company, provided under the terms of legislation and controlled by the Department of Education |
61 |
Home credit |
The provision of credit, typically for small-sum loans, on flexible terms. Repayments are collected in instalments by collectors who call at the customer’s home |
62 |
Education |
A loan for the purposes of education fees |
63 |
Not available in CAIS |
N/A |
64 |
Other rental |
Rental agreement where the customer makes payments for the use of goods |
65 |
Not available in CAIS |
N/A |
66 |
Not available in CAIS |
N/A |
67 |
Not available in CAIS |
N/A |
68 |
Not available in CAIS |
N/A |
69 |
Mortgage and unsecured loan |
For accounts where there is a mixture of a loan for the purchase of a property that is secured by a mortgage deed until the final payment is made and an unsecured element. Typically a >100% mortgage-type product |
70 |
Gambling |
A credit account used for the purpose of gambling (for example, spread betting) |
71 |
Basic bank account |
A bank account that allows the customer to receive money and pay bills, but has no overdraft facility |
Status code |
Description |
U |
Unclassified. The member is unable to make any statement, positive or adverse, on the performance of this account for the period in question. A U may be used for the an account when the first payment is yet to be made (for a maximum two months, unless it’s a buy-now-pay-later or Student Loan account) |
D |
Dormant. The account has been inactive for a period of time, usually with a zero balance. This code should be supplied each and every month until the account is used again or closed. |
0 |
In advance, up to date or less than one payment due but unpaid (or were due and unpaid when settled) |
1 |
More than one but less than two payments due but unpaid (or were due and unpaid when settled) |
2 |
More than two but less than three payments due but unpaid (or were due and unpaid when settled) |
3 |
More than three but less than four payments due but unpaid (or were due and unpaid when settled) |
4 |
More than four but less than five payments due but unpaid (or were due and unpaid when settled) |
5 |
More than five but less than six payments due but unpaid (or were due and unpaid when settled) |
6 |
Six or more payments due but unpaid or (or due and unpaid when settled) |
8 |
Defaulted balance. At the date of default the customer had failed to meet the contractual obligations and had failed to satisfactorily respond to requests that the account be put into order. The circumstances where an account should be defaulted are explained further in the Principles for the reporting of Arrears, Arrangements and Defaults at Credit Reference Agencies and members are advised to follow this as a guide to best practice. The main principles state that: · defaults should not normally be filed where the debt is less than three consecutive months in arrears. · accounts where payments have not been received for six months should normally be filed as default. · exceptions may apply where the credit is over a very short or very long term or where there is some element of fraud or insolvency. |
Flags should be used where they describe the current account relationship.
The hierarchy of CAIS flags is as follows. Where more than one applies the flag with the greatest hierarchy should be submitted. Where a flag currently exists it can only be replaced by one that’s higher up in the hierarchy. The only exception to this is gone away flags – see below.
Flag setting |
Description |
|
1 |
D |
Deceased |
2 |
P |
Partial or no settlement |
3 |
C |
Debt assigned (non-CAIS member) |
4 |
S |
Debt sold to CAIS member |
5 |
G |
Gone away |
6 |
R |
Recourse |
7 |
V |
Voluntary termination |
8 |
A |
Arrangement |
9 |
M |
Debt management programme |
10 |
I |
Credit insurance claim |
11 |
Q |
Account query |
Deceased (D)
Where you receive evidence that an account holder is deceased (for example a death certificate, probate or letters of administration) you should set a D flag.
Partial or no settlement (P)
Where a partial settlement has been agreed or the debt has been discharged by bankruptcy, a P flag should be set.
Debt assigned (C)
The debt-assigned (C) flag should be used where the rights to a debt have been assigned to a new owner who is not a member of CAIS and so will not be registering the debt on CAIS in their own name. The record remains in the original lender's name, shown as settled or satisfied, together with the debt-assigned flag to indicate that the record is closed due to its sale.
Debt sold to CAIS member (S)
The debt-sold-to-CAIS-member (S) flag should be used where the rights to a debt have been assigned to a new owner that is already a CAIS member. In this case, the new owners will continue to supply the performance of the record via their own portfolio. The original record will remain on CAIS indicated as sold to CAIS member, shown as settled or satisfied together with this flag to indicate the record is closed due to its sale.
Gone away (G)
Where the address of the customer is no longer known and the account is falling into arrears, a G flag should be used together with the last known address.
Recourse (R)
Where an account is invoked with a recourse agreement (for example between a dealer and a lender), the record should be set with an R flag.
Voluntary terminations (V)
A V flag can only be set if the record is a hire purchase agreement. It should be used: where a Consumer Credit Act Section 100 balance is outstanding and there is no arrangement (together with a CAIS status of 8); where a Section 100 balance is outstanding and there is an arrangement; and where a Section 100 balance has been met (in this case the account should be closed with the appropriate status code and a balance of zero).
Arrangement (A)
Where a customer is given a payment arrangement, the arrears against the original contract should be shown using the status code, together with an A flag. Where the customer is making monthly payments (on certain CAIS account types only) the payment amount should also be given.
Debt management programme (M)
The M flag should be used where the customer has entered into a debt management programme such as those run by the Citizens' Advice Bureau. The arrears against the original contract should be shown using the status code.
Credit insurance claim (I)
The I flag is set when the customer notifies the lender of the claim, along with a status of U for the life of the claim.
Account query (Q)
Where a query exists on an account, such as a merchandise complaint or a dispute over a defaulted account, the record should be flagged with the letter Q and a status of U or 8.
The following payment frequency indicators that can be supplied on a CAIS record:
CAIS flag |
Description |
W |
Weekly |
F |
Fortnightly |
M |
Monthly |
Q |
Quarterly |
A |
Annually |
P |
Periodically |
The following definitions provide guidelines for creating CAIS records for consumer current accounts. The guidance given for CAIS status codes has been taken from the BBA (British Bankers Association) proposal to SCOR regarding current account sharing and recognises that the operation of current accounts is more flexible and varied than that of other types of account. They therefore recognise that definitions have to cater for a range of circumstances. For each CAIS status code there is a selection of criteria that may trigger its use. However, these conditions may not automatically trigger the status code because current accounts are subject to a greater degree of manual review than other account types.
Start date:
The date the current account was opened.
Settlement date:
The date the account was closed.
Default date:
For CAIS 8 records, this is the date at which the lender decides the account has gone into default – as defined below – and has decided to file a CAIS 8 against that customer.
Credit limit:
The 'overdraft limit' as disclosed to the customer. Any shadow limit that the customer is not aware of should not be supplied in this field. Sharing overdraft limits is not mandatory as some lenders manage current accounts taking the wider customer picture into account. Here, reporting apparent excess whilst managing the position internally with a different approach could be misleading. You should provide this where appropriate.
Current balance:
This should be the 'overdraft balance' and indicates how amount by which the account is actually overdrawn. If the current account is in credit the current balance field should be populated with zeros and the credit balance indicator should be left blank. The nature of current accounts means there are several ways to calculate the balance field. For example, you could give the average monthly balance or a ‘snapshot’ as at the day the field was created. You should use the most appropriate way of representing your data.
Status codes:
These definitions act as a guideline for creating current account status codes that are consistent with those for other types of CAIS records. ‘Possible triggers’ recognise that current accounts are more flexible and varied than for other account types. They should not be seen as over prescriptive and it is recommended that you give the status codes you feel are most appropriate to your product and business.
Status 0: possible triggers
Given when:
Status 1: possible triggers
Given when:
Status 2: possible triggers
Given when:
Status 3: possible triggers
Given when:
Status 4-6: possible triggers
If status 3 has been set and the customer is showing no realistic attempt to repay the overdraft a status 8 would normally be set.
Stats 4-6 will normally only be needed if the customer has offered and is making a realistic effort to repay the overdraft, but the overdraft is more than three months beyond its repayment date and no formal arrangement is in place.
Status U: possible triggers
Given when:
Status D: possible triggers
Given when:
Status 8 – account in default: possible triggers
As with other types of credit, a number of factors may indicate that the contractual relationship with the customer has broken down. The below conditions must be considered alongside the Principles for the reporting of Arrears, Arrangements and Defaults at Credit Reference Agencies and the requirements under the banking code. The status code may be given when:
CAIS flags – D, P, C, G, A, M, I, Q, S:
Provided where appropriate to their current account relationship.
Balance type:
CAIS members may calculate the current balance in a variety of ways and the flag should be used to indicate this appropriately:
Credit turnover:
This field may be used for detecting money laundering activities and soft fraud, and assessing affordability. It should contain the value of all payments into the account during the last month, excluding any internal transfers from other accounts within the same organisation or group. It should also exclude any credit transactions from a savings account into the current account within the month.
Primary account indicator:
This field is used in assessing affordability. The performance of a primary account can be more predictive than a non-primary account. Populating this field indicates that you believe this record to be the customer’s primary current account, usually because the customer’s regular income is paid into the account.
Transactions flag:
This field is to indicate where cheques or direct debts from a current account have not been paid due to insufficient funds within the last month.
Below we’ve included guidelines for creating credit card and store card behavioural data-sharing fields within CAIS records, taken from the UK Cards proposal on behalf of credit and store card lenders. These fields will form part of the existing monthly CAIS data supplied for this type of account.
Payment amount:
This should include true payments only (not non-payment credits such as refund), credited to the account in the previous billing period after any reversals (such as a bounced cheque, direct debit or standing order). It may include multiple payments received in the same period.
The examples below show how the payment amount should be calculated. The guiding principle is to show the true net payment made within that particular payment cycle. Where the total of payment reversals is more than the total of payments made in that cycle, the payment amount will be negative.
Scenario 1
Customer pays £100 against their account in cycle 1 – payment amount field to show £100.
Scenario 2
Customer pays £500 in cycle 1 that bounces in cycle 1 and then pays £100 in cycle 1 – payment amount field to show £100.
Customer pays £500 in cycle 1 that bounces in cycle 1 and they pay £600 in cycle 1 – payment amount field to show £600.
Scenario 3
Customer has a credit balance of £200 on their account and has requested this is paid back to them – payment amount field to show £0.
Scenario 4
Customer pays in £200 in cycle 1 and has a payment reversal of £300 in cycle 1 – payment amount field to show negative £100.
Scenario 5
Customer pays £500 in cycle 1 that bounces in cycle 2 – payment amount field to show negative £500 in cycle 2.
Customer pays £500 in cycle 1 that bounces in cycle 2, then pays £100 in cycle 2 – payment amount field to show negative £400 in cycle 2.
Previous statement balance:
This field should contain the balance at the date of the previous statement date relating to the requested payment amount. This should be given in addition to the current balance field.
Cash advances:
This fields records the number and value of cash advances within the reporting period. This includes UK ATM transactions, foreign ATM transactions and over-the-counter cash, for example bureau de change. It should not include retail cashback or quasi cash transaction, credit card cheque transactions, gambling cash advances and any fees or charges.
It is best practice not to include any cash advances fee(s) which, if recorded, do not add to the field for the number of cash advances count.
Payment code:
This is to indicate where only the minimum requested payment has been made by the customer. An M should be given where a payment is within a one pound tolerance either way of the expected amount, with any pence rounded to the nearest pound. Any other payments should be set to blank to indicate the minimum payment was not made.
Promotional activity:
This field is used to indicate any form of current promotional activity on the account. This may reflect new or life of balance rates, whether purchase, balance transfer, credit card cheque, or other promotions. This relates only to accounts that are actually benefiting from the promotion.
Where a loan is a ‘buy now pay later’ arrangement:
Where a loan is a 50/50-type deal and an amount (for example, 50%) has been put down as a deposit at the start, with the remainder payable as a lump sum at the end of the term:
Where a loan is a 50/50-type deal and normal amounts are paid throughout the term with a single lump sum payable at the end:
Where a loan is a 50/50 deal and an amount (for example, 50%) has been put down as a deposit at the start and the remainder is payable as normal over the life of the term:
SCOR mandated a group to look at the way data is shared for flexible and current account mortgages. The group included a number of lenders that offer or are about to offer this type of product, together with a representative from the Council of Mortgage Lenders and credit reference agencies.
What is a flexible or current account mortgage?
For the purposes of this guide, a flexible or current account mortgage is defined as:
For tax reasons this guidance is not designed to include products that are netted for interest purposes.
Guidance for supplying flexible mortgages
The group agreed that the current method of some lenders providing a net position and some reporting the constituent parts is could be confusing for both consumers and lenders. Reporting of numerous accounts could also have a negative impact on scoring models.
It was decided that such products should be identified as a specific product type so they can be modelled and scored separately, if analysis indicates that it is appropriate. A new product type – ‘flexible mortgage’ – was created for CAIS submissions.
Since lenders and consumers consider the net situation on such accounts, and it is impossible for other members of the shared database to identify the constituent parts, it is further recommended that the net position be reported on the one flexible mortgage. This enables the total exposure position to be accurately reported to CAIS, taking into consideration credit and / or advance payment positions on other accounts in the overall product.
Where applicable, CAIS members should share the:
Other appropriate CAIS fields – for example, start date, flags – should also be shared.
The Competition Commission requires larger home credit lenders to share their customer credit accounts with credit reference agencies.
These definitions are agreed with the Consumer Credit Association, Competition Commission and Information Commissioner’s Office. The rules recognise that home credit accounts are more flexible and varied than that of other types of account, so the definitions have to cater for a range of circumstances. In particular, as most home credit accounts work on weekly terms, the loan term and the amount outstanding must be calculated and recorded as a monthly figure so it can be easily compared with other credit accounts on CAIS. Also, there will be situations when a CAIS status code 6 is recorded for longer periods of time.
Monthly payment:
This field shows the value of, and is equivalent to, one month of weekly payments. For consistency, this value should not be changed during the term of the loan, even when the number of days in the month differ. The monthly payment value is calculated by multiplying the weekly payment by 4.33. The field should only record whole pounds, without rounding up or down, so £10.23 and £10.78 would both be recorded as £10.
Repayment period:
This field gives the term of the loan. Standard practice in the home credit market is to grant loans over a number of weeks. For data to be comparable to other credit accounts on CAIS, any loan term of weeks must be converted into monthly terms. For consistency the monthly value should be calculated by dividing the weekly term by 4.33 and rounding up. So a 12-week loan would be recorded as three months, a 13-week loan would be recorded as three months, and a 14-week loan would be recorded as four months.
CAIS account status codes:
The status code is a monthly indication of the payment performance of the account. An unclassified status code (U) is used the first time an account is reported to CAIS. It shows the first payment is not yet due or allows time to make sure any customer issues with the credit agreement are raised before performance reporting is started.
Account status codes indicate the number of months in arrears a credit account is in. Home credit accounts status codes should be calculated by dividing the total value of arrears by the Monthly Payment value. Only full months arrears should be reported and any part months’ arrears should be rounded down. In allocating a status code 1 to indicate an account moving into arrears, it is advisable to include a seven-day period of grace, to allow for a payment which has been unusually delayed.
Defaults (status code 8):
According to the ICO, a default occurs when the relationship between the borrower and lender has broken down. For home credit, this occurs when:
No default is filed even if the customer is making part or irregular payments without an arrangement being in place, with the customer is held at status code 6 for up to 12 months. If a default is filed on such accounts at a later stage, the default date should be backdated to the date the first status code 6 was reported. The nature of the home credit market means this would only happen in unusual circumstances.
Payment frequency indicator:
This field shows how often payment is received. Home credit accounts on weekly terms will include a W in this field. The contents of this field have no effect on the monthly payment field, which is calculated separately to give a monthly amount.
Flag settings:
Flags are used to give a more detailed picture of an individual’s current position. They have a hierarchy and where more than one flag applies, the flag with the greatest hierarchy is submitted.
For home credit accounts, the flags are:
CAIS flag Description
D Deceased
P Partial settlement
C Debt assigned (non-CAIS member)
S Debt sold to CAIS member
G Gone away
A Arrangement
M Debt management programme
Q Account query
Arrangement (A):
If the customer and lender have made a formal agreement to reduce the monthly payment amount for a limited period of time, an A flag is used. The payment terms are amended to the new agreed payments, and the payment profile updated accordingly. Any arrears accrued against the original contract continue to be shown by the appropriate status code before the date of the arrangement, together with an A flag and the arranged monthly payment at that particular time.
In instances where smaller payments are accepted, but no formal re-scheduling of the agreement is made; an A flag should not be reported. In these cases the status code should be based on the new agreed rate, rather than the contractual rate.
Debt management programme (M):
The M flag is used when the customer has entered into a debt management programme with a separate company. The status code reflects the arrears at the time the program was entered into. After the customer enters the program, two monthly payment amounts are recorded on CAIS – the revised (managed) amount and the original monthly payment amount.
Since 1990, government-funded loans have played a key role in students’ access to higher education. From 1990 to 1998 these loans were regulated by the Consumer Credit Act 1974 and were sometimes referred to as ‘mortgage-style student loans’. Customers who took out these loans receive an annual statement and interest is also adjusted annually.
The two main differences between student loans and other types of credit are that:
If the borrower is on a low income (defined as 85% of the national average) payment may be suspended through a process known as deferment. This must be sought and agreed each year.
The deferral is effectively a payment holiday similar to other credit agreements that have a deferred start or the possibility to take a holiday. A deferral on a student loan will be reported as U.
If the borrower applies for deferral but is already in arrears, either because they were late in applying for deferral or because there were already arrears on the account before deferral was possible, there may be records showing an arrears status followed by a U. It should not be assumed that the arrears have been brought up to date.
These accounts will be marked as P.
Account type:
The student loans account type 60 should be set on all student loan records.
Status code:
On a full CAIS record, normal status codes will apply. While a consumer defers payment this is reported into CAIS as a status of U until the loan becomes payable.
Arrangements:
Can be reported on student loans, including those in status U – for example, if an agreement has been reached to repay arrears incurred before eligibility for deferral.
Start date:
Given as the first scheduled repayment date.
Definition of default:
The account is not in a viable arrangement and is 180 days past due.
Original default balance:
If an account is in deferral but has previous arrears every effort will be made to establish a repayment programme for the outstanding arrears. If this is not possible, the account will be brought out of deferral and default proceedings commenced. The default will be registered for the full amount owed.
This type of loan allows consumers to borrow a relatively small amount of money (usually between £50 and £1,000). It’s a short‐term, high-interest, unsecured loan that’s expected to be repaid when the consumer receives their next regular income payment (normally around or within 30 days of having been granted the loan). It’s not designed for longer-term borrowing, but to improve short-term personal cash flow.
Where the balance outstanding is rolled over to the following pay day, you should ensure that the same account number currently reported to CAIS is updated to ensure a continuation of the payment and status code history.
Where the consumer wishes to take out additional lending this would be deemed to be a new agreement and the account number on CAIS is reported with a closed date and the current balance set with zeros. A new account number is then reported for the new agreement.
Accounts that are opened and closed within the same month of CAIS reporting are reported as closed with a zero balance on the CAIS extract. This shows other CAIS members that a lending agreement was previously in place.
CAIS fields include:
Balance:
The balance outstanding reflects the total amount of the loan and includes any interest and charges that have accrued over the life of the agreement.
Monthly payment:
Where a monthly payment is agreed this field reflects the agreed amount. This field is not always applicable – for example, where a payday loan agreement is paid either within the same CAIS reporting cycle or is paid in full the following month.
Status codes:
In line with the Principles for the reporting of Arrears, Arrangements and Defaults at Credit Reference Agencies, payday loan lenders must allow a minimum of 90 days of arrears and a 28-day notice period before reporting an agreement in default.
If a default is not registered at this stage the account can go to a maximum of 180 day overdue and progress through the arrears status codes as per standard CAIS reporting. Once an account is 180 days overdue a default should be registered. To prevent the account from continually being reported in arrears an arrangement to pay could be agreed with the consumer.
Energy
Energy accounts can be reported into CAIS in line with all other credit agreements. The exception is pre-payment meters. Where a consumer signs up to energy supply on a pre-payment meter from the onset, this will never be reported into CAIS. Where a pre-payment meter is fitted as a result of arrears, only payments made to clear the arrears are reported, not the on-going consumption via the pre-paid meter. Once the warrant process is underway, and provided the account is over 90 days in arrears, a notification of intention to file a default may be sent to the consumer and a default registered 28 days later. This is in line with the Principles for the reporting of Arrears, Arrangements and Defaults at Credit Reference Agencies.
Water
As with many non-standard credit products there are specific rules for the sharing of water accounts data. Water providers do not have the choice of ceasing to do business with a defaulting customer, which brings added complexity. This may lead to them continuing to provide the service and, potentially, finding themselves in a similar position of default from that customer again. This means water accounts need to be recorded slightly differently.
However, to be consistent with other data providers, defaults should be registered after 90 days and before 180 days of non-payment, in line with the Principle for the Reporting of Arrears, Arrangements and Defaults at Credit Reference Agencies.
As long as they are clearly communicated to the customer or business, a number of triggers may be considered to be grounds for registering a default:
Even though the service cannot be disconnected, default should still occur within the normal timescales of between 90 - 180 days past due. In these cases the water provider will register a new account or agreement will be commenced within their internal systems to register the ongoing supply. Providers supplying positive as well as negative data will register a second account on CAIS and the performance on that account will be supplied as normal.
To prevent a large volume of defaults for the same product type and from the same supplier being reported, just one default can be registered over a six-year period. So at any time during a six-year period a customer should have a maximum of one defaulted account and (potentially) one active full data record. The balance on the defaulted account will change as more defaults are added and settlements occur. The only time that this may change is if there is a break in the incidence of defaulting, where one default is satisfied and another default is registered.
If you’ve sold on a customer record to another company or Debt Collections Agency (DCA), there is still an obligation to bring the CAIS record to a complete end.
This is carried out through the use of a flag setting within the monthly submission that will update the record to reflect the debt sale.
How should this be reported to CAIS?
A common misconception is that records that have been sold, should be deleted.
This is inaccurate advice and would not create a true reflection of the account activity.
Deleting the record would cause it to disappear from any credit searches or credit reports meaning lenders and consumers alike would no longer be able to view the account data.
The correct course of action in this scenario is to apply a debt sale flag to your CAIS record, report as settled/satisfied, with a zero-current balance outstanding.
Once these changes have been updated on your monthly CAIS file, you no longer need to supply a record for that CAIS account.
Which flag setting should be applied?
There are two debt sale flags that can be applied to a record through the monthly file:
C - where the record has been assigned to a non-CAIS member.
S - where the record has been sold to a CAIS provider.
When should this be reported?
The changes should be reported on your CAIS input file in the very next submission following the debt sale.
What is the impact to the consumer?
The ultimate outcome is that the CAIS data is reported and retrieved with a high degree of accuracy for both consumer and lender, with no loss of data. This leads to better lending decisions for clients, and a customer journey that shows a logical progression for the life of the account.
Where can I find more information?
Details on how to apply the debt sale flag and report into CAIS can be found in the frequently asked questions section of the website and the CAIS2007 format guide.
UMAs are also known as Active Without Updates (AWUs) if you fail to update an active/open account each month, it will cause the whole record to become frozen, viewable at the status it was when it last received an update. This is known as an Unmatched Active.
How should this be reported to CAIS?
All active (open) records must be updated (by reference to the account number) each month, even if there is no movement on the account, until they become either genuinely settled or defaulted.
What is the impact to the consumer?
Unmatched Actives can create consumer queries and complaints to either Experian or directly to our clients. The account balance may not be accurate which would affect the overall balance a consumer owes on their credit report; the account may have been settled by the consumer which would indicate to other lenders that the consumer can successfully complete a credit agreement; the account could be delinquent (consumer has fallen behind on payments for at least 3 months) or even defaulted (the credit agreement has broken down). If we receive a subsequent update to an Unmatched Active, our systems will auto-fill the missing months status history with a question mark(?) which could also cause consumer queries.
Where can I find more information?
You can email the Consumer CAIS team at cais.control@experian.com or call 0115 9768933 for more information. If potential project work is required, please email cais.consultancy@experian.com. Unmatched Actives are also referred to in the bi-annual CAIS Audit document under section 7 of the audit report.
An Active Without Update (AWU) record is an active account record that has not received a successful update in the latest data submission.
It is important that all active account records receive a monthly update to avoid the risk of detriment to data subjects. For example, a CAIS member viewing a credit report will not receive a complete and up-to-date view of a subject’s performance if an account record is not updated regularly.
An AWU is primarily caused in two ways:
1. Your monthly input file included an update for an account record previously reported to CAIS, but the update failed one or more of the quality checks in our validation process and was rejected. To help you to address this we send you an audit file each month that identifies the account records rejected as a result of failing quality checks.
2. An account record last reported to CAIS as active for which updates are no longer being provided within your monthly input file.
If you would like further information regarding AWU account records and how we can assist with remediation, please contact us.
There could be a number of reasons for this, if you have logged in but the file isn’t transferring then please get in touch with Commercial CAIS directly. Check you are uploading to the ‘to_xpn’ folder otherwise this will cause the submission to fail.
Please contact the Technical Support Team, they can check the account and talk you through the password reset process if you are unable to do this yourself.
Please contact your dedicated Account Manager or alternatively Commercial CAIS directly.
Contact your Account Manager and Commercial CAIS as soon as you are aware of any issue to enable contingency processes to be agreed and employed.
Commercial CAIS are equipped to be able to make corrections to your data to both slight and significant scale issues.
There is no fee although naturally, there will be resourcing requirements to supply your data.
Data Processing & Loading:
Data Quality:
Data Processing & Loading:
Data Quality:
If you can't find what you need, please get in touch via email at Cais.Control@experian.com
Experian working with UK Finance, have made changes to the fair processing notices that will be used for credit account information sharing. This can be seen in the CRAIN notification document that can be found below.