Procore Commitment Invoices and SOV Allocation

How it works

Start with the commitment, not just the vendor

One subcontractor may have multiple contracts on the same project. Match the source invoice to the exact purchase order or subcontract and verify its scope. A similar contract title or vendor name is not enough to establish the right destination.

• Check the project, contract company and commitment reference.
• Use the source invoice and contract scope to resolve ambiguous matches.
• If the bill has no associated commitment, review whether Direct Cost is the appropriate path.

Check the billing setup in Procore

Procore’s invoice creation requirements include the applicable commitment status, invoice contact and billing period. Where the optional Subcontractor SOV is used, its rows must be approved. Confirm the current requirements with your Procore administrator before preparing the invoice.

• Confirm that the invoice belongs to the intended billing period.
• Check that the commitment and relevant SOV rows are ready for invoicing.
• Resolve missing access or setup in Procore before trying to submit.

Allocate the current invoice to the SOV

Read each source line and compare it with the work described on the commitment’s SOV. Denize’s suggested allocations are editable. A row with similar wording can still refer to a different phase, location or scope of work.

• Review each proposed SOV row and amount.
• Distinguish current-period billing from cumulative billed-to-date amounts.
• Check prior billing and remaining contract values before accepting an allocation.
• Reconcile retainage, tax and payable total with the source rather than adding an amount twice.

Example: two scopes on one invoice

Illustrative example: an invoice requests $3,000 for rough-in and $2,000 for trim work. If those scopes exist as separate SOV rows, review a $3,000 allocation to rough-in and a $2,000 allocation to trim. The current billing totals $5,000 before any applicable tax or retainage. Do not copy a cumulative contract total into the current invoice.

Handle exceptions before submission

Stop and resolve an allocation when the invoice references work missing from the SOV, the scope is ambiguous, or the requested amount conflicts with prior billing. A change order or contract correction may need to be handled in Procore by the responsible team.

• Keep unsupported or uncertain amounts under review.
• Compare the final prepared totals with the complete source invoice.
• Submit only after review, then open the resulting Procore record to verify the draft.

Sources and requirements

Use these references alongside your company’s Procore configuration and review process.

Related invoice workflows