FieldproxyIntegration guide ยท NetSuite

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.

Book your demo

60 minute video call ยท Step 1 of 2: your details, then pick a time

Number of employees

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.

ObjectDirectionWhen it moves
CustomersBoth waysMatched on the NetSuite internal ID, so finance and the field team work from one customer.
Items, prices and locationsNetSuite โ†’ FieldproxyPulled from NetSuite for job line items, so technicians quote and bill what finance has set up.
Sales ordersNetSuite โ†’ FieldproxySales orders that need installation or service create jobs with the customer, site and ordered items.
Invoices and fulfilmentFieldproxy โ†’ NetSuiteWhen a job is completed or approved, Fieldproxy creates the invoice in NetSuite, or marks the order fulfilled.
Cases and job statusSet up per accountCases that need a visit can create work orders, with status back to NetSuite. Set up per account.
Parts used and stockSet up per accountWhich system is the stock master, and whether parts used are written back to NetSuite inventory, is set up per account.
Serialized assetsSet up per accountSerialized 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 Demo

The workflow

From sales order to completed job and NetSuite invoice

For equipment installs, commissioning, and service sold on an order.

  1. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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
Running several companies? See multi-company field service. Support on Zendesk or another helpdesk? See helpdesk to field dispatch and the Zendesk integration, which is often paired with NetSuite.

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.

  1. 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.
  2. Job: Fieldproxy creates an install job with both items and a not-to-exceed amount for extra work.
  3. Parts: The dishwasher's drain kit is not in the North warehouse, so the coordinator raises a purchase order from the job.
  4. Schedule: The Dispatch agent suggests engineer Marta Kowalski, who is gas-certified and nearby on install day; the coordinator confirms.
  5. 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.
  6. 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.
  7. 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 Demo

Setup

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

    Connect NetSuite

    Your administrator creates the integration record and a role with the permissions you approve. Fieldproxy connects with token-based authentication.
  3. 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. 4

    Test with one order

    One real order is run from job to invoice, then checked in NetSuite: customer, subsidiary, items and totals.
  5. 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.

ApproachFits whenWhat you give up
NetSuite plus spreadsheets and emailed job sheetsA handful of installs a monthNo technician app, late invoices, parts used never billed.
A field service module inside the ERPFinance owns the process and wants one systemERP 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 proofA 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?
Fieldproxy works with NetSuite for this. NetSuite stays the system of record for customers, items, orders, invoices and finance, and Fieldproxy is the dispatch board and the technician app. Customers sync both ways on the NetSuite internal ID, items, prices and locations come from NetSuite, sales orders that need a visit create jobs, and completed jobs create the invoice in NetSuite or mark the order fulfilled. Subsidiaries and locations are mapped at setup, so a job for your EMEA or US subsidiary invoices under that subsidiary and currency and tax stay with NetSuite. Technicians in both regions use the same Android and iOS app, offline when needed. Your Salesforce Field Service data is moved across for you, it is live within a day, and it is one price per company with unlimited users, so 8 technicians or 80 cost the same.
Does Fieldproxy integrate with NetSuite?
Yes. Customers sync both ways on the NetSuite internal ID, items, prices and locations are pulled from NetSuite, sales orders that need a visit create jobs, and completed jobs create invoices or mark the order fulfilled in NetSuite.
Do we need NetSuite's own field service module?
No. The field work runs in Fieldproxy: dispatch, the technician app, checklists, stock on the van and service agreements. NetSuite keeps finance, and Fieldproxy is one price per company with unlimited users, so contractors and crews do not need NetSuite logins.
Can NetSuite cases become work orders?
Yes. Cases or sales orders that need someone on site can create work orders in Fieldproxy, and status updates flow back to NetSuite. Which records and which statuses is set up per account.
Where does stock live, NetSuite or Fieldproxy?
Agreed per account. Items, prices and locations come from NetSuite. Fieldproxy can hold warehouse and van stock with purchase orders; whether parts used on a job are written back to NetSuite inventory, and which system is the stock master, is decided at setup.
Does it handle subsidiaries and locations?
Subsidiaries, locations and item types are mapped at setup, so a job for one subsidiary invoices under that subsidiary. For several companies run as one field operation, see multi-company field service.
Do serialized assets link to Fieldproxy?
Serialized items sold in NetSuite can be linked to equipment records in Fieldproxy, so every visit is on the asset's history. How serial numbers are matched is set up per account.
How does Fieldproxy connect to NetSuite?
Through token-based authentication with a NetSuite integration record and a role your administrator controls. NetSuite has concurrency limits, so large syncs are queued and sent in order.
Can I use not-to-exceed amounts on jobs?
Yes. A not-to-exceed amount can be set on a job, so the technician knows when to stop and get approval before doing more work. That matters when the sales order sets the price.
Can I create jobs or invoices from Claude or ChatGPT?
Yes. Fieldproxy's MCP server lets Claude, ChatGPT or Copilot do anything a user can do in Fieldproxy, including invoices, with a preview to confirm before anything is saved. The invoice then reaches NetSuite like any other.
How long does it take to set up?
The field side is set up around your process and live within a day of the mapping call. The NetSuite integration record and role are created by your administrator, and one order is tested end to end before go-live.

Related

Where to go from here

Multi-company field service

Several subsidiaries or brands, one field operation.

Helpdesk to field dispatch

Tickets and cases that need a visit become dispatched jobs.

Spare parts and stock

Warehouse and van stock with purchase orders.

Fieldproxy MCP server

Jobs, quotes and invoices from Claude, ChatGPT or Copilot, with a confirm step.

Zendesk integration

Ticket to job, often paired with NetSuite for billing.

Dynamics 365 integration

The same pattern for Microsoft Dynamics 365.

All Fieldproxy integrations

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 Demo

Live within a day. Free, assisted migration. Unlimited users on one price per company.