Zuper + Business Central Integration
Connect Microsoft Dynamics 365 Business Central to Zuper so completed field jobs post straight to your general ledger — invoices, inventory usage, and job costing — without anyone re-keying a work order into the ERP.
What Does This Integration Do?
Field service and back-office finance rarely run on the same system. Business Central holds your customers, items, and general ledger; Zuper holds your technicians, schedules, and completed work. Without a connection, finance re-keys every job into a sales invoice by hand, and nobody in the field can see current stock or pricing.
This integration pushes customer, item, and pricing master data from Business Central into Zuper, and pushes completed jobs back as sales invoices, inventory consumption, and job costing entries — so field data becomes financial data without a second round of data entry.
What Syncs, and Which Way
Most Zuper + Business Central projects sync the same core objects. Whether job costing posts at completion or at invoice approval is the first thing we scope with you.
Customers
Business Central → Zuper
Customer, site, and billing details kept current for scheduling
Items & Pricing
Business Central → Zuper
Parts, labor rates, and price lists available to technicians in the field
Job Completion
Zuper → Business Central
Completed jobs become sales invoices or orders
Inventory Consumption
Two-way
Parts used on a job decrement warehouse stock in real time
Job Costing & GL
Zuper → Business Central
Labor, parts, and travel cost posted against the right job dimension
Invoices
Zuper → Business Central
Invoice status and payment terms reflected back on the job record
How We Build It
Business Central exposes standard OData v4 API pages and supports custom AL extensions; Zuper exposes its own REST API and webhooks for job and inventory events. Power Automate can also sit between the two for lighter-weight flows.
| Approach | What it is | Best for | Watch out for |
|---|---|---|---|
| Business Central API pages (OData v4) | Standard REST endpoints for customers, items, and sales documents | Reliable, supported field-level access | Complex custom fields may need an AL extension |
| Custom AL extension | Purpose-built API pages and business logic inside Business Central | Job costing dimensions and non-standard postings | Requires ERP developer resource and a sandbox environment |
| Zuper REST API + webhooks | Fires on job completion, inventory usage, and status change | Triggering ERP postings at the right moment | Retry and idempotency handling needed for webhook delivery |
| Power Automate / iPaaS | Orchestration wrapping both APIs | Mid-complexity flows without heavy custom code | Complex job costing logic may exceed no-code limits |
Where a template usually falls short: posting one invoice from one completed job is the easy half. Getting job costing dimensions right, keeping inventory in sync without double-counting parts used across two systems, and handling partial or re-opened jobs cleanly is where a real ERP integration earns its keep.
How Much Does It Cost?
A Zuper + Business Central integration typically costs between $5,000 and $20,000 to implement, depending on whether job costing and inventory sync are included alongside basic invoicing.
| Approach | Implementation | Ongoing |
|---|---|---|
| Job-to-invoice sync (one-way) | $5,000 – $8,500 | Support retainer only, no platform fee |
| Two-way with inventory sync | $8,000 – $14,000 | iPaaS/Power Automate + support retainer |
| Full job costing & GL dimension mapping | $12,000 – $20,000+ | Support retainer only, no platform fee |
The number moves most on whether inventory consumption syncs in real time, how many job costing dimensions need to post to the general ledger, and whether a custom AL extension is required versus the standard API pages. We quote a fixed price after a scoping call, so you know the cost before we write a line of code.
How Long Does It Take?
The usual bottleneck is agreeing on job costing dimensions and how partial or re-opened jobs should post — both settled before go-live.
Job-to-invoice only
Completed jobs post as sales invoices via the standard API, one-way.
Costing & inventory sync
Two-way inventory consumption, job costing dimensions, and GL posting.
What Does Our Integration Process Look Like?
Every engagement follows the same five stages — you get a fixed-price scope and a mapping sheet you sign off before we build.
Discover
We review your Business Central item catalog, costing setup, and which job events should post.
Map
We document every field, direction, transformation, and error rule before building.
Build
We implement against a Business Central sandbox environment and a Zuper sandbox.
Test
We run real job scenarios — partial completions, re-opens, retries, and inventory edge cases.
Support
We monitor after go-live, with alerting, logging, and a named contact.
Frequently Asked Questions
Yes. When a job is marked complete, the job, parts used, and labor are transformed into a sales invoice or order through Business Central's standard API pages.
Yes, if you choose two-way sync. Item availability and pricing can be pulled into Zuper so technicians and dispatchers see accurate stock before scheduling a job.
Yes. Labor, parts, and travel cost from a completed job can post against the job costing dimensions your finance team already uses in Business Central.
That's scoped up front. We can create a credit memo, hold the posting, or route it for manual review — whichever fits your accounting policy.
Most projects run $5,000 to $20,000 depending on whether inventory sync and job costing dimensions are included. See the cost table above for a full breakdown.
Yes. Rescue work — jobs that stopped posting invoices and inventory counts that drifted out of sync — is a regular part of our practice.
Ready to Connect Business Central to Zuper?
Every completed job that gets re-keyed into the ERP by hand is a chance for a pricing mismatch or a missed invoice. A scoped integration removes that gap permanently — and you'll know the exact cost before we start.