In real projects...

Subcontractor pay is where cash, lien risk, and schedule meet—applications for payment must tie to percent complete and retention. Job cost context: job costing.

A common issue we see...

Paying from field approvals without lien waiver tracking or joint check rules.

For example...

  1. Match pay apps to schedule of values lines.
  2. Track retention release milestones contractually.
  3. Collect conditional/unconditional waivers per jurisdiction.
  4. Segregate vendor setup changes from payment initiation.
  5. Forecast cash needs by project phase—not only AR.

Common mistakes (and how to avoid them)

  • Letting joint checks become informal.
  • Ignoring change-order linkage before paying increases.
  • Weak audit trail for lien notices received.
  • Underestimating sales tax on materials pass-through.

Note: Representative scenarios for education; follow construction law and contract terms.

Methodology: This article is an educational guide built from public ERP documentation and widely used implementation patterns. Any mini “scenario walkthroughs” are illustrative and not client-specific.

Subcontractor payment disputes are expensive and disrupt project progress. This walkthrough connects the pay application review to a traceable payment record in the ERP so entitlements, retentions, and approvals are auditable.

  1. Receive the subcontractor's pay application and verify it against the contract: scope, rates, quantities measured to date, and retention terms.
  2. Compare the application to the certified value from the most recent site valuation and flag any discrepancies for the quantity surveyor to review.
  3. Approve the gross certified amount and calculate the net payment after retention deduction, any contra charges, and any agreed variations.
  4. Route the payment certificate through the financial approval workflow, linking it to the relevant subcontract record in the ERP.
  5. Release the payment to accounts payable and post the transaction against the correct project and cost code, with retention separately recorded.
  6. Track retention balances by subcontract and configure alerts for retention release milestones (practical completion, defects liability expiry).

Artifacts to expect:

  • Subcontract record in ERP with agreed scope, rates, and retention terms.
  • Pay application and payment certificate per application cycle.
  • Retention register by subcontract with release milestone dates.
  • Approval record for each payment certificate.
  • Subcontract ledger reconciliation at project completion.

What usually goes wrong (failure modes)

  • Retention is released without confirmation that the release condition has been met
    Retention release dates are tracked in a spreadsheet outside the ERP, and the ERP has no visibility of whether practical completion or defects liability conditions have been satisfied.
    Mitigation: Configure retention release conditions in the ERP subcontract record, linked to a documented milestone or sign-off date. Require approval evidence before the retention payment is released.
  • Payment is made for work that has not been measured or certified
    Pay applications are approved based on the subcontractor's stated completion percentages rather than independently verified site measurements.
    Mitigation: Require a quantity surveyor valuation to support every payment certificate before financial approval is granted. Link the QS report to the payment record in the ERP.
  • Contra charges are not offset correctly and create disputes
    Materials supplied or costs incurred on behalf of the subcontractor are not consistently deducted from payment certificates, leading to disputes at final account.
    Mitigation: Record all contra charges in the ERP subcontract record at the point they are incurred, and automate the deduction in the payment certificate calculation.

Controls and evidence checklist

  • Require a quantity surveyor valuation to support every subcontract payment certificate.
  • Record retention by subcontract in the ERP with release milestone conditions.
  • Route all payment certificates through a documented financial approval workflow.
  • Log all contra charges in the subcontract record at the point of incurrence.
  • Reconcile subcontract ledger to the payment register at project completion.
  • Maintain an audit trail of all payment certificate versions and amendments.

Implementation checklist

  1. Configure subcontract records in the ERP before the first pay application cycle, including retention terms and contra charge categories.
  2. Test the payment workflow with one subcontract covering a full application cycle, including a retention deduction and a contra charge.
  3. Train quantity surveyors and accounts payable staff on the evidence requirements for payment release.
  4. Establish a pay application cycle calendar aligned with the project payment schedule.
  5. Run a retention balance report after the first practical completion and confirm release approvals are in place.
  6. Review the subcontract payment process at project completion and document any workflow improvements for future projects.

Frequently asked questions

Where do teams usually lose time in ERP subcontractor payment processes?

Most time is lost when pay application reviews lack a standard checklist, and project managers and accounts payable work from different versions of the subcontract scope. A single shared payment log—updated after every pay application review—keeps both teams aligned and reduces the back-and-forth that delays payment approval. Poor retention tracking is the second most common time sink—retention release disputes are much harder to resolve without a structured ERP record.

What should we confirm before the first payment application cycle?

Confirm that retention tracking is configured correctly in the ERP before subcontract work begins, and that retention release conditions are documented and linked to specific contract milestones. Retention disputes are one of the most common causes of subcontractor payment delays and project cashflow problems. A retention register in the ERP with milestone-based release approvals is the minimum control standard.

When should we adjust payment workflow rules?

Adjust payment workflow rules when approval queues are consistently delayed at the same review stage. This usually means the approver does not have the information they need at the point of review—adding the relevant contract clause and cost code history to the approval screen often resolves the bottleneck without escalating the approval limit. Review workflow rules at the start of each new project phase when scope or subcontractor base changes.

Sources

Conclusion and next steps

Subcontractor payment control in ERP depends on connecting the pay application to a measured, certified, and approved record before any payment is released.

Configure retention tracking and the payment approval workflow before the first pay application arrives. The cost of configuration at project start is far lower than the cost of retrospective disputes at project completion.