Continuous Over/Under: Aspire's headline report, recomputed on every sync

Bottom line: Over/Under is Aspire's headline job report, and it used to arrive once a month. TreasuryFlow now recomputes it every time your job data lands.

What Over/Under is

For each job, earned revenue minus billed to date. Positive means you have done work you have not invoiced yet. Negative means you have billed ahead of the work.

We kept Aspire's sign convention so the number reads the way your team already reads it.

What shipped

Over/Under is now a live column in the Operator Cockpit, recomputed on every upload or sync rather than at month end.

The portfolio view totals it across every job. When nothing more urgent is in the way, the headline names the most underbilled job, so the next invoice to write is obvious.

Honest when data is missing

Earned comes from the earned-revenue column when your export has one. Otherwise it is derived from contract value and percent complete, and the row is flagged as derived.

If either earned or billed is missing, the job shows no Over/Under at all. We do not print a number we cannot support.

Percent billed beside it

Next to Over/Under sits percent billed, billed against contract. Together they separate a small gap on a large job from a large gap on a small one.

It needs a job export with billed to date and either earned revenue or percent complete. Nothing else changes about how you run Aspire.

From number to invoice

An underbilled job becomes a billing handoff: a file your bookkeeper can invoice from, shaped to the landscape job layout it detects.

Why it matters

Underbilled work is cash you have earned and not asked for. Seeing it on Monday instead of at month end shortens the gap between finishing work and getting paid. That gap is where crews wait on payroll.

Our security practices are described on the security page.