Every construction ERP conversation eventually turns into a conversation about commitments versus change orders, because that is where the money actually moves and where I see the most confused configurations. Getting this distinction right in Acumatica Construction Edition is not academic — it is the difference between a project manager who trusts the "committed cost" number on their dashboard and one who keeps a shadow spreadsheet because the system's number is wrong.
Commitments are not the contract, they are what you owe against it
A construction contract in Acumatica represents the agreement — original scope, schedule of values, retainage terms. Commitments (subcontracts and purchase orders tied to the project) are separate records that represent what you have actually obligated to pay against that contract's budget. The commitments feature exists specifically to prevent cost overruns by tracking committed-but-not-yet-invoiced amounts against budget lines in real time, which is the number a PM actually needs when deciding whether to approve another subcontractor invoice.
The mistake I see most often: teams enter subcontractor invoices directly against the budget without ever creating the commitment record first. The invoice posts fine, the job cost report looks fine, but the "committed" column — the number meant to catch overruns before they happen, not after — stays empty. You get an accurate history and a useless forecast.
Change orders have to flow through the commitment, not around it
A change order that adds scope to a subcontract needs to update that subcontract's commitment value, not just the project budget. Approved change orders update the schedule of values automatically, which is what keeps the pay application correct — but that automation only works if the change order is entered against the actual commitment record, with the right cost code, rather than as a generic budget revision.
Project Budget (cost code 03-300, Concrete)
└─ Commitment: Subcontract SC-00042 (ABC Concrete LLC)
└─ Original value: $180,000
└─ Change Order CO-004: +$12,500 (additional footings, owner-directed)
└─ Revised commitment: $192,500
└─ Invoiced to date: $140,000
└─ Open commitment: $52,500 <- this is the number that should
drive your "money left to spend" viewCommitments, change orders, and the schedule of values only reconcile cleanly if they all reference the same cost code structure. If a change order is coded to a different cost code than the original commitment line, Acumatica will not silently merge them for you — you will get two lines that both look partially right. Standardize the cost code list at project template setup, before the first subcontract is written, not after the second one is wrong.
Wrapping up
Contracts, commitments, and change orders are three distinct record types that have to be entered in the right order and coded consistently to produce a trustworthy job cost report. Most of the "Acumatica's numbers don't match reality" complaints I get called in to fix trace back to a commitment that was skipped or a change order coded off-structure — not to a platform limitation.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.