How Do You Submit and Certify an AIA Pay Application?

The pay app claims more than the contract, the retainage math is off, and the invoice goes out before anyone certifies it.

Claim percent complete per SOV line, hold retainage per line, certify against the gates, and generate the invoice only on certification, so you never bill more than earned or ahead of approval.

What this workflow is

An AIA pay application is the standardized request for a progress payment on a commercial job, claiming the percent complete of each schedule-of-values line for the period. Submitting and certifying one is the work of computing what was earned, withholding retainage, getting it certified, and only then sending the invoice.

Why it matters

The pay app is how a contractor gets paid over the life of a long job, and it is where billing integrity is enforced. You cannot bill more than the contract or more than was actually earned, and retainage has to be withheld correctly on each line. The failure mode is billing ahead of the work or ahead of certification: an invoice that goes out before the pay app is certified, or a draw that claims more than the line has earned, which becomes a dispute and erodes trust with the owner.

How to do it

1. Claim percent complete per line

   At the end of the period, each schedule-of-values line is claimed at its actual percent complete, the basis for what is earned this draw.
2. Compute retainage per line

   Retainage is withheld on each line per the contract, so the held amount is correct line by line, not estimated in aggregate.
3. Number the application

   The pay app gets its sequential application number for the project and scope, so the draws form an ordered, auditable series.
4. Submit for certification

   The application goes for certification, where the gates are checked: billing spine, reconciliation, and lien-release clearance.
5. Generate the invoice on certification

   Certification generates the invoice first, and only then advances each SOV line's billed and retainage amounts, so the record and the invoice stay in sync.
6. Receive payment against the invoice

   Payment comes in against the generated invoice, reducing its outstanding amount. The accounting system books the receivable.

Common mistakes

How Scaftra runs it

Scaftra builds a pay application from SOV rows with sequential per-project, per-scope application numbers. Certification runs the gate chain, billing-spine assertion, reconciliation, and lien-release clearance, generates the sales invoice first, and only then advances each SOV row's billed and retainage amounts, so you cannot bill more than earned or more than the contract. Scaftra prepares and certifies the pay app and triggers the invoice; the accounting system receives and books the receivable.

Key capabilities

• SOV-driven applications: Pay apps are built from schedule-of-values rows with sequential per-project, per-scope numbers, so draws form an ordered, auditable series.
• Certification gate chain: Certification checks the billing spine, reconciliation, and lien-release clearance, so an application cannot certify with a broken financial state or missing waivers.
• Invoice-first certification: Certification generates the invoice first, then advances billed and retainage amounts, so the billing record and the invoice never fall out of sync.
• Earned and contract ceilings: The workflow prevents billing more than was earned on a line or more than the contract total, so over-billing is caught at certification.

Benefits

• Billing never exceeds what was earned or the contract total.
• The invoice is generated on certification, so the record and the invoice stay in sync.
• Certification is gated on reconciliation and lien clearance, so draws go out clean.

Who runs this

• Commercial and AIA-billing GCs.Contractors billing progress draws on long jobs who need certification integrity and correct retainage.
• Controllers managing draws.Finance staff who need each application numbered, gated, and tied to a generated invoice.

Related on Scaftra

Go deeper