What is GC Pay? The product, the workflow, and where it fits
GC Pay usually means GCPay, the construction payment software. It can also mean how a general contractor gets paid. Here is both, plainly.
Search "what is gc pay" and you get two different answers, depending on who's asking.
Some people mean GCPay, the software product (now an Autodesk company). Others mean the general process of how a general contractor gets paid on a job. This post covers both, in that order, then explains where lien waiver tools fit alongside either one.
No marketing fluff. No "the future of construction payments." Just the actual landscape.
GCPay the product
GCPay is a cloud-based pay-application platform built for general contractors who manage a lot of subcontractors. It launched in 2003, and Autodesk acquired it in 2024.
The core job it does: replace the email-and-spreadsheet way of running monthly pay apps with a structured, web-based workflow.
What you get inside the platform:
- Pay-application intake. Subs log in, fill in their schedule of values, attach backup, and submit. The GC reviews on screen instead of in a stack of PDFs.
- Lien waiver exchange. GCPay generates the waiver, the sub e-signs, the document is filed against the pay app.
- Compliance tracking. Insurance certificates, W-9s, license expiries — the system blocks payment if a required doc is missing.
- ePayments. Optional ACH layer that pays the sub once the pay app is approved.
- ERP integration. Connects to Sage, Viewpoint, Foundation, CMiC, and others, so approved pay apps feed your accounting system without re-keying.
GCPay claims it cuts pay-application processing time by up to 70%. Independent reviews on G2 and Capterra back up the rough shape of that — most users report saving days per cycle, not hours.
Pricing is quoted by sales. The one published number is a $15 fee per ePayments and lien-waiver-exchange transaction, which the GC can either eat or pass to the sub.
That's the product. Now the second meaning.
"GC pay" as the construction payment workflow
When someone outside the SaaS world asks "what is GC pay," they usually mean: how does a general contractor actually get paid on a construction job, and how do they pay the subs underneath them?
The answer in four steps:
- The schedule of values. At the start of the job, the GC and owner agree to a line-item breakdown of the contract: foundation, framing, MEP, finishes, each with a dollar value. This is the SOV, and it's the spine of every pay application that follows.
- The pay application. Once a month (sometimes twice), the GC submits a pay application, usually on AIA forms G702 (cover) and G703 (continuation sheet). The G702 summarizes total contract value, work completed to date, retainage, and the current amount due. The G703 shows the line-by-line progress against the schedule of values.
- The owner's review and payment. The owner (or their architect) reviews, certifies the amount, and pays the GC. Net 30 is common; net 60 happens; on some public jobs it stretches to net 90.
- The GC pays the subs. The GC takes the money from the owner and distributes it down the chain. Subs submit their own pay applications upward, the GC approves them, lien waivers get exchanged, and checks (or ACH transfers) go out.
Lien waivers thread through every step. The owner asks the GC for a waiver before releasing payment. The GC asks every sub for a waiver before paying them. If the chain breaks (a waiver missing, a check uncashed), the whole cycle stalls.
Across all those steps, the average GC spends about 55 minutes manually processing a single pay application. On a job with 30 subs, that's 27 hours a month of paperwork. Pay-app software (GCPay, Procore Pay, Textura, Siteline) exists to compress that.
For more on the documents themselves, see pay application construction — that post walks through the AIA G702 / G703 line by line.
How GCPay fits into the workflow
Map GCPay against the four steps above and it covers most of step 2 and step 4:
- Schedule of values: GCPay imports it from your ERP and locks the line items.
- Pay-application intake from subs: the platform's main screen.
- Owner-side review and payment: partially. The GC still sends the certified G702 to the owner; GCPay doesn't usually live on the owner's side.
- Sub-side payment + lien waiver: ePayments and the waiver exchange handle this.
What GCPay doesn't do: replace your accounting system, manage the contract negotiation, or handle bonding and insurance underwriting. It's the layer between your subs and your ERP, not a full project management suite.
That's why companies running Procore for project management often run a separate pay-app tool. They're solving different problems.
The lien waiver question
Every pay-app cycle generates lien waivers. Conditional on the front end (signed before the money moves), unconditional after the money clears.
If the pay-app platform handles waivers well, that's one less tool to buy. GCPay, Procore Pay, Textura, and Siteline all include waiver workflows.
The catch: the waiver experience for the subcontractor is often the weakest part. Subs have to create an account in your pay-app system before they can sign. That's fine for the 10 subs who do every job with you. It's friction for the 50 specialty subs who you use once and never see again.
Three patterns we see GCs land on:
- All-in on one platform. Pay app, ePayments, and waivers all live in the same system. Best fit when 90% of your subs are repeat and willing to set up accounts. Common with enterprise GCs running Textura or Procore Pay end-to-end.
- Pay-app tool + separate waiver tool. Pay app lives in GCPay or similar. Waivers live in a tool with no-account signing for the long tail of one-off subs. The waiver tool plugs into whatever you already have.
- No platform, all email. Common with GCs under $20M revenue. Cheap, but the waiver chase eats hours every pay period and the audit trail is whatever's in someone's Gmail.
The second pattern is where LienDone fits. We don't replace GCPay or Procore Pay. We're the waiver layer for GCs who either don't have a pay-app platform yet or whose pay-app platform makes subs jump through hoops to sign.
If you're sending 10 waivers a month to subs who'd rather not set up another account, send a waiver in two minutes shows how the no-account flow works.
When GCPay makes sense, and when it doesn't
A short, opinionated take.
GCPay is a good fit if:
- You run more than $50M in annual volume.
- Most of your subs are repeat partners on multi-year projects.
- Your accounting team uses Sage 300 CRE, Viewpoint, Foundation, or CMiC.
- You're already paying $15 a transaction worth of value in time saved.
GCPay is probably overkill if:
- You're a $5M–$20M GC running 5–15 active jobs.
- Your sub list churns every project.
- You don't have an ERP yet (you're in QuickBooks).
- Your problem is "subs won't sign waivers," not "pay-app review takes too long."
For the second group, a construction pay-app software tool that handles the waiver layer specifically, without forcing subs to create accounts, usually solves more problems for less money.
The takeaway
"GC pay" means one of two things. GCPay the product, or the general process of paying subs on a construction job. They're related but not the same.
If you're researching software, GCPay is one option in a category that includes Procore Pay, Textura, Siteline, and a handful of ERP add-ons. They each cover slightly different ground.
If you're researching the workflow, the four steps haven't changed in 40 years: schedule of values, pay application, owner pays GC, GC pays sub. Software compresses the time. It doesn't change the structure.
And if your specific bottleneck is lien waivers (subs who won't sign, PDFs that vanish in email, a compliance person who's spent half their week chasing), that's a narrower problem with a narrower fix. You don't need a full pay-app platform to solve it.
FAQ
Is GCPay the same as the "GC payment process"?
No. GCPay is a software product, owned by Autodesk since 2024. The "GC payment process" is the broader workflow of how a general contractor invoices the owner and pays subcontractors.
How much does GCPay cost?
GCPay doesn't publish a list subscription price. The one disclosed fee is $15 per ePayments and lien-waiver-exchange transaction, which the GC can absorb or pass to the sub. Get a custom quote from their sales team.
Do I need GCPay if I already use a different pay-app system?
No. Procore Pay, Textura, Siteline, and several ERP-bundled tools handle similar work. Pick the one that integrates with your accounting system and fits how your subs prefer to work.
Where does lien waiver software fit if I already have a pay-app platform?
If your pay-app platform handles waivers well, you don't need a second tool. If waivers are still slow because subs won't create accounts, a focused waiver tool slots in next to your pay-app system without replacing it.
What does a typical GC payment cycle look like?
Schedule of values agreed at job start. Pay application submitted monthly on AIA G702 / G703. Owner reviews, certifies, and pays the GC on net 30 to net 60 terms. GC pays subs after collecting their pay applications and signed lien waivers. Total cycle: 30 to 60 days.
Send your next waiver in two minutes.
Pick the project, pick the sub, hit send. The signed PDF lands in your dashboard.
Get startedSee pricing