Heavy Equipment Rental Invoice Extraction to Excel

A heavy equipment rental invoice line is one equipment unit charged for one billing period at one rate tier. It is not a SKU. The same physical excavator, aerial lift, or compressor can produce five or more lines on a single invoice as billing windows roll or rate tiers switch, with each line dragging its own cascade of RPP, environmental services, fuel, and delivery surcharges.

That structural fact is what breaks goods-invoice mental models when an AP processor first tries to pull a rental invoice into Excel. A construction AP clerk who reaches for a rental invoice with the same instincts they use for a materials invoice will look at six lines tagged to the same fleet number and treat five of them as duplicates. They are not duplicates. They are five separate billing periods, or one period with mid-cycle rate-tier switches, each with its own surcharge cascade hanging off it. Sum them as duplicates and the spreadsheet undercounts the spend; roll the surcharge cascade into the base rental column and the audit angle disappears before the controller can see it.

Heavy equipment rental invoice extraction is the operational task of pulling that line-per-period structure out of a folder of mixed-vendor rental PDFs and into a working spreadsheet that reflects it accurately. At minimum, every line needs the equipment number or fleet number, the contract or order number, the period start and period end, the rate tier in effect, the base rental amount, and a separate column for each element of the surcharge cascade rather than a single rolled-up subtotal. With those columns intact, the AP team can sanity-check the math, code the lines to jobs, and post to Sage 300 CRE, Foundation, Viewpoint Vista, Procore, or QuickBooks without a second round of cleanup.

What follows is the cross-vendor field schema across United Rentals, Sunbelt, Herc, Cat dealers, and regional houses, the citable per-vendor rate and cap detail that makes an extraction output audit-ready, and three concrete routes from a folder of rental PDFs to a spreadsheet that imports cleanly to the construction ERPs AP teams actually run.

The Cross-Vendor Field Schema on a US Rental Invoice

The fields on a heavy equipment rental invoice arrive in a roughly consistent order across the major US rental houses, but each house labels them differently and lays them out differently on the page. The schema below is the unified extraction target — every field worth pulling from a UR, Sunbelt, Herc, Cat dealer, or regional invoice — with the vendor-specific naming variations called out where they matter for AP reconciliation.

Before the schema itself, one piece of scope: a per-rental invoice is a different document from a monthly account statement. The statement is an account-level rollup that lists invoices and their balances; the line-item invoice is what AP extracts and codes. Statements are useful for cash applications and aging reports, but they are not a substitute for the invoice when the goal is line-level data. Heavy equipment rental invoices are also a different document family from AIA pay applications — if you arrived here from adjacent searches, the AIA G702/G703 workflow on the GC-to-owner side has its own structure and its own extraction shape, covered separately in process AIA G702 and G703 pay applications.

Equipment-identifier fields. Every rental invoice carries the rental house's internal asset identifier. United Rentals uses a 7-digit fleet number; Sunbelt uses an alphanumeric in the shape of 0070008; Cat dealer invoices carry the dealer's own asset code; regional houses each follow their own conventions. This number is the rental house's record key, not the customer's, and it is the field that lets AP tie a line back to a specific physical asset on a job site. Make, model, and category sit alongside the equipment number and describe the equipment class. Equipment serial number sometimes appears on the invoice and sometimes does not — when an AP team's insurance policy tracks rental fleet exposure by serial number, the ability to extract equipment serial number from rental invoice is essential, even if the field is intermittently populated and has to be backfilled from the rental contract or call-out confirmation when missing.

Contract and job-coding fields. The contract or order number links the invoice line back to the rental contract origination. The job site address and the customer's job number are the cost-coding key the AP team records, and on a multi-job AP setup the job number is what controls how the line eventually posts. PO number is often blank because heavy equipment rentals are commonly non-PO — a real characteristic of the document family rather than a missing field, and the schema should accommodate the blank rather than treat it as an extraction failure.

Period and rate fields. Period start and period end define the billing window for one line. Rate tier names which tier governs that window — hourly, daily, weekly, monthly, 4-week, or 28-day — and rate amount carries the unit price for that tier. Quantity is usually one per line because each line represents one asset for one period; line subtotal is the base rental amount before the surcharge cascade attaches.

The surcharge cascade. This is where the line-per-period structure compounds. Each rental line typically carries some combination of: RPP — also published as Rental Protection Plan, damage waiver, or LDW depending on the house — environmental services charge (ESC); fuel surcharge or refueling charge, distinct from the environmental fee; delivery and pickup, sometimes labeled as haul or freight; transportation surcharge; miscellaneous (cleaning, lost-key, tire damage); and state and local sales or use tax. Some houses break each surcharge out per line; others roll some elements up at the invoice footer; some do both, with the per-line surcharge driven by the rental contract setup and the footer charges driven by the order. An extraction schema that assumes every surcharge appears in the same place on every invoice will mis-handle one of these patterns. The reliable approach is to treat each surcharge as its own column and let it be empty on lines where it does not apply.

