Setting up an AP exception log for rental invoice disputes

By RentalSpend · October 7, 2026

A strong AP exception log gives you one place to track every disputed rental charge, the evidence behind it, and the deadline to act. It helps AP keep invoices moving while unresolved items stay visible and owned.

Set up the AP exception log as a single searchable register for every equipment-rental invoice item that cannot be cleared on first review. The log should capture the charge, the contract basis, the supporting evidence, the owner, and the deadline to resolve or dispute it so invoices do not disappear into email threads or fall past a contract notice window.^[1][2][3][4]

1. Define the exception categories you will track for rental invoices, such as rate mismatch, date mismatch, missing off-rent, duplicate invoice, missing PO, unauthorized charge, transportation, fuel, mileage, damage, loss, tax, and surcharge.
2. Choose the minimum fields every log entry must contain: invoice number, supplier, project or job, equipment ID, charge type, disputed amount, affected dates or quantities, reason for dispute, evidence attached, owner, status, aging, and next action.
3. Set the workflow so unresolved items stay in an exception queue or processing log until they are approved, clarified, credited, or formally disputed under the contract.
4. Assign ownership by issue type, not just by invoice, so AP, project controls, equipment management, or procurement each know which exceptions they must clear.
5. Add aging and deadline rules so the log alerts users before a supplier-specific dispute notice period or internal approval target expires.

Sources: ^[1][2][3][4]

1. Start with the records that prove what should have been billed

Begin by matching each invoice to the rental agreement, rate sheet, delivery or receipt evidence, off-rent confirmation, pickup record, and any change order or field approval that affects the charge. For a rental invoice, the question is not just whether the math is right. It is whether the charge belongs on that invoice at all under your agreement and the actual use dates on the job.^[4]

Use the log to force that match. If the invoice shows rental days that do not line up with the delivery or return record, or a line item appears with no supporting service ticket, write that gap into the exception description instead of a generic note like “review needed.” Clear descriptions make it easier for AP to route the item and faster for the supplier to respond.^[1][2][3]

2. Build the log fields around the decision you need to make

A useful exception log does not just store invoice data. It captures the exact decision AP needs: should we pay it, hold it, ask for backup, request a credit, or submit a formal dispute? SAP’s invoice-exception guidance emphasizes recording exceptions in a processing log and resolving them in exception or work views, which is the same basic idea you want in your own process: one controlled queue until the item is cleared.^[1][2]

If your ERP already exports invoice data, build the log from that export rather than rekeying everything by hand. Common fields such as invoice number, vendor ID, invoice date, amount, approval status, purchase order, department, and payment terms are enough to generate an exception report, then you can add rental-specific columns on top of them.^[3]

3. Separate the exception types so the right people can act

One invoice can carry more than one exception. That matters for rental spend because the fix for a wrong rate is often different from the fix for a missing off-rent date or an unapproved fuel surcharge. Track each exception type separately on the same invoice when needed so AP does not close the item after resolving only one problem.^[3]

• Rate or term mismatch: billed rate does not match the contract or rate sheet.
• Date mismatch: billed rental days do not match delivery, pickup, or off-rent records.
• Quantity mismatch: hours, days, mileage, or quantities are higher than support shows.
• Missing approval or PO: invoice lacks the authorization your process requires.
• Duplicate invoice: same invoice number or duplicate line appears in the system.
• Unclear charge type: transportation, fuel, refueling, service, tax, or surcharge needs review.
• Damage or loss charge: needs incident evidence, inspection record, or claims review.

Sources: ^{[1][2][5][3][4]}

Herc Rentals’ US terms, for example, state that customer invoices can include rental, time, mileage, service, transportation, refueling service, surcharges, and taxes, and that disputed charges must be notified in writing within 30 days of invoice receipt under that agreement. That is a reminder to build your log around the terms in your own contract, not a generic AP assumption.^[4]

4. Make the workflow visible from intake to resolution

The log should reflect where the item sits today, not just what went wrong. A simple status set usually works best: new, under review, waiting on backup, waiting on supplier, approved to pay, hold payment, credit pending, disputed formally, and closed. Keep comments and attachments with the record so anyone who inherits the issue can see the history without searching email.^[1][2]

If your team uses different systems, keep one master log and link out to the ERP, invoice image, email chain, delivery proof, and dispute notice. The point is not to make the log a second accounting system. The point is to make it the control point for exceptions until they are resolved.^[1][2][3]

5. Add aging rules before a deadline is missed

For rental invoices, aging is not just about payment delay. It also protects your right to dispute. Add a field for the contract notice deadline and another for your internal follow-up target. Then use color or status flags to show items that are nearing the notice limit, waiting too long on a field response, or likely to roll into late-payment exposure.^[4]

This matters because supplier terms vary. Some agreements require written dispute notice by email, portal, or another method, and some allow only a short window. Your log should therefore store the method used, the date sent, and the person who sent it, so the dispute is defensible later.^[4]

6. Standardize how exceptions are described

Use plain labels that explain the problem in one line. Good examples are: extra rental week without off-rent record, fuel surcharge not supported by contract, duplicate invoice number, or transportation charge above agreed amount. Avoid vague notes like discrepancy found or issue pending. Specific wording makes reporting better and shortens the supplier follow-up cycle.^[1][2][3]

It also helps to keep the dollar amount and the disputed basis together. If only part of the invoice is wrong, log the exact line amount in dispute rather than blocking the full invoice by default. That gives AP a clean record of what can still be paid and what must remain open.^[2][3]

7. Review the log weekly and close the loop

Review open exceptions at least weekly with AP, project, equipment, and procurement stakeholders. Focus on the oldest items, the highest-dollar items, and any item nearing a supplier notice deadline. Resolve the cause, not just the invoice, so repeat errors can be traced back to the right branch of the process.^[1][2][3][4]

When an item is closed, keep the final disposition in the log: paid as billed, corrected and repaid, credit memo received, dispute accepted, dispute denied, or written off under company policy. That history is what turns the log from a temporary tracker into a control tool for future rental spend review.^[1][2][3]

What to do when the invoice does not match the records

If the invoice conflicts with the contract, rate sheet, or field records, do three things right away: hold the item in the exception queue, document the exact variance with supporting evidence, and send the issue to the person who can correct that specific charge type. If the contract requires written notice within a set period, send it before the deadline even if the internal review is still underway. Then update the log with the notice date and next follow-up date.^[1][2][4]

If the records are incomplete, use the log to request only the missing proof you need, such as off-rent confirmation, signed delivery ticket, or approval record. That keeps the request narrow and makes it easier for the field or supplier to answer. If the supplier disputes your claim, retain the response and route it to the owner who can decide whether to accept, escalate, or negotiate a credit.^[1][2][3][4]

Practical next steps

Start with a simple spreadsheet or queue in your AP system, then add the rental-specific fields, aging rules, and ownership columns. Test it on one supplier or one region, confirm that every open exception has an owner and a deadline, and then expand the same structure across the rest of your rental spend. The goal is one reliable log that keeps disputed charges visible until they are resolved, credited, or formally closed under your contract terms.^[1][2][3][4]

← All resources