FieldEdge unbilled work: the sync that feels like billing but isn't

Last updated November 16, 2026 · 6 min read

Short answer

FieldEdge's QuickBooks sync moves invoiced data to the books — it does not create invoices. Work orders that never completed the invoice-ready step sync nothing, silently. The check joins completed work orders against invoices and lists every WO that never billed.

The data reality

Where to export: FieldEdge exports/reports — completed work orders crossed against invoices synced to QuickBooks; the check lists completed WOs with no invoice counterpart.

Columns that matter: WO # · Customer · Completed date · WO total · Invoice #

FieldEdge's QuickBooks sync is one-way per invoice and runs on triggers — a work order not marked invoice-ready syncs nothing, silently. Membership-based flat-rate pricing shows partial WO totals until invoicing. The check distinguishes 'synced invoice exists' from 'WO complete' rather than trusting either status alone.

Why this system leaks

A residential service call completes at 4:40 pm. The tech marks the WO complete; the office's invoice-ready step — setting the WO to bill and letting the sync carry it to QuickBooks — happens during a review that Friday's volume overruns. The WO is complete in FieldEdge, absent from QuickBooks, and every report in each system is internally consistent. The office believes the sync guarantees billing; the sync only guarantees transport of whatever was invoice-ready.

The sync creates an illusion of automatic billing that the invoicing step's manual nature contradicts. FieldEdge's dashboards count completed WOs; QuickBooks counts synced invoices; no screen in either system compares the two sets. The leak lives exactly in the comparison nobody performs — until a check reads both sides from exports.

The sync is a courier, not a clerk

FieldEdge's QuickBooks integration transports invoice-ready data; it does not decide what should be invoiced. The 'invoice-ready' flag is a human step, and steps skipped on busy days produce WOs that complete without ever becoming transportable. Understanding the sync as a courier — not a clerk — is the mental fix; the check is the operational one.

Two dashboards, zero comparisons

FieldEdge counts completed WOs. QuickBooks counts received invoices. Each dashboard is accurate; neither compares against the other. The shop's true billing completeness exists only in the join — which the check performs from exports, with the sync triggers, membership terms, and flat-rate cases handled.

Back-invoice through FieldEdge, not around it

Found WOs should be invoiced through FieldEdge so the sync carries them to the books — side-door invoices in QuickBooks create the next reconciliation problem. The check's exception list is designed for this: each line becomes a FieldEdge invoice, and next month's count of gaps approaches zero.

A worked example

A residential HVAC shop's FieldEdge data, Jan–Oct: 1,876 completed WOs, 1,867 invoices synced. Nine uninvoiced — several held at 'complete' without the invoice-ready flag after peak-day chaos, one a membership tune-up with added repair work never billed, totaling $723.

Recorded work
$723.00
Invoiced
$0.00
Residual
$723.00

Residual = $723 across nine WOs — under half a percent, but concentrated in exactly the shapes the sync hides best: incomplete invoice-ready flags and membership add-on repairs. All nine recover with back-invoicing through FieldEdge so the books stay clean.

What the data cannot show

  • Membership flat-rate coverage is verified against the membership's terms where exports show them — disputed coverage terms resolve from the membership agreement, not the check.
  • The check reads exports, so it sees the FieldEdge account as it stands — WOs deleted or merged before export are outside any export-based verification.

Questions shops ask

Does FieldEdge automatically invoice completed work orders?

No — WOs must be made invoice-ready; the QuickBooks sync then transports them. Skipping the flag leaves the WO complete and unbilled indefinitely. The check finds every such WO from your exports.

If it synced to QuickBooks, is it invoiced?

Invoices that sync are real — but the sync says nothing about WOs that never became invoices. Both systems look internally consistent around the hole. Only the completed-WOs-versus-invoices join reveals it.

How do membership jobs leak in FieldEdge?

Tune-ups bill at membership coverage, but repair work discovered during the visit still needs its own billing — and 'member' often triggers a mental no-charge. The check verifies membership add-on work against the plan's terms and flags the free repairs.

See a sample report for your export

See a sample report for your export

Related