Check an invoice against a quote: find what changed

This helps when the agreement is scattered across several records: an event booking, equipment hire, a supplier order or a small project. It is unnecessary for a two-line bill you can check yourself. It is not a replacement for professional help with a contractual dispute.

The easy-to-miss problem: an invoice can add up correctly while using the wrong agreement. A later email may change quantities but not prices. A credit may be additional, not a replacement. Two differently named charges may describe the same service.

Download the worked source pack and reusable template. It includes every fictional record used below, the checked answer and a blank version for organizing your own permitted information.

Prefer a spreadsheet? Download the invoice-check worksheet with three filled examples and blank rows for your own checks.

The invoice added up. Six things still needed correcting.

We gave Claude Opus 5.5, at Medium effort, seven fictional event-rental records in a new chat. We calculated the expected answer before running the test. No real customer documents or connected accounts were involved.

The supplier's final invoice showed a 1,222 balance. Its addition was correct. The source records supported these questions:

View full size ↗

Those six differences total 447. A separate 85 access charge remained unresolved because the supplied records said it needed later confirmation but did not contain that confirmation.

That distinction matters. The records produced a balance of 690 excluding the unresolved charge, or 775 if that charge was confirmed. Neither number was a legal ruling or an instruction to pay. “The approval is not in this packet” is not the same as “the charge is invalid.”

Open the actual CSV produced in this test. It includes each line's source references, status and next question. Detail rows and summary rows are both present, so do not sum the entire amount column.

If two receipts disagree, ask before choosing

View full size ↗

Then we added another fictional receipt for the same payment, on the same date, showing 300 instead of 400. Neither receipt said it replaced the other.

Claude changed the deposit from a confirmed discrepancy to an unresolved conflict. It did not choose 300 simply because that matched the invoice. The established differences dropped from 447 to 347, with four possible balances depending on the receipt and access-charge confirmations.

Its next question was the right kind of output: ask which payment amount was actually received and whether one receipt replaced the other. It did not need permission to contact the supplier, because nothing was sent.

This was one small text-record test and one conflicting-record follow-up. It does not establish a success rate for real invoices, scanned PDFs or unfamiliar contracts. A separate Analytics Vidhya test found that Opus 5.5 could catch a calculation trap yet still make factual and contextual mistakes elsewhere. Check the output, including its confident-looking tables.

Why the paperwork matters more than a strong opinion

In an owner discussion about disputed change orders, the difficulty was not adding the final invoice. It was establishing what the original scope included and which changes had been discussed.

The visible replies asked about the contract, scope and exclusions; some recommended professional help. That is the useful lesson, not an invitation to let AI take sides. If the agreement is unclear, organize the evidence and ask a specific question. Do not have the model invent the missing agreement.

Run a document check without connecting your accounts

Tools and cost

Our test used Claude on the web with Opus 5.5 Medium on a Max account, plus a downloaded CSV. No Excel add-in, API subscription, mailbox connector or paid invoice app was used.

Check that your own account offers the model before buying anything. The Pro help page lists US $20 per month, with regional prices and taxes varying. It has session and weekly limits; allowance depends on the model, conversation and attachments. This is not a promise that every plan exposes the same models or file tools. Canadian readers should check local pricing rather than rely on a currency conversion here.

Permissions and inputs

Start with the fictional packet. For your own work, use only records you are permitted to share with the service. Remove names, addresses, account and card details, signatures and unrelated confidential material. Keep original records unchanged.

For the text method tested here, give each source a simple label, its date, whether it was accepted or merely proposed, and the exact relevant wording. The labels help you find the evidence again; they are not software IDs or extra setup.

Trigger and output

You start this check manually when an invoice arrives. It is not an ongoing automation. The output is a downloadable comparison table plus questions for you to review. No payment, accounting entry or supplier message should happen automatically.

Setup steps

1. Gather one order's records. Include accepted revisions, credit notes and payment receipts, not just the first quote and final invoice.
2. Put the source text in a fresh chat. Preserve wording about what a revision changes. If tax or currency differs, state that explicitly; if unknown, say unknown.
3. Ask for an evidence table. Use the instruction below. Request source references for every finding, and separate unresolved items from confirmed mismatches.
4. Download and check the result. Open each cited source yourself and independently recalculate the affected lines. A convincing explanation without a matching passage is not a verified finding.

Human handoff and stop rules

You or the responsible bookkeeper checks each finding before it is used. Pause a conclusion when approval, delivery evidence, a credit's meaning or a payment amount is missing or contradictory. Request the missing record rather than converting uncertainty to zero.

For contested obligations, penalties or deadlines, get appropriate professional advice. This guide does not establish the law in the United States, Canada or any particular jurisdiction.

Failure handling

If source references are wrong, correct the source packet and rerun the affected comparison. If documents contradict one another, retain both and ask for clarification. Do not select the version that gives the preferred answer.

If the file does not download, keep the visible table and request CSV text as a fallback. That fallback was not needed in our test. If you hit an account limit or cannot verify the output, use the reusable template manually; do not let an AI availability problem delay a necessary human response.

Measurable test

With the supplied fictional packet, the first result should show 447 in confirmed discrepancies, 85 unresolved, and the two conditional balances 690 and 775. The conflicting-receipt example should reduce confirmed differences to 347, not continue treating the 100 payment difference as proved. These checks let you inspect the worked example; they do not certify a model for your real documents.

Why use Claude here, and when not to

Anthropic released Opus 5.5 on September 22 and reports improvements in knowledge work and source accuracy. That prompted this test. It does not mean invoice comparison is a new or exclusive capability. Our earlier simple budget check worked on both Opus 5 and Opus 5.5; we have not established that upgrading is necessary for this task.

The practical reason to consider chat is a one-off packet of scattered records that does not already live in a purchasing system. For a short invoice, a manual side-by-side check may be faster. For recurring purchasing, start with the tools you already use:

• Dext's purchase-order matching links invoices to existing Xero or QuickBooks Online purchase orders and warns when totals differ.
• Ramp documents three-way matching across purchase orders, receipts and invoices, plus change-order approvals. Do not replace established approval controls with a chat answer.

Use Claude to prepare a specific, checkable question, not a forceful accusation. For example: “The accepted revision changes quantities but retains the original rates. Could you confirm why the table rate changed from 18 to 20?” That is more useful than “AI says you overcharged me.”

If you issue quotes as well as receive invoices, keep scope and next actions clear in your own customer communication. Our quote follow-up guide covers that separate job. Reliable enquiry follow-up is also distinct from document review; see what our lead-response service includes.