Canonical reference for every field on the Customer entity in Marquis IQ. These fields appear across Enrich, Explore, Analyze, and Excel exports.
Fields that represent the Marquis-level customer structure sitting above individual ERP records.
The unified name assigned to this Master Customer record. When matched to Dun & Bradstreet, defaults to the D&B primary name. When unmatched, uses a cleansed version of the ERP customer name. Users who create a Master Customer manually can enter any name they choose.
The top-level corporate family grouping for this Master Customer. Defaults to the Global Family Name provided by D&B enrichment. Users can change it at any time in the Maintain workflow to reflect their own grouping preferences (for example, using a parent name that matches their internal reporting structure).
Note: Revenue, margin, and inventory roll-ups across all IQ modules use Family Name as the top-level hierarchy. Keeping it accurate pays dividends across every module.
The worldwide ultimate parent company name as identified by Dun & Bradstreet. This is the original default value for Family Name. If a user has updated Family Name in Maintain, those two fields may differ.
Fields pulled directly from the client's source ERP system, unchanged from how they are stored there.
The customer name exactly as it appears on the ERP record, without any cleansing or modification. This is the raw value from the source system.
The internal company name used within the client's own organization. A company operating two separate businesses would have two distinct organization names - one for each. This reflects how the client refers to its own legal entities internally, not the external customer-facing name.
The unique identifier assigned to this customer record in the source ERP system. The format varies by ERP (e.g., numeric in SAP, alphanumeric in Epicor).
The ERP platform from which this customer record was loaded (for example, SAP, Epicor, Dynamics 365, NetSuite). Useful for filtering when working cross-ERP portfolios where the same customer may appear under different records across systems.
The federal tax identification number (EIN) for this customer, as recorded in the ERP system. When present and accurate, this is one of the strongest signals used during the matching process.
The payment terms assigned to this customer in the ERP system (for example, Net 30, Net 60, 2/10 Net 30). Sourced directly from the ERP customer record.
The active or inactive status of this customer record as maintained in the source ERP system. Reflects the ERP's own status field and is not modified by Marquis IQ.
Indicates whether this customer record represents an intercompany transaction counterparty rather than an external customer. Intercompany records are typically internal business units transacting with each other.
A unique identifier for this customer that is consistent across all connected ERP systems. Enables cross-ERP tracking and deduplication when the same customer exists under different numbers in multiple source systems.
Address fields from the ERP customer record. The full combined Billing Address is shown by default; individual components are available as separate columns.
The full billing address for this ERP customer record, combining street, city, state, and postal code into a single field. Shown by default. Use the individual Billing City, State, Country, and Postal Code columns when you need to filter or sort on a specific address component.
The city component of the ERP billing address.
The state or province component of the ERP billing address.
The country name of the ERP billing address, as stored in the source system.
The two-letter ISO 3166-1 country code for the billing address country (for example, US, CA, DE).
The postal or ZIP code of the ERP billing address.
Fields that describe how each ERP record was linked to its Master Customer and how confident the system is in that link.
Indicates that a user manually assigned this ERP account to a Master Customer, rather than accepting the system's automatic match. In the grid, a blue dot appears on the row for any manually assigned record. Records matched automatically by the system do not show this indicator.
Note: Manual assignment takes priority and is preserved across enrichment refreshes. It will not be overwritten by subsequent auto-matching runs.
The date this ERP customer record was first loaded into Marquis IQ from the source system. Useful for identifying recently imported records that may not yet have been through the mastering workflow.
The date this ERP account was assigned to its Master Customer record, either by auto-match or manual assignment. Combined with Added Date, this lets you see how long a record sat unmatched before assignment.
The blended, final confidence score (0-100) that Marquis IQ assigns to the match between this ERP account and its Master Customer. Combines signals from the Marquis internal algorithm and Dun & Bradstreet data. Scores above 70 indicate a high-confidence match. Lower scores warrant review before relying on the assignment.
Note: This is the single best column for prioritizing records that need manual review. Sort ascending to surface low-confidence assignments first.
The internal code used by the Marquis IQ matching algorithm to score this record using non-third-party data signals (for example, Taxpayer ID, address structure, name similarity). One input to the overall Match Confidence score.
The match quality grade returned by Dun & Bradstreet, reflecting how well individual elements of the ERP record (name, address, etc.) matched the D&B database entry. Provided as-is from D&B. Refer to D&B documentation for grade definitions.
The numeric score returned by Dun & Bradstreet indicating how closely the ERP customer name matched the D&B recommended name for this record. A component of the overall matching process - a low Name Match Score on a high-confidence record often means the ERP name is abbreviated or formatted differently, not that the match is wrong.
Identifies the method Marquis IQ used to automatically link this ERP account to its Master Customer (for example, matched on Tax ID, matched on name and address, matched on D&B enrichment). Helps you understand why the system made the match it did.
Describes how precisely the ERP billing address matched the D&B address during enrichment (for example, exact street-level match, city-level match, postal code match). A weaker address match type does not necessarily mean the overall record match is wrong - name and Tax ID signals may have provided sufficient confidence.
All fields in this section are provided by Marquis IQ - either from Dun & Bradstreet data or from the Marquis matching algorithm. None of these values come from the client's ERP systems.
Marquis IQ's internal identifier (format: EN-XXXXX) for the Site level of the customer hierarchy. ERP accounts that share the same physical address are grouped under the same Enrichment Number, even if they are formatted differently across records or ERP systems. Acts as Marquis's equivalent of a D&B DUNS number at the location level.
Note: See the Enrich Overview for a full explanation of the Family - Master - Site hierarchy.
The official primary business name returned by the Marquis IQ enrichment process for this customer record. For D&B-matched records, this is the name as registered with D&B. Useful for comparing against the raw ERP Customer Name to understand how much the ERP record differs from the official business name.
The status assigned by the Marquis IQ matching algorithm indicating whether enrichment was successful for this record. Records with a non-enriched status may have limited data in the other MIQ columns.
The real-world operating condition of this business as reported by Dun & Bradstreet (for example, Active, Out of Business). Reflects the company's actual operating status, which may differ from its status in the ERP if the ERP has not been updated. Marquis IQ displays this value as-is from D&B.
The 6-digit NAICS (North American Industry Classification System) code for this customer's primary industry, provided by Marquis IQ enrichment. NAICS codes describe the economic activity of a business. Use alongside Primary NAICS Description for readability.
The plain-English industry description corresponding to the Primary NAICS Code (for example, "Motor Vehicle Parts Manufacturing" or "Industrial Machinery Distribution"). This is the column to show by default when industry classification is needed.
The 4-digit SIC (Standard Industrial Classification) code for this customer's primary industry, provided by Marquis IQ enrichment. SIC is an older classification system but still widely used in financial and government reporting contexts.
The plain-English industry description corresponding to the Primary SIC Code.
The UNSPSC (United Nations Standard Products and Services Code) classification code for this customer's primary industry, provided by Marquis IQ enrichment. UNSPSC is a global coding system used in procurement and supply chain contexts.
The plain-English description corresponding to the Primary UNSPSC Code.
The company website address, provided by Dun & Bradstreet enrichment data. May be blank for customers that did not return a D&B match or where D&B does not have a website on record.
The date when Marquis IQ last refreshed the D&B enrichment data for this customer record. Enrichment data is periodically updated; this field helps identify records that may be carrying stale enrichment results.
Invoiced revenue figures used for prioritization and filtering. These are not financially validated totals - use them to focus mastering effort on high-value records first.
Total invoiced revenue for this ERP customer record over the last twelve months, through yesterday. Shown by default because it is the most practical signal for prioritizing the assignment queue - sort descending to work highest-revenue unassigned records first.
Important: LTM Invoiced is not a financially validated number and should not be used for reporting. It is intended for prioritization and filtering only. Use the IQ modules for reconciled revenue analytics.
Total invoiced revenue for this ERP customer record over the last five years. Useful for identifying customers with longer commercial relationships that may have lower recent activity but represent significant historical value. Not a financially validated figure.
Total all-time invoiced revenue for this ERP customer record across all available transaction history. Helpful for identifying dormant but historically significant customers. Not a financially validated figure.
Missing a column or need clarification? Let us know.