SAP for finance and stock. Fieldproxy for the technician. The order ties them together.
Keep SAP as the system of record for finance and stock, and run the field work in a system built for technicians. In Fieldproxy, business partners and ship-to addresses come from SAP so jobs use SAP's customer numbers, and material numbers and prices come from SAP too. A service or maintenance order that needs a visit creates a job; when the job is done, confirmation, time and the parts used go back to the order, with parts sent for goods issue. Completed jobs can create billing requests in SAP, so invoicing stays in SAP. This works with SAP S/4HANA and SAP Business One.
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, van stock, service agreements and invoicing. Set up for you, live within a day, with unlimited users on one price per company.
See your SAP service orders turn into jobs
Tell us which order types need a visit. We map your plants, materials and confirmations before you commit.
Why teams connect them
SAP is the record. It is not the technician's favourite app.
SAP runs finance, materials and orders for a lot of service organisations. The field side is where it struggles: technicians and contractors need something fast on a phone, that works offline in a plant room, with checklists and photos, and SAP mobile options often mean extra licences and a long project. So orders are printed, job sheets come back on paper or in a separate app, and someone confirms them in SAP days later, with parts used often missing.
A field service system that replaces the field tools and talks to SAP keeps SAP in charge of finance and stock, and sends confirmations and goods issues back from the job itself, not from a job sheet typed in later.
What syncs
What moves between SAP and Fieldproxy, and when
A typical setup for SAP S/4HANA or SAP Business One. Order types, plants and material groups are mapped with your SAP team, and anything beyond the core objects is scoped per account.
| Object | Direction | When it moves |
|---|---|---|
| Customers and sites | SAP โ Fieldproxy | Business partners and ship-to addresses are pulled, so jobs use SAP's customer numbers. |
| Materials and prices | SAP โ Fieldproxy | Material numbers and prices are pulled for the job's parts and line items. |
| Service or maintenance orders | Both ways | Orders that need a visit create jobs. Confirmation, time and parts go back to the order. |
| Parts used | Fieldproxy โ SAP | Parts used on the job are sent back for goods issue against the order. |
| Billing | Fieldproxy โ SAP | Completed jobs can create billing requests in SAP, so invoicing stays in SAP. |
| Equipment and functional locations | Set up per account | Fieldproxy holds sites and assets with QR codes. Reading equipment from SAP is set up per account. |
| Service contracts and warranty | Set up per account | Set up per account. |
Connection: a technical user in SAP with roles your SAP team approves. Your SAP team runs a test order through to confirmation before go-live.
See one of your own SAP order types run through to confirmation.
Get DemoThe workflow
From service order to confirmation and billing in SAP
For repairs, inspections and installs raised as orders in SAP.
- 1
An order needs a visit
Planner, in SAP
A service or maintenance order of a mapped type is released. Orders that don't need anyone on site stay in SAP. - 2
A job is created
Fieldproxy
Business partner, ship-to address, order number and planned materials come across. The order type sets the job type and checklist. - 3
It is scheduled
Dispatcher, with the Dispatch agent
The Dispatch agent ranks technicians by skills, certifications, location and van stock; the dispatcher confirms. Changes are previewed and can be undone. - 4
The work is done on the phone
Technician or contractor
GPS check-in, the asset's QR code history, your checklist with required photos and readings, materials used by SAP number, and the customer's signature. Works offline. - 5
SAP gets the confirmation
Fieldproxy to SAP
Confirmation and time go back to the order, and parts used are sent for goods issue. - 6
Billing stays in SAP
Fieldproxy to SAP
Billable work creates a billing request in SAP, and finance invoices as it does today.
Contractors and planned work
Contractors and recurring visits, without SAP seats
Where the field team includes people SAP was never going to license.
- 1
Contractors get their own access
Regular contractors get a login, one-off contractors get a job link. They see only their jobs. - 2
Same proof as your own staff
The same required checklist items, photos, readings and signatures, so SAP gets the same quality of confirmation. - 3
Planned visits on schedule
Service agreements in Fieldproxy create recurring visits with the checklist for each visit type, alongside orders coming from SAP.
What stays where
What stays in SAP, and what moves to Fieldproxy
SAP stays the system of record for finance and stock. Fieldproxy owns the work in the field. The paper job sheets, spreadsheets and field apps between them are replaced.
Stays in SAP
- Finance, billing and receivables
- Material master, prices and stock valuation
- Service and maintenance orders, and their planning
- Business partners and customer master data
- Reporting on top of SAP
Moves to Fieldproxy
- Scheduling and dispatch, including contractors
- The technician app: checklists, photos, readings, signatures, offline, GPS check-in
- Sites and assets with QR codes and visit history
- Van stock day to day, with purchase orders
- Service agreements and planned visits
- Quotes for extra work found on site
- Your own stages and forms, in any of 27 languages
Worked example
A compressor repair, order to goods issue
An industrial equipment service company runs SAP S/4HANA for finance and materials, with two plants and a mix of employed and contract engineers.
Demo data. The company, people and numbers are made up.
- Order: Planner Lukas Brandt releases a repair order for a compressor at Eastbrook Foods (a fictional client), with a valve kit as planned material.
- Job: Fieldproxy creates a repair job with the business partner, ship-to address, order number and the valve kit by SAP material number.
- Dispatch: The Dispatch agent suggests contract engineer Priya Shah, who is certified for that compressor range and has the valve kit on her van. Lukas confirms.
- On site: Priya scans the compressor's QR code, sees its last two service visits, fits the valve kit, uses one extra gasket, records pressures and gets the site manager's signature.
- Back in SAP: Confirmation and time go back to the order, and the valve kit and gasket are sent for goods issue.
- Billing: A billing request is created in SAP; finance invoices Eastbrook as usual.
Priya never needed an SAP licence, and the extra gasket, usually lost on a paper job sheet, reached SAP.
See it built around how your team already works.
Get DemoSetup
Connected and live within a day
Your SAP team creates the technical user and exposes the services. The field side is built by Fieldproxy's team.
- 1
A mapping call
Which order types need a visit, which plants and material groups apply, and what goes back: confirmation, time, parts, billing. - 2
SAP access
Your SAP team creates a technical user with the roles they approve and exposes the services for the objects being synced. - 3
Map order types and materials
Order types, plants and material groups are mapped to Fieldproxy job types, checklists and stock locations. - 4
Build the field side
Checklists, forms, assets, van stock, contractor access and service agreements. Sites and assets come across with free, assisted migration. - 5
Test an order, then go live
A test order is run through to confirmation in SAP before go-live. The field side is live within a day of the mapping call.
Fit
Who it's for, and when it isn't the right fit
A good fit if
- SAP S/4HANA or Business One runs your finance and materials
- Technicians and contractors need a fast app that works offline
- Confirmations and parts used reach SAP late or incomplete today
- You have planned maintenance or contractor work SAP was never set up for
- You want SAP to stay the system of record
Probably not the right fit if
- You have already rolled out SAP's own field service product and it works
- Your SAP team cannot create a technical user or expose services this year
- You need deep plant maintenance planning to move out of SAP: Fieldproxy runs the visit, SAP keeps the planning
- 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 SAP, by kind of tool.
| Approach | Fits when | What you give up |
|---|---|---|
| SAP with printed orders and paper job sheets | A small in-house team | Late confirmations, parts used missing, no photos or proof. |
| SAP's own field service or mobile products | You want everything inside SAP and have the budget and team | Licences per user, including contractors, and a longer project. |
| A field service system that replaces your field tools, connected to SAP (Fieldproxy) | You want SAP to stay the record and the field side running quickly | A second system for the field team. Agree the objects and write-backs with your SAP team. |
Straight answers
SAP and field service: questions we get asked
Does Fieldproxy integrate with SAP?
Does SAP stay the system of record?
How do parts used in the field get back to SAP?
Does invoicing happen in SAP or Fieldproxy?
What does Fieldproxy need on the SAP side?
Does it work with SAP ECC or SAP Plant Maintenance?
Do technicians or contractors need SAP licences?
How are order types and plants handled?
Can I use Copilot, Claude or ChatGPT with it?
How long does it take?
Related
Where to go from here
Keep SAP. Get the field work back into it without retyping.
Tell us which order types need a visit. We show it running on your own plants, materials and job types.
Get DemoLive within a day. Free, assisted migration. Unlimited users on one price per company.