ERP
Financial Management
Travel and Expense Management
Ramp NetSuite Integration: Setup, Field Mapping and Sync Errors

Last updated: November 3, 2026 · Independent guide · We do not sell rankings or coverage.
The Ramp NetSuite integration connects through a Ramp SuiteApp, a dedicated Ramp Accountant role and token-based authentication, then posts card transactions as NetSuite credit card transactions, reimbursements and Bill Pay bills as vendor bills, and statement payments as checks. The ongoing work, and the sync errors this guide covers, center on field mapping: subsidiaries, required segments on NetSuite forms, vendors and closed periods.
For the month-end process once the data lands in NetSuite, see our corporate card reconciliation guide.
How we researched this
Every setup step, menu path and error fix below comes from Ramp’s support center, whose articles show no publication date and were checked on November 3, 2026, along with Ramp’s pricing page. We also read the ranking guides from RSM and Anchor Group, which both sell NetSuite services, and Ramp’s blog. They cover the connection steps but say little about specific NetSuite errors and their causes. We did not test a live account.
Before you start
- Ramp plan. Ramp lists the NetSuite integration as “Available on Ramp Plus” (Ramp, no date shown). Ramp’s pricing page lists Plus at $15 per user per month plus a platform fee based on team size, with 20% off for annual billing; the free tier integrates only with QuickBooks Online and Xero (Ramp pricing, no date shown, checked November 3, 2026).
- NetSuite access. You need to sign in to NetSuite as an Administrator. In Ramp, you need the “Connect and disconnect your accounting integration” permission, which a Ramp Admin can grant (Ramp, no date shown).
- Your NetSuite edition. If Setup > Company shows Subsidiary Settings Manager, you have OneWorld and follow the subsidiary setup; if not, Ramp has a separate standard setup (Ramp, no date shown).
- Existing integration. RSM, a NetSuite consultancy, notes that NetSuite will not show in Ramp while another accounting integration is connected (RSM, April 8, 2024).
- Clean vendor list. Duplicate vendor names in NetSuite, including inactive ones, cause sync failures (Ramp, no date shown). Merge them first.
Step 1: Start the connection in Ramp
In Ramp, open the Accounting tab, click Get started now and choose NetSuite. Enter your Account ID from the NetSuite URL, answer the Subsidiary Settings Manager question and click Continue (Ramp, no date shown).
Answer the subsidiary question carefully: linking a OneWorld account through the standard setup causes “Primary Subsidiary” sync errors that need a full reset (Ramp, no date shown).
Step 2: Enable web services and token-based authentication
In NetSuite, go to Setup > Company > Enable Features and open the SuiteCloud tab. Check SOAP Web Services and REST Web Services, then check Token Based Authentication, which sits under Manage Authentication rather than SuiteTalk. Save and click Continue in Ramp (Ramp, no date shown). The integration uses token-based authentication, not OAuth 2.0 (Ramp, no date shown).
Step 3: Install the Ramp SuiteApp and assign the role
Open the SuiteApps button at the top of NetSuite (under the three-dot menu if it is hidden), search for the Ramp SuiteApp and install it. Then go to Setup > Users/Roles > Manage Users, edit your Administrator user, add the Ramp Accountant role on the Access tab and save. If the role does not appear in your role list, sign out and back in (Ramp, no date shown).
On a standard (non-OneWorld) account, you instead create the integration record at Setup > Integration > Manage Integrations > New, customize NetSuite’s Accountant role into a Ramp Accountant role and deploy the Ramp RESTlet script. Copy the client secret into Ramp before leaving that page, because it is shown only once (Ramp, no date shown).
Step 4: Connect the RESTlet and approve access
Go to Customization > Scripting > Script Deployments, filter by script, search for “Ramp API” and click View on customdeploy_ramp_restlet. Paste the External URL into Ramp. Then click Approve access in NetSuite, choose the Ramp Accountant role and click Allow. NetSuite then returns you to Ramp to configure entities (Ramp, no date shown).
Step 5: Map subsidiaries to Ramp entities
Ramp treats each NetSuite subsidiary as a legal entity in one Ramp account and recommends connecting NetSuite before creating extra entities. Create entities at Settings > Companies > + Create legal entity with the name, country, EIN and functional currency. The functional currency cannot be changed later (Ramp, no date shown).
Plan this before you issue cards. A transaction takes the entity of its card, and a card takes the entity of the cardholder’s location when issued. Employees who spend for several entities need a virtual card or fund per entity, since each can hold only one physical card. You can change a transaction’s entity only before the statement is generated (same source).
Step 6: Map the GL accounts
Under Settings > Companies, select the entity, open Payments and then More entity settings to set the credit card liability account, the statement payment account, the cashback account and the default accounting date (Ramp, no date shown).
Each Ramp record posts to NetSuite as shown below (Ramp, no date shown; Ramp blog, November 6, 2025).
| Ramp record | NetSuite record | Accounting effect |
|---|---|---|
| Card transaction | Credit card transaction | Debits expense, credits the card liability account |
| Reimbursement | Vendor bill, employee as vendor | Bill payment also syncs if paid through Ramp |
| Bill Pay bill | Vendor bill | Can sync automatically on approval |
| Statement payment | Check | Debits card liability, credits bank; appears after it clears |
| Accruals, transfers | Journal entry | Transfers debit or credit the Ramp Checking Account |
| Cashback | Entry to the Ramp card account | Debits the Ramp card account, credits your chosen income or expense account |
You can set a default AP account for bills and reimbursements synced from Ramp; otherwise NetSuite uses the vendor’s AP account or the last one used for that subsidiary (same source). Statement payments arrive as checks while your bank feed shows the same withdrawal, so match the two rather than recording the payment twice. Our NetSuite bank reconciliation guide covers the matching pages.
Step 7: Expose departments, classes, locations and custom segments
Ramp maps subsidiary, vendor and body-level custom fields per transaction, and account, department, class, location, customer, billable and expense-tab custom fields per line (Ramp, no date shown).
For a custom segment to show in Ramp:
- The segment appears on the Credit Card, Bill, Bill Payment or Purchase Order form.
- The Ramp Accountant role has Value Management Access set to Full, and Record Access and Search/Reporting Access set to Edit. Set these at Customization > Lists, Records, & Fields > Custom Segments, on the segment’s Permissions tab (Ramp, no date shown).
New NetSuite values such as GL accounts or departments appear in Ramp at the next refresh (Ramp blog, November 6, 2025). If a new value is still missing, refresh Accounting fields in Ramp (Ramp, no date shown).
Step 8: Set coding rules and sync settings
Set field defaults at Accounting Settings > Accounting fields > Edit and build rules at Accounting > Settings > Coding Rules. Mapping rules link one Ramp field, such as merchant, to one accounting field; advanced rules add conditions and percentage splits. Card rules override other rules (Ramp, no date shown).
If you post reimbursements to one vendor, choose an active NetSuite vendor at Accounting > Settings > Sync Settings on the Reimbursements tab (Ramp, no date shown).
Common sync errors and how to fix them
Ramp’s list of sync errors includes rejections for an empty required field, a value not valid for the subsidiary and a missing role permission (Ramp, no date shown).
| Error | Likely cause | Fix |
|---|---|---|
| Please enter value(s) for: Department, Location or another field | Field is mandatory on the NetSuite form but blank in Ramp | Fill the field in Ramp, or open the form (for bills, Transactions > Payables > Enter Bills), click Customize > Customize Form and uncheck Mandatory under Screen Fields, then retry (Ramp) |
| Invalid Field Value for the following field: subsidiary | Inactive subsidiary, vendor not assigned to it, or mapping mismatch | Check Setup > Company > Subsidiaries and the vendor’s Subsidiaries subtab, then retry (Ramp) |
| Account is not available in the chosen default subsidiary | Vendor not mapped to that subsidiary, or a NetSuite vendor approval layer | Add the subsidiary to the vendor record (Ramp) |
| Location must match across line items | Different locations on lines of one transaction | Use one location, or make splits in Ramp before syncing (Ramp) |
| Accounting period closed | Date in a closed period; Ramp does not move the date again on a retry | Change the accounting date or reopen the period, then retry (Ramp) |
| Too many vendors with the same name | Duplicate vendor names, including inactive vendors | Search vendors including inactives, remove duplicates, refresh Ramp (Ramp) |
| Permission Violation: Transactions -> Pay Bills | Role level too low | Set Pay Bills to Edit on the role, then click Retry Sync (Ramp) |
Required fields: fix the coding before you change the form
Ramp’s fix for missing-field errors often includes unchecking Mandatory on the NetSuite form (Ramp, no date shown), and for statement payment errors it calls its form change temporary (Ramp, no date shown). If your reports depend on department or class on every expense, add a Ramp coding rule or default that fills the field instead, so records keep that dimension.
Closed periods: the retry trap
Ramp normally moves a bill dated in a closed period to the next open period, but not when you retry a failed sync. Posting to locked periods needs the Override Period Restrictions permission. If you fix the record directly in NetSuite, use Mark as synced in Ramp so it stops retrying (Ramp, no date shown).
As a month-end control, you can build a NetSuite saved search of transactions posted to the Ramp card liability account in the period you are closing and compare its total to Ramp’s statement for each entity. Our NetSuite saved search guide shows how to build and schedule one.
Limitations of the native integration
- Reconciliation stays in NetSuite. Ramp says that to reconcile, you go to your accounting system and match the amount paid to Ramp (Ramp, no date shown).
- Account-wide limits. Spend limits and underwriting are set for the whole account, not per entity (Ramp, no date shown).
- Batched payments wait. A batched reimbursement payment does not sync until every reimbursement in the batch has synced (Ramp, no date shown).
When companies add a third-party tool or partner
The native SuiteApp covers the connection, mapping and record types above. Teams bring in a NetSuite partner when they need scripting beyond it, such as copying department, class or location from lines to transaction headers (Ramp publishes a bill payment classification script bundle that does this), or when custom forms and approval workflows keep rejecting records. RSM and Anchor Group sell this work; neither lists a price in its guide.
If you match bills to purchase orders, Ramp can pull NetSuite item receipts for three-way match once you enable it in Bill Pay settings (Ramp, no date shown). Our three-way match guide covers the controls around it.
Related guides
- Best AP Automation for NetSuite: Native vs Third-Party
- NetSuite Integration Options: SuiteTalk, RESTlets and iPaaS
- NetSuite Bill Capture: Setup, Accuracy and Limits
Frequently asked questions
Does the Ramp NetSuite integration cost extra?
NetSuite is not available on Ramp’s free plan. Ramp’s pricing page lists it under Plus, at $15 per user per month plus a platform fee based on team size, as checked on November 3, 2026. Enterprise pricing is not published.
How often does Ramp sync with NetSuite?
Ramp’s blog says updates flow every 15 to 20 minutes, and you choose whether records post right after approval or after a second review.
Can one Ramp account post to several NetSuite subsidiaries?
Yes, on Ramp Plus. Each subsidiary becomes a Ramp entity with its own currency and posting accounts, and a transaction takes the entity of its card. One transaction cannot be split across subsidiaries.
What does “Please enter value(s) for: Primary Subsidiary” mean?
Ramp says this error appears when a OneWorld NetSuite account was connected with the standard, no-subsidiary setup. The fix is a full reset of the connection, then reconnecting with the subsidiary setup.
Sources
- Ramp Help: NetSuite integration: Set up with Ramp, no date shown, checked November 3, 2026
- Ramp Help: NetSuite integration: Set up with Ramp (no subsidiaries), no date shown
- Ramp Help: NetSuite overview, no date shown
- Ramp Help: NetSuite integration: API and authentication requirements, no date shown
- Ramp Help: NetSuite integration: Multi-entity changes, no date shown
- Ramp Help: Managing Accounting Rules, no date shown
- Ramp Help: Troubleshoot Integrations, no date shown
- Ramp Help: NetSuite Sync Error, Requires additional information for fields such as Account, Reference No., Location, no date shown
- Ramp Help: NetSuite Sync Error, Statement Payment Requires Additional Info, no date shown
- Ramp Help: NetSuite Sync Error, Please enter value(s) for: Primary Subsidiary, no date shown
- Ramp Help: NetSuite Sync Error, Invalid Field Value for the following field: subsidiary, no date shown
- Ramp Help: NetSuite Sync Error, Subsidiary is not a valid selection, no date shown
- Ramp Help: NetSuite Sync Error, Location Must Match Across Line Items, no date shown
- Ramp Help: Sync error: Accounting period closed, no date shown
- Ramp Help: NetSuite Sync Error, Too many vendors with the same name in NetSuite, no date shown
- Ramp Help: NetSuite Sync Error, Vendor Unapproved for NetSuite Sync, no date shown
- Ramp Help: NetSuite Sync Error, Permission Violation for Transactions -> Pay Bills, no date shown
- Ramp Help: NetSuite sync error, Invalid Field Value for item, no date shown
- Ramp Help: NetSuite integration: Bill payment classification script, no date shown
- Ramp: Pricing, no date shown, checked November 3, 2026 (Ramp sells the product)
- Ramp blog: Common questions about the Ramp NetSuite integration, November 6, 2025 (Ramp sells the product)
- RSM: Setting up NetSuite with Ramp, April 8, 2024 (RSM sells NetSuite services)
- Anchor Group: Integrate Ramp with NetSuite, September 3, 2026 (Anchor Group sells NetSuite services)