01
Money arrives sooner
Collections slip because chasing is manual and nobody owns it end to end. Agents run the follow-up on schedule, which shortens the gap between invoicing and payment without anyone having to remember.
14 Billing AI Agents, Live in Production.
14 live billing agents across 7 processes — invoicing, collections, disputes and refunds.
-
Debit Memo Verification
Check a debit memo against the invoice it references — totals, lines and reason — and list every mismatch before it reaches the ledger.
-
Discount Verification
Pull every discount off an invoice or quote and test each one against the discount policy and the customer's entitlement, before unapproved pricing reaches the customer.
-
Invoice Adjustment Request
Read a customer's request to change an invoice, test it against billing policy, and prepare the reply the decision implies. Nothing is sent.
-
Invoice Generation
Turn billable lines into a draft invoice with terms, tax treatment and totals applied, then check it before Billing issues it.
-
Overdue Invoice Alerts
Bucket the receivables ledger by age, rank what needs attention this week, and prepare the internal alert for the AR owner. Nothing goes to customers.
-
Payment Status Update
Match incoming payments to open invoices, work out the resulting status for each one, and produce the ledger updates for review.
-
Surcharge Management
Work out the card surcharge due on each payment under your published rate, exclude what is not eligible, and show the recovery before anything is billed.
-
Dunning Management
Place every overdue account at the right stage of the dunning sequence, set the next action and date, and hand the escalations to a person. No customer contact is drafted here.
-
Overdue Invoice Chasers
Draft a collection note for each overdue invoice, pitched to how late it is. Every draft is approved individually — nothing is sent.
-
Credit Memo Application
Decide which open credit memo settles which invoice, respecting age and reason codes, and lay out the application plan with the residual balances.
-
Customer Credit Monitoring
Review every credit account against its limit and payment behaviour, rank the ones drifting toward trouble, and prepare the credit watch list.
-
Data Privacy Compliance
Classify the personal data in a billing extract, apply the retention rules to each class, and recommend what to keep, archive or destroy — with the reason on record. Recommendations only; nothing is deleted.
-
Chargeback Handling
Read the chargeback, weigh the evidence against the reason code, and draft the representment for the acquirer — or say plainly that the loss should be accepted.
-
Refund Validation
Test a refund request against the original transaction and the refund policy, then prepare the reply the decision implies. Nothing is refunded and nothing is sent.
Billing AI Agents: Getting the Invoice Right Before the Customer Sees It
Billing errors are unusually expensive relative to their size. An invoice with the wrong discount, the wrong tax treatment or a line the customer did not agree to does not just get corrected — it stops the payment, opens a dispute, consumes time on both sides, and costs a measure of trust that survives the credit note. And the error is almost always preventable at the point of issue, because the information needed to catch it was already present: the discount policy, the customer’s entitlement, the original transaction, the reason code. What is missing is a step that checks against them before the document goes out.
The other half of billing is collections, and it is where automation most often goes wrong. Chasing money is a relationship activity dressed as an administrative one. A dunning sequence that escalates on a schedule with no human reading the account will eventually send a firm demand to a customer who is disputing the invoice for a good reason, or to one whose payment crossed in the post. So the agents below split the two deliberately: the sequencing, staging and prioritisation are automated, and every message to a customer is drafted and approved individually. Nothing here refunds, deletes, or contacts anyone on its own — the privacy agent recommends what to destroy and destroys nothing, the refund agent prepares the reply and refunds nothing.
Invoice Management
Testing every discount against policy before it reaches the customer
What this moves
- Unapproved pricing reaching an invoice
- Each discount is pulled off the document and tested against the discount policy and the customer's entitlement before issue.
- Invoices disputed on a preventable error
- Terms, tax treatment and totals are applied and then checked before Billing issues the document, which is the last free opportunity to catch a mistake.
- Debit memos posted with a mismatch
- Totals, lines and reason are checked against the invoice referenced, and every mismatch is listed before it reaches the ledger.
Accounts Receivable
Ranking what needs attention this week, without contacting anyone
What this moves
- Collection effort aimed at the right accounts
- The ledger is bucketed by age and ranked by what needs attention this week, so effort follows recoverability rather than the order of a report.
- Ledger status matching received payments
- Incoming payments are matched to open invoices and the resulting status produced for review, so the ageing reflects money actually received.
- Surcharges billed without eligibility checked
- The card surcharge due under your published rate is calculated with ineligible items excluded, and the recovery shown before anything is billed.
Collections
Automating the sequence, approving every message individually
What this moves
- Accounts at the correct dunning stage
- Every overdue account is placed at the right stage with a next action and date, so the sequence advances by rule rather than by whoever had time.
- Firm demands sent to the wrong account
- Collection notes are drafted and approved one at a time, so a customer with a legitimate dispute or a payment in transit does not receive an escalation.
- Escalations reaching a person
- The accounts that need judgement are handed to someone rather than escalated automatically to the next template.
Credit Management
Applying credit memos by age and reason, not by whatever clears fastest
What this moves
- Credit memos applied against the right invoice
- Application respects age and reason codes, so a credit raised for one issue does not silently settle an unrelated invoice.
- Accounts drifting toward trouble
- Every credit account is reviewed against its limit and payment behaviour and ranked, producing a watch list before the limit is breached.
Compliance Management
Recommending what to keep, archive or destroy, and deleting nothing
What this moves
- Billing data held past its retention period
- Personal data in an extract is classified and the retention rules applied per class, so over-retention is identified rather than assumed away.
- Retention decisions with a recorded reason
- Each recommendation carries the reason on record, which is what makes a retention decision defensible if it is ever questioned.
Dispute Management
Saying plainly when the loss should be accepted
What this moves
- Representments built against the actual reason code
- Evidence is weighed against the specific reason code cited, which is what determines whether a representment can succeed at all.
- Effort spent contesting unwinnable chargebacks
- Where the loss should be accepted, that is stated plainly rather than producing a submission that will fail.
Refund Processing
Testing the request against the original transaction, refunding nothing
What this moves
- Refunds issued outside policy
- The request is tested against the original transaction and the refund policy before any decision, so an out-of-policy refund is a knowing exception rather than an oversight.
- Time to a decision the customer can be told
- The reply the decision implies is prepared alongside the assessment, so the response does not wait for someone to draft it separately.
What this changes
What billing agents do for the business
In plain terms, without the engineering detail. The individual agent pages carry the technical specifics.
02
Disputes stop ageing in an inbox
Each dispute is assembled into a case with the invoice, the history and the likely cause already set out, then routed to whoever can decide. The delay in these is almost always gathering, not deciding.
03
Nothing touches a balance unapproved
Refunds and credits are prepared and evidenced, and a person releases them. The agent makes the decision fast; it does not make the decision.
- Collections follow-up, without reminders
- On schedule
- Disputes arrive as cases, not as emails
- Prepared
- Releases every credit and refund
- Human
Where to start
Start with collections follow-up. It is entirely internal until a message goes out, the sequence is already defined in your policy, and the effect lands directly in your ageing report.
Next Step
Deploying billing agents into your stack
These run as-is, and most engagements adapt one to the way your process actually works — different source systems, different tolerances, a different approval path. The first call establishes which base agent fits and what has to change.