Can an AI agent issue customer invoices?

Yes, when the invoice follows from records rather than judgement. If a signed contract sets the price and a delivery or milestone record shows what was supplied, an AI agent can raise and send the invoice at depth 3. A new contract's first invoice, non-standard terms and amounts above a set value are drafted for the billing lead to approve.

What decides whether an invoice needs a person?

Whether every figure on it can be traced to a sealed record. A monthly subscription at a contracted price, a shipment confirmed by a signed delivery note, a milestone marked complete by the customer: each gives the agent a quantity, a price and a date it did not have to decide.

Invoices go wrong when something has to be interpreted. A contract with tiered pricing that resets annually. A project billed on time and materials where some hours are non-chargeable. A customer who agreed a discount by email that never reached the contract. The agent can still prepare these, but a person should check them before they go out. The method for turning contracts into invoices is set out in how to raise customer invoices from signed contracts.

Where is the line between agent and billing lead?

The agent issues at depth 3 when: - the contract is signed and held in the contract repository; - the delivery, usage or milestone record is in the system of record; - the price, tax treatment and billing contact are already approved on the customer record; - the invoice is not the first under this contract; - the amount is within the set value.

The agent drafts and the billing lead approves when: - it is the first invoice under a new contract, so the set-up is checked once; - the contract has non-standard terms: tiered pricing, caps, rebates, milestone acceptance; - the amount is above the set value; - the agent found a mismatch, such as a delivery quantity above the order; - the customer has an open dispute.

Who must not approve?

The salesperson who owns the account. Sales teams paid on invoiced revenue have a reason to bill early or bill more, and a billing lead outside sales is the check on that. The same applies in reverse to credit notes: the person who decides money is owed and the person who decides it is forgiven should not be the account's own salesperson.

An illustrative example

Take an equipment rental firm with about 1,200 active contracts. Each month the agent invoices rental charges from the contract and the asset tracking system.

For most contracts the rental rate, period and customer details are fixed, and the agent issues invoices directly. Three cases are held. One is the first invoice for a new construction customer, so the billing lead checks the set-up. One contract includes a damage clause, and the return inspection lists a cracked panel, so the agent drafts a damage charge of 850 with the inspection photos for the billing lead to approve. The third shows an excavator still on hire though the customer's site manager emailed to say it was collected; the asset tracker disagrees. The agent holds the invoice and asks the depot to confirm the collection date.

Clean invoices also make collection easier. Disputes caused by billing errors are the most common reason invoices go overdue, which is why the rules for chasing overdue customer invoices start with checking the invoice was right.

What controls make it safe?

• Customer master data is not the agent's to change. Prices, tax codes and billing contacts are maintained by people.
• Contract and delivery as sealed sources. An email from a salesperson saying "bill them for the extra work" is declared and does not support a depth 3 invoice.
• First-invoice review. Each new contract's set-up is checked once by a person.
• Value limits. Set by the finance manager per customer segment.
• Sequential numbering preserved. The agent issues through the billing system so numbering, tax fields and records follow the rules your invoicing must meet.
• Every invoice filed with its sources. The contract clause and delivery record sit alongside it.

Where Pryme fits

In Pryme, the Pryme Context Protocol labels the contract and delivery record as sealed and a salesperson's instruction as declared, and the invoicing capability only reaches depth 3 when sealed sources support every line. The rest are held for the billing lead.

Once invoices go out, the step-by-step approach to chasing overdue invoices picks up. The wider controls are in AI agents for finance: books you can audit.