Skip to main content

Transaction Types (SuiteBuilder)

Comprehensive guide to transaction types in NetSuite and how they affect custom fields, forms, workflows, and reporting.


Overview

Transaction types determine where your custom fields, forms, and automations apply. Understanding transaction types is essential for proper SuiteBuilder configuration.

TRANSACTION TYPE SCOPE
═══════════════════════════════════════════════════════════════════════════════

When you create a:
┌─────────────────────────────────────────────────────────────────────────────┐
│ Custom Transaction Body Field │
│ Custom Transaction Line Field │
│ Custom Transaction Form │
│ Workflow │
│ Saved Search │
└─────────────────────────────────────────────────────────────────────────────┘


You must specify which transaction
types it applies to:
─────────────────────────────────
☑ Sales Order
☑ Invoice
☐ Cash Sale
☑ Purchase Order
☐ Vendor Bill
... etc.

Transaction Types by Category

Sales Transactions

Transaction TypeInternal IDDescriptionGL Impact
EstimateestimateQuote/proposal to customerNone
Sales OrdersalesorderCustomer purchase commitmentNone (until fulfilled)
Item FulfillmentitemfulfillmentShip goods to customerCOGS, Inventory
InvoiceinvoiceBill customer for goods/servicesRevenue, AR
Cash SalecashsaleImmediate payment saleRevenue, Cash
Credit MemocreditmemoCredit to customerReduces Revenue, AR
Return AuthorizationreturnauthorizationRMA approvalNone
Customer PaymentcustomerpaymentReceipt of paymentReduces AR, Cash
Customer RefundcustomerrefundReturn payment to customerReduces Cash
Customer DepositcustomerdepositAdvance paymentLiability

Purchase Transactions

Transaction TypeInternal IDDescriptionGL Impact
Purchase RequisitionpurchaserequisitionInternal purchase requestNone
Purchase OrderpurchaseorderOrder to vendorNone (commitment)
Item ReceiptitemreceiptReceive goods from vendorInventory
Vendor BillvendorbillBill from vendorExpense/Inventory, AP
Vendor CreditvendorcreditCredit from vendorReduces AP
Vendor Return AuthorizationvendorreturnauthorizationReturn approval to vendorNone
Vendor PaymentvendorpaymentPay vendorReduces AP, Cash
Vendor PrepaymentvendorprepaymentAdvance to vendorAsset

Inventory Transactions

Transaction TypeInternal IDDescriptionGL Impact
Inventory AdjustmentinventoryadjustmentAdjust quantitiesInventory, Adjustment
Inventory TransferinventorytransferMove between locations (instant)None (same GL)
Transfer OrdertransferorderMove between locations (tracked)In-Transit
Assembly BuildassemblybuildBuild assembly from componentsInventory
Assembly UnbuildassemblyunbuildDisassemble to componentsInventory
Work OrderworkorderManufacturing orderWIP
Work Order IssueworkorderissueIssue materials to WOWIP
Work Order CompletionworkordercompletionComplete assembly to inventoryInventory
Work Order CloseworkordercloseClose work orderVariance

Financial Transactions

Transaction TypeInternal IDDescriptionGL Impact
Journal EntryjournalentryManual GL entryVarious
Statistical Journal EntrystatisticaljournalentryNon-posting journalNone
Intercompany Journal EntryintercompanyjournalentryIC journalVarious
DepositdepositBank depositCash
Deposit ApplicationdepositapplicationApply customer depositLiability
CheckcheckWrite checkCash, Expense
Expense ReportexpensereportEmployee expenseExpense, Payable
PaycheckpaycheckEmployee payPayroll

CRM Transactions

Transaction TypeInternal IDDescriptionGL Impact
OpportunityopportunitySales pipeline recordNone
CasesupportcaseCustomer support ticketNone
IssueissueBug/issue trackingNone

Using Transaction Types in SuiteBuilder

Custom Transaction Body Fields

TRANSACTION BODY FIELD - APPLIES TO
═══════════════════════════════════════════════════════════════════════════════

Navigation: Customization → Lists, Records, & Fields → Transaction Body Fields

Field: Delivery Priority (custbody_delivery_priority)

Applies To: Best Practice:
───────────────── ───────────────
☑ Sales Order Select ONLY the transaction
☑ Item Fulfillment types where this field is
☐ Invoice relevant to avoid form
☐ Cash Sale clutter.
☑ Transfer Order
☐ Purchase Order
☐ ... (many more)

IMPORTANT:
• Field will appear on all selected transaction types
• Selecting too many creates maintenance overhead
• Consider if field should "flow" between linked transactions

Custom Transaction Line Fields

TRANSACTION LINE FIELD - APPLIES TO
═══════════════════════════════════════════════════════════════════════════════

Navigation: Customization → Lists, Records, & Fields → Transaction Line Fields

Field: Warehouse Instructions (custcol_warehouse_instruct)

Sublist: Transaction Types:
───────── ─────────────────
● Items ☑ Sales Order
○ Expenses ☑ Item Fulfillment
○ Partners ☐ Invoice
○ Sales Team ☑ Purchase Order
☑ Item Receipt

Line fields appear in the specified sublist
only on the selected transaction types.

Custom Transaction Forms

TRANSACTION FORMS BY TYPE
═══════════════════════════════════════════════════════════════════════════════

Navigation: Customization → Forms → Transaction Forms

Each transaction type has its own form(s):

Sales Order Forms:
┌────────────────────────────────────────┐
│ • Standard Sales Order │ ← Default
│ • Sales Order - Wholesale │ ← Custom
│ • Sales Order - E-Commerce │ ← Custom
│ • Sales Order - International │ ← Custom
└────────────────────────────────────────┘

Purchase Order Forms:
┌────────────────────────────────────────┐
│ • Standard Purchase Order │ ← Default
│ • Purchase Order - Capital │ ← Custom
│ • Purchase Order - Services │ ← Custom
└────────────────────────────────────────┘

Form Features:
• Show/hide fields per form
• Reorder fields and tabs
• Set default values
• Assign to specific roles

Transaction Type Groups

For efficiency, NetSuite provides transaction type groups for bulk selection.

TRANSACTION TYPE GROUPS
═══════════════════════════════════════════════════════════════════════════════

When configuring "Applies To" for fields:

☑ All Sales Transactions
└── Includes: Estimate, Sales Order, Invoice, Cash Sale,
Credit Memo, Return Authorization, etc.

☑ All Purchase Transactions
└── Includes: Purchase Requisition, Purchase Order,
Vendor Bill, Vendor Credit, etc.

☑ All Inventory Transactions
└── Includes: Inventory Adjustment, Transfer Order,
Assembly Build, Work Order, etc.

☑ All Financial Transactions
└── Includes: Journal Entry, Check, Deposit, etc.

Tip: Use groups for broadly applicable fields,
individual types for specific fields.

Transaction Field Flow

Understanding how fields flow between linked transactions.

FIELD VALUE FLOW (CREATEDFROM)
═══════════════════════════════════════════════════════════════════════════════

Sales Order #SO-001 Invoice #INV-001
┌─────────────────────────────┐ ┌─────────────────────────────┐
│ custbody_project: PRJ-100 │──────▶│ custbody_project: PRJ-100 │
│ custbody_priority: High │ │ custbody_priority: High │
│ │ │ (Values copied) │
└─────────────────────────────┘ └─────────────────────────────┘

Field Flow Behavior:
────────────────────
1. When Invoice is created from Sales Order
2. Body fields on both types are COPIED automatically
3. Line fields also flow to matching lines

Configuration:
• Field must "Apply To" both transaction types
• Sourcing available on child transaction
• Scripts can modify after copy

Transaction Types in Workflows

WORKFLOW TRANSACTION TYPE SELECTION
═══════════════════════════════════════════════════════════════════════════════

Navigation: Customization → Workflow → Workflows → New

Base Record: [Transaction]
Sub Types:
☑ Sales Order
☑ Invoice
☐ Cash Sale
☐ Estimate
... (select applicable types)

IMPORTANT:
• Workflow applies ONLY to selected sub types
• State conditions can reference type-specific fields
• Actions execute in context of the transaction type

Example: Approval Workflow
Sub Types: Purchase Order, Vendor Bill
Condition: amount > 10000
Action: Route to finance manager

Saved Searches and Reporting

TRANSACTION SAVED SEARCH - TYPE FILTER
═══════════════════════════════════════════════════════════════════════════════

Navigation: Reports → Saved Searches → All Saved Searches → New

Search Type: Transaction

Criteria:
┌─────────────────────────────────────────────────────────────────────────────┐
│ Type is any of Sales Order, Invoice, Cash Sale │
│ Date within This Month │
│ Status is any of Open, Pending Fulfillment │
└─────────────────────────────────────────────────────────────────────────────┘

Results:
┌─────────────────────────────────────────────────────────────────────────────┐
│ Date | Type | Document Number | Customer | Amount | Status │
└─────────────────────────────────────────────────────────────────────────────┘

Type Formulas:
• {type} returns internal ID: "SalesOrd", "CustInvc"
• {recordtype} returns full name
• Use CASE statements for custom labels

Best Practices

Field Applies-To Strategy

ScenarioRecommendation
Field relevant everywhereUse "All Sales Transactions" group
Field for specific processSelect only needed types
Field should flowEnsure both parent and child selected
Reporting fieldConsider if needed on all transaction types

Form Management

PracticeBenefit
Create forms per roleSimplified UI per function
Hide unused fieldsFaster data entry
Consistent field orderTraining efficiency
Test with real rolesVerify access works

Performance Considerations

ConsiderationImpact
Fewer applies-toLess form loading overhead
Targeted workflowsFaster transaction saves
Specific searchesQuicker search execution

References