RULES DESCRIPTION DOCUMENT Version 2.2, June 2019 COPYRIGHT INFO Copyright © 2019 by AXY7 All rights reserved. This document or any portion thereof may not be reproduced or used in any manner whatsoever without the express written permission of AXY7 except as help and reference for the use of Axy Validator App. Axy Validator Rules Description Document Page 2 of 72 INDEX: Document purpose 9 Validation Rules Types 10 LOCAL VALIDATIONS 10 CHECKSUM VALIDATIONS 10 OPERATING VALIDATIONS 10 Action Types 11 WARNING ACTIONS 11 ERROR ACTIONS 11 Rule Configuration generic description 12 Other Axy Validator Features 18 Bypass feature 18 Local Axy Validator Rules 19 US Social Security Number - SSN 19 Summary 19 Description 19 Format to validate 19 Special Cases 20 What is not validated 20 Examples 20 US TIN - ITIN 21 Summary 21 Description 21 Format to validate 21 Special Cases 22 What is not validated 22 Examples 22 UK Company Registration Number - CRN 23 Summary 23 Description 23 Format to validate 23 Axy Validator Rules Description Document Page 3 of 72 Special Cases 24 What is not validated 24 Examples 24 UK National Insurance Number - NINo 25 Summary 25 Description 25 Format to validate 25 What is not validated 26 Examples 26 UK Postcode 27 Summary 27 Description 27 Format to validate 27 What is not validated 28 Examples 28 Eircode 29 Summary 29 Description 29 Format to validate 29 What is not validated 30 Examples 30 US TIN - EIN 31 Summary 31 Description 31 Format to validate 31 What is not validated 32 Examples 32 VAT European Union - MultiField 33 Summary 33 Description 33 Format to validate 33 Special Cases 34 What is not validated 35 Axy Validator Rules Description Document Page 4 of 72 Examples 35 VAT European Union - OneField 37 Summary 37 Description 37 Format to validate 37 Special Cases 38 What is not validated 38 Examples 38 VAT Europe - OneField 39 Summary 39 Description 40 Format to validate 40 Special Cases 40 What is not validated 42 Examples 42 Canadian TIN - BN 44 Summary 44 Description 44 Format to validate 44 What is not validated 45 Examples 45 Australian Business Number - ABN 46 Summary 46 Description 46 Format to validate 46 What is not validated 47 Examples 47 Brazil TIN - CNPJ 48 Summary 48 Description 48 Format to validate 48 What is not validated 49 Examples 49 Axy Validator Rules Description Document Page 5 of 72 Credit Card Number Basic 50 Summary 50 Description 50 Format to validate 50 What is not validated 51 Examples 51 Credit Card Number Advance 52 Summary 52 Description 52 Format to validate 52 Special Cases 53 What is not validated 53 Examples 53 BIC Code 55 Summary 55 Description 55 Format to validate 55 What is not validated 56 Examples 56 IBAN Multicountry - Multifield 57 Summary 57 Description 57 Format to validate 57 What is not validated 58 Special Cases 58 Examples 61 Phone UK 62 Summary 62 Description 62 Format to validate 62 What is not validated 63 Examples 63 Phone US 64 Axy Validator Rules Description Document Page 6 of 72 Summary 64 Description 64 Format to validate 64 Special Cases 65 What is not validated 65 Examples 65 ZIP Code US 66 Summary 66 Description 66 Format to validate 66 What is not validated 67 Examples 67 Checksum Axy Validator Rules 68 IBAN Checksum 68 Summary 68 Description 68 Format to validate 68 What is not validated 69 Special Cases 69 Examples 69 Spanish CIF 70 Summary 70 Description 70 Format to validate 70 What is not validated 71 Examples 71 PPS Number (Ireland) 72 Summary 72 Description 72 Format to validate 72 What is not validated 73 Examples 73 Axy Validator Rules Description Document Page 7 of 72 1. DOCUMENT PURPOSE Axy Validator from AXY7 provides you with common or complex validations to improve your salesforce data quality and maximize your business performance. Axy Validator is easily installed and configured by any Salesforce Administrator, just with a few clicks The purpose of this document is the listing and detailed description of the complete set of rules included in the Axy Validator app. You will see below the explanation of the different rules, with an extensive description of how they are applied and the definition and characteristics of the fields you want to validate with every rule. The validation rules come from official organizations and standards and AXY7 continuously works on updated versions. You only need to choose the rule you want to use and apply it to the relevant data for your processes. You will then have the data quality your business need. Axy Validator Rules Description Document Page 8 of 72 2. VALIDATION RULES TYPES Our App provides three different validation types, depending on your business needs. Sometimes, the need to be very agile on data input only requires a format validation. There are other business situations where you need a more precise validation, so you need a checksum validation. And, finally, you may need to assure that data are not only correct but they “exist”, they are alive. LOCAL VALIDATIONS Some of the Axy Validator prebuilt rules help you to be sure that the LENGTH and SYNTAX of a code are correct, so the FORMAT accomplishes the definition of that type of data. This is the case of the US Social Security Number rule, that validates the input has a length of 9 digits with a first group of 3 digits, a second group of 2 digits and a third group of 4 digits. And does not begin with ’666′, as one of the syntax conditions. These rules are noted in the App as LOCAL. CHECKSUM VALIDATIONS This type of rule not only validates LENGTH and SYNTAX but AVOIDS any TYPING ERROR. This data quality check is performed using the checksum algorithm that the managing organization or the ISO standard body has defined for that code. This is the case of the IBAN Checksum rule, which follows the ISO 13616 and uses a MOD-97-10 algorithm. These rules are noted in the App as CHECKSUM. OPERATING VALIDATIONS The ultimate validation rule. You will be sure that the data you are using defines a VALID and OPERATIVE code, so will always work for your business process. This means, as an example, if you need to be sure that and European VAT number belongs to the company you are doing business with, you should use this type of rule. The way it works is sending a query to the remote service of the official organization that manages and/or issues that code. Please go to our ​Roadmap plan in ​Axy Validator web page​ to check availability for this type of rules. Axy Validator Rules Description Document Page 9 of 72 3. ACTION TYPES Improving the classic Salesforce Validation Rule functionality, our application supports two types of actions during the validation: Warning and Error. Axy Validator gives your business more flexibility to capture the right information in the right process moment. WARNING ACTIONS Allows you to configure a specific field to set a warning message when the checked data is not correct. But this action allows the user to save the record. ERROR ACTIONS This action prevents the user to save the record when informed data is no matching the expected format. So you assure the business process only goes on if every data is correct. Axy Validator Rules Description Document Page 10 of 72 4. RULE CONFIGURATION GENERIC DESCRIPTION We are describing in this section a generic rule in order to understand the different options and menus of the Rules Configuration Wizard on Validator Setup. We are using the US SSN - Social Security Number as an example. In the ​first screen of the wizard​, you find the ​RULE SELECTION​ page: ● TYPE​: If you want to use a ​LOCAL ​or a ​CHECKSUM ​rule ● PACKAGE​: This will allow you to use rules from different Axy Validator Packages that you have installed in your org. Basic is the one by default. ● CATEGORY​: We have classified the rules in different categories, to make easier to decide the rules you want to apply. We currently have three categories ○ Legal / Tax​. Validation rules for taxes or legal purposes, like a VAT Number (Value Added Tax Number). ○ Bank / Payments​. Applied to validate Bank codes or Payment Methods (Credit Cards) ○ Contact Information​. These rules validate contact numbers or identifiers, like phone numbers or email addresses. In the ​second wizard screen​, you find the ​OBJECT and FIELD SELECTION page. In this page, you have to decide the Field Mapping for the rule. Axy Validator Rules Description Document Page 11 of 72 The rule has to be mapped to a FIELD (Labeled in Validator Setup as ​Social Security Number Field​ for this example) in an OBJECT previously configured in your org. This will be the field where you have the data you want to be validated by the rule. Axy Validator will show you a Picklist with the objects in your org and the Text Fields in the object you select. In this example, we have selected the standard object CONTACT and the user-defined field SOCIAL SECURITY NUMBER in it. The FIELD has to have a minimum length for the rule to be applied. The minimum length is defined in every rule description. There are rules that need two fields to validate. For this kind of rules we need to map the two FIELDs, and both have to be previously configured in your org. Below you have the case of the IBAN Multicountry - Multifield, as an example, where you need the Country Code in order to apply the IBAN rule for every .