Vendor-Specific Rate and Cap Detail Across United Rentals, Sunbelt, and Herc

The schema gets the columns right; the per-vendor terms tell you whether the numbers in those columns are correct. When an environmental services charge or an RPP line lands on an invoice, the AP processor needs a reference point — what does the rental house's own published terms say this charge is supposed to be? The figures below are that reference, drawn from each vendor's own legal documentation and worth carrying into the AP workflow as a check.

United Rentals. The Environmental Service Charge on a UR invoice is 2.00% of the service charge, capped at $99 per invoice — so an ESC line over $99 on a UR invoice is the audit lead, not the norm. The Rental Protection Plan is 15% of rental charges plus state and local taxes, and under RPP, UR waives liability above the lesser of 10% of replacement value, 10% of repair, or $500 plus tax for theft or direct damage. Refueling charges vary per store location on the date of return, which is why the same fuel charge can look different across two UR branches on the same job. These figures are published in United Rentals' rental service terms; an AP team disputing a charge should cite the same source.

Sunbelt Rentals. Sunbelt's RPP caps customer liability at 10% of fair market value up to $500 per piece for lost equipment, and 10% of repair charges up to $500 per piece for accidental damage. The customer account must be current at the time of loss for RPP to apply — a condition that bites when a delinquency on an unrelated line voids the RPP coverage for an asset returned damaged. The delinquency charge itself is the lesser of 1.5% per month or the maximum legal rate in the jurisdiction, which means the published-terms percentage is a ceiling rather than a guaranteed figure. Sunbelt's published US terms and conditions are the audit reference for any of these calculations.

Herc Rentals. Herc's RPP cap is $500 or 10% per item, whichever is less, and Herc's own US rental agreement terms describe RPP explicitly as "NOT insurance" — language that matters because some customers carry the assumption that the protection plan is an insurance product. RPP can only be accepted at or prior to commencement of the rental, so a request to add coverage mid-rental is not honored under the published terms. Herc's late payment fee is at the jurisdiction's maximum legal rate.

Cat dealers and regional rental houses each publish their own rate sheets and terms. The structural pattern is similar — an environmental fee with some cap, an RPP percentage with some per-piece ceiling, a delinquency percentage at the legal rate — but the specific figures vary house by house. An AP team that handles Cat or regional invoices in volume should pull the matching terms documents into the same audit reference shelf as the three above and verify the same way.

The reason these specifics earn shelf space in the AP workflow is exactly that they make overcharge flags legible. When an extracted line on a UR invoice shows an ESC over $99, when a Sunbelt delinquency calculation looks above 1.5% per month, when a Herc RPP line carries more than $500 per piece, those flags are the audit leads. The full taxonomy of overcharge categories — rate-roll failures, off-rent verification, RPP misapplication, accessorial inflation — sits in the companion piece on how to audit rental invoices for rate-roll, RPP, and off-rent overcharges, which goes deeper than this article does.

Rate Tiers, the Daily-to-Weekly-to-Monthly Rate Roll, and the Blue Book Hour Basis

Underneath the rate amount on every rental invoice line is a small set of conventions every AP processor should know well enough to verify. They govern the math the rental house used to produce the figure, and they are the mechanism that determines whether a rented asset on a long-running job was billed correctly or whether the invoice missed a tier transition.

The standard hour basis used across the US heavy equipment rental industry is 8 hours per day, 44 hours per week, and 176 hours per month. The 176-hour monthly basis carries weight beyond rental-house tradition. On Federal-aid construction contracts, the FHWA accepts an hourly equipment rental rate calculated by dividing the Blue Book monthly rental rate by 176, establishing 176 hours as the federal-standard monthly basis for equipment rental cost — see the FHWA equipment rental rate guidance for Federal-aid contracts for the underlying contract administration framework. That federal acceptance gives the convention regulatory standing on public-works contracts and also makes 176 hours the natural reference point when an AP team needs to pressure-test a vendor's monthly calculation against an external benchmark.

The Blue Book inter-tier ratios let an AP team sanity-check whether the daily-to-weekly-to-monthly progression on an invoice is internally consistent. The daily Blue Book rate runs at approximately 25% of the weekly rate; the hourly Blue Book rate runs at approximately 15% of the daily. So when a UR or Sunbelt invoice shows a daily rate that does not roughly match a quarter of the corresponding weekly rate on the same equipment class, the discrepancy is worth a closer look — usually it is the rate sheet rather than an error, but the ratio is the first check.

