For construction & contractors

Every job costed. Revenue that matches the work.

The WIP schedule is what your bank and your surety read first. Aleq derives it from posted job costs — percent complete cost-to-cost under ASC 606, earned against billed, over- and under-billings on the balance sheet — and keeps it current every day.

job-level WIP · cost-to-cost 606 · committed costs from POs
Job 214 · Riverside build
incl. approved COsContract value$12,600,000
budget $9,000,000Costs to date$5,580,000
cost-to-cost · 62%Revenue earned$7,812,000
Billed to date$7,200,000
costs + earnings in excess of billings$612,000
The reality today

The job knows its costs. The books find out at month-end.

Field ops lives in Procore, hours in a timesheet app, the WIP schedule in Excel, and the ledger in QuickBooks — so percent complete is a quarter-end argument, and over- and under-billings surface after the margin is already gone.

your stack todaydays lost
Procore / field ops0
Timesheets & receiptsexported to CSV+1
Excel WIP schedulekeyed by hand+2
QuickBooksweeks late+6
quarter-end true-upreconciled at close+5
a number you can trustday 14
Aleq — one ledger, real-time
day 0DRCash$12,400.00
CRAccounts receivable$12,400.00
balanced · posted day 0 · source: bank line BT-1142
Worked example

One job, month three — earned, billed, and tied.

Percent complete comes from posted costs, not a spreadsheet cell. Revenue follows the work, and the over- or under-billing lands on the balance sheet where it belongs.

Job 214 · percent-complete revenue
1
the job
Contract and budget, on the ledger
Contract value$12,600,000 · incl. approved COs
Cost budget$9,000,000
Costs posted this month$558,000 · bills, subs, labor
2
the engine
Cost-to-cost runs from posted costs
Percent complete$5,580,000 ÷ $9,000,000 = 62%
DRContract assetcosts + earnings in excess$781,200
CRContract revenueJob 214 · this period$781,200
earned $7,812,000 · billed $7,200,000under-billed $612,000 · on the balance sheet
3
the change order
CO-7 · +$1,140,000 — a contract modification
TreatmentASC 606 modification · schedule re-derives from the change date
Waits foryour sign-off — prior periods untouched
Sub invoice · three-way matched posted to the job
Auto Proven on your books — runs alone, every entry logged and reversible.
BillMeridian Concrete · $445,200
ChecksPO + work-in-place tie · within cost code budget
Sub invoice · three-way matched

A subcontractor bill that ties to its PO and the work in place posts straight to the job's WIP — coded to the cost code, inside budget, logged and reversible.

DRWIP · Job 214 · concrete$445,200
CRAccounts payable$445,200
matched · coded to the job · logged

The books for construction, run for you.

Aleq is the system of record and the controller that runs it. The work runs inside your policy and against your approval thresholds, and every entry it posts is signed, sourced, and reversible.

Job WIP, live. Costs to date, percent complete, earned revenue, billings, and over/under — per job, off the ledger.

job cost & WIP · derived from posted costs

The job, from committed cost to earned revenue.

01

Committed costs

POs three-way matched to receipts and sub invoices before a dollar moves.

02

Percent-complete revenue

Cost-to-cost under ASC 606, derived from posted job costs — not a spreadsheet estimate.

03

Change orders

Treated as contract modifications: the schedule re-derives from the change date, held for sign-off.

04

Budget vs actual per job

Every job against its budget, flagged when a cost code runs hot.

It speaks your accounting natively.

The standards and subledgers your model runs on — derived and posted by Aleq, not configured by you.

ASC 606 · revenue over timeASC 842 · equipment leasesJob WIP subledgerCommitted costsRetainage
FAQ

Questions, answered.

The WIP schedule is a live view off the ledger.

Connect read-only. Aleq posts your job costs, derives percent complete from the ledger, and hands you a live WIP schedule — earned, billed, and tied.