Reconcile invoices against contracts or POs

Claude compares a batch of invoices to contracts or purchase orders and flags discrepancies before you pay.

A reconciliation report: matching invoices, discrepancies with line-item detail, and what to query.

1. 1

   Redact sensitive details

   Remove account numbers and full banking details. The agent needs pricing and line items, not payment credentials.

2. 2

   Query discrepancies before paying

   Email the vendor with the specific line item and amount. Do not approve the invoice until they respond.

3. 3

   Mark matching invoices for payment

   The reconciliation is not payment. You still approve the actual transaction in your accounting system.

Reconcile these invoices against the contracts or purchase orders I will provide. I need to know what matches and what does not before I approve payment.

Invoices:
[paste or describe: vendor, invoice number, line items, amounts]

Contracts or POs:
[paste the agreed pricing, terms, quantities, or attach a reference doc]

For each invoice return:
- Invoice number
- Status: matches, discrepancy, or missing reference
- Line-item breakdown: what matches and what does not
- Discrepancy detail: price difference, quantity difference, or unexpected charge
- Next action: pay, query the vendor, or escalate

Do not approve payment. Do not invent contract terms. If the contract is ambiguous, mark that invoice "needs review" and say what is unclear.

A small discrepancy can be a keying error or a price change you did not agree to. Always query it.

Sample case written by Hidden Logic Lab. Not affiliated with Claude.