Synchronising phone numbers to Xero
When you are trying to input long phone numbers such as those with country codes, area codes and extensions you may have experienced synchronisation issues. This is most likely due to a formatting issue due to Xero's phone number format requirements.
Users will need the Integration: Accounting - Xero permission in order to use this feature.
Note: All characters are allowed in a phone number.
In Xero, phone numbers are stored in three fields. When synchronising a phone number to Xero, Cin7 Core first checks how many parts a phone number has, separated by spaces.
Phone number - max. length 50 characters.
Area code - max. length 10 characters.
Country code - max. length 20 characters.
Examples:
0424717890#507 - This number has no spaces, so it will be synchronised to Xero's phone number field. Phone number max. length is 50 characters.
04-24717890#507- This number has no spaces, so it will be synchronised to Xero's phone number field. Phone number max. length is 50 characters.
0424717890 #507 - This number has a space, so the system will split it into phone number (#507) and area code (0424717890). Phone number max. length is 50 characters. Area code max. length is 10 characters. This number will sync.
04-24717890 #507 - This number has a space, so the system will split it into phone number (#507) and area code (04-24717890). Phone number max. length is 50 characters. Area code max. length is 10 characters. This number will sync, as the area code has 11 characters.
04 24717890#507 - This number has a space, so the system will split it into phone number (24717890#507) and area code (04). Phone number max. length is 50 characters. Area code max. length is 10 characters. This number will sync.
04 24717890 #507 - This number has two spaces, so the system will split it into phone number (#507) and area code (24717890), and country code (04) Phone number max. length is 50 characters. Area code max. length is 10 characters. Country code max. length is 20 characters. This number will sync.
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB