How to raise customer invoices from signed contracts with an AI agent

Bill from the signed contract. The agent reads each signed contract's billing terms, builds a billing schedule, checks triggers such as milestones or usage, and drafts invoices. A person approves the first invoice under every contract and anything non-standard. Recurring invoices can be issued at depth 3 once certified, and credit notes always go to a person.

What does billing from contracts involve, and who owns it?

Billing turns what the customer agreed to pay into invoices on the right dates for the right amounts. Contracts can bill in many ways: fixed recurring fees, milestones, time and materials, usage, minimum commitments, annual price increases tied to an index, discounts in the first year. Each contract's terms must become a schedule, and each invoice must follow it.

The billing or accounts receivable team owns invoicing. Sales owns the customer relationship and often the contract negotiation. The finance controller owns billing policy and credit notes. The weak point is the handover: billing teams often work from an order form or an email summary rather than the signed contract, and errors follow.

Whether an agent should issue customer invoices at all depends on that handover being fixed first. The wider bounds for finance agents are in AI agents for finance.

What are the steps, and at what depth?

1. Agent, depth 1: reads the signed contract. Only the executed version, with all amendments. A signed source is one a named party answers for, and that is the standard for billing terms. Drafts, quotes and emails are not.
2. Agent, depth 2: builds the billing schedule. Dates, amounts, currency, tax treatment, billing contact, payment terms, purchase order requirements and any price change rules.
3. Person, billing lead: approves the schedule. Once per contract and after every amendment. Evidence: approval on the schedule version.
4. Agent, depth 1: checks triggers. For milestones, that acceptance was recorded by the right person; for usage, that the usage data is final for the period; for time and materials, that timesheets are approved.
5. Agent, depth 2: drafts invoices. In the billing system, with the contract and schedule reference, the customer's purchase order number where required, and the correct tax.
6. Person, billing lead: approves the first invoice under each contract. And any invoice that differs from the schedule.
7. Agent, depth 3 once certified: issues recurring invoices. Fixed fees exactly matching an approved schedule, to the billing contact on the contract.
8. Person, finance controller: approves all credit notes. The agent drafts them with the reason.

What stays with a person, and why?

The first invoice under a contract is where misreadings show up, so a person checks it. Credit notes reduce revenue and can hide errors or fraud, so a person approves each one. Disputes are relationship matters; the agent informs sales and billing but does not negotiate. And any change to billing terms not supported by a signed amendment stays with a person, however reasonable it sounds in an email from the account manager.

Which controls matter, and what evidence does each leave?

Executed contract only. Evidence: the contract version and signature status on the schedule.

Schedule approval. Evidence: the approved schedule version on each invoice.

Trigger evidence. Milestone acceptance, usage data or approved timesheets attached. Evidence: links on each invoice.

Price change rules applied as written. Index-linked increases use the index and date in the contract. Evidence: the calculation on the invoice record.

Separation from revenue. The agent that issues invoices does not post revenue journals for the same contracts. Evidence: identities on each.

What does billing look like for one contract?

Take an illustrative services contract: a monthly fee of 15,000 billed in advance, an implementation fee of 30,000 split into two milestones, and an annual increase on each anniversary tied to a named price index. The agent builds a schedule with twelve monthly lines, two milestone lines conditional on acceptance by the customer's named project lead, and an increase line on the anniversary date. The billing lead approves the schedule and the first invoice; the monthly fees then issue at depth 3, and each milestone waits for recorded acceptance.

What should you measure?

• Invoices disputed by customers, by cause.
• Credit notes issued, by reason. A cluster points to schedule or contract reading errors.
• Revenue leakage found: contracted charges never billed, such as price increases not applied.
• Days from trigger to invoice.
• First invoices changed at approval.

Where does it usually go wrong?

Billing from the order form. The order form says monthly; the signed contract says quarterly in advance. Always read the executed contract.

Price increases forgotten. Annual increases tied to an index are often never applied. The agent's schedule should include them with the date and the index source, so the increase is billed on time.

Customer purchase order rules ignored. Large customers reject invoices without their purchase order number. The agent should hold invoices where the contract requires a reference that is missing.

Milestones billed before acceptance. The project team says it is done; the customer has not accepted. Bill on the acceptance the contract requires, not on internal sign-off.

Late billing becomes a collections problem. Invoices raised late are paid late. When they do go overdue, chasing overdue customer invoices with an AI agent picks up from the same schedule.