Skip to content
NetSuite Reference

transactionbillingaddress

transaction

The 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.

Module: TransactionsNo partition column
Grain note

this is the address AT THE TIME OF THE DOCUMENT, not the customer's current address — never substitute the entity record's address for it when restating history.

Notes

Browser page name is transactionBillingAddress (label "Address") — same shape, same nkey convention, same point-in-time caveat as transactionshippingaddress. Two separate records rather than one address table with a role column, so a document that ships and bills to different places needs both joins.

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

14 fields · 1 key

14 fields.

Table fields: position, field name, description, data type, and flags. 14 fields.
#FieldDescriptionTypeFlags
1nkeyAddress key — what transaction.billingaddress resolves toNUMBER
Primary-key field
2addresseeAddresseeVARCHAR
3attentionAttention lineVARCHAR
4addrtextThe whole address as one formatted blockVARCHAR
5addr1Address line 1VARCHAR
6addr2Address line 2VARCHAR
7addr3Address line 3VARCHAR
8cityCityVARCHAR
9stateState or province as textVARCHAR
10dropdownstateState or province (internal id)NUMBER
11zipPostal codeVARCHAR
12countryCountry (internal id)NUMBER
13addrphonePhoneVARCHAR
14overrideAddress was edited away from the entity default on this documentVARCHAR

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the Connect-landed copy of transactionbillingaddress 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

2 parameters not filled: <catalog>, <schema>

-- ============================================================
-- Table  : transactionbillingaddress — The 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.
-- Purpose: Column-selected read of transactionbillingaddress — auto-generated from field metadata
-- Grain  : One row per nkey
-- Caution: this is the address AT THE TIME OF THE DOCUMENT, not the customer's current address — never substitute the entity record's address for it when restating history.
-- 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.nkey AS "Address key — what transaction.billingaddress resolves to",
  t.addressee AS "Addressee",
  t.attention AS "Attention line",
  t.addrtext AS "The whole address as one formatted block",
  t.addr1 AS "Address line 1",
  t.addr2 AS "Address line 2",
  t.addr3 AS "Address line 3",
  t.city AS "City",
  t.state AS "State or province as text",
  t.dropdownstate AS "State or province (internal id)",
  t.zip AS "Postal code",
  t.country AS "Country (internal id)",
  t.addrphone AS "Phone",
  t.override AS "Address was edited away from the entity default on this document"  -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
FROM <catalog>.<schema>.transactionbillingaddress t
WHERE
  1 = 1  -- no partition column on this record; the filters below are optional
  -- no lastmodifieddate on this record — there is no watermark column, so incremental extraction must full-refresh it (see quirks #deletes)
ORDER BY t.nkey;

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

  • transactiontransactionbillingaddressforeign key · N:1
    ON transaction.billingaddress = transactionbillingaddress.nkey

Browse more Transactions tables

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