Invoice preparation
Draft an invoice from approved order and delivery records.
Compare amounts, tax treatment and references with the source records. Route missing or conflicting evidence to the billing owner before issue.
There is no single percentage for every enterprise. The Agentic Enterprise (2026) uses a 30/40/30 framing for automation candidates, human and AI collaboration, and human-led work, alongside its study of 2,143,500 tasks across six industries, 60 roles and 11 companies. Use the framing as a planning reference, not a measured deployment rate or a target for your workflow.
From The Agentic Enterprise (2026), co-authored by Giridhar LV, Kashi KS, and Rajan. Available on Amazon Kindle.
Use the categories to examine candidate responsibilities, then test the proposed changes.
Automate / augment / human. Use these categories to discuss a proposed division of work. They do not measure a reduction in workload or headcount.
The study discussed in The Agentic Enterprise (2026) covers 2,143,500 tasks, six industries, 60 occupational roles and 11 companies. Its 30/40/30 framing should not be combined with the wider job-posting catalogue or the separate O*NET occupational analysis. This page does not provide the task-level records needed to reproduce that study.
Read the published study context and classification framework. The book citation above identifies the publication. For a project decision, examine your own records, tools and controls rather than adopting its proportions as a target.
Illustrative design examples. These are proposed responsibilities and checks, not deployed customer results.
Draft an invoice from approved order and delivery records.
Compare amounts, tax treatment and references with the source records. Route missing or conflicting evidence to the billing owner before issue.
Assemble identity-check results and draft a risk memo.
An authorized reviewer resolves screening matches, missing evidence and the onboarding decision. A drafted memo does not authorize an account action.
Propose or execute tests for an agreed user journey.
Compare behavior with executable assertions, known defects and expected permissions. Engineers review missed defects and changes to the tests before accepting a release.
Summarize asset history and propose a work priority.
Qualified owners check inspection evidence, uncertainty, permits and safety controls before authorizing field work.
Within each example, different steps may need different treatment. An agent might prepare a recommendation while a person decides. A rules-based service might execute an approved action. Missing evidence or an unusual case may require a stop and review. Record these distinctions before choosing an automation target.
What the figures can and cannot tell you.