When the B2B Notice 80 process is enabled, DQE adds company enrichment output columns to the processed file.
These columns help you understand the result returned by the B2B Notice 80 process and review the company information identified or enriched by DQE.
Who should read this article
Use this article if your file-based batch processing includes B2B Notice 80 processing 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 Notice 80 columns
The exact output columns returned by B2B Notice 80 depend on your project configuration and the company data sources enabled for your processing.
In general, B2B Notice 80 output columns can include company identification, matching status, labels, and confidence indicators.
| Column | Description |
|---|---|
DQE_FOUND |
Indicates whether a matching company record was found. |
DQE_STATUS |
Status returned by the B2B Notice 80 matching or enrichment process. |
DQE_LABEL_STATUS |
Readable label associated with the returned status. |
DQE_CERTAINTY |
Confidence level associated with the returned company match. |
How to use B2B Notice 80 results
Use B2B Notice 80 output columns to decide whether a company match can be accepted automatically or requires manual review.
- Use
DQE_FOUNDto identify whether a company record was found. - Use
DQE_STATUSandDQE_LABEL_STATUSto understand the returned matching status. - Use
DQE_CERTAINTYto assess the confidence level of the company match.
Best practices
- Review low-certainty or ambiguous company matches before updating production data.
- Keep the original company input fields so that you can compare them with DQE enrichment results.
- Define internal rules for accepting, reviewing, or rejecting company matches.
- Only use B2B Notice 80 columns when this service is enabled for your project.
Related articles
- Understand DQE output columns
- B2B output columns
- Understand file-based batch processing