AI Agents That Code Your Invoices and Draft Your Change Orders: What Adaptive's Construction Accounting Launch Means for Job Costs

Every invoice your back office touches by hand costs you about $42. Nearly one in four has to be reworked because of an error. And across the industry, billing mistakes and payment delays quietly consume about 5 percent of revenue — enough to erase the entire margin on a competitively bid job. If you run a contracting business, none of this is news. Your project accountant already knows the numbers arrive late, the change orders are half-documented, and the work-in-progress report describes last month instead of today.

That gap — between what is happening on the jobsite right now and what your books say — is exactly what Adaptive, a construction finance software company, says its new AI agents are built to close. In June 2026 the company launched Project Accounting Agents: software co-workers, each holding a named role on your finance team, that code invoices, call the field for updates, draft change orders, assemble pay applications, and keep the WIP current around the clock. Three months later, investors led by Tidemark put $30 million behind the bet, bringing Adaptive's total funding to $57 million. More than 750 construction companies now run the platform.

Should you care? Even if you never buy the product, the launch is a useful mirror. It names, with unusual precision, the exact bookkeeping workflows where contractors bleed money — and every one of them has a fix you can apply with the tools you already have. Here is what the agents do, where your margin actually leaks, and the checklist for tightening up before (or without) handing the keys to software.

What Adaptive actually launched: seven agents, seven back-office jobs​

Adaptive's pitch starts from a plain observation about what project accountants really do all day. They collect the numbers, they talk to the field, and they reconcile what is happening on site with what is in the books so they can flag problems and act. The company's agents attempt all three at once, working continuously across the jobsite and the back office so finance leaders see issues as they happen rather than after they land on the profit and loss statement.

"The biggest challenge for construction accounting teams is knowing what's actually happening on site today that will impact the books tomorrow," Adaptive co-founder and CEO Matt Calvano said in the June launch statement. "When you're constantly chasing information, it's hard to spend time thinking about how to get ahead."

The agents arrive as named roles, each owning one workflow:

• AP Clerk reads incoming invoices, codes each one to the right job and cost code, and routes it for approval. No manual entry.
• Change Order Clerk watches every project for change events, drafts the paperwork, and chases vendors and owners until signatures land.
• Field Coordination Clerk calls superintendents and crews for hours, project updates, and missing information, then turns the conversation into structured accounting data.
• Billings Clerk assembles pay applications from job cost data, flags missing backup, and gets bills out the door faster.
• WIP and Forecasting Analyst keeps work-in-progress current as costs and revenue move, so the margin picture is live instead of a month-end surprise.
• Cards and Bank Recs Clerk codes card transactions to the right job, matches them against receipts, and reconciles bank activity continuously.
• Lien Waiver and Insurance Tracking Clerks collect, verify, and chase compliance documents across every vendor on every job.

The agents integrate with common project management and ERP systems, so customers can start without a large migration, and a contractor can hire the full team as a platform or a single agent for one workflow. Whether that menu appeals to you or not, notice what it implies: invoice coding, change orders, field communication, billings, WIP, reconciliations, and compliance chasing are the seven places where construction back offices drown. The rest of this guide takes them in that order, starting with the biggest one.

Why invoice coding is the right problem to automate first​

Start with the arithmetic. Manual invoice processing in construction runs about $42 per invoice, while automated processing drops the same invoice to roughly $2.36. About 23 percent of manually processed invoices require revision for errors or compliance issues. AP automation purpose-built for construction workflows cuts processing time by around 73 percent. And the stakes behind those numbers are enormous: payment delays and billing disputes cost the global construction industry an estimated $273 billion a year.

Coding is where the damage starts. Every bill that arrives — materials, subcontractor pay apps, equipment rental, fuel — has to land on the right job, the right phase, and the right cost code, get matched against its purchase order or subcontract, account for retainage — the share of each payment the owner holds back until completion — and route to the right approver. A bill coded to the wrong job does not just misstate one account. It poisons the job cost report, which feeds the WIP, which feeds the billing, which feeds the cash forecast. One wrong code at the bottom quietly corrupts every decision stacked on top of it.

