Key Takeaways
- The payment due date is determined by the subcontract's payment terms and applicable state laws, including any provisions that affect when payment is required.
- The expected payment date estimates when the GC will actually pay, based on its payment history, the current pay app's status, and any outstanding requirements.
- Tracking both dates improves cash flow forecasting and collections prioritization by distinguishing when payment is owed from when it's likely to arrive.
- Notice, lien, and bond claim deadlines must be tracked separately because they may depend on project milestones rather than contractual payment dates.
When I talk with subcontractors about collections, I’m always interested in what their finance teams can tell me about a GC without looking anything up. They know who cuts the checks, who’ll give them a straight answer about the draw, and who means “we’ll put it in the mail Friday” when they say “you’ll be paid Friday.” I’d want all of that in front of me if I were trying to figure out what’ll clear before payroll.
The trouble is, that knowledge doesn’t always make it into the cash forecast. What a GC owes you by a certain date and when you can realistically expect to receive it are often two different things. Tracking both dates helps you plan cash flow more accurately and prioritize collections, so you're not spending a morning chasing payments that are already scheduled while other balances need attention.
What sets the payment due date?
The payment due date depends on the subcontract's payment terms and the laws governing the project. Depending on those terms, the clock might start when a pay app is approved, when the GC receives payment from the owner, or when another specified payment event occurs.
Say you're an electrical subcontractor with a $180,000 pay app approved on November 2. If your subcontract requires payment within 30 days of approval, the contractual due date is December 2.
But if your subcontract includes a pay-when-paid provision, the due date can be harder to pin down. These clauses generally tie your payment to when the GC gets paid by the owner, so you may not know exactly when your money is due until that happens. Pay-if-paid provisions take things a step further: Depending on state law, the GC may not be obligated to pay you at all if the owner never pays them.
State prompt-payment laws can also override or limit certain contractual provisions, so the date stated or calculated under the subcontract isn't necessarily the date payment is legally required.
For A/R purposes, understanding the payment terms and laws that apply to each project helps you determine when a payment is actually overdue and when it's time to follow up or escalate.


What sets the expected payment date?
The expected payment date is your best estimate of when the money will actually reach you. Start with the GC’s payment history, ideally on the same project or comparable jobs. If the GC typically pays 45 to 50 days after approving the pay app, you’d expect that $180,000 from Pay App 08 to arrive between December 17 and 22, despite its December 2 due date.
You also need to consider where the current pay app stands. Has the GC submitted the draw to the owner? Has the owner approved or funded it? Are there outstanding lien waivers, compliance documents, or billing issues that could hold up payment? These details can help you refine your estimate beyond what the GC's payment history suggests.
Say the GC confirms on November 30 that the draw has been funded, all outstanding requirements are satisfied, and your ACH is scheduled for December 18. You now have a specific date to use in your forecast, though you'll still want to follow up if the GC has a history of missing payment commitments.
What changes when you track both dates?
The difference between December 2 and December 18 matters when you've got payroll on December 11. Say your cash forecast shows $95,000 remaining after payroll, with that $180,000 payment included. Move the receipt to December 18, and you're suddenly looking at an $85,000 shortfall. Knowing that ahead of time gives you a chance to confirm other incoming payments or arrange to draw on your line of credit.
For collections, the due date tells you when a balance becomes overdue, while the expected date helps you decide how and when to follow up. A GC with a confirmed ACH date and a history of honoring payment commitments may require a different approach than one that has repeatedly missed.
Both balances need attention, but the urgency and next steps will depend on how confident you are that payment is coming. If the December 18 ACH doesn't arrive, you'll need to find out what happened and whether it's time to escalate. Our stalled pay app decision tree can help you determine next steps.
Regardless of when you expect to be paid, keep applicable notice, lien, and bond claim deadlines on a separate calendar. These deadlines may be tied to project milestones rather than payment due dates, and a GC's promise to pay doesn't extend them. Check the lien requirements for your project’s state to make sure you’re protecting your payment rights.
How do you start tracking expected payment dates?
You don't need an entirely new system to get started. Focus first on outstanding payments that could affect your near-term cash flow, using the spreadsheet or A/R software your team already has.
- Record the expected payment date and its source. Use the GC’s confirmed payment date if you have one. Otherwise, estimate one based on payment history and note how you arrived at it. For Pay App 08, your entry might read, “December 18 ACH, confirmed by GC accounting November 30.”
- Assign someone to follow up. Whether it’s A/R or the PM, someone should be responsible for updating the expected payment date as approvals come through, holds get resolved, or payment commitments change. During your weekly cash review, prioritize receipts you’re counting on before payroll. If a GC says payment is coming through with the “next check run,” ask which day and whether your pay app made the cut.
- Compare expected dates with actual payments. Once the money arrives, record the receipt date and keep the original estimate in your notes. Over time, you’ll get a clearer picture of which GCs consistently meet their commitments and which require more conservative forecasts. It also means the next person working that GC’s account has something to go on—a point Claire makes in her Founder Note on documenting what you know about your GCs.
How does Siteline make tracking both dates easier?
In Siteline, you can track Estimated Payment Due Date alongside a separate Predicted Payment Date. Siteline suggests the latter using the project’s average time to payment, followed by the GC’s payment history across your projects—and then across all Siteline projects. If historical payment data isn’t available, it falls back on the project’s payment terms and then a standard 30-day term.
You can accept the suggested date or adjust it as new information comes in. For Pay App 08, that means keeping December 2 as the due date while updating the predicted date to December 18 once the GC confirms the scheduled ACH.
With both dates in view, Siteline’s cash flow forecast helps you see which payments are expected in time to cover payroll or other upcoming cash obligations. This gives your team time to follow up on uncertain receipts and make adjustments before cash gets tight.
Want to see it for yourself? Book a Siteline demo here.
AIA®, G702®, and G703® are registered trademarks owned by The American Institute of Architects and ACD Operations, LLC. Siteline is not affiliated with The American Institute of Architects or ACD Operations, LLC. Users who wish to use Siteline’s software to assist in filling out AIA® forms must have or secure the AIA® forms. Siteline does not and will not provide users with the forms.
%202.webp)