Skip to content
NetSuite Reference

customer

master

The customer master: identity, status, terms, credit control and the entity-level balance rollups, plus the sales-history date stamps.

Module: EntitiesNo partition column
Grain note

the balance columns here are entity-level rollups — PER-SUBSIDIARY receivables live on customersubsidiaryrelationship, and in a OneWorld account that is the number finance means.

Notes

There is no plain subsidiary column on this record; representingsubsidiary is the intercompany representation, not the customer's owning subsidiary. Join through customersubsidiaryrelationship for the real customer-to-subsidiary edge.

What the badges mean
master
Data class: what the record holds — master data, transaction documents, control/configuration, or a documented convenience record. NetSuite has no product-family or schema axis, so this is the whole classification.

Structural facts — how the record is partitioned, not a trap by itself

Subsidiary-scoped
The record carries a subsidiary column that partitions its rows, so the generated SQL anchors it. On a few records the column is a multiselect rather than a scalar foreign key — the table notes say which (see the quirks guide).
Location-scoped
The record carries a location column — an org segment in NetSuite before it is a warehouse — and the generated SQL anchors it the same way.

Join & extract hazards — verify before you rely on this

View
A documented convenience record rather than a stored one. Land the records it stands in for instead of assuming it extracts as-is — the table notes say where the rows actually live.
In field listings, the Key chip marks a primary-key field, and the T/F chip marks a check-box column Connect returns as a 'T'/'F' string.

Business record

The business record this table holds, with Oracle’s own documentation for it: the Analytics Browser page that defines the queryable fields, and the current-release Records Browser page that corroborates it.

Fields

19 fields · 1 key

19 fields.

Table fields: position, field name, description, data type, and flags. 19 fields.
#FieldDescriptionTypeFlags
1idInternal IDNUMBER
Primary-key field
2entityidEntity IDVARCHAR
3entitytitleCustomer ID as displayedVARCHAR
4altnameCustomer nameVARCHAR
5companynameCompany nameVARCHAR
6ispersonIndividual rather than a companyVARCHAR
7isinactiveInactiveVARCHAR
8datecreatedDate createdTIMESTAMP
9lastmodifieddateLast modified — the incremental watermarkTIMESTAMP
10parentParent customer (internal id)NUMBER
11currencyCustomer currency (internal id)NUMBER
12termsPayment terms (internal id)NUMBER
13categoryCustomer category (internal id)NUMBER
14pricelevelDefault price level (internal id)NUMBER
15entitystatusCustomer status (internal id)NUMBER
16creditlimitCredit limitNUMBER
17oncreditholdOn credit holdVARCHAR
18balancesearchEntity-level balance — per-subsidiary balances live on customersubsidiaryrelationshipNUMBER
19representingsubsidiarySubsidiary this customer represents for intercompany (internal id)NUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the Connect-landed copy of customer on Databricks — dates are real DATE/TIMESTAMP columns and need no conversion, and the partition anchors are already in place. The lastmodifieddate watermark is in place too. Set your Unity Catalog location, schema, and filter values below; they’re substituted into the SQL and the copy button.

Query parameters

4 parameters not filled: <catalog>, <schema>, <id>, <watermark>

-- ============================================================
-- Table  : customer — The customer master: identity, status, terms, credit control and the entity-level balance rollups, plus the sales-history date stamps.
-- Purpose: Column-selected read of customer — auto-generated from field metadata
-- Grain  : One row per id
-- Caution: the balance columns here are entity-level rollups — PER-SUBSIDIARY receivables live on customersubsidiaryrelationship, and in a OneWorld account that is the number finance means.
-- Notes  : Auto-generated skeleton for NetSuite data landed in your lakehouse from a SuiteAnalytics Connect (or SuiteQL) extract — it never addresses live NetSuite. Identifiers are lowercase as NetSuite2.com renders them. Select-type columns hold numeric internal ids: BUILTIN.DF() display resolution exists only at extraction time, so decode ids by joining the landed list records; see quirks #display-values. Check-box columns arrive as 'T'/'F' strings; see quirks #tf-booleans.
-- ============================================================
SELECT
  t.id AS "Internal ID",
  t.entityid AS "Entity ID",
  t.entitytitle AS "Customer ID as displayed",
  t.altname AS "Customer name",
  t.companyname AS "Company name",
  t.isperson AS "Individual rather than a company",  -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
  t.isinactive AS "Inactive",  -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
  t.datecreated AS "Date created",
  t.lastmodifieddate AS "Last modified — the incremental watermark",
  t.parent AS "Parent customer (internal id)",
  t.currency AS "Customer currency (internal id)",
  t.terms AS "Payment terms (internal id)",
  t.category AS "Customer category (internal id)",
  t.pricelevel AS "Default price level (internal id)",
  t.entitystatus AS "Customer status (internal id)",
  t.creditlimit AS "Credit limit",
  t.oncredithold AS "On credit hold",  -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
  t.balancesearch AS "Entity-level balance — per-subsidiary balances live on customersubsidiaryrelationship",
  t.representingsubsidiary AS "Subsidiary this customer represents for intercompany (internal id)"
FROM <catalog>.<schema>.customer t
WHERE
  1 = 1  -- no partition column on this record; the filters below are optional
  -- AND t.id = <id>
  -- AND t.lastmodifieddate >= TIMESTAMP '<watermark>'  -- inserts and updates only — deletes never appear here; diff deletedrecord, which is itself blind to line-level deletes (see quirks #deletes)
ORDER BY t.id;

Verified August 2026 · Analytics Browser 2021.1 · corroborated 2025.2

Select columns hold internal ids, not display text — see decoding display values.

Relationships

Diagram of 1-hop neighbors — join details below. Document-link edges are highlighted; they chain one document to the next and are the joins newcomers most often get wrong.

Join details

  • entitycustomerforeign key · 1:1
    ON entity.customer = customer.id
  • customercustomersubsidiaryrelationshipforeign key · 1:N
    ON customer.id = customersubsidiaryrelationship.entity
  • customercurrencyforeign key · N:1
    ON customer.currency = currency.id
  • customertermforeign key · N:1
    ON customer.terms = term.id

Browse more Entities tables

More Entities tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle or NetSuite. NetSuite is a registered trademark of Oracle and/or its affiliates.