buildflowsLet’s build

Offer

WIP & Cash Forecast

An automated WIP schedule and cash forecast your controller can trace to the source rows.

WIP, over/under billing and retainage usually live in workbook formulas nobody can test, fed by exports from systems that share no project key. A WIP schedule can satisfy every accounting identity and still be wrong, and a project missing from accounting simply shows as zero. Cash forecasting gets rebuilt from scratch every month instead of refreshing on its own.

Start your scoping brief Or book a 30-min call

Who it's for

  • CFOs and controllers who rebuild the WIP schedule by hand at every month-end
  • Contractors whose sureties or lenders read the WIP and expect it to tie out
  • Finance teams running Procore with Sage, QuickBooks or another construction accounting system
  • Owners who want to see margin fade on a job before the job is over

What you get out of it

  • A WIP schedule with earned revenue, billed to date, over billing, under billing and gross profit that refreshes from source data
  • Backlog, AR and a cash forecast built from issued invoices and bills, read alongside the WIP
  • Project drill-downs by cost code: budget, committed, cost to date, EAC and fade or gain by month
  • An exceptions page for unmapped projects, jobs over EAC and cost variances between project and accounting systems
  • Blank shown as blank, never zero, so an unintegrated job cannot pass for an idle one
  • Read-only SQL access to the gold layer so finance can check the exact rows behind any total

What's included

WIP logic review

We document how your team calculates percent complete, earned revenue, over/under billing and retainage today, and agree the definitions before any code is written.

Project-to-job crosswalk

Procore projects are linked to accounting jobs through a controller-maintained mapping first, then exact project numbers, and name matches only when unambiguous. The rest go to an exceptions list.

Fabric lakehouse and governed measures

Source data lands in bronze, silver and gold layers, and a semantic model defines each WIP measure once so every page computes it the same way.

Quality gate

Checks run before every refresh, such as every project with cost being mapped or listed as an exception. A blocking failure stops publishing and keeps the last good version live.

Power BI WIP and cash pages

Portfolio, WIP schedule, project drill-down, backlog, billing and retainage, AR and collections, cash forecast and exceptions.

Handoff package

Metric definitions, runbooks, a repository with every pipeline and report definition, and a session with the people who will maintain it.

How it runs

  1. 01

    Free scoping call

    We review your current WIP schedule, systems and close process, then agree a fixed scope and fixed price.

  2. 02

    Definitions and mapping

    We agree WIP definitions with your controller and build the project-to-job crosswalk, surfacing unmatched records early.

  3. 03

    Build and validate

    Pipelines, quality rules and measures are built as code and tested against a month you have already closed.

  4. 04

    Parallel month-end

    The automated WIP runs alongside your spreadsheet for a close so every difference is explained before you rely on it.

  5. 05

    Handoff

    We hand over the repository, definitions and runbooks, including who renews which credentials and when.

What we need from you

  • Your current WIP schedule and the workbook or process behind it
  • Read-only access to Procore and your accounting system
  • A controller or project accountant who can confirm definitions and review the parallel close
  • A Microsoft Fabric or Power BI workspace, or approval to create one in your tenant

Not included

  • Accounting or revenue-recognition advice; your team and your CPA own the policies, and we implement them
  • Posting entries or writing anything back to your accounting system
  • Microsoft Fabric capacity and Power BI licensing
  • Fixing historical source data; unmatched or invalid records are flagged for your team to correct at the source

See it in real builds

Frequently asked questions

How much does it cost?

Fixed scope, fixed price, agreed after a free scoping call. The quote depends on your systems, how many projects need mapping and which pages you need beyond the core WIP schedule.

How long does it take?

It depends on your systems and how quickly read access is granted, so we scope the timeline in the call. We plan around a parallel month-end, so the schedule also follows your close calendar.

Will it match our current WIP schedule?

It will match the definitions we agree with your controller. Where it differs from the spreadsheet, the parallel close shows why. In our builds those reviews have exposed formula errors that the old workbook was hiding.

Which accounting systems do you support?

We have built WIP reporting on Sage 100 and QuickBooks Online alongside Procore. Other construction accounting systems can work if their data is reachable by API, database or reliable export, which we check in the scoping call.

Do you need write access to our accounting system?

No. The build only reads, using scoped credentials, and production credentials belong in Azure Key Vault. Nothing changes in your systems of record.

Can we start with the free WIP template?

Yes. The free WIP schedule template is a good way to agree definitions first. When updating it by hand each month becomes the bottleneck, the same definitions carry into an automated build.

Start with a free scoping call

Fixed scope, fixed price, agreed before we start.

Tell us your systems and what the result needs to look like. We reply within two business days with an honest take on fit, scope, and next steps.

Start your scoping brief Estimate what your monthly report costs

Other ways to start