paymentmethod
masterThe payment-method list: one row per method a document can carry, with its type and the GL account payments land in.
Browser page name is paymentMethod. transaction.paymentmethod points here. merchantaccounts (the payment-processing profiles a method is wired to) is a MULTISELECT — it holds several ids at once, so it is authored as a field row for completeness but is never an equality filter and no edge is drawn from it.
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
7 fields · 1 key
7 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | id | Internal ID | NUMBER | Primary-key field |
| 2 | name | Payment method name | VARCHAR | |
| 3 | methodtype | Method type (internal id) | NUMBER | |
| 4 | account | GL account payments on this method land in (internal id) | NUMBER | |
| 5 | merchantaccounts | Payment-processing profiles — MULTISELECT, not a scalar foreign key | VARCHAR | |
| 6 | isinactive | Inactive | VARCHAR | |
| 7 | externalid | External ID | VARCHAR |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the Connect-landed copy of paymentmethod 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 : paymentmethod — The payment-method list: one row per method a document can carry, with its type and the GL account payments land in.
-- Purpose: Column-selected read of paymentmethod — auto-generated from field metadata
-- Grain : One row per id
-- 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 "Payment method name",
t.methodtype AS "Method type (internal id)",
t.account AS "GL account payments on this method land in (internal id)",
t.merchantaccounts AS "Payment-processing profiles — MULTISELECT, not a scalar foreign key",
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>.paymentmethod 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.paymentmethod = paymentmethod.id
More Transactions tables
- previoustransactionlinelinkThe backward line-link table: the exact mirror of nexttransactionlinelink, travelling upstream from an invoice line to the sales-order line it originated on.
- salesinvoicedThe invoiced-sales analytics view: the ordered twin plus a posting period, one row per invoiced transaction line with amount, quantity and the estimated cost and gross-profit columns.
- salesorderedThe ordered-sales analytics view: one row per sales transaction line with the amount, quantity, estimated cost and estimated gross profit already computed, alongside the customer, item, and the class/department/location segments.
- transactionThe document header for every transaction type NetSuite records — sales orders, purchase orders, fulfillments, receipts, invoices, journals — separated by the type column rather than by table.
- transactionaccountinglineThe accounting projection of a transaction line: base-currency amount, debit, credit and net, per accounting book, with the GL account and audit-number stamps.
- transactionbillingaddressThe billing address stamped on a document: the same fourteen columns as the shipping twin, keyed by the address key the transaction header's billing pointer resolves to.