Construction pay applications to Excel, every line item.
Thirty subcontractors send AIA G702/G703 pay apps as PDFs, scans and photos. ParserBee reads every one and gives you one row per schedule of values line, with the G702 totals, ready to check in your own spreadsheet.
How do I get line items from AIA G702/G703 pay applications into Excel?
Build one pay application Parser Template from a sample, then upload every subcontractor's pay app and download one Excel file. Each G703 line becomes a row; the G702 totals sit on the first row of each pay app.
- Contractor, application number, period and project
- All nine G702 lines, from contract sum to balance to finish
- Every G703 line, across every page of the continuation sheet
- Change order lines and stored materials kept apart
| A | B Description | C Scheduled | D Previous | E This period | F Stored | G To date | % | H Balance |
|---|---|---|---|---|---|---|---|---|
| 1 | Mobilization | 12,000 | 12,000 | 12,000 | 100% | 0 | ||
| 2 | Underground conduit | 46,500 | 46,500 | 46,500 | 100% | 0 | ||
| 3 | Rough-in, level 1 | 88,000 | 61,600 | 17,600 | 79,200 | 90% | 8,800 | |
| 4 | Rough-in, level 2 | 88,000 | 26,400 | 30,800 | 57,200 | 65% | 30,800 | |
| 5 | Switchgear and panels | 96,500 | 38,600 | 38,600 | 40% | 57,900 | ||
| 6 | Lighting fixtures | 63,000 | 6,300 | 6,300 | 10% | 56,700 | ||
| 7 | CO-03 EV chargers | 18,000 | 4,500 | 4,500 | 25% | 13,500 | ||
| Grand total | 412,000 | 146,500 | 59,200 | 38,600 | 244,300 | 59% | 167,700 | |
How a construction pay application adds up, line by line.
Each month a subcontractor adds this period's work and stored materials to every G703 line, takes off retainage, and the result has to match line 8 of the G702. ParserBee reads every one of these numbers into your sheet, so you check the math instead of typing it. Build the template from one pay app, then run the month's stack in Data Lab, up to 100 files at once.
- 1Mobilization
100%100% - 2Underground conduit
100%100% - 3Rough-in, level 1
70%90%17,600.00 - 4Rough-in, level 2
30%65%30,800.00 - 5Switchgear and panels
0%40%38,600.00 - 6Lighting fixtures
0%10%6,300.00 - 7CO-03 EV chargers
0%25%4,500.00
- This period (E + F)
- 97,800.00
- Less retainage, 10%
- -9,780.00
- Payment due
- 88,020.00
Thirty subcontractors, one billing week, every number keyed in by hand.
Most pay application software either helps subcontractors create pay apps or runs a portal that every subcontractor must bill through. If your pay apps still arrive as PDFs, the numbers still have to reach your spreadsheet before anyone can check them.
Hundreds of numbers per pay app
A G703 with 25 lines has nine columns of figures. Thirty subcontractors on a job means thousands of values to key in every month.
Every sub sends it differently
A clean AIA PDF from one, a scan with handwritten figures from another, a spreadsheet printed to PDF from a third.
The math has to tie
The G703 total must match line 4 of the G702, and this month's previous column must match last month's approval. Checking by eye is slow.
Every box on the AIA forms, mapped to a column in your sheet.
Line numbers and column letters as printed on AIA's G702 and G703 (1992 editions). The field names are what the AI typically proposes; rename them to match your own sheet.
| G702 line | On the form | Field |
|---|---|---|
| 1 | Original contract sum | original_contract_sum |
| 2 | Net change by change orders | net_change_orders |
| 3 | Contract sum to date | contract_sum_to_date |
| 4 | Total completed and stored to date | total_completed_stored |
| 5 | Retainage (5a completed work, 5b stored material) | retainage_total |
| 6 | Total earned less retainage | total_earned_less_retainage |
| 7 | Less previous certificates for payment | previous_certificates |
| 8 | Current payment due | current_payment_due |
| 9 | Balance to finish, including retainage | balance_to_finish |
| G703 column | On the form | Field (one row per line) |
|---|---|---|
| A | Item number | line_items.item_number |
| B | Description of work | line_items.description |
| C | Scheduled value | line_items.scheduled_value |
| D | Work completed, from previous application | line_items.previous_application |
| E | Work completed, this period | line_items.this_period |
| F | Materials presently stored | line_items.materials_stored |
| G | Total completed and stored to date (D + E + F) | line_items.total_to_date |
| G ÷ C | Percent complete | line_items.percent_complete |
| H | Balance to finish (C - G) | line_items.balance_to_finish |
| I | Retainage, where the rate varies by line | line_items.retainage |
Automate pay app review with five checks.
ParserBee reads the numbers; the checks run where your job costs already live, in Excel, Google Sheets or your ERP after a CSV import. With every line in the same columns, each check below is one formula, and together they catch the math errors that get a pay app sent back.
- Each line adds up
previous + this period + stored = total to date - G703 ties to the G702
sum of line totals = G702 line 4 - Previous matches last month
previous = last month's previous + this period - Retainage is at the contract rate
line 5 = rate x (D + E) + rate x F - No line billed past 100%
total to date <= scheduled value
=SUMIF(Lines!A:A, A4, Lines!J:J)| A | B | C | D | E | F | |
|---|---|---|---|---|---|---|
| 1 | Contractor | App | G702 line 4 | Sum of G703 | Payment due | Status |
| 2 | Ridgeline Electric | 7 | 244,300.00 | 244,300.00 | 88,020.00 | OK |
| 3 | Summit Mechanical | 5 | 318,750.00 | 318,750.00 | 41,175.00 | OK |
| 4 | Keystone Drywall | 3 | 96,400.00 | 93,400.00 | 12,825.00 | Check |
| 5 | Harbor Plumbing | 6 | 151,200.00 | 151,200.00 | 8,820.00 | OK |
| 6 | Northgate Concrete | 9 | 402,600.00 | 402,600.00 | 10,080.00 | OK |
| 7 | BluePeak Roofing | 2 | 37,800.00 | 37,800.00 | 17,010.00 | OK |
Construction pay application software, or a reader for the pay apps you already get?
Pay app portals such as GCPay run the whole submit, approve and pay cycle, but every subcontractor has to bill through them. ParserBee reads the pay apps you already get. Portal facts from GCPay's and Siteline's own websites, checked November 2026. Check their sites for current terms.
| Pay app portal | Typing into Excel | ||
|---|---|---|---|
| Who uses it | ParserBeeThe GC, owner, lender or accountant who receives pay apps | Pay app portalSubcontractors submit, the GC reviews and pays | Typing into ExcelWhoever has time this week |
| What subs must change | ParserBeeNothing. They keep sending PDFs, scans or photos | Pay app portalEvery sub signs up and bills through the portal | Typing into ExcelNothing |
| Line items in Excel | ParserBeeYes, one row per G703 line, from every sub | Pay app portalFrom the portal's own reports and exports | Typing into ExcelYes, typed by hand |
| Approvals, lien waivers and payments | ParserBeeNo. Those stay in your current process | Pay app portalYes, the main job of these tools | Typing into ExcelNo |
| Set-up | ParserBeeOne sample pay app, about 20 seconds | Pay app portalA rollout to every subcontractor | Typing into ExcelNone |
| Price | ParserBeeFrom $29 a month for 250 pages; 25 pages free | Pay app portalCustom quote (GCPay and Siteline publish no prices) | Typing into ExcelStaff hours |
Three jobs a pay app portal does better.
You are the subcontractor
To create and submit pay apps, use pay app software such as Siteline or the GC's own portal. ParserBee reads pay apps; it does not fill them in.
Every sub already bills in a portal
If all your subcontractors submit through GCPay, Procore or a similar portal, the line items are already data. Export them from there.
You need approvals and payments
ParserBee does not route approvals, collect lien waivers or pay anyone. It feeds the spreadsheet or system where you do that.
Sub invoices, COIs and delivery tickets from the same jobs.
83 ready-made document parser templates across 16 industries. Building your own app? The document parsing API returns the same fields as JSON.
Subcontractor invoices
Supplier and sub invoices with every line, for job costing.
Invoice OCR software →Certificates of insurance
Insurer, policy numbers, limits and expiry dates for every sub.
Certificate of insurance tracking →Construction pay application questions
How do I get line items from AIA G702/G703 pay applications into Excel?
Build a pay application Parser Template from one sample, then upload the month's pay apps in Data Lab and click Download as Excel. Each G703 line becomes a row with its scheduled value, previous, this period, stored, total to date, percent complete and balance to finish, and the G702 totals sit on the first row of each pay app.
Can it read G703 continuation sheets that run over several pages?
Yes. ParserBee reads the whole PDF as one document, so lines from page 1 to page 5 land in one list in their original order. AIA's instructions put a column C subtotal at the bottom of each page except the last; add "skip page subtotal rows" to the line items description and those rows stay out.
Is there a ready-made pay application template?
Not yet. Click Create Template, choose Build it with AI and upload one pay app (PDF, PNG, JPG or WebP, up to 15 MB). The AI template builder proposes the G702 fields and the G703 line items in about 20 seconds. Rename or add fields in plain English, run the test, and check it against the paper.
Does it work with pay apps that are not on AIA forms?
Yes. ParserBee reads each document by meaning, not by where a value sits on the page, so one Parser Template reads AIA G702/G703, ConsensusDocs forms and a subcontractor's own schedule of values printed to PDF. If a sub calls column E "this month" instead of "this period", it still lands in the same column.
Is ParserBee construction pay application software for subcontractors?
No. Subcontractors who need to create and submit pay apps are better served by pay app tools such as Siteline, or by the general contractor's own portal. ParserBee is for the other side of the desk: the people who receive pay apps as PDFs and need the numbers in a spreadsheet.
Can it automate pay app review for a general contractor?
It automates the reading, which is most of the typing. The review checks then run as formulas in your sheet: each line adds up, the G703 total ties to G702 line 4, the previous column matches last month's application, retainage is at the contract rate, and no line is billed past 100%. ParserBee does not approve pay apps, collect lien waivers or pay subcontractors.
Can it read scanned or handwritten pay apps?
Yes. It reads PDF, JPG, PNG, WebP and HEIC files, so scans and phone photos of signed pay apps work. Check handwritten figures in the test run before you send a whole batch.
How long can a pay application be?
Paid plans read PDFs of up to 24 pages each (12 on the free trial). A G702 with a long G703 fits easily. If a sub sends one file with backup invoices and lien waivers attached, split off the pay app pages and read the backup invoices with the ready-made invoice data extraction template.
Does it work with Procore, Sage, QuickBooks or my construction ERP?
Through a CSV import, Zapier, Make, n8n or the document parsing API, where your system accepts one of them. ParserBee has no direct connector to a construction ERP or accounting system today. Google Sheets and Airtable are built in.
How much does it cost?
New accounts get 25 free pages, no credit card. Each page uses one page credit: 30 subcontractors sending 4-page pay apps is 120 pages a month, which fits the $29 Starter plan (250 pages). See pricing.
Is my data used to train AI?
No. Your documents are never used to train AI models, and files travel to ParserBee over an encrypted (HTTPS) connection.