Overtime conventions follow the same hour basis. On a daily rental, hours over 8 in a single day bill at 1/8 of the daily rate per hour. On a weekly rental, hours over 40 in a week bill at 1/40 of the weekly rate per hour. The rental contract governs which convention applies, and the contract should be the reference whenever an overtime line on the invoice does not match the AP team's expectation.

The rate-roll convention is the central mechanism on a heavy equipment rental invoice and the reason the line-per-period structure exists in the first place. When a rental that started at the daily rate runs long enough to qualify for a weekly rate, the invoice should switch retroactively to the weekly rate from the start of that week — not just charge the weekly rate going forward. The same logic applies daily-to-weekly-to-monthly: a rental that crosses into monthly territory should re-bill the prior weekly periods at the monthly rate from the start of the month-equivalent window. This is why the same asset can produce two or more lines on a single invoice as the rate tier changes mid-period: each line reflects the tier that ultimately governed that span of time after the rate roll resolved.

When the rate roll does not happen, the AP team is being charged the higher tier through a span that should have been re-billed at the lower one. That is the most common rental-invoice overcharge finding on construction AP queues. The audit companion piece picks up the rate-roll, off-rent, RPP, and accessorial taxonomy from there; the rate-tier mechanics in this section are the math that lets an extraction output be checkable in the first place.

---

Three Routes from a Folder of Rental PDFs to a Working Spreadsheet

The right route from a folder of rental PDFs to an Excel file depends on rental volume and vendor mix more than on extraction-tool sophistication. A specialty subcontractor processing twelve rental invoices a month from one local Cat dealer faces a different operational reality than a mid-market GC pulling four hundred invoices a month from UR, Sunbelt, Herc, two regional houses, and a Cat dealer. The three routes below cover the realistic options, with honest fit notes for each.

Route 1: manual entry from PDF copy-paste into Excel. This is the right route for very low rental volume, single-AP-clerk shops, and one-off invoices a team is still learning the shape of. A controller who is also the AP processor and handles a handful of rental lines per week can sit with each PDF, transcribe the fields into a working spreadsheet, and reconcile the math by eye in less time than it takes to set up anything more elaborate. The route's honest limit is the line-per-period structure. Manual transcribers consistently miss the retroactive rate-roll switch, treat multi-period lines on the same fleet number as duplicates, and roll the surcharge cascade into the base rental column to keep the spreadsheet narrow. Each of those slips either hides spend or hides the overcharge signal, and they compound as volume grows. By the time an AP queue is moving fifty rental invoices a month, manual entry is no longer the cheap option even when no software has been bought.

Route 2: vendor portal export. Each of the major US rental houses publishes a customer portal with invoice export. United Rentals' Total Control portal supports invoice download alongside EDI, cXML, JSON, and consolidated invoice spreadsheet exports for enrolled accounts. Sunbelt's Command Center and Herc's customer portal offer comparable exports from within their own ecosystems. When a contractor's rental spend is concentrated with one or two houses, the portal route is genuinely strong: the AP team gets a clean structured file straight from the vendor with no intermediate extraction step, and the file shape matches the rental house's own internal billing system rather than a downstream guess.

The portal route's limit is the multi-vendor reality. An AP team that pulls from six or more houses each month is staring at six portals to log into, six different file shapes to download, and a stitching job by hand to merge the outputs into a single consolidated working file. The portal route does not solve that — it relocates the work from extraction to consolidation. Some houses do not export the surcharge cascade in the same column shape the AP team uses for ERP import, which means even a clean portal export can need re-shaping before it posts. The downstream piece on building a monthly cross-vendor rental ledger and reconciling it against vendor statements covers the consolidation shape that absorbs these mixed portal exports into a single working ledger.

Route 3: batch prompt-based extraction across mixed-vendor folders. This is the operational answer to the multi-portal stitching problem and the natural fit for multi-vendor mid-market construction AP. The setup is straightforward: a folder of mixed-vendor rental PDFs from UR, Sunbelt, Herc, a Cat dealer, and a regional house goes into a single batch; one prompt describes the unified extraction schema (equipment number, contract, period start and period end, rate tier, base rental, RPP, ESC, fuel, delivery, tax, with one row per distribution line); the output is a consolidated spreadsheet ready for ERP import. Because the cross-vendor field schema is consistent enough at the data layer — every house carries the same set of fields under different labels — one prompt template, written once, runs across the whole vendor set. This is what makes rental invoice ap automation construction workflows practical at multi-vendor scale rather than vendor-by-vendor.

