Professional services team reviewing timesheets and unbilled balances
Services · Unbilled WIP

AI Agents for Unbilled Revenue in Professional Services

Unbilled work ages quietly. By the time anyone reviews it, the client conversation is harder and the write off is larger.

Key Takeaways
  • Unbilled balances are an asset on paper and a negotiation in practice. Age is the best predictor of how much survives.
  • Billing terms differ by engagement, so an aged balance may be perfectly correct or a warning sign, and only the contract tells you which.
  • Fixed fee engagements need a completion view rather than a time view, which most time systems do not produce.
  • Realisation is often measured after write offs, hiding the pattern of which engagements and which managers generate them.
  • ChatFin monitors unbilled balances against engagement terms, flags risk with reasons, and drafts billing proposals and reserves.

In professional services the gap between doing the work and being paid for it runs through a balance almost nobody enjoys reviewing.

Time gets recorded, expenses get charged, and the balance grows until somebody decides to bill it. That decision depends on the engagement terms, the client relationship, and whether the work was within scope, which are three different conversations.

This page covers why unbilled balances age, what makes a balance genuinely at risk, and how a governed agent can keep the position visible while there is still time to do something about it.

Professional ServicesUnbilled WIPRealisationEngagement LettersReservesBilling
Diagram of an AI agent layer running unbilled revenue management above the ERP
The agent sits above your ERP. the ERP stays where it is.
01

Why the balance ages

Some ageing is contractual. Milestone billing and completion based engagements are supposed to accumulate before they invoice, and treating that as a problem creates noise.

The rest is avoidable: work done outside scope that nobody wants to raise, time recorded against the wrong engagement, and balances waiting on a manager review that never gets scheduled.

Scope questions: Work performed beyond the engagement letter, where billing requires a client conversation somebody is avoiding.
Coding errors: Time posted to the wrong engagement or phase, which surfaces only when the balance looks wrong.
Review bottlenecks: Balances waiting on a partner or manager who has not had time to look at them.
02

Fixed fee needs a different view

On a time and materials engagement, unbilled time is a billing question. On a fixed fee engagement, unbilled time is a margin question, and the two need different reports.

For fixed fee work the useful number is effort against the fee, compared to progress against the deliverable. A time system alone cannot produce that, because it does not know what proportion of the work is done.

Bringing the engagement letter into the analysis is what makes the distinction possible, since the terms determine which view applies.

A finance team working on unbilled revenue management
Age is the best predictor of how much of an unbilled balance survives. Photo by Alena Darmel via Pexels
03

Time is recorded, terms are not

Hours and expenses land in the practice management system, and the engagement letter that decides when they can be billed sits in a folder. Without those terms an ageing report treats a contractual milestone balance and a stalled one identically.

Read

What the agent needs to see

Ledger detail from the ERP, plus engagement letters and contracts taken from the source they arrive in, read through the API surface your ERP already exposes rather than the database.

Write

What it should be allowed to do

Prepare a billing proposal and a WIP reserve entry and leave it for the finance director to approve. Reading widely and writing narrowly is the line that keeps this safe.

That division matters more than which model sits underneath. An agent that can read engagement letters and contracts, time and expense detail and billing history while posting only through the validated path a person uses gives you the coverage without handing over the ledger, and ChatFin works that way on every ERP it connects to.

04

What the agent watches

The agent reads the engagement terms, applies the right view per engagement, and monitors the balance against its expected billing pattern.

It flags balances that are ageing beyond their terms, with a reason where one can be determined, and prepares the billing proposal so the review is a decision rather than an assembly job.

Read the engagement terms

Fee structure, billing triggers, scope description, rate card and any cap or retainer.

Apply the right view

Billing readiness for time based work, effort against fee for fixed fee work.

Flag balances at risk

Age against expected billing pattern, scope questions and coding anomalies, each with a reason.

Draft the proposal

Prepare the invoice detail or the reserve entry, with the time and expense support attached.

Governed agent actions compared with unattended automation for unbilled revenue management
Prepared and approved, not posted blind.
05

Making realisation honest

Realisation measured after write offs flatters everybody. Measured before, it shows which engagements were priced wrong and which were run wrong, and those are different problems.

Keeping the write off attached to its cause and its engagement is what makes the next scoping conversation better.

Agent

Visibility and preparation

Balance ageing against terms, reasons where determinable, billing proposals and reserve drafts.

Human

The client conversation

Scope discussions, relationship judgment, and the decision to write off or pursue.

06

The client conversation stays yours

Whether to bill, write down or absorb unbilled work is a relationship decision with commercial consequences. ChatFin prepares the billing detail or the reserve with the time and expense support attached, and the engagement leader decides what actually goes to the client.

The record kept against unbilled WIP is deliberately plain: the engagement letters and contracts the agent read, the reasoning it applied, the draft it produced, what the finance director changed, and the moment it posted. That is the trail an auditor asks for, and it is assembled while the work happens rather than reconstructed afterwards.

The wider argument for that design sits in why finance AI should read widely but write narrowly and connecting without database credentials.


A is prepared, reviewed and approved before it posts, and every step is logged from the source document to the entry. billing proposal and a WIP reserve entry
07

How ChatFin watches unbilled work

Engagement terms determine which view applies, so time and materials balances are judged on billing readiness and fixed fee work on effort against fee. Balances ageing past their own billing trigger are flagged with a reason rather than listed by age alone.

It connects to the ERP, the professional services automation system and the time and expense system through the interfaces those systems already expose, which keeps the security review short and the setup measured in days rather than quarters.

Read the engagement terms

Fee structure, billing triggers, scope, rate card and any cap or retainer.

Apply the right view

Billing readiness for time and materials, effort against fee for fixed fee engagements.

Flag balances at risk

Age against expected billing pattern, scope questions and coding anomalies with reasons.

Draft billing or reserve

Invoice detail or reserve entry prepared with the underlying time and expenses attached.

A first run is usually read only against a period you have already closed, so you can compare what the agent found against what your team found before anything is trusted with a billing proposal and a WIP reserve entry.

The connection is built once. Whether you run NetSuite, SAP Business One, Acumatica or another supported system, the next agent reuses it and the same approval step.

"

On time and materials, unbilled work is a billing question. On fixed fee, it is a margin question.

ChatFin
The wider set of ChatFin finance agents that run on the same connection
One connection, one approval pattern, many workflows.

Frequently Asked Questions

How does it tell a normal milestone balance from a problem balance?

By reading the engagement terms. A balance accumulating toward a contractual milestone is expected and is not flagged. A balance ageing past its billing trigger is, and that distinction removes most of the noise from an ageing report.

Can it identify out of scope work?

It can flag work that does not correspond to the activities described in the engagement letter, which is usually enough to prompt the right conversation. The scope judgment itself stays with the engagement leader.

Does it raise invoices?

It prepares the billing detail with the supporting time and expenses attached. Approval and client communication remain with your team, and the invoice posts through the normal path once approved.

See it while it is still billable

Watch unbilled balances against the terms that govern them.

ChatFin reads your engagement letters, applies the right view to each engagement, and flags balances ageing beyond their expected billing pattern with a reason attached.

Billing proposals and reserve entries are drafted for review, so the monthly conversation is about decisions rather than assembly.

Book a Demo
See it on your own data

See your unbilled balances tested against engagement terms.

Bring a set of engagement letters and the related unbilled detail. We will show which balances are ageing beyond their terms and why, with billing proposals drafted.

✓Runs on the ERP you already have, on your current version, with no database credentials
✓Reads through the governed API surface your ERP already exposes and writes back only approved drafts
✓Full audit trail from prompt to prepared payload on every action
Schedule a Demo
Confidential & private
Hero photograph by Gustavo Fring, free to use under the Pexels License (commercial use permitted, attribution not required). Inline photograph by Alena Darmel under the same licence. Product visuals © ChatFin.