Thailand Branch ID Enablement
Requirement
Link to Epic - CMD1-5224 -Getting issue details... STATUS
There is a regulatory requirement to enable the branch ID for every customer that is registered in Thailand to prevent invoice failures of ~USD 208 mil.
Backend Changes
Database:
- A new Customer Reference Type (BID) has been added in the
MDM_SMDS.REF_CUSTOMER_REFERENCE_TYPEStable
Corresponding Reference API response object
{
"referenceNumberCode": "BID",
"referenceNumberName": "Branch ID",
"referenceNumberDescription": "Branch ID",
"referenceNumberGroupCode": "EXT_REF_NUM"
}
- A new Ruleset has been introduced in the
MDM_SMDSMD.SMDS_GENERIC_COUNTRY_RULEStable for the Country Code ‘TH’ with the conditional check column containing the value TAXNO1 & BID
Corresponding Reference API response object
{
"fieldType": "BID",
"conditionalCheck": "TH3",
"formatCheck": "^\\d{5}$",
"formatCheckDescription": "For Thailand, the Branch ID is mandatory if the Thailand tax ID is entered and the format is ‘NNNNN’. For example, “00000”, “00001”, … “99999” etc.”",
"isMandatory": true,
"isApplicable": true,
"isExternalCheckApplicable": false
}
Customer Ingest API
- Currently, before implementing this change, the Ingest API supports conditional check validation only when both terms separated by the delimiter belong to the tax number type table (e.g., TAXNO1, TAXNO2, etc.) and not to the Customer Reference Identifiers (e.g., EOR, CRN, BID, etc.).
- With a few adjustments, the current implementation of the Brazil Tax change can be leveraged for the upcoming solution as well.
- The Validation API will also take into consideration the Customer Reference Types, along with the Tax Type Codes, for the conditional check of the rulesets.
- The error messages will be returned accordingly based on the conditional term, indicating whether the type code belongs to the Tax Type or the Reference Type category.
Was this page helpful?