Construction Invoice From Daily Reports: Stop the Retype

Every month the same numbers travel the same path: a driller writes footage and hours into a field book, someone types them into a running Excel cost sheet, someone else pulls totals from that sheet and types them into an invoice template, and sometimes those invoice lines go into QuickBooks a third time. Three passes, three chances to drop a shift or transpose a number.

The invoice already exists. It has lived in the cost sheet since the last daily was entered. The missing piece is not the data - it is the link between the data and the document the client receives.

The fix is structural, not technological. No new software is required. Building the invoice tab as a formula sheet that references the daily log means the invoice is always current as of the last daily entered, and the backup attaches automatically.

Worked example

A 2-rig underground driller logs 40 shifts a month - 20 shifts per rig. Say the office manager earns $35/hr and each retype pass takes 6 minutes per shift record for number entry only, not verification. Say the average shift bills at $8,000 at the contracted drilling rate.

Answer: Retype labor in this example costs $5,040 a year before a single number is wrong. If 1 shift in 40 falls off each invoice - a late daily, a skipped row - and that shift bills at $8,000, the unrecovered total reaches $96,000/year. Both figures drop to zero when the invoice pulls directly from the daily log.

Where the numbers live now

Every drilling contractor already maintains the data that belongs on the invoice. It lives in the running Excel cost sheet the office keeps through the month: one row per daily report, with columns for the rig number, the date, meters drilled, rig hours, consumables used, and any delay codes that affect the rate. By the end of the month, that sheet holds a complete record of billable work.

The problem is that nobody connects it to the document that goes to the client.

The standard process runs like this. The office manager finishes posting the last daily into the cost sheet, then opens a separate invoice template - a different Excel file, a Word document, or a formatted PDF. They pull the monthly totals from the cost sheet: meters by rig, hours by rig, consumables by category. They type those totals into the template. If the client requires footage by zone or delay codes by cause, they go back to the cost sheet and pull those breakdowns separately, typing each one.

That is a second full pass through numbers already entered once.

The three passes

In most underground and surface drilling offices, a number from a daily report moves through 3 separate typing passes before it reaches the client:

Pass 1: field to Excel. The daily arrives from site - scanned, photographed, emailed, WhatsApped. The office manager reads the number and types it into the running cost sheet. Meters, hours, consumables, delay codes. This is the entry everyone accounts for.

Pass 2: cost sheet to invoice. At month end, someone opens the invoice template and types totals from the cost sheet. Footage for the month. Total hours. Consumables by category. Multiple lookups, multiple typed transfers. This is the pass most people forget to count.

Pass 3: invoice to accounting. The invoice line items go into QuickBooks, Xero, or another accounting system. The same figures move again, now as dollar values, stripped of the production backup that gave them context.

Three passes mean 3 chances for a transposition, a missed row, or a rounding choice that creates a discrepancy between the invoice and the backup. For 40 shifts a month at $35/hr and 6 minutes per pass, retype labor runs $5,040 a year before a single number is wrong. One shift in 40 that arrives late and falls off the invoice entirely, at $8,000/shift, adds $96,000 in unrecovered billings over the year.

The harder problem is the missing daily. A report that arrives after the invoice has already gone out either holds for next month or disappears. Finding out which requires comparing the daily log count against the invoice - a reconciliation that rarely happens until a client raises a query.

What a construction invoice needs as backup

The backup that prevents payment delays is specific. It is not every document in the month's folder. For a drilling contract, it typically includes:

• A dated and signed daily per shift, showing the rig, the date, and the key production fields
• A monthly summary that matches every invoice line exactly, with no unexplained rounding
• A delay log identifying cause and responsible party, for any shift where standby is being billed
• A running contract-to-date total so the client can see where you sit against any cap

The difficulty is assembly, not availability. The information exists. When the invoice and the backup are separate files, pulling together a clean package at month end takes an hour. When a dispute arrives six weeks later, finding the specific daily for a specific shift means sorting through scanned files, matching dates to invoice lines, and hoping the file names were consistent.

The MSHA Program Policy Manual describes the underlying principle: "At the conclusion of the investigation, the company will receive an invoice for the processing of the application" (MSHA Program Policy Manual, Volume II, p. 2). The documented work is the bill's foundation, not its attachment. When the record and the invoice are the same document, that relationship is automatic. When they are separate files connected by someone typing the same number twice, it is fragile.

Under 30 CFR Part 50, mine operators must maintain employment and production records covering shifts worked, hours, and output. Those records are the same data that should feed the contractor's monthly invoice. When they live in the same file, the compliance record and the billing record are one thing, not two things that need to agree.

One spreadsheet, one source

The structural fix is a second tab in the spreadsheet you already use.

Tab 1 is the daily log: one row per shift, every billable field in a column. The office manager already maintains this through the month. Nothing changes here.

Tab 2 is the invoice. It is a formatted invoice template whose number cells are SUMIFS formulas referencing Tab 1. Total meters for a given rig and billing period: one formula. Total hours: one formula. Consumables by category: one formula each. When the last daily goes into Tab 1, the invoice in Tab 2 is already correct. No second pass.

The backup is automatic. Printing both tabs gives you the invoice and the full daily log in the same file, in the same order. A number on the invoice and the corresponding figure in the daily share the same cell reference: they cannot diverge.

For contracts billed by zone, add a zone column to the daily log and add that column to the SUMIFS criteria. For contracts with multiple rate codes, add a rate code column and write one formula per code. For consumables billed separately, add consumable columns and a SUMIFS per item. The structure scales to the contract, but the logic stays the same: every invoice line is a formula, never a typed number.

Two details worth building in from the start. First, lock the invoice tab against direct editing. If someone types over a formula, the connection breaks and the retype chain restarts. Sheet protection in Excel takes about 30 seconds to configure. Second, name the file with the contract and billing period before sending - "Shaft 7 October 2026.xlsx." When a client questions a line item eight months later, the file name is its own reference. Open the file, go to Tab 1, filter by date: the answer is there in the same form it was in the day the invoice went out.

The audit trail that wins disputes

Payment disputes on drilling contracts usually come down to 3 things: meters the contractor says were drilled versus meters the mine's survey shows, delay the contractor says was standby versus delay the mine attributes to the contractor, or a holdback calculation run differently on each side.

None of these gets easier when the invoice number has been separated from its source by 2 manual typing passes. When the invoice shows 1,240 meters and the backup shows 1,238, the question is which figure is correct and the answer requires tracing a number that moved twice.

When the invoice pulls from the daily log directly, the question resolves in under a minute. Filter the daily tab by rig and date range, sum the meters column: the result agrees with the invoice because they reference the same data. A client who can follow that trail pays faster than one who receives a number with no visible path back to the field.

The same structure makes the production record easier to produce if it is ever needed for compliance review. The daily log is the production record. It is in one place, sorted by date, with every shift accounted for.

What this does not fix

Getting the daily out of the field and into the spreadsheet accurately is still a manual step. Nothing here changes the paper sitting on a drill deck waiting to be photographed, the shifter who left 3 fields blank, or the report that arrives 48 hours after the shift ended.

It also does not replace a human review before the invoice goes out. An office manager who has been entering dailies all month will notice when the total shows 42 shifts on a 2-rig operation that was idle for a week. A formula does not notice that. The pre-invoice check is still necessary.

What this fixes is the retype chain: the time-consuming, error-prone manual transfer between a record that already exists and a document that needs to be sent. The record and the document become the same file, and the invoice is always as current as the last daily entered.

To size what your own retype chain costs before changing anything, the reporting chain cost calculator takes your shift count, your retype time per pass, and your office rate and returns a monthly exposure figure. It is worth running before deciding the number is too small to matter.

Run your own numbers

Rather than work it by hand every time, the reporting chain cost calculator does this arithmetic and shows its working. The rest of the set is on the mining calculators page.

Common questions

All field tools