Prepare the Change Order Details
Before entering a change order, identify the existing job and review its original contract amount, current budget, posted costs, and previously approved changes. Confirm whether the request affects labor, materials, subcontractors, equipment, project milestones, or customer billing.
Gather the customer authorization, revised estimate, supplier quotations, and any supporting correspondence. If the change requires additional purchasing, review requisitions, sourcing decisions, and approval requirements. Resources such as Purchase Order Automation Tools for ERP Integration can help explain how procurement controls connect purchasing decisions with approved project requirements.
Finance teams can also use User-Friendly PO Automation Software for Finance Teams as a reference when evaluating how purchase order workflows support spend visibility and consistent authorization. Separately, Fraud Prevention in Purchase Orders | Secure Automation discusses procurement controls that help verify purchasing legitimacy and approval authority.
Enter the Change Order in Sage 100
Exact navigation varies by Sage 100 edition, configuration, and installed modules. Start by opening the relevant Job Cost or project-related function and locating the existing job. Look for the available change order, contract adjustment, estimate revision, or job budget maintenance workflow supported by your installation.
Enter the change order identifier, description, date, and applicable job or cost code details. Record the revised quantities, labor hours, material costs, subcontractor amounts, or other values supported by the approved change. Where the system records revised contract values separately from original amounts, preserve the original figures and enter the adjustment in the appropriate change field rather than overwriting historical information.
Review each line against the approved documentation before saving. If your Sage 100 configuration does not include a dedicated change order entry screen, follow the documented workflow for your installed modules and confirm how contract revisions, budget adjustments, and billing changes should be recorded.
Update Contract Values and Job Costs
A customer-approved change may increase or decrease the contract amount while also changing expected project costs. Enter each adjustment in the appropriate financial category and confirm that the revised amounts flow to the intended job reports and billing records.
For example, assume a construction job has an original contract value of $120,000. The customer approves additional work worth $15,000, with expected additional costs of $9,000. The revised contract value becomes $135,000, and the expected incremental gross profit is $6,000 before other project expenses.
Calculation: Revised contract value = Original contract value + Approved change order value.
Using the example: $120,000 + $15,000 = $135,000. The expected margin on the additional work is $6,000 divided by $15,000, or 40%. Confirm whether the revised cost budget and billing schedule reflect the approved scope before using these values for forecasts.
Maintain Approvals and Change Records
Keep a traceable record of who requested, reviewed, approved, entered, and verified each change. Change Tracking provides a useful framework for understanding how revisions to amounts, dates, cost codes, and supporting records can be documented over time. Coding Change Management is also relevant when a change requires adjustments to job cost codes, general ledger classifications, or reporting structures.
For organizations using multiple financial systems, Sage Intacct Integration is a related ERP integration concept that illustrates why consistent data mapping and reconciled financial records matter when information moves between applications. It is not a substitute for verifying the specific integration and posting behavior of Sage 100.
Where additional automation supports finance workflows, Hyperbots Platform offers company-specific configuration for ERP integration, workflows, user roles, and general ledger structures. Its Process Specific Capabilities address process-oriented finance automation, while Ready to Deploy Capabilities focus on pre-trained agents and pre-built ERP connectors. Self Learning Capabilities allow systems to improve from human feedback, and Human in the Loop describes oversight for exceptions and approval decisions. These are broader finance automation concepts rather than native Sage 100 change order features.
Verify the Change Order and Review Reports
After saving the entry, compare the revised contract amount and job budget with the approved change documentation. Check that the change is associated with the correct job, cost codes, billing arrangements, and reporting period. Confirm that any related purchase orders, subcontract commitments, and customer invoices reflect the authorized scope where applicable.
Review job cost reports, budget-versus-actual comparisons, contract summaries, and billing schedules available in your installation. If the change affects a sales transaction or customer purchase order, distinguish the customer's authorization from the contractor's internal job records. PO in Sales: Purchase Orders in the Sales Cycle Guide explains the relationship between purchase orders and sales transactions.
Resolve discrepancies before closing the period or relying on revised figures for project profitability, cash flow forecasts, and management reporting. Retain supporting documents according to company policy so the change can be reviewed during reconciliation or an audit.
Summary
To enter change orders in Sage 100, verify the job, gather approved documentation, use the appropriate change or budget adjustment workflow, update the relevant contract and cost values, and validate the resulting reports. Because screens and capabilities vary by edition and configuration, confirm the exact procedure for your installed modules. Consistent approvals, traceable records, and reconciled financial updates help contractors maintain reliable job costing, billing accuracy, and project profitability.