term
masterThe 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.
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.
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.
- Subsidiary-scoped
- The record carries a
subsidiarycolumn 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
locationcolumn — an org segment in NetSuite before it is a warehouse — and the generated SQL anchors it the same way. - 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.
Structural facts — how the record is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
'T'/'F' string.Fields
17 fields · 1 key
17 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | id | Internal ID | NUMBER | Primary-key field |
| 2 | name | Terms name | VARCHAR | |
| 3 | daysuntilnetdue | Days till net due | NUMBER | |
| 4 | dayofmonthnetdue | Day of month net due | NUMBER | |
| 5 | duenextmonthifwithindays | Roll to next month if raised within this many days | NUMBER | |
| 6 | discountpercent | Early-payment discount percentage | NUMBER | |
| 7 | discountpercentdatedriven | Date-driven discount percentage — the twin of discountpercent | NUMBER | |
| 8 | daysuntilexpiry | Days till the discount expires | NUMBER | |
| 9 | daydiscountexpires | Day of month the discount expires | NUMBER | |
| 10 | installment | Terms pay in installments | VARCHAR | |
| 11 | splitevenly | Installments split evenly | VARCHAR | |
| 12 | recurrencecount | Number of installments | NUMBER | |
| 13 | recurrencefrequency | Installment frequency (internal id) | NUMBER | |
| 14 | repeatevery | Repeat every n frequency units | NUMBER | |
| 15 | preferred | Preferred terms | VARCHAR | |
| 16 | isinactive | Inactive | VARCHAR | |
| 17 | externalid | External ID | VARCHAR |
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.
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
ON transaction.terms = term.idON customer.terms = term.idON vendor.terms = term.id
More Pricing tables
- pricelevelThe price-level list: one row per level (base price, online price, a customer tier), each with the markup or discount percentage that defines it.
- pricingThe item price matrix: one row per item, price level, currency, quantity break and sale unit, carrying the unit price. This is where a price actually lives.
- pricinggroupThe pricing-group list: four columns naming the groups items are bucketed into for group-level price rules.
- quantitypricingscheduleVolume-break pricing schedules: one row per schedule, naming the base discount, the unit the breaks are counted in, and whether the discount applies marginally or to the whole order.