Every submission captured, structured, and routed. Before anyone touches it.

Yes. Enrichment is configured per carrier, not shipped as one fixed pipeline. You define which data elements matter for your clearance and underwriting workflow, the priority order used when the same field appears in more than one document, and the confidence threshold a value must clear before it passes through. Where a submission arrives with a schedule of values, an ACORD form, and an email that disagree, triangulation resolves the conflict in the order you set. Values that fall below your threshold are routed for human review rather than passed through silently.

Submission Ingestion operates in 27 countries and 6 languages, and the engine is built for the details that usually break ingestion across borders: local date conventions, local classification schemes such as NAF alongside NAICS, local currency, and country-specific forms. A submission does not have to be reformatted to a US standard before it can be read.

Three places, in order. First the submission itself, where DeX ai extracts every field it can find across all 21 document types, from ACORD forms and schedules of values to loss runs, financials, and the body of the broker’s email. Second, third-party enrichment, which fills the gaps the submission left open. Third, triangulation, which compares every source against the others and resolves disagreements into one normalized record, with a confidence score attached to each field so your team knows what to trust and what to check.