When the Phone process is enabled, DQE adds phone output columns to the processed file.
These columns help you understand whether the phone number is valid, read the reformatted phone number returned by DQE, and identify whether the number is a mobile number.
Who should read this article
Use this article if your file-based batch processing includes Phone validation and you need to understand the DQE phone columns added to your output file.
This article applies to file-based batch processing via SFTP. It does not apply to real-time API responses.
Dynamic phone field names
Phone output column names include the placeholder {FIELD_NAME_PHONE}.
This placeholder is replaced by the name of the input phone field processed by DQE.
For example, if your input phone column is named mobile, the output column DQE_{FIELD_NAME_PHONE}_ERROR_CODE may appear as DQE_mobile_ERROR_CODE.
Phone columns
| Column | Description |
|---|---|
DQE_{FIELD_NAME_PHONE}_ERROR_CODE |
Return code after Phone processing. |
DQE_{FIELD_NAME_PHONE} |
Reformatted phone number returned by DQE. |
DQE_{FIELD_NAME_PHONE}_IS_MOBILE |
Mobile detection Boolean. |
Phone error code values
The DQE_{FIELD_NAME_PHONE}_ERROR_CODE column indicates whether the phone number is valid after Phone processing.
| Value | Description |
|---|---|
0 |
Invalid number. |
1 |
Valid number. |
Mobile detection values
The DQE_{FIELD_NAME_PHONE}_IS_MOBILE column indicates whether DQE detected a mobile number.
| Value | Description |
|---|---|
False |
Number is not a mobile. |
True |
Number is a mobile. |
Best practices
- Use
DQE_{FIELD_NAME_PHONE}_ERROR_CODEto identify valid and invalid phone numbers. - Use the reformatted phone number returned in
DQE_{FIELD_NAME_PHONE}when your business rules allow standardized values to replace the original value. - Use
DQE_{FIELD_NAME_PHONE}_IS_MOBILEto adapt communication channels, for example SMS or voice calls. - Keep the original input phone field so that you can compare it with the DQE reformatted value.