When the B2B process is enabled, DQE adds company enrichment output columns to the processed file.
These columns help you understand whether a company was identified and how confident the matching result is.
Who should read this article
Use this article if your file-based batch processing includes B2B enrichment and you need to understand the DQE company enrichment 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.
B2B columns
| Column | Description |
|---|---|
DQE_FOUND | Indicates whether a matching company was found. |
DQE_STATUS | Status returned by the B2B matching process. |
DQE_LABEL_STATUS | Readable label associated with the returned status. |
DQE_CERTAINTY | Confidence level associated with the match. |
How to use B2B results
- Use
DQE_FOUNDto identify whether a company match was found. - Use
DQE_STATUSandDQE_LABEL_STATUSto understand the matching result. - Use
DQE_CERTAINTYwhen business rules depend on the confidence level of the match.
Best practices
- Review low-certainty matches before updating production data.
- Keep the original company information to compare source data and enrichment results.
- Document internal thresholds for automatic acceptance or manual review.
Related articles
- Understand DQE output columns
- B2B Notice 80 output columns
- Understand file-based batch processing