NEW 21-day free trial · onboard your first project in a day · cancel anytime Start free

What the Field Reported Isn't What the Accountant Booked

What the field reported isn't what the accountant booked. The pay application math doesn't match the schedule of values, and the sub invoice doesn't match the work that was agreed.

Drive billing from the field record so the pay app, the SOV, and the AR all match reality by construction.

Start free

What's actually breaking

The money has to match the work, but in a disconnected stack the field reports progress in one place and the accountant books revenue in another. The pay app gets built from a stale SOV, the sub invoice references work nobody confirmed, and the AR slowly stops describing the actual job.

Why it happens

Field and accounting drift apart because the billing is built separately from the work. When the schedule of values, the pay application, and the field progress are not the same record, every billing cycle is a manual reconciliation, and the reconciliation is where the errors live.

The fixes that make it worse

Try
Rebuild the pay app by hand each month
Reality
Re-deriving the pay app from a spreadsheet every cycle reintroduces the same math errors and the same drift from the SOV.
Try
Book revenue from a stale SOV
Reality
A schedule of values that is not tied to field progress bills against numbers that no longer match the job.
Try
Approve sub invoices without the field record
Reality
Paying a sub invoice that references unconfirmed work is how backcharges and overpayments happen.

How to fix it

  1. Anchor billing to the SOV
    The schedule of values is the authority, and the pay app is computed from it, not re-typed.
  2. Drive progress from the field
    Billable progress comes from the captured field record, so the pay app matches what was actually done.
  3. Hold retainage by rule
    Retainage is applied by the workflow, not calculated by hand, so it is right every cycle.
  4. Match sub invoices to confirmed work
    A sub invoice is checked against the field record before it is approved.

Where Scaftra fits

Scaftra drives AR from the work: the schedule of values is the authority, the pay application is computed from it against captured field progress, and retainage and lien releases ride the same workflow. The AR matches reality because it is built from the field record, not reconciled to it.

Scaftra runs the Pay App, SOV, and retainage off the field record, so the money describes the work by construction instead of being reconciled to it every month.

The surfaces that close the gap

  • SOV as the authority: The schedule of values owns the billing structure; the pay app computes from it.
  • Field-driven progress: Billable progress comes from the captured field record, not a re-type.
  • Retainage and lien releases by workflow: Held amounts and releases ride the billing workflow, computed not hand-keyed.
  • Sub invoices checked against work: Invoices are matched to confirmed field activity before approval.

What changes

  • The pay app matches the SOV every cycle, no manual rebuild.
  • AR describes the actual job, not a stale spreadsheet.
  • Fewer overpayments and surprise backcharges to subs.
  • Billing cycles get faster because the math is already right.

Who feels this most

Controllers reconciling pay appsPMs managing draws and subs
  • Controllers reconciling pay apps.Controllers who rebuild the pay app by hand and chase why it doesn't match the SOV.
  • PMs managing draws and subs.PMs reconciling field progress against billing and sub invoices.

Frequently asked questions

How does Scaftra keep AR matching the field?
Billing is driven from the captured field record: the SOV is the authority, the pay app computes from it against real progress, and retainage rides the workflow, so the money matches the work by construction.
Does it handle retainage and lien releases?
Yes, they're part of the billing workflow rather than a hand calculation, so they're consistent every cycle.
Who feels this most?
Controllers and PMs reconciling pay apps, where the pay app math doesn't match the SOV and the sub invoice doesn't match the agreed work.

One job. One record. From the field to the books.

Bring one project onto Scaftra. We'll set up your trades, your rooms, your proof chain, and your vendor portal, and connect it to the financial system you already run.