AI invoice processing: checks before payment

AI invoice processing uses artificial intelligence to read supplier invoices, extract financial details, compare them with purchase orders and flag anything that needs attention. An AI agent can also identify possible duplicate bills and prepare draft bookkeeping entries. These tasks take time when handled manually, particularly when invoices arrive in different formats or contain inconsistent descriptions. But preparing an invoice for payment and authorising the payment are separate responsibilities. An agent can assemble the evidence. A person should approve the transfer, accept new suppliers and authorise changes to bank details.

Consider a familiar situation: a supplier sends an invoice that looks perfectly ordinary, but its bank account differs from the one already on file. Or the same bill arrives twice under different filenames. A correct total does not prove that the payment request is genuine. Good AI invoice processing catches these problems before they reach the payment stage and gives the reviewer enough information to investigate them.

Give the agent a clear reading task

Invoices arrive as PDFs, scanned documents, email attachments and files exported from supplier portals. Their layouts vary. One supplier puts its invoice number near the top right, another places it below the address, and some use abbreviations for products or services. An AI agent can read these documents and extract the information needed for bookkeeping.

A useful first pass should capture the supplier name, invoice number, issue date, payment due date, currency, tax details and total payable. It should also record the description of the goods or services and the bank details printed on the invoice.

The original document should remain attached to the extracted information. The agent should distinguish between fields it read clearly and those it could not establish with confidence. For example, a blurred scan might make the final digit of an invoice number difficult to identify. That uncertainty belongs in the review record. A guessed value should never quietly become a bookkeeping fact.

Compare the invoice with the purchase order

An invoice tells you what a supplier says is owed. It does not prove that the business ordered the goods, received them or agreed to the price. Comparing an invoice with its purchase order is therefore one of the most useful tasks to delegate.

Suppose a business orders 20 replacement keyboards at €35 each. The purchase order records the quantity, unit price and supplier. The invoice arrives for 20 keyboards at €38 each. An agent can compare the documents, calculate the €60 difference and flag the discrepancy. It should not quietly replace the agreed price with the invoice amount.

Quantity and description checks matter too. An invoice for 30 units against an order for 20 deserves attention. So does a charge for installation when the purchase order covers equipment only. If delivery records or goods-received notes are available, the agent can compare those documents as well.

The review should show the purchase order reference, invoice value, difference and reason for the flag. If no purchase order exists, the agent should say so. Some legitimate expenses do not require formal purchase orders, but a person still needs to check who authorised them.

Find duplicate bills and unusual amounts

A supplier might resend an attachment, send a payment reminder or submit the same invoice through two different channels. The filenames can be completely different. Comparing filenames alone will miss many duplicates.

An agent should compare supplier identity, invoice number, date, currency and total amount. It can also flag near matches, such as two invoices from the same supplier with identical totals but slightly different reference numbers. A possible duplicate should go to a person for review, not be deleted automatically. It might be a corrected invoice, a credit note or a legitimate recurring charge.

Amount checks can reveal other problems. A monthly software bill might suddenly increase, a familiar supplier might introduce an unfamiliar charge, or the tax calculation might differ from previous invoices. When earlier records are available, an agent can compare them and explain what changed.

A difference is a reason to investigate, not automatic proof of an error. An annual renewal might explain a larger bill. A smaller amount might indicate that part of an order has not yet been invoiced. The agent should provide the comparison and supporting documents. The person responsible for the budget decides whether the explanation is acceptable.

Keep supplier and bank changes under human control

Adding a supplier to an accounting system creates a route for future payments. Changing an existing supplier's bank details creates another. Neither action should happen simply because an invoice contains new information.

A new supplier requires a person to verify the business and approve its addition to the records. A changed bank account requires independent verification before anyone uses the new details. The reviewer should contact the supplier through an established channel, using contact information already held by the business rather than a telephone number or link in the message requesting the change.

This distinction matters even when every other invoice check passes. A matching purchase order does not authorise a supplier change. A correct invoice total does not validate a new bank account. An established supplier name does not prove that an email requesting different payment details came from that supplier.

The agent can compare the invoice details with the approved supplier record and flag any mismatch. It can prepare the information for verification, but the decision to create a supplier or change payment details belongs to an authorised person.

Prepare the bookkeeping entry for review

After the invoice checks, an agent can prepare a draft bookkeeping entry. It might suggest the supplier account, expense category, tax treatment, invoice date and payment due date. It can also attach the source invoice and purchase order reference.

The draft should explain any assumptions. An invoice for office chairs might be classified as an office equipment expense, but the correct accounting treatment depends on the business's policies and the nature and value of the purchase. If the relevant policy is missing, the agent should ask rather than invent a rule.

A bookkeeper should check the supplier identity, tax calculation, account classification and supporting documents before accepting the entry. They should also check whether the invoice has already been recorded. If the business has different rules for subscriptions, capital purchases or reimbursable expenses, those rules belong in the agent's brief.

The Delagents bookkeeper template provides a starting role for invoice and bookkeeping preparation. Define which records the agent may read, which entries it may draft and which actions require human approval. An assignment limited to preparing and checking invoices is easier to review than an instruction to manage all accounts payable.

Make payment a separate approval

Even when an invoice has passed every check and its bookkeeping entry is ready, the agent should not decide that money can leave the business. Payment approval belongs to someone with the authority and context to make that decision.

A useful approval request should include the supplier name, receiving account, invoice number, due date, currency and total amount. It should also show the purchase order or other evidence supporting the expense, any differences found during checking, the duplicate check and the proposed bookkeeping entry. The reviewer should be able to open the original invoice without searching through email attachments.

Approval must apply to the exact proposed action. Approving a €700 invoice for a named supplier is different from allowing an agent to pay every future invoice from that supplier. If the amount, recipient or bank details change after approval, the revised action needs another review. An earlier approval should not silently carry over.

In Delagents, actions that affect something outside the workspace wait in an approvals inbox. Each card shows the exact proposed action, the cost so far and a deadline. A person can approve, change or reject it. Moving money and changing records remain subject to human sign-off. Every delegation also has a hard budget cap, while an append-only activity log records tool calls, approvals and policy changes.

Test with a small batch before expanding

Start with a small batch of recent invoices rather than handing over the entire accounts payable queue. Include an ordinary recurring bill, an invoice with a price difference, a possible duplicate and a document with unclear information. If available, include a supplier record with changed bank details so the verification process can be tested without authorising a transfer.

Compare the extracted fields with the original documents. Check whether the agent found the correct purchase orders, calculated differences accurately and explained its warnings. Have the bookkeeper review every proposed entry. Pay particular attention to invoices reported as clean matches. An obvious error is easy to spot; an incorrect result presented with confidence is harder to catch.

Write down the boundaries before increasing the workload. Specify which folders and accounting records the agent may access, which checks it must perform and which situations require a person. Keep supplier creation, bank-detail changes and payment authority with named people. Set a hard budget cap for the delegation.

For the first assignment, choose one supplier group or one month's invoices. Ask the bookkeeper to compare every draft with its source documents and record any missed discrepancies. Then revise the brief to address those mistakes. Start by giving the agent a batch of invoices to read and match, with instructions to stop whenever supplier details, amounts or supporting documents do not agree.