For construction & contractors

Every job costed. Revenue that matches the work.

Aleq is the books for contractors — job costs post as bills clear, percent-complete revenue derives from posted costs under ASC 606, and the WIP schedule is live instead of a month-end spreadsheet.

job-level WIP · cost-to-cost 606 · committed costs from POs
Job 214 · Riverside buildlive
incl. approved COsContract value$4,200,000
budget $3,000,000Costs to date$1,860,000
cost-to-cost · 62%Revenue earned$2,604,000
Billed to date$2,400,000
costs + earnings in excess of billings$204,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 revenuederived
1
the job
Contract and budget, on the ledger
Contract value$4,200,000 · incl. approved COs
Cost budget$3,000,000
Costs posted this month$186,000 · bills, subs, labor
2
the engine
Cost-to-cost runs from posted costs
Percent complete$1,860,000 ÷ $3,000,000 = 62%
DRContract assetcosts + earnings in excess$260,400
CRContract revenueJob 214 · this period$260,400
earned $2,604,000 · billed $2,400,000under-billed $204,000 · on the balance sheet
3
the change order
CO-7 · +$380,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 matchedposted to the job
Auto Proven on your books — runs alone, every entry logged and reversible.
BillMeridian Concrete · $148,400
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$148,400
CRAccounts payable$148,400
matched · coded to the job · logged
what Aleq does

The books for construction, run for you.

Aleq is the system of record and the controller that runs it — it does this work autonomously, inside your policy, and signs every move. Not a tool your team feeds; the colleague that closes the books.

built on the standards you live on

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
See it on your own books.We connect read-only and close one of your months, live. Every entry is logged, sourced, and reversible.
FAQ

Questions, answered.

A work-in-progress schedule reports, for every open job, the contract value, costs to date, estimated cost to complete, percent complete, revenue earned, amounts billed, and the resulting over- or under-billing. Banks and sureties read it before they extend credit, which is why it can't be a quarterly reconstruction. Aleq keeps the WIP schedule live off the ledger: job costs post as bills clear, percent complete derives from posted costs, and earned versus billed is current every day — not rebuilt in Excel at month-end.

Still building the WIP schedule by hand?

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.