Verity for accounting firms
An accounting practice knows every deadline a year ahead. What it cannot predict is when each client will send the records. Verity makes the chase a tracked, owned process rather than a personal one.
Verity runs the practice. Your accounting and filing software stays where it is.
Verity / Practice
LiveJobs in progress
184
Awaiting client records
61
Deadlines in 30 days
43
Unbilled work
₹24 L
Needs attention
Illustrative figures. Verity shows your own practice in this shape.
How the business runs
Unlike most professional firms, an accounting practice knows its entire year in advance. Every client has a set of recurring obligations with fixed dates, and the total work is calculable months ahead. That should make it the easiest professional business to plan.
It is not, because the work cannot start until the client sends their records, and clients send them late, incompletely, and in a rush at the end. So a firm with a perfectly predictable calendar experiences it as a series of crises, with capacity idle in one month and overwhelmed in the next.
The chase is therefore the practice’s core operational activity, and in most firms it is entirely personal. A junior emails a client, gets nothing, mentions it to a manager, emails again. There is no record of how many times, no visibility of which clients are chronically late, and no way to see that a job with a deadline in three weeks has not started.
The second problem is recovery. Recurring compliance work is usually quoted as a fixed fee against an assumed volume of effort, and when a client’s records are disorganised the actual effort is several times the assumption. Firms know this happens and generally cannot say which clients it happens to, because effort is not recorded against the recurring job.
Verity holds the client, their recurring obligations, the records outstanding, the effort spent and the recovery achieved as one set of records — so both the chase and the capacity plan work from evidence.
What Verity calls these things
What gets in the way
Accounting practice problems come from work that cannot start on time and effort that is never measured against the fee.
The chase for records is personal and untracked
Someone emails a client. Nothing comes. They email again. There is no record of how often, so no one can say which clients are chronically late.
In Verity Outstanding records are items on the job with an owner and an age, so the chase is a worked list and lateness becomes a client attribute.
Jobs with near deadlines have not started
A filing is due in three weeks and the job has not begun, which is only discovered when someone looks at the deadline list.
In Verity Every recurring obligation is a job with a start-by date derived from its deadline, so not-started work surfaces while it is still recoverable.
Recovery on fixed-fee work is unknown
Effort is not recorded against recurring jobs, so a client whose disorganised records consume three times the assumed hours is billed the same as one who does not.
In Verity Effort recorded against the job makes recovery per client measurable, which is the basis for repricing or resigning.
Capacity is planned by feeling
The firm knows the calendar and does not model it, so it discovers overload during the peak rather than three months before.
In Verity Recurring obligations across all clients produce a forward workload against team capacity by period.
Review bottlenecks are invisible
Work sits completed and unreviewed because the reviewing partner is the constraint, and nobody measures the queue.
In Verity Review is a workflow step with an owner and an age, so the bottleneck is measurable rather than felt.
Scope creep is absorbed silently
Additional advice and cleanup work is done inside a compliance fee because it seemed small at the time.
In Verity Out-of-scope work is raised as a variation, so it is either billed or is a recorded decision not to.
The complete system
One system across the calendar, the chase, capacity and recovery.
Work
Every obligation is a job with a client, a deadline, a derived start-by date, an owner, a state and the effort recorded against it.
Why it matters here A practice’s entire workload is knowable in advance, and it only becomes plannable when each obligation is a record rather than a line in a calendar.
In practice Forty-three deadlines inside thirty days with nine jobs not started, ranked by the effort each usually takes.
Records
Each job carries the specific records it needs, their state and their age, with documents attached as they arrive.
Why it matters here The outstanding-records list is the operational heart of an accounting practice and is usually held in an inbox.
In practice Sixty-one jobs awaiting client records, eighteen of them for more than a fortnight, ranked by deadline proximity.
Relationships
Clients are records with their entities, obligations, engagement terms, fee basis, responsiveness history and balances.
Why it matters here The commercially relevant fact about a client is often not their fee but how much effort they cost to serve.
In practice A client whose records arrive an average of nineteen days late, alongside the recovery achieved on their jobs.
Workflows
Deadlines, review steps, partner sign-off and filing confirmation are defined steps with owners and escalation.
Why it matters here A missed statutory deadline is the failure a practice cannot absorb, and review queues are the most common cause of near-misses.
In practice Work completed and waiting on review, aged by reviewer, which is the queue nobody currently measures.
People
The team is modelled once, and every job, review and record request shows who owns it.
Why it matters here Capacity planning is impossible without knowing who is carrying what across a calendar that is already known.
In practice Committed job hours per person by month against the known calendar.
Reports and analytics
Forward workload against capacity, recovery by client and job type, records lateness, review queues and deadline compliance come from the operational records.
Why it matters here The two questions that decide an accounting firm’s year — can we deliver it and are we recovering — are both calculable from the calendar and the effort.
In practice Recovery by client on recurring work, which frequently identifies the clients that should be repriced.
Communication
Requests, reminders and responses attach to the job and client they concern.
Why it matters here A chase with no record is a chase that gets repeated, forgotten or denied.
In practice Three reminders sent on a job, visible to the manager without asking the associate.
Control
One permission model and one audit trail, with fee variations and write-offs as approval steps.
Why it matters here Client financial data requires deliberate access control, and write-offs are where recovery quietly disappears.
In practice A write-off above the manager’s threshold becomes an approval with the recovery position attached.
Verity AI
Verity AI answers from your own job, client, record and effort data, respects permissions, and can create assigned follow-ups.
Why it matters here The questions worth asking cross the calendar, the chase and recovery at once.
In practice "Which jobs with deadlines inside thirty days have not started?" returns nine, with chases and assignments raised.
Locations
Organisational units roll into the firm, with permissions and reporting following the same structure.
Why it matters here Multi-office practices cannot compare recovery or capacity unless work is recorded identically.
In practice Recovery and deadline compliance by service line and office.
Work in motion
The calendar is already known. These make it plannable.
The start-by date is what turns a deadline into something that can be missed early enough to fix.
Recording the chase is what turns chronic lateness from an impression into a client attribute you can act on.
The calendar is known a year ahead. Modelling it is the difference between a plan and a peak.
The review queue is usually the firm’s real constraint and the one nobody measures.
A client recovering at forty percent for four consecutive periods is a commercial decision, not an accident.
Work beginning before an engagement letter is signed becomes a visible exception.
Verity AI
Verity AI reads the same job, client, record and effort data the practice runs on. It answers from your own firm, respects each user’s permissions, and can turn an answer into chases and assignments.
Verity / Ask
Verity AI only returns what the person asking has permission to see.
Without chasing
Each runs from the job and client records at the point the condition is met.
When
A recurring obligation falls due to start
When
Records remain outstanding past threshold
When
Work sits in review beyond its threshold
When
Effort on a job exceeds its expected hours
When
A deadline approaches with work incomplete
When
Work remains unbilled beyond threshold
What you can understand
Capacity, delivery and recovery from the practice’s own records.
Verity holds the practice records. Your accounting, tax and filing software continues to hold the accounting itself.
One system, different ways of seeing it
Everyone works from the same records, and each role opens on what they need.
Partner
Can we deliver the calendar, and are we recovering?
Forward workload against capacity, recovery by client, deadline risk, unbilled ageing.
Manager
What is blocked and what is late?
Jobs not started, records outstanding, review queue, effort against expected hours.
Associate
What do I owe this week?
Assigned jobs by deadline, records received, review points to clear, effort to record.
Practice administrator
Who has not sent what?
Outstanding record requests by client and age, chases due, engagement letters outstanding.
Where it is used
Every client obligation as a job with a deadline and a derived start-by date, so not-started work surfaces while it is still recoverable.
Outstanding items on the job with an owner, an age and a recorded chase history, replacing a personal email thread.
Average lateness and chase count per client, turning chronic non-responsiveness into a fact that can be priced or acted on.
Forward obligations against team capacity by period, so overload is identified months ahead rather than during the peak.
Effort recorded against recurring jobs, so clients consuming several times the assumed hours are identified rather than suspected.
Review as a workflow step aged by reviewer, exposing the constraint that causes most deadline near-misses.
Out-of-scope advice raised as a variation, so it is either billed or is a recorded decision.
Plain-language questions across calendar, chase, capacity and recovery, with follow-ups assigned in the same step.
Getting there
Your accounting, tax and filing software continues to run and is mapped during implementation. Clients, entities, recurring obligations, engagement terms and open jobs are brought across, and Verity is introduced as the practice layer over them.
Implementation runs about four weeks: discovery and mapping, configuration, migration, then an ongoing operations partnership.
Questions
No. Your accounting, tax and filing software continues to do that and is mapped during implementation. Verity runs the practice around it — the obligation calendar, record chasing, job ownership, capacity, review queues, recovery and reporting.
Verity AI answers questions from your own job, client, record and effort data: which jobs with deadlines inside thirty days have not started, which clients have records outstanding beyond two weeks, which clients recover worst on recurring work, what committed workload looks like against capacity next quarter. Each answer can become a chase or an assignment.
Outstanding items sit on the job with an owner and an age, reminders are recorded, and escalation follows the start-by date rather than the deadline. The chase becomes a worked list, and chronic lateness becomes a recorded client attribute.
Because every recurring obligation is a record with a deadline and historical effort, forward workload can be compared against team capacity by period, so overload periods are identified months ahead rather than experienced.
Effort recorded against each recurring job is compared with the agreed fee, so clients whose disorganised records consume several times the assumed hours become identifiable — which is the basis for repricing rather than absorbing.
Review is a workflow step with an owner, so completed work waiting on a reviewer is aged and reported. That queue is usually the practice’s real constraint and the least measured part of it.
Verity has one permission model and one audit trail, so client access is set deliberately by team and every access is recorded.
A three-person practice has the same calendar, the same chasing problem and the same recovery blind spot, with less capacity to absorb any of them.
About four weeks: discovery and mapping of how the practice actually works, configuration of the obligation calendar, migration of clients and open jobs, then an ongoing operations partnership.
Every practice has a list of them and no reliable way to produce it. Tell us how your calendar is tracked today.