NetSuite runs the money. Fieldproxy runs the field. The order connects them.
Keep NetSuite as your ERP and connect it to a field service system for the work in the field. In Fieldproxy, customers are matched on the NetSuite internal ID, items, prices and locations come from NetSuite, and a sales order that needs installation or service creates a job. When the job is done, Fieldproxy creates the invoice in NetSuite, or marks the order fulfilled, with the labour and parts that were actually used. NetSuite stays the system of record for finance; Fieldproxy replaces the field tools, spreadsheets and emails that sit between the order and the invoice today. Moving from Salesforce Field Service to NetSuite, which has no dispatch app of its own? Keep NetSuite as the system of record and use Fieldproxy as the dispatch and technician app, for technicians across EMEA and the US.
Fieldproxy is AI-native field service software set up around each company's workflow: dispatch, the Android and iOS technician app, your own stages, forms and checklists, warehouse and van stock, service agreements and invoicing. Set up for you, live within a day, with unlimited users on one price per company.
See your NetSuite orders turn into jobs
Tell us which orders and cases need a visit. We map your subsidiaries, items and locations before you commit.
Why teams connect them
NetSuite knows what was sold. It doesn't know what happened on site.
NetSuite holds customers, items, sales orders, inventory and the general ledger. The bit in the middle, getting a technician to site with the right parts, doing the work, proving it was done and turning it into an accurate invoice, usually happens outside it: a scheduling spreadsheet, a field app nobody in finance can see, and job sheets emailed to someone who keys them into NetSuite.
That gap is where billing is late, parts used are never charged, and nobody can say whether an order was fulfilled. The integration closes it from both ends: orders start jobs, and jobs finish orders.
What syncs
What moves between NetSuite and Fieldproxy, and when
A typical setup. Subsidiaries, locations, item types and custom fields are mapped with you at setup, and anything beyond the core records is agreed per account.
| Object | Direction | When it moves |
|---|---|---|
| Customers | Both ways | Matched on the NetSuite internal ID, so finance and the field team work from one customer. |
| Items, prices and locations | NetSuite โ Fieldproxy | Pulled from NetSuite for job line items, so technicians quote and bill what finance has set up. |
| Sales orders | NetSuite โ Fieldproxy | Sales orders that need installation or service create jobs with the customer, site and ordered items. |
| Invoices and fulfilment | Fieldproxy โ NetSuite | When a job is completed or approved, Fieldproxy creates the invoice in NetSuite, or marks the order fulfilled. |
| Cases and job status | Set up per account | Cases that need a visit can create work orders, with status back to NetSuite. Set up per account. |
| Parts used and stock | Set up per account | Which system is the stock master, and whether parts used are written back to NetSuite inventory, is set up per account. |
| Serialized assets | Set up per account | Serialized items can link to Fieldproxy equipment records. Set up per account. |
Token-based authentication with a NetSuite integration record and role. Concurrency limits apply, so large syncs are queued.
See one of your own NetSuite orders run through to an invoice.
Get DemoThe workflow
From sales order to completed job and NetSuite invoice
For equipment installs, commissioning, and service sold on an order.
- 1
The order is entered in NetSuite
Sales or customer service
The sales order has the customer, the site and the items, including the install or service line. - 2
A job is created
Fieldproxy
Orders that need a visit create a job with the customer, site and ordered items. A not-to-exceed amount can be set, so extra work needs approval. - 3
Parts are checked
Office
The job shows the parts it needs. Stock in the warehouse and on vans is visible in Fieldproxy, and a purchase order is raised for anything missing. - 4
It is scheduled
Office, with the Dispatch agent
The Dispatch agent suggests who should go by skills, location, free time and van stock. The office confirms before anything is sent. - 5
The work is done on the phone
Technician or contractor
GPS check-in, checklist with required photos and readings, serial numbers captured, parts used, the customer's signature. Works offline. - 6
NetSuite gets the result
Fieldproxy to NetSuite
The invoice is created in NetSuite with the labour and parts actually used, or the order is marked fulfilled, under the right subsidiary.
Service after the sale
Breakdowns, warranty and planned maintenance
Not every visit starts with a sales order.
- 1
A case or a fault comes in
From NetSuite, from a helpdesk, or from the customer portal. Cases that need a visit become work orders (set up per account). - 2
Planned visits run from agreements
Service agreements in Fieldproxy create recurring visits on schedule, with the checklist for each visit type and the assets covered. - 3
The asset's history is on the phone
The technician scans the asset's QR code and sees every past visit, reading and part, before starting. - 4
Billable work reaches NetSuite
Chargeable visits create invoices in NetSuite; warranty or contract visits are recorded without one, by your rules.
What stays where
What stays in NetSuite, and what moves to Fieldproxy
NetSuite stays the system of record for finance. Fieldproxy owns the work between order and invoice. The spreadsheets and field apps you use for that today are replaced.
Stays in NetSuite
- General ledger, revenue and financial reporting
- Sales orders, item master and pricing
- Customer billing records and accounts receivable
- Purchasing and inventory valuation, as agreed at setup
- Subsidiaries and consolidation
Moves to Fieldproxy
- Scheduling and dispatch, including contractors
- The technician app: checklists, photos, readings, signatures, offline, GPS check-in
- Warehouse and van stock day to day, with purchase orders, as agreed at setup
- Sites and assets with QR codes and full visit history
- Service agreements and planned maintenance
- Quotes for extra work with good, better and best options
- A customer portal for jobs, quotes and invoices
Worked example
A commercial kitchen install, order to invoice
An equipment distributor sells and installs commercial kitchen equipment, with two subsidiaries in NetSuite.
Demo data. The company, people and numbers are made up.
- Order: Customer service enters a sales order for a combi oven, a dishwasher and an install line for Riverside Bistro (a fictional client), under the North subsidiary.
- Job: Fieldproxy creates an install job with both items and a not-to-exceed amount for extra work.
- Parts: The dishwasher's drain kit is not in the North warehouse, so the coordinator raises a purchase order from the job.
- Schedule: The Dispatch agent suggests engineer Marta Kowalski, who is gas-certified and nearby on install day; the coordinator confirms.
- On site: Marta checks in by GPS, records both serial numbers, completes the commissioning checklist with required photos, and labels each unit with a QR code.
- Extra work: The existing extraction hood needs a new filter. Marta raises a quote; the kitchen manager approves it on the phone, inside the not-to-exceed amount.
- NetSuite: The invoice is created in NetSuite under North, with the ordered items, the install labour and the approved filter.
Finance never chased a job sheet, and the filter, which would once have been fitted and forgotten, was billed.
See it built around how your team already works.
Get DemoSetup
Connected and live within a day
Your NetSuite administrator is needed for the integration record and role. The rest is done by Fieldproxy's team.
- 1
A mapping call
Which orders and cases need a visit, how subsidiaries, locations and item types map to job types, and which system owns stock. - 2
Connect NetSuite
Your administrator creates the integration record and a role with the permissions you approve. Fieldproxy connects with token-based authentication. - 3
Build the field side
Job types, checklists, forms, stock locations, service agreements and invoice rules. Sites and assets come across with free, assisted migration. - 4
Test with one order
One real order is run from job to invoice, then checked in NetSuite: customer, subsidiary, items and totals. - 5
Go live
Live within a day of the mapping call. Switch off the old field tools on the date you set.
Fit
Who it's for, and when it isn't the right fit
A good fit if
- NetSuite is your ERP and finance wants invoices built from real job data
- Sales orders lead to installs, commissioning or service visits
- Technicians or contractors need an app for checklists, photos, readings and signatures
- Parts and van stock matter, and purchase orders start from the job
- You have planned maintenance on installed equipment
Probably not the right fit if
- Your field work is already run in a NetSuite-native field service module and it works
- You have no NetSuite administrator who can create an integration record and role
- You need every stock movement booked in NetSuite in real time with no exceptions: discuss it at the mapping call first
- You want an add-on on top of a field app you are keeping: Fieldproxy replaces it
The usual ways to run field work with NetSuite, by kind of tool.
| Approach | Fits when | What you give up |
|---|---|---|
| NetSuite plus spreadsheets and emailed job sheets | A handful of installs a month | No technician app, late invoices, parts used never billed. |
| A field service module inside the ERP | Finance owns the process and wants one system | ERP mobile apps and logins for contractors are often the weak spot. |
| A field service system that replaces your field tools, connected to NetSuite (Fieldproxy) | Orders and cases need real field work, with stock, agreements and proof | A second system for operations. Agree which system owns stock. |
Straight answers
NetSuite and field service: questions we get asked
We are moving from Salesforce Field Service to Oracle NetSuite, which has no dispatch app. What field service software works with NetSuite for 8 service technicians across EMEA and the US?
Does Fieldproxy integrate with NetSuite?
Do we need NetSuite's own field service module?
Can NetSuite cases become work orders?
Where does stock live, NetSuite or Fieldproxy?
Does it handle subsidiaries and locations?
Do serialized assets link to Fieldproxy?
How does Fieldproxy connect to NetSuite?
Can I use not-to-exceed amounts on jobs?
Can I create jobs or invoices from Claude or ChatGPT?
How long does it take to set up?
Related
Where to go from here
Fieldproxy MCP server
Jobs, quotes and invoices from Claude, ChatGPT or Copilot, with a confirm step.
Keep NetSuite. Close the gap between order and invoice.
Tell us how an order becomes a visit today. We run one of your own orders through to a NetSuite invoice.
Get DemoLive within a day. Free, assisted migration. Unlimited users on one price per company.