A robust extraction approach also has to handle layout diversity. UR invoices are two-column with a line table. Sunbelt invoices are single-column. Herc invoices run multi-page with statement-style breaks, and Cat dealer invoices are each idiosyncratic to the dealer. A route 3 tool that assumes one canonical template will mis-handle three of the four; the operational requirement is reading the field schema regardless of layout.

This is where our own product fits in route 3. AI rental invoice data extraction for multi-vendor construction AP runs against the same prompt-based pattern: an AP team writes one prompt describing the unified rental schema — equipment number, contract, period start and end, rate tier, base rental, the surcharge cascade — and gets back a spreadsheet with one row per distribution line, run across whatever folder of mixed-vendor PDFs the AP cycle produced. The prompt is saved once and re-applied each cycle, which is what keeps the column shape stable month over month. Each output row carries a reference back to its source PDF and page number, which is the verification path when a controller queries a line.

For AP teams comparing extraction route 3 against the broader AP-automation landscape — workflow, approval routing, three-way match, ERP integration depth — the compare AP automation software for construction companies piece sits adjacent to this article's scope and is the right next reference. For rental teams in oilfield operations, the related guide to oilfield rental invoice workflows covers field-ticket matching, AFE and well coding, and off-rent review. And for readers who arrived here from a more general construction-extraction search and want to place the rental document family inside the wider picture, the construction-industry invoice data extraction overview covers the umbrella context — rental invoices, AIA pay applications, materials invoices, and the rest — that this article deliberately scopes down from.

The Spreadsheet Column Schema and the Bridge to Construction ERP Import

The rule that makes a rental-invoice extraction output post cleanly to a construction ERP is one row per distribution line in the spreadsheet. Each rental line and each accessorial element typically posts to its own GL account or its own cost code, so the spreadsheet's grain has to match the import's grain. An output that compresses the cascade into a single subtotal forces an AP processor to expand it back out before posting, and at that point the extraction has not actually saved the work.

Working backward from the ERP import, the columns the spreadsheet needs are: vendor (the rental house); invoice number; invoice date; contract or order number; equipment number or fleet number; equipment description (make, model, category); job number; cost code or phase code; period start; period end; rate tier; rate amount; units; base subtotal; then a separate column for each element of the surcharge cascade — RPP or damage waiver, environmental services charge, fuel or refueling, delivery and pickup, transportation, miscellaneous, and sales or use tax. The RPP column, the rental invoice rpp environmental fee column, the fuel column, the delivery column, and the tax column have to be split out rather than rolled into the line subtotal. That separation is what lets AP code each element to the right account, and what lets the controller audit any element later when a question comes up. Pulling the rental invoice line items excel-side into this shape is the operational target for extraction.

Each major construction ERP expects an import shape close to this column set, with one structural variation worth knowing. Sage 300 CRE Accounts Payable invoice import expects an invoice header line plus one or more distribution lines, with a separate tax line where the company tracks taxes by jurisdiction. The most common surprise for AP teams new to Sage 300 CRE rental import is the tax-line treatment — taxes do not piggyback on the distribution; they ride a dedicated line. Foundation Software and Viewpoint Vista accept similar invoice-plus-distribution-line structures with their own field names and validation rules. Procore Pay imports against committed contracts and POs and expects the cost-code allocation to appear in the import file rather than being applied after the fact. QuickBooks (Online and Desktop) accepts a flatter line-per-distribution import shape, which is the right fit for construction AP teams not on a dedicated construction ERP — typically smaller specialty subcontractors and bookkeepers running multi-client rosters.

The downstream coding workflow — the actual mapping of each extracted distribution line to the right job, phase, and cost code — is its own piece of work. Rental invoices are one of several document families an AP team codes this way, and the deeper reference on how to code construction invoices by job, phase, and cost code covers the workflow without re-deriving the rental schema each time.

One additional case worth naming explicitly: when a single rental invoice covers a piece of equipment that moved across multiple jobs in one billing cycle, the AP team has to split a single rental invoice across multiple jobs using field-log days or hours. That allocation is a discrete workflow that sits downstream of extraction and is handled in its own companion piece, so the schema in this article stops at the line-per-distribution grain and lets the allocation companion pick up from there.

Once the extracted spreadsheet carries the right columns at the right grain, with one row per distribution line and the surcharge cascade split out, the ERP import is mechanical. The audit angle stays visible in the columns; the cost-coding step has the field it needs in job number; the controller can query any line back to its source PDF. That is the difference between an extraction output that posts and one that needs a second round of cleanup before it becomes useful.