Educational overview only. Prudent Guardian (www.inspirecodingedu.com) is not an insurance company, broker, law firm, or registered investment adviser, and does not provide personalized insurance, investment, tax, medical, or legal advice. Verify details with licensed professionals and official issuers.
A line subtracts what was already certified. You are checking that subtraction. Your pen hovers over the printed line item labeled “Less Previous Certifications” on the current pay application you’re reviewing for the active commercial build on the north side of town. You have the last three approved pay apps stacked to your left, post-its marking the total certified amounts from each cycle. The hum of your office space fades as you cross-reference each number to avoid overpaying or underpaying the concrete subcontractor who submitted this request.
Verify previous pay period totals
You pull each of the prior approved pay apps from the file folder associated with this project, matching each certified total to the line items listed on the current application. You cross out any handwritten add-ons that don’t match the formal certified amounts from prior cycles, noting the discrepancy in the margin in blue ink so you can follow up later if needed. You make sure to exclude any amounts from prior pay apps that were marked as disputed, since those were never formally certified and should not be included in the cumulative subtraction figure. Illustrative example: If the subcontractor has received $142,800 in certified payments across the first three pay cycles of the project, the line marked “Less Previous Certificates” should reflect that exact amount, not a rounded or estimated figure. Even a $200 discrepancy can throw off the rest of the pay app’s calculations, so you take extra care to transcribe each prior certified total exactly as it appears on the signed documents.
Cross-reference signature pages for approval status
You flip to the signature block of each prior pay app to confirm every required party signed off on the certified total before you add it to the cumulative amount. If a prior pay app lacks a signature from the project foreman, you set it aside to get sign-off before you finalize the current calculation, since unapproved prior amounts can’t be counted as certified for the subtraction line. You also check for any attached addenda that adjust prior certified totals, like small credits for unused materials that were agreed to after the original pay app was signed. These addenda often get lost in the back of file folders, so you take an extra minute to flip through every page of each prior pay app to make sure you don’t miss any adjustments that would change the cumulative total. You also confirm that each signature is dated after the work period covered by that pay app, to rule out any backdated approvals for work that wasn’t actually completed when the pay app was first submitted.
Adjust for any approved retentions held to date
You follow a consistent process to account for retentions that are held out of each certified pay amount, so the subtraction line only reflects funds that were actually disbursed to the subcontractor:
- Pull the retention rate outlined in the signed subcontract for this trade, which applies to every pay cycle until substantial completion is reached. For most commercial projects, this rate falls between 5% and 10% of each pay period’s total certified amount.
- Multiply each prior certified pay amount by the retention rate to get the total held for each cycle. You write each of these figures in the margin of the current pay app to make it easy to add them up for the total held retention across all cycles.
- Subtract the total held retention from the cumulative certified amount to get the actual total funds paid out to date. This is the figure that should appear on the “Less Previous Certificates” line, not the pre-retention certified total.
- Compare that disbursed total to the amount listed on the “Less Previous Certificates” line to confirm alignment. If there is a gap, you cross-check each individual retention calculation to see if you or the subcontractor made an arithmetic error.
You note any retention releases that were approved in prior cycles, so you don’t double-count held funds that have already been paid out to the subcontractor for completed milestone work. For example, if the subcontractor completed the foundation pour milestone last month and 50% of the held retention was released as part of that pay cycle, you subtract that released amount from the total held retention to get an accurate cumulative total.
Flag unapproved change order amounts for follow-up
You scan the current pay app for any change order amounts that the subcontractor included in the previous certified total, even though those change orders haven’t been formally approved by the project team. You circle those amounts in red ink, and jot a short note to send to the subcontractor’s billing contact later that day to request formal change order documentation before those amounts can be added to the certified total. You also cross-reference the project’s change order log to confirm no approved change orders were left off the cumulative total, which would lead to an incorrect, lower amount on the subtraction line. If you find missing approved change order amounts, you add them to the cumulative total and note the adjustment in the margin, referencing the change order number for full traceability. You log the adjustment in your project payment tracking tool, Draw Jacket, to keep all related records tied to the same project file for easy access later. You also make a note to add the approved change order amount to your running list of certified totals for the next pay cycle, so you don’t have to recheck the change order log again next month.
Confirm the final subtraction matches line item math
You run the full calculation manually, even if the pay app was generated by software, to catch any auto-calculation errors that might have slipped through when the subcontractor prepared the document. You start with the total amount requested on the current pay app, subtract the confirmed cumulative previous certified amount, and compare the resulting current amount due to the number listed on the pay app’s final line. If the numbers match, you initial next to the “Less Previous Certificates” line to confirm you’ve reviewed and approved the figure. If they don’t match, you recalculate twice more to rule out your own math errors before reaching out to the subcontractor to correct the discrepancy. You also make a copy of the fully reviewed pay app for your own project files, so you have a record of the confirmed cumulative certified amount for future pay cycles. Once you’ve completed this final check, this reading is done, and you can move on to reviewing the rest of the pay application line items before sending it for final approval.
Pull this record when you process next month’s pay app
When you sit down to review the next pay application for this same subcontractor in 30 days, you grab this annotated pay app first, to use its confirmed cumulative certified total as the starting point for your next “Less Previous Certificates” review. You’ll be able to reference the margin notes you added today to quickly account for approved change orders, released retention, and any discrepancies you resolved during this review, cutting down on the time you spend cross-referencing older pay apps. You’ll also check that the subcontractor carried over the exact confirmed cumulative amount to the next pay app’s subtraction line, to avoid repeated errors that can delay payment for completed work. You keep this document in the front of the project’s pay app file folder, so you don’t have to dig through old paperwork to find it when you need it next. You’ll also be able to use the notes you added today to walk the subcontractor’s billing team through any adjustments you made, if they have questions about the figures on the next pay app. This simple step of keeping the most recent reviewed pay app at the front of your file cuts down your review time for each subsequent pay app by as much as 15 minutes, which adds up significantly over the 18-month lifecycle of the project.
