A field can be visible on a NetSuite transaction but absent from Ramp. Check which sublist contains the field. Ramp’s native integration supports custom line fields on the Expenses sublist.
The Expenses Sublist vs. the Items Sublist
NetSuite transaction records can contain two separate sublists for expenses and items:
Expenses Sublist
Use the Expenses sublist for costs coded directly to a GL account. Lines can include Account, Amount, Department, Class, Location, Customer, and Memo. Common examples include software, travel, meals, and services.
Items Sublist
Use the Items sublist for inventory and other items selected from the NetSuite Item catalog. It supports purchasing and receiving processes and has a separate field structure from the Expenses sublist.
Create custom line fields under Customization › Lists, Records & Fields › Transaction Column Fields. The Applies To settings determine which transactions and sublists use the field. Expense and item contexts are separate, and Ramp only imports supported fields from the expense context.
What Ramp supports
Per Ramp's own documentation, expense level sync includes:
"Expense level fields: Account, department, class, location, customer, and Billable (Y/N) as well as any line level expense custom fields."
Ramp also states:
"Line level custom fields should be on the expense tab to be available."
Ramp must find the field on the Expenses sublist for it to be available for coding or automation. This also applies to custom segments used as transaction line columns. Custom segments must be visible on the relevant Credit Card, Bill, or Bill Payment forms.
Common configuration issues
PO Backed Purchasing Fields
Teams often use custom fields on purchase order item lines for project codes, contract references, or approval tiers. Those fields may work in NetSuite’s purchasing process while remaining unavailable through Ramp’s native expense integration.
Broad "Applies To" Configurations
A field can appear on a Bill’s Items sublist without being enabled for expenses. Its presence on the transaction alone does not make it available in Ramp.
Migration from Middleware or CSV Workflows
A connector or CSV process may have used Items sublist fields that Ramp’s native integration cannot access. Review those dependencies when changing integrations.
How to Check Which Sublist Your Custom Field Is On
- Go to
Customization › Lists, Records & Fields › Transaction Column Fields - Click into the custom field in question
- Navigate to the Applies To subtab
- Review which transaction types and sublist contexts are checked
- Confirm the field is applied to the expense context of Credit Card Transaction and/or Bill records, and is visible on those forms
A field enabled only for purchasing or item receipt contexts will not be available through Ramp’s expense integration. Check its expense settings for bills and card transactions.
What You Can Do
Before relying on a custom field in Ramp, check its Applies To settings, the sublist where it appears, and its visibility on the relevant forms. Fields on the Items sublist will not be available for Ramp’s expense coding and automation.