Pay app review: spreadsheet or software?

Published 17 October 2026. Updated 17 October 2026.

Every month a controller or project accountant gets a pay application and has to decide whether the percent complete on each line is believable. There are three common ways to do that check: by hand in a spreadsheet, inside billing or pay application software, or with a tool built for one task, comparing the claim to the field reports. They answer different questions, and the right choice depends on your volume, your jobs and what has gone wrong before.

This guide compares the three honestly, including when the cheapest option is the right one.

What the check actually takes

Whichever route you pick, the job has the same parts:

1. Paper checks. Do the lines add up to the summary page? Does this period plus previous work stay at or under each line's scheduled value? Is retainage the rate in the contract? Does the new total match the old total plus this period?
2. Progress checks. Does the claimed percent complete on each line match what the field reports say is done?
3. Judgment. Which differences matter, which are timing, and who needs a call before payment?

Paper checks are mechanical, so they are easy to automate and easy to get wrong by hand when you are tired. Progress checks are the expensive ones: they mean reading prose and turning it into a number for every line. Our step by step method for checking a pay app against field reports shows how much work that is when done properly.

Option 1: a spreadsheet and your own reading

This is a common way to do it, especially at smaller firms. A template holds the schedule of values, you key in or paste the new percentages, and you read the superintendent's notes next to it.

Where it works well

• You control everything and can see every formula.
• It costs your time and nothing else.
• For a few short schedules, the whole check takes a short sitting.
• You learn the job by reading the notes yourself, which has value in its own right.

Where it breaks down

• Retyping errors. Numbers keyed in from a PDF go wrong in small ways that look right.
• Broken formulas. Rows get inserted, ranges stop covering them, and totals quietly stop including a line. It can go unnoticed until something is off by a visible amount.
• Version confusion. Which template is current, and did the sub's revised file replace the one you already checked?
• The reading gets skipped. When the month-end queue is long, the field reports are the first thing to go. The arithmetic gets done because it is quick; the comparison to the field gets a glance.
• Nobody checks the second time. The person who built the sheet is also the person who trusts it.

Option 2: billing or pay application software

A full billing platform for contractors holds the contract, the schedule of values, change orders and payment history, and routes pay applications through a workflow. It keeps everyone on the same numbers.

Where it works well

• A single source of truth for the contract and schedule, so a line billed past its scheduled value is easier to catch.
• When subs submit through it, the format is consistent and the retyping goes away.
• History and audit trail across jobs and years.
• Payment workflow, lien waiver tracking and reporting, if the platform includes them.

Where it may fall short

• It is built around the contract and the paperwork. Whether it compares a claimed percent to what the superintendent wrote is a question to put to each vendor; do not assume.
• It usually means a rollout, training, and getting every sub onto the same system. Pricing is often by quote, so ask early.
• It checks that the application is consistent with the schedule. It does not know that the roof is not on yet unless something reads the field notes.

Option 3: a single-task reconciliation tool

A tool built for one job reads the pay application and the field notes together and reports where the claim and the field disagree. It does not hold your contract history or route payment. It covers the reading in option 1, not the platform in option 2.

Where it works well

• It reads every line every month, including the month when the queue is long.
• Nothing to install or connect to your accounting system.
• It can sit next to a spreadsheet or a billing platform you already use.

Where it falls short

• It only knows what is in the documents you give it. Anything not written in the field notes is not evidence.
• It does not replace a site visit when a large line is in doubt.
• Output is a prompt for your judgment, not a decision.

Side by side

When a spreadsheet is enough

Stay with the spreadsheet if you have a few active jobs, simple lump-sum subcontracts, a superintendent who writes useful daily notes, and a controller who actually reads them. If errors have been rare and small, adding a platform buys you little.

Make it stronger without buying anything: lock the formula cells, keep one master template, tie the continuation sheet to the summary page every time, and have someone other than the author spot check one job a quarter.

When billing software makes more sense

Choose a platform when you have many subs submitting in many formats, need an audit trail across jobs, or want payment and waiver workflow in the same place. These are problems of volume and process, not of progress. If your losses have come from paying for work that was not there, a platform alone may not touch that, so ask whether it reads field reports.

When a reconciliation tool adds the most

It fits best where the dollars on a few lines are large, the notes exist but nobody has time to read them against the schedule, and you want a second look that does not depend on who is in the office that week. It pairs with either of the other options.

A short checklist, whichever way you go

• Check the summary page against the continuation sheet on every application.
• Rank lines by dollar movement and read the notes for the biggest ones first. Our checklist of pay app errors to catch before you pay lists what to look for.
• Treat a note like "good progress" as no evidence, not as agreement.
• Keep the version you checked, not just the latest.
• Write down what you decided on each flag.

How GroundClaim does this step

GroundClaim is the single-task option. You upload one job's monthly pay application (a spreadsheet, a Word or PDF table, or a scan or photo, up to 400 lines) and the field notes for the same period as free text. Code checks the arithmetic: percent complete never going backwards, the G702 and G703 tie-out, retainage and the schedule totals. The notes are searched for progress on each line, and every excerpt it quotes is checked word for word against your notes. Each line billed this period gets a supported percent range, a note that the evidence is insufficient, or a place on the list for you to check, and code works out the dollar gap.

You get an exceptions memo ranked by dollar exposure and a line-by-line reconciliation that also shows the clean lines, plus a one-line recommendation that is only a suggestion. A second, stronger AI model reviews every result, fixes what it can, and lists what is left for you to decide. Results are model output checked by code and by a second model; they are not verified by a person. GroundClaim does not accept or reject a pay application, does not connect to billing systems today, and does not hold your contract or payment history.

One pay application costs 25 credits, with no subscription. Create an account and try it on a closed-out project where you already know the answer.

Questions

Is a spreadsheet good enough for a small contractor?

Often yes. With a handful of jobs and short schedules, a well built template plus a disciplined read of the field reports covers the main risks. The trouble starts when volume grows or the person who built it leaves.

Does billing software check progress against the field?

Billing and pay application software is usually built around the contract, the schedule of values and the payment workflow. Whether it reads field reports depends on the product, so ask the vendor before assuming it does.

Can I mix approaches?

Yes. Use billing software to hold the contract and the history, and use a separate check of claimed progress against the field on the jobs or lines where the money is.