Customer Ingestion

• Customer Ingestion Flow
  • Customer Validation
  • Customer Processing
  • Customer Saving to Database

Customer Ingestion Flow

Customer Validation

1. Eligibility for Updates
   • Check status and workflow.
2. Country Validation
3. Source System Validation
4. External System Identifiers Validation
   • Mandatory Check
   • Create a customer with the external identifier’s delete flag set to true.
   • SCV code is restricted in create scenarios.
   • Validate external identifier code against reference data.
   • Ensure BE code is not already taken.
5. Format Validation for Core Customer Attributes
   • Trading name, website, group type, and country.
   • Address attributes including street name, number, apartment/floor, city, PO box, postal code, etc.
   • Audit details.
6. Region Validation
7. City Validation
8. Custom Rules Validation
   • Customer Code: Check length and ensure the first two characters match the country code.
   • Website: Validate URL format using the Apache Commons URL Validator library.
   • Customer Address Rules:
     • Complete address is mandatory for Japan.
     • Either PO box or street name must be provided.
     • Both city and country are mandatory.
   • Status Reason Rules:
     • For customer creation, the status attribute must be sent only as ‘A’. An error is thrown if either ‘S’ or ‘I’ is sent, or if any status reasons are included.
     • If suspending a customer, an error is thrown if status reasons are absent.
   • Language Code: Validate against country-specific accepted language codes reference data.
   • Workflow Rules: Check the workflow indicator attribute against accepted values.
   • Source System Rules:
     • Customer creation from BVD source is restricted.
     • SCV source is not allowed for updates.
     • BVD information persistence is not permitted from non-BVD sources.
     • Updates related to customer workflow are not allowed from Excel sources.
9. Telecommunication Validation
   • Format check.
   • Country check.
   • External API: Perform real-time phone number validation using Informatica.
10. Customer Identifiers Validation

• Check country and identifier code combinations.
• Verify mandatory identifiers.
• Validate identifier number patterns.
• Real-Time Tax Validation:
  • VIES validation check for VAT in EU countries.
  • Use respective government tax verification APIs for the UK & NZ.

11. Customer Brands Validation
12. SCPI Source-Based Validation

• SCPI customer creation is restricted to the portal source system.
• Primary email is mandatory when creating an SCPI customer.

Customer Processing

1. Duplicate Check
   • Call the customer match API and tag the duplicate workflow.
2. Payload Enrichment
   • Set invoice ISO language code preferences based on country code.
   • Format the website by appending HTTP correctly.
   • Ensure the legal name is not nullified if not passed in the payload during updates.
   • Include communication details in update cases.
3. Extract Tax and References from Database
4. Customer Create Case – Pre-Validation for Non-Portal Source Systems
   • Classify customer as Internal/External by calling the Customer Type Identification API.
   • Assign ACC_GRP_CHG.
   • If the customer group type is SCPI Tax exempted, assign the customer group change workflow.
5. Customer Update Case – Pre-Validation
   • Detect tax changes and assign workflow.
   • Detect trading name changes and assign workflow.
   • Detect address changes and call an external API to reassign coordinates based on the new address.
   • If any of the following change: address, reference, tax, or trading name, trigger the Duplicate API to find a duplicate customer.
   • If SCPI changes, assign the group change workflow.

Customer Saving to Database

1. If no workflow is assigned, save the customer to the database; otherwise, send the customer to workflow.
2. Sync the customer to the database.
3. Publish the customer to EMP.