Field Ticket to Invoice: How Crane Companies Get Paid Faster Without Chasing Paper

Here is a situation I have heard from crane company owners across the country. The operator works a 10-hour day plus 2 hours of standby while the GC's site gets ready. He hands a handwritten ticket to the GC's foreman, who puts it in his truck. The operator drives home. The ticket eventually makes its way to the GC's office. Your office gets a fax or a photo three days later. Someone at your office types the hours into your accounting system. The invoice goes out a week and a half after the job was completed. The GC reviews it 5 days later, disputes the standby hours because your operator's handwriting was unclear, and asks for backup documentation. You do not have any. You negotiate the standby down to keep the relationship. The GC pays the reduced invoice 45 days after receipt.

You just financed their project for 60 days, at a discount, with your own working capital. That is not a payment terms problem. It is a documentation and workflow problem. The fix is not to negotiate payment terms more aggressively. It is to build a field ticket to invoice workflow that produces a signed, timestamped, defensible record the moment the job is complete, and converts it to an invoice before the operator's truck leaves the site.

How the Broken Workflow Actually Looks

The manual billing cycle in the crane industry has more failure points than most owners consciously recognize because each failure point is small and the total cost is distributed across multiple jobs and multiple billing cycles.

The handwritten ticket is failure point one. Handwriting is ambiguous. Hours that look like "10" can be read as "10" or "1.0". A standby entry of "2 hrs" means nothing without knowing the start and stop time of the standby period. When the GC disputes the hours, you have no metadata to back up the number on the handwritten form.

The photograph or fax transmission is failure point two. Photos taken on job sites in poor lighting are often unreadable. Fax machines are still in use at enough GC offices that this is a real workflow step. A faxed field ticket that arrives partially cut off at the bottom is missing whatever information was at the bottom of the form. Nobody calls to ask for a resend until the invoice is disputed.

Manual data entry into your accounting system is failure point three. Data entry errors are statistical. If your office staff is entering 40 field tickets a week, the error rate across those 40 entries is not zero. A transposed digit in the job number attaches the ticket to the wrong project. An hours entry that rounds down rather than up costs you money you earned.

The delay between job completion and invoice delivery is failure point four, and it is the one that most directly affects cash flow. Every day between job completion and invoice delivery is a day the GC has not started their payment clock. If your payment terms are net 30 and you invoice 10 days after job completion, you have effectively given yourself net 40 terms. Over a year of operations, that delay represents tens of thousands of dollars in working capital that is sitting in receivables instead of in your account.

The absence of documentation when disputes arise is failure point five. When the GC disputes standby hours and you have a handwritten ticket, a fax, and a manual data entry, you have three documents that may not agree with each other and none of which have metadata showing when they were created or by whom. You are in a negotiation, not a documentation review, and you will lose some portion of legitimate revenue in that negotiation.

What a Digital Field Ticket Captures

A digital field ticket built for crane operations captures the data that matters for both billing and compliance in one mobile-submitted record.

Start time and stop time are logged by the operator when they clock into and out of the job, with GPS coordinates stamping each event. Standby time is a separate log entry with its own start and stop time. When the GC disputes standby, you produce the log entry showing that standby began at 7:14 AM when the crane arrived on site and the GC's site supervisor signed off that the site was not ready, and ended at 9:31 AM when work began. That is a 2 hour 17 minute standby event with a timestamp and a GPS coordinate at the job address. There is nothing to dispute.

Operator ID is linked to the job record from the dispatch record. The operator who submitted the field ticket is authenticated through their app account, not through their signature on a piece of paper. The NCCCO certification status of that operator at the time of the job is captured in the operator record and retrievable from the job history.

Crane ID is linked from the dispatch record. The specific machine operated, its registration and inspection status at the time of the job, and its load chart are all part of the machine record attached to the field ticket.

Materials used are captured as line items within the field ticket. Rigging hardware, consumables, fuel surcharges, and any materials supplied by the crane company are entered by the operator during or at the conclusion of the job. They flow to the invoice as separate line items with unit prices from your billing rate table, not typed manually by office staff.

Photos of the lift or site condition, captured during the job and attached to the field ticket, provide visual documentation of the work performed and site conditions. If there is later a question about whether a lift was performed safely or what the ground conditions were for the outrigger setup, those photos are part of the record.

GC signature is captured on the operator's mobile device at the conclusion of the job. The GC's site representative signs the field ticket on the operator's phone or tablet. The signature is timestamped and attached to the field ticket record. The signed record is the billing authorization.

OSHA 1926.1400 Record-Keeping and Why Your Field Ticket Is Also a Compliance Record

A field ticket that captures crane ID, operator ID, date, job address, and pre-shift inspection status is doing double duty. It is a billing document and a compliance record simultaneously.

OSHA 29 CFR 1926.1400 establishes the general scope of crane safety in construction and, through the broader Subpart CC framework, imposes record-keeping obligations that follow the equipment and the operator. The pre-shift inspection under 1926.1412(d) must be documented. The operator certification verification required by 1926.1427(k) should be documented. The training required by 1926.1430 must be documented. When OSHA investigates an incident, they look at all of these records together.

A field ticket for a given job should connect to the pre-shift inspection record for that crane on that day. When you can produce a digital record showing that the crane was inspected at 6:45 AM, the operator was verified as NCCCO-certified for the crane type, the job began at 7:14 AM, and the work was completed at 3:30 PM with a signed field ticket at 3:42 PM, you have documented the entire compliance and operational chain for that lift. OSHA has a complete picture without you having to reconstruct anything from memory.

This is the difference between a field ticket as a billing artifact and a field ticket as a compliance asset. The billing side gets you paid faster. The compliance side protects you when something goes wrong. Neither function is optional for a crane company operating on commercial construction projects in 2026.

The record retention requirements for Subpart CC apply to the inspection records. Pre-shift inspection records must be retained for three months. Monthly inspection records must be retained for twelve months. Annual inspection records must be retained for the life of the equipment. Your field tickets, which reference the inspection records by date and crane ID, should be retained at least as long as your standard accounts receivable retention period, which for most companies is seven years. A cloud-based system that retains all records without manual archiving is the right infrastructure for this.

The 10-Second Invoice Path

When the GC signs the field ticket on the operator's mobile device at 3:42 PM, the invoice should be ready within 10 seconds. Not 10 days. Ten seconds.

That timeline is achievable because the invoice contains no new information. Every piece of data on the invoice was captured during the dispatch and field ticket process. The job address, GC name, work order number, crane ID, operator name, hours worked, standby time, materials, and applicable billing rates are all in the system. The invoice generation is a database read and a PDF render, not a data entry task.

The invoice reflects the exact hours, standby, and materials from the field ticket because it reads directly from the field ticket record. There is no opportunity for a rounding error in transcription or a forgotten line item in manual entry. The invoice is a faithful reflection of the signed field ticket.

The PDF is delivered to the GC's billing contact email within seconds of invoice generation. The GC's payment clock starts running at 3:42 PM on the day of job completion, not at some point in the following week when your office staff gets around to processing the paperwork. If your payment terms are net 30 and you invoice the same day, you collect two weeks earlier than if you invoice 14 days after job completion. Across a full year of operations, that cash flow difference is material.

The signed field ticket attached to the invoice is the backup documentation for every line item. When the GC reviews the invoice and has a question about the standby charge, the answer is in the attached field ticket: the timestamped standby log entry, the GPS coordinates showing the crane was at the job address during the standby period, and the GC site representative's digital signature acknowledging the work. Most disputes resolve without a phone call.

Getting Paid: ACH, Card, and Wire

Sending an invoice does not mean you get paid. Getting paid requires making payment easy and removing the friction between the GC's intent to pay and the money moving into your account.

Invoice emails from CraneOp include a payment link that processes ACH and card payments through Stripe Connect. The GC's accounts payable team does not need to issue a physical check, mail it, and wait for it to clear. They click the link, enter payment details, and submit. ACH payments typically settle in 2 to 3 business days. Card payments settle faster. Either option is faster than a mailed check.

First-payment hold is a standard practice for new GC relationships. When a GC makes their first payment through the platform, the ACH payment is held until the bank verification process confirms the account. Subsequent payments from the same GC process without a hold. This protects against ACH fraud on new customer relationships while maintaining fast settlement for established ones.

Wire transfer is available for large project invoices where the GC prefers it. The invoice email includes ACH and wire routing information alongside the payment link, so the GC's accounts payable team has all three options without having to call your office to ask for wire instructions.

The payment status is visible in your dashboard in real time. When the GC's payment settles, the invoice status updates automatically and the job is marked as closed in the financial records. There is no manual reconciliation step where your bookkeeper matches payments to invoices.

Conclusion

The cash flow problem in crane companies is not primarily a net-terms problem. It is a documentation-speed problem. The longer it takes to produce a defensible field ticket, the longer it takes to issue an invoice, the longer it takes to get paid, and the more of your working capital is sitting in receivables instead of in your account.

Fixing the workflow does not require negotiating harder with your GCs. It requires a mobile field ticket that captures everything at the moment it happens, converts to an invoice the moment it is signed, and delivers that invoice while the GC's site representative is still on site. Stop financing your customers. The technology to fix this exists today.

Written by LaSean Pickens, founder of CraneOp.