Skip to content
NetSuite Reference

term

master

The payment-terms master: one row per terms code with the whole date-driven rule set behind it — days till net due, discount percentage and expiry, day-of-month due, and the installment schedule columns.

Module: PricingNo partition column
Grain note

terms are a RULE, not a date: nothing here tells you when a specific invoice is due. Read the document's own duedate and use these columns to explain it, not to recompute it.

Notes

Analytics label is "Terms"; the record id is singular. customer.terms, vendor.terms and transaction.terms all point here. Two discount columns coexist — the plain percentage and the date-driven one — and which is in force depends on how the terms record was configured, so read both. The installment percentages hang off a record that is not cataloged here.

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.

Fields

17 fields · 1 key

17 fields.

Table fields: position, field name, description, data type, and flags. 17 fields.
#FieldDescriptionTypeFlags
1idInternal IDNUMBER
Primary-key field
2nameTerms nameVARCHAR
3daysuntilnetdueDays till net dueNUMBER
4dayofmonthnetdueDay of month net dueNUMBER
5duenextmonthifwithindaysRoll to next month if raised within this many daysNUMBER
6discountpercentEarly-payment discount percentageNUMBER
7discountpercentdatedrivenDate-driven discount percentage — the twin of discountpercentNUMBER
8daysuntilexpiryDays till the discount expiresNUMBER
9daydiscountexpiresDay of month the discount expiresNUMBER
10installmentTerms pay in installmentsVARCHAR
11splitevenlyInstallments split evenlyVARCHAR
12recurrencecountNumber of installmentsNUMBER
13recurrencefrequencyInstallment frequency (internal id)NUMBER
14repeateveryRepeat every n frequency unitsNUMBER
15preferredPreferred termsVARCHAR
16isinactiveInactiveVARCHAR
17externalidExternal IDVARCHAR

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the Connect-landed copy of term on Databricks — dates are real DATE/TIMESTAMP columns and need no conversion, and the partition anchors are already in place. This record carries no modification stamp, and the snippet says so where the watermark would otherwise go. Set your Unity Catalog location, schema, and filter values below; they’re substituted into the SQL and the copy button.

Query parameters

3 parameters not filled: <catalog>, <schema>, <id>

-- ============================================================
-- Table  : term — The payment-terms master: one row per terms code with the whole date-driven rule set behind it — days till net due, discount percentage and expiry, day-of-month due, and the installment schedule columns.
-- Purpose: Column-selected read of term — auto-generated from field metadata
-- Grain  : One row per id
-- Caution: terms are a RULE, not a date: nothing here tells you when a specific invoice is due. Read the document's own duedate and use these columns to explain it, not to recompute it.
-- 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.name AS "Terms name",
  t.daysuntilnetdue AS "Days till net due",
  t.dayofmonthnetdue AS "Day of month net due",
  t.duenextmonthifwithindays AS "Roll to next month if raised within this many days",
  t.discountpercent AS "Early-payment discount percentage",
  t.discountpercentdatedriven AS "Date-driven discount percentage — the twin of discountpercent",
  t.daysuntilexpiry AS "Days till the discount expires",
  t.daydiscountexpires AS "Day of month the discount expires",
  t.installment AS "Terms pay in installments",  -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
  t.splitevenly AS "Installments split evenly",  -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
  t.recurrencecount AS "Number of installments",
  t.recurrencefrequency AS "Installment frequency (internal id)",
  t.repeatevery AS "Repeat every n frequency units",
  t.preferred AS "Preferred terms",  -- '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.externalid AS "External ID"
FROM <catalog>.<schema>.term t
WHERE
  1 = 1  -- no partition column on this record; the filters below are optional
  -- AND t.id = <id>
  -- no lastmodifieddate on this record — there is no watermark column, so incremental extraction must full-refresh it (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

  • transactiontermforeign key · N:1
    ON transaction.terms = term.id
  • customertermforeign key · N:1
    ON customer.terms = term.id
  • vendortermforeign key · N:1
    ON vendor.terms = term.id

Browse more Pricing tables

More Pricing 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.