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.
Two covers are on the desk. They share one application number. You flip open the top one first, cross-reference the line items against your field log, and immediately spot the discrepancy before you even reach for the second folder. Neither cover is marked as a revised submission, so you need to walk through each line to avoid overpaying, underpaying, or logging incorrect progress against your project budget.
Match work completed dates against daily field reports
You pull the two pay apps side by side, and first note the date range each claims to cover. The first pay app lists work completed between the 1st and 30th of last month, while the second lists work completed between the 15th of last month and the 15th of the current month. The duplicate number is almost always a clerical error from the subcontractor’s billing team, but you still need to verify that no work is double-counted across both submissions. You cross-reference each line item against your daily field reports, which are signed off by your site foreman at the end of each workday, to confirm what percentage of each scope was actually completed during each window.
| Line Item Description | Pay App 1 Claimed Complete | Pay App 2 Claimed Complete | Verified Field Complete |
|---|---|---|---|
| Framing rough-in | 100% | 0% | 100% |
| Exterior sheathing installation | 75% | 25% | 100% |
| Window rough opening prep | 0% | 100% | 95% |
| Weather barrier application | 0% | 30% | 30% |
Illustrative example: If the total claimed value across both pay apps is $142,870, you first subtract the $21,300 of overlapping sheathing work that is counted in both submissions before you calculate any adjusted payment amount. You also adjust the window prep line down to reflect the verified 95% completion, since the last set of window openings still need to be squared off before they pass inspection.
Flag unapproved change order line items
Now you sift through each attached supporting document to check for change order requests that haven’t yet been signed off by your project manager. The second pay app includes a $9,200 line item for additional framing for a modified entryway that was only discussed in a site meeting last week, with no formal approval submitted. You highlight that line in neon pink, and attach a sticky note to the pay app cover to request the signed change order form before you move forward with any review of that line’s value. You also note that neither pay app includes dated progress photos of the completed window prep work, so you add that to your list of follow-up items for the subcontractor’s billing coordinator. You set aside the change order line to revisit once you receive the signed documentation, so you don’t hold up review of the rest of the approved scope of work.
Cross-check submitted retainage hold percentages
Your contract with the framing subcontractor specifies a 10% retainage hold on all pay applications until substantial completion is reached and the punch list is fully resolved. The first pay app applies the correct 10% hold to its total claimed value, but the second pay app only applies a 5% hold, with no attached documentation explaining the reduction. You cross-reference the contract addenda to confirm there was no agreed-upon reduction for early completion of critical scope, and find no addendum referencing a retainage adjustment. You adjust that line on your internal review sheet to reflect the contracted 10% hold, and note the discrepancy for your next check-in with the subcontractor’s team. You can input these adjusted values into Draw Jacket to keep all project payment documentation aligned for future reference. You also cross-check the sales tax applied to each line item to confirm it matches the local tax rate for your project site, and find no errors there.
Pause follow-ups until you resolve the duplicate number
This is where you stop for now. You do not send any approval or rejection notices to the subcontractor, and you do not pass either pay app along to your accounting team, until you resolve the duplicate number issue first. Sending either document forward without addressing the overlapping number will create a logjam in your payment system, leading to missed payment deadlines, incorrect budget tracking, and unnecessary back-and-forth with your finance department later. You set both pay apps in a dedicated folder on the corner of your desk, and add a 24-hour follow-up reminder to your calendar to reach out to the subcontractor’s billing team to clarify which submission is intended to be the official pay app for the current period, and whether the other is a revised version of a past submission or an erroneous draft. You make a quick note on your calendar to also request confirmation of which pay app includes all approved, up-to-date line items, so you don’t waste time reviewing a discarded draft.
Log the resolution in your project payment tracker
Once the subcontractor confirms which pay app is the official submission, and whether the other is a discarded draft or a revised version of a previously submitted application, you update your project payment tracker to reflect the correct numbering sequence. If the duplicate was a clerical error where the billing team reused a number from the prior pay period, you assign the newer submission the next available number in your sequence, and mark the older duplicate as void in your system. You also attach a short note to both documents explaining the discrepancy and the resolution, so anyone reviewing the payment history for this project later can immediately understand why two documents carry the same original number. You make a copy of the resolution confirmation email from the subcontractor and attach it to the official pay app before you send it along to accounting for processing. You also add a note to your pre-review checklist for future pay apps to first confirm the submission number is not already in your system, to catch these errors earlier.
Next time you pull up this duplicate pay app entry
You will be able to immediately reference the resolution notes to answer any questions from your accounting team, the subcontractor, or the project owner about the overlapping number. You will also be able to cross-reference the adjusted values you calculated today to confirm the payment amount sent matches the verified completed work, no additional double-counted line items, and the correct retainage hold applied. You will not need to redo any of the line item verification work you completed today, as all your notes are attached directly to the document entry in your system, saving you time if any disputes arise about the payment amount or progress logged for this period. You will also be able to use this discrepancy as a reference point for future pay app reviews, to spot duplicate numbers or overlapping work claims earlier in the review process before they cause delays in payment processing. You will have clear documentation to show that you caught the error early, followed your internal review process, and resolved the issue before it impacted project timelines or budget tracking.
(Word count: 1327)