That is why an AP agent that reads each bill the moment it arrives, matches it to the job and cost code, requests missing information from the vendor automatically, and queues it for approval is worth more than the data-entry hours it saves. It moves the error check to the front of the line, when the invoice is still cheap to fix, instead of the back, when the mistake has already flowed into a pay application. Contractors with real-time cost visibility finish projects about 23 percent faster — not because they build faster, but because they stop steering from stale numbers.

You can capture half of this value with no software at all. Standardize one cost-code list and require a job, phase, and code on every bill before it gets paid. Match every invoice to a purchase order or subcontract before approval, and kick back the ones with no match instead of coding from memory. Keep approval authority human no matter what: the agent routes, a person approves, and nobody who can create a vendor can also approve that vendor's invoices. Automation scales whatever discipline you already have, including the absence of it.

Change orders: where your margin actually leaks​

If invoice coding is where errors enter, change orders are where profit exits. Construction CFO analyses attribute 40 to 60 percent of profit fade — the slow bleed between estimated margin and actual margin — to change-order handling. The mechanism is painfully ordinary: the client asks for an upgrade on Tuesday, the foreman handles it Wednesday, and by Friday everyone has forgotten to document it. The work is real, the cost is real, and the revenue never happens because nobody wrote it down.

The contractors who escape this trap share one habit: they document changes the same day and submit the change order within about 72 hours. Firms that do recover 85 to 95 percent of their additional costs. Firms that reconstruct change orders from memory at billing time recover far less, because every undocumented hour becomes a negotiation instead of an invoice.

A properly handled change order touches four systems, and most contractors fumble at least one:

1. Pricing. Price at full burdened labor cost — wages plus payroll taxes, workers' comp, and benefits — plus overhead plus margin, using the contract's stated markup rates consistently, not a field-guess time-and-materials number scribbled on a tailgate.
2. The contract record. An executed change order adjusts the contract value the day it is signed, not whenever someone updates the spreadsheet.
3. The WIP schedule. Approved change orders enter revenue. Unapproved ones enter cost, with the treatment disclosed — never book revenue on work the owner has not agreed to pay for, or the profit you report today becomes the fade you explain tomorrow.
4. Billing. The change order appears on the next pay application, priced and documented, instead of whenever somebody remembers it.

The classic mistakes all rhyme: verbal agreements never documented, field managers forgetting to push changes into the billing system, unapproved and unbilled change-order claims recorded as revenue, and unprofitable change orders accepted without scoping the work first. Adaptive's Change Order Clerk is aimed squarely at this list — watching for change events, drafting the paperwork, chasing signatures. Your no-software version is a rule with teeth: nothing proceeds without a signed change order except genuine emergencies, emergencies get documented the same day anyway, and the office drafts every change order within 72 hours of the field log. Photograph the condition, log the hours and materials, and price from the contract rates. Boring, and worth more than any software feature.

WIP, billings, and lien waivers: the month-end that never ends​

The work-in-progress schedule is the one report that tells you whether your jobs are making money while there is still time to act. Costs to date, billings to date, and the estimated cost to complete combine into overbilling and underbilling positions — billed ahead of, or behind, the work actually performed — and a projected final margin per job. A WIP that is current is a steering wheel. A WIP assembled once a month from a week-old job cost report is archaeology.

Two habits separate a live WIP from a dead one. First, book committed costs, not just cash out the door: open purchase orders, signed subcontractor commitments, and approved change orders belong in the forecast now, because they are already part of the cost to complete whether or not the invoice has arrived. Second, keep the job cost ledger and the general ledger flowing into each other. When the two live in silos, the numbers drift apart and every downstream report quietly stops being accurate. Reconcile them monthly at minimum, and treat any unexplained difference as a defect, not a rounding choice.

Billings are the payoff for getting the upstream data right. Pay applications — whether AIA billing forms or your own schedule of values — assemble directly from job cost data, which means missing backup is the usual reason bills go out late. Firms that generate draw requests from current cost data cut billing cycles from weeks to days, and faster bills mean faster cash. The same logic covers the compliance tail: lien waivers and vendor insurance certificates have to be collected, verified, and chased across every vendor on every job. An expired certificate means uninsured exposure on your site, and a missing waiver means surrendered leverage in a payment dispute. Chasing paper is nobody's favorite work, which is precisely why it is always behind — and why it made Adaptive's agent roster alongside the more glamorous forecasting role.

What to fix in your books before (or without) an agent​

Strip the product announcement away and the underlying advice fits on an index card:

1. One cost-code list, used everywhere. Job, phase, and cost code on every bill, card charge, and timesheet — the same codes in the field app and the ledger.
2. Book committed costs in the forecast. Signed subcontracts and open purchase orders hit the cost-to-complete today, not when the invoice arrives.
3. Split approved from unapproved change-order costs. Costs hit the job when incurred; revenue waits for the owner's signature.
4. Reconcile job cost to the general ledger monthly. Same total, two views — or the reports are fiction.
5. Review the WIP with the field weekly. The estimate to complete is a judgment call from the people standing on the slab, not a formula in the office.

The same structure works in any ledger, including a plain-text one. The trick is making the job, phase, and cost code part of the account name, so every posting carries its own job-cost allocation and the WIP inputs fall out of a balance report. A week of framing labor and a signed change order's materials might look like this:

2026-01-05 open Expenses:JobCost:Job-24-118:Framing:Labor
2026-01-05 open Expenses:JobCost:Job-24-118:CO-007:Materials
2026-01-05 open Assets:Checking
 
2026-06-09 * "Framing crew, week 23" "Job 24-118"
  Expenses:JobCost:Job-24-118:Framing:Labor  4850.00 USD
  Assets:Checking  -4850.00 USD
 
2026-06-10 * "LVL beams, change order 007 (signed 06-09)" "Job 24-118"
  Expenses:JobCost:Job-24-118:CO-007:Materials  1320.00 USD
  Assets:Checking  -1320.00 USD

Note what the postings record beyond the dollars: which job, which cost code, and — on the change-order line — the signature date that makes the cost billable. An unapproved change order's costs would post to the job the same way but stay out of revenue until the paperwork lands, which is exactly the discipline the WIP section above asks for. If your ledger is plain text, the docs show how postings shaped like these roll up into the job-level reports a Friday WIP review runs on.

The skeptic's checklist: what software can't sign for you​

Suppose you adopt every agent on the menu. Six responsibilities stay human no matter what, and they are worth stating plainly because software demos glide past all of them:

• Approval authority. Agents route invoices; people approve them. Separation of duties is a fraud control, not a workflow preference — the person who creates vendors must not approve vendor payments, with or without AI in between.
• Revenue recognition. The accounting rules do not change when software drafts the paperwork. Unapproved change orders are cost with disclosed treatment, never revenue, until the owner agrees to pay.
• Lien waiver verification. Collecting a waiver is clerical; verifying it is professional. Conditional versus unconditional, dates and amounts tied to the right pay application — the agent fetches, you confirm.
• Data quality. Agents learn your cost codes and your habits. If your code list is a decade of accumulated improvisation, automation will miscode invoices at machine speed. Clean the list before you automate it.
• Insurance dates, not just files. A certificate on file that expired mid-job is decoration. Track expiration dates and chase renewals before the gap, not after the incident.
• The estimate to complete. No agent standing in the trailer can tell you the foundation crew hit rock. Cost-to-complete is a field judgment carried into the books, and the carrying is the only part software can do.

Start this week with the invoice pile: freeze one cost-code list, require a job and code on every bill before it gets paid, and review your WIP with your foreman every Friday. Whether the coding ends up done by a clerk, an agent, or you at nine in the evening, those three habits are what turn job costing from archaeology into a steering wheel.