Claude Cowork for Fund Administration: An AI Agent for the Back Office

1. The Back Office Is a Documents Business

The fund back office runs on a calendar. Capital calls go out on a date. The quarterly pack is due a fixed number of days after quarter-end. The audit has a timeline, and K-1s have a deadline that does not move. Miss any of them and an LP notices.

Almost all of that work is documents. A capital-call notice is the LPA terms, the allocation math, and a template, rendered per investor. A reporting pack is a narrative plus a set of schedules in a house format. A reconciliation is two sources tied to each other line by line. The thinking is real, but most of the hours go to assembly, and assembly is exactly what an agent compresses.

That makes the back office close to an ideal case for an agent, with one condition that runs through this whole guide. The work touches money and investor relationships, so every number it produces has to be checked and reconciled to the source before anyone relies on it. An agent that assembles the pack and a person who reconciles and signs is a strong pair. An agent trusted to be right about a figure is a liability.

2. Chat Answers, Cowork Does the Task

There are two ways to use Claude in the back office, and the difference decides whether you get help or a finished deliverable.

Claude Chat answers a question. What does this clause in the LPA mean for the management-fee offset. Explain how a European waterfall sequences. Draft me the wording for a cover note. You ask, it answers, you take it from there. That is the right tool when you have a question, not a task.

Claude Cowork does the task. It is Anthropic's agentic mode, built to take a whole multi-step job end to end on your own files. Point it at the LPA terms, the allocation schedule, and the notice template, and it works through the steps and hands back the drafted notices, ready for a controller to reconcile. It plans, you approve, it proceeds, and you can steer it at any point. The difference between asking how to assemble the quarterly pack and getting the assembled pack back is the difference between Chat and Cowork. Which job belongs to which is laid out in Claude Cowork vs Chat.

For the back office, the agentic mode is the one that pays. The volume work is multi-step and repetitive on a deadline, which is exactly what Cowork is for. The fuller treatment of how the agent works, on a credit book rather than a fund admin desk, is in Claude Cowork for private credit, and the same mechanics apply here.

3. Hand to Cowork, Keep Reconciled and Signed

The whole model fits on one line. The agent assembles and drafts. A person reconciles and signs. Get that split right and the rest is detail.

Notice what is on the right. None of it is the typing. It is the reconciliation, the cash, and the signature, the parts where being wrong has a cost. Hand those to an agent and you have automated the one thing that should never be automated. Keep them with a person and the agent is doing the work that was eating the week.

4. Capital-Call and Distribution Notices

A capital-call notice is a good first job because it is the same shape every time. The LPA sets the terms. The allocation schedule sets each investor's share. The template sets the wording. The work is rendering all three, per investor, without a typo in an account number.

Give Cowork the call amount and purpose, the LPA terms that drive the calculation, the allocation schedule, and the notice template. It drafts the notices, fills the per-investor figures, and produces the set ready for review. It does the same for a distribution notice, working from the waterfall terms instead of the call mechanics. What you get back is a draft, not a sent notice.

Then the part that does not move. A controller reconciles every figure on every notice back to the allocation schedule and the books before a single one goes out. The agent drafted faster than a person could. The reconciliation and the send are still a human decision, because a wrong number on a capital call is the kind of error an LP remembers.

5. Quarterly Reporting Packs

The quarterly pack is the back office job that eats the most time and looks the most like assembly. A narrative, a set of schedules, the portfolio summaries, the capital-account statements, all in a house format that the fund has used for years.

This is what an agent is for. Give Cowork the source numbers, the prior quarter's pack as the format reference, and the portfolio inputs, and it assembles the schedules in your house format and drafts the narrative around them. It puts the pack together in the shape the LPs already expect, so the work becomes review instead of construction. The whole arc of investor reporting, of which the pack is the centerpiece, is in the AI investor reporting guide, and the valuation marks that feed it are their own discipline, covered in AI for portfolio valuation marks.

The discipline is the same as everywhere else here. The agent assembles the pack. A person reconciles every schedule to the source and signs off on the narrative before it reaches an investor. The marks are a judgment the valuation committee owns, not a number an agent decides.

6. Reconciliations, K-1 and Audit Prep Support

Reconciliations, K-1 work, and audit prep are where the back office spends its hardest weeks. They are also heavy on organizing and tying out, which is where an agent helps without ever being the one who concludes.

Reconciliations. Cowork can line up two sources, surface where they differ, and draft the working file that shows the breaks. It does not decide the reconciliation is clean. A person ties out every line and signs it.

K-1 and audit prep support. It organizes the support, assembles the tie-out files the auditor asks for, and drafts the schedules that back each number. It is doing the gathering and the formatting that consume the timeline. It is not preparing the return and it is not the auditor. The fuller picture of where an agent fits across the admin function is in AI for fund administration.

The line holds through all of it. The agent organizes and drafts the support. The fund administrator, the tax preparer, and the auditor still do their work, and a person reconciles and signs. The agent shortens the timeline. It does not own the conclusion.

7. The Governance of an Agent on Investor and Financial Data

Capital accounts, allocation schedules, and investor lists are some of the most sensitive data a fund holds. An agent that touches them has to be set up with that in mind, and the setup is not complicated.

The plan, not a personal account. Investor and financial data belongs on Claude Team or Claude Enterprise, never a personal account. On Team and Enterprise your business data is not used to train public models. That is the data rule, and it is the first thing to settle before anyone points an agent at a capital-account file.

Scope it and read the plan. An agent that works on files gets two controls. Scope it to the reporting folder and the templates it needs, not the whole finance drive. And read the plan it shows you before it runs, so you approve the steps before it touches anything. Plan-approve-steer is the control, and you use it.

For the most sensitive work, Cowork can run inside your own cloud or tenant, so investor data never leaves your perimeter. The broader frame for putting an agent on confidential fund data, and the questions an LP or an examiner will ask about it, sit alongside this in the fund administration guide.

8. Why Not a Calculator Matters Most Here

Every guide about AI agents says verify the output. In the back office that warning is the whole point, not a footnote, because the output is money owed to and from investors.

Cowork is not a calculator. It assembles a notice and drafts a schedule, and the figures in them are checked and reconciled to the source, never trusted. A number that looks right and is wrong is worse than an obvious error, because it ships. So the rule is plain. Every figure ties to the allocation schedule, the books, or the wire before anyone relies on it, and the tie-out is a person's job.

The agent never closes the books. It does not send the wire. It does not sign the notice or make the representation to the auditor. It drafts and assembles, and a person reviews, reconciles, and signs. That line is not a limitation you tolerate. It is the design, and it is what makes an agent safe to run on a fund's most sensitive work.

9. From One Desk to a System

Cowork on one controller's desk is the start. The value compounds when the setup becomes shared instead of personal.

That means shared Claude Projects holding your reporting formats, the LPA terms that drive the calculations, and the notice templates, so every notice and every pack comes out in the same house shape without anyone rebuilding the instructions. It means connecting the agent, through MCP, to the fund accounting system and the document store, so the source numbers and the files are where the work happens. The capital-call run, the quarterly pack, and the audit prep become standing capabilities the back office runs on, not a one-off someone figured out and then forgot.

That is the AI operating system idea applied to the back office: the agent, the house formats, and the data store wired into one place, deployed in your own environment and owned by you.

10. Where to Start

Pick the plan and the data rule this week. Team or Enterprise, scoped to the reporting folder. Then give the agent the next real job: the upcoming capital-call notice, or the next quarterly pack. Let it assemble the draft, and have a controller reconcile every figure to the source before anything leaves the building. One cycle on real work tells you more than any demo.

If you want it built into your reporting rather than tried on the side, an AI Readiness Sprint scopes the first workflow and the data rule around your fund in one to two weeks. The Investor Reporting Engine builds it into the pack and the notices, and an AI Operating Partner runs it with you while your team keeps the reconciliation and the sign-off.

The back office is a documents business on a deadline. An agent is good at documents on a deadline. Point it at the assembly, keep the reconciliation and the signature with your people, and the calendar stops owning the team.