Explore the build library
consultance.ai
Deal Copilot
Build libraryControlsAboutCase studiesBlogBook an audit
consultance.ai

Systems

WorkflowsDeal CopilotPrivate knowledgeFinance automationBuild library

Company

About usCase studiesBlogContact

Start a conversation

Free AI auditfounder@consultance.ai

Teams

Investment bankingCFOs & financePrivate equityPrivate creditReal estateProperty managementProfessional servicesOther industriesAll industries

Legal

Privacy policyTerms of service

Our approach

Audit the workflow.Build in your environment.Hand over a system you own.
Build something useful © 2026 consultance.ai
Build library/Portfolio Company Reporting Kit

Finance and data

Portfolio Company Reporting Kit

For PE firms to hand to every portfolio company: the monthly package for the sponsor, with management accounts, KPIs, covenants from the credit agreement and 13 week cash, tied before it is sent.

Medium setup4 steps13 prompts
Open the setup guide Discuss an implementation
Finance and data

Start with the guided setup

Follow the setup below in your own workspace. For a demonstration of the prompt-copying process, open the optional walkthrough.

Watch the setup walkthrough
Step 1 · setup
Three minutes, four steps, nothing to install by hand

Claude sets it up for you. You just paste.

Never used Claude? It is free and takes 30 seconds to open. Copy the instruction below, paste it into Claude, and it reads this page and walks you through everything, one question at a time.

  1. Tell Claude how to talk to you

    One tap. It changes how much Claude explains, and how slowly it goes. You can change it any time.

  2. Copy your setup instruction

    A short instruction plus a link to this page lands on your clipboard. First copy asks for your email once. That unlocks every button across the whole library.

  3. Open Claude in a new tab

    Free account, no card, 30 seconds. This tab stays open so you can come back.

    Open claude.ai
  4. Paste, send, and answer one question

    Claude reads this page, asks one question about your work, then guides you step by step until your first output is right. If anything looks wrong, tell Claude what you see, and it fixes it with you.

▸Prefer the full prompt instead of the link? (optional)
Click to copy
I am comfortable copy-pasting and following instructions, but I am not a developer.
There is nothing to install for this one and no commands to type: it all happens inside Claude. If any instruction below implies a Terminal, translate it into the equivalent click path for me instead.
- Plain English. Define jargon the first time it appears.
- One step at a time, then wait for me to confirm before the next one.
- Tell me what success looks like at each step, and diagnose any error before moving on.

Follow the instructions below with those rules applied.

If you can browse the web, open and read this page in full first, it has the complete guide and every prompt you will run (the vault is under the-vault anchor): https://consultance.ai/library/portco-reporting-kit#the-vault . If you cannot open links, tell me and I will paste the page in, do not guess the prompts.

You are the setup concierge for the Portfolio Company Reporting Kit from consultance.ai. Your job is to get one portfolio company CFO from "my PE owner wants the monthly package" to a tied package ready to send, calmly, one step at a time.

House rules for you:
- Ask ONE question in your first message. Nothing else.
- Define a term the first time you use it. The sponsor is the PE firm that owns the company. A covenant is a test in the loan agreement, such as debt no more than 4.25 times EBITDA. Headroom is how far the company is from failing that test.
- One step at a time. Wait for them to say it worked before the next step.
- Select Claude Opus 5.5 in the model picker for every unit.
- Nothing is sent to the PE firm by this pack. The CFO sends the package.

First message, exactly this and nothing more:

"Which of these do you have for this month: the trial balance, the bank and loan statements, the credit agreement, and your PE owner's reporting template?"

Then route on the answer:

If THEY HAVE ALL FOUR:
1. A few files: a private Project in the Claude app. A folder of exports every month: Claude Code opened in that folder.
2. Paste prompt 01 and answer its questions. Then run prompt 02, the fake sample. If it reports 3.70x or AMBER for Kestrel Components, stop and find out why: the right answer is 3.92x, RED.
3. Run unit 04 once to map the books to the template, then units 05 to 13 for the month.

If THE CREDIT AGREEMENT IS MISSING: say plainly that covenants cannot be computed without it, run everything else, and mark the covenant section OPEN with the document named.

If THE TEMPLATE IS MISSING: map to a standard P&L, balance sheet and cash flow, label it ASSUMED, and ask the PE owner for their template.

Know these facts and say them when they matter:
- Covenant EBITDA follows the credit agreement, not the management adjusted EBITDA in the board deck. Add-back caps often make it lower.
- The proof check, unit 12, recomputes the covenant, cash and LTM figures from the documents and blocks the package on any difference.
- Use Team or Enterprise, or turn model training off, before adding the company's real books.
Step 2 · run it on your data

Step 1 set it up. These 13 prompts do the work.

the vault

The 13 prompts

Grab the whole pack as one file, or tap any prompt below to copy it on its own. Placeholders that look like {{THIS}} get swapped for your own numbers — and if you ran Step 1, Claude fills them in for you.

One .md file · all 13 prompts, numbered, in order · nothing left out.
Click to copy
PORTFOLIO COMPANY REPORTING KIT: SHARED RULES
Every unit in this pack follows these rules. They are written here once.

1. WHERE TO RUN IT
- One month's trial balance and a few files: the Claude app, in a private Project.
- A folder of exports (ledger, bank statements, CRM, payroll) or the same run every month: Claude Code, opened in that folder, so every output lands as a file.
Model: select Claude Opus 5.5 in the model picker. Use Claude Sonnet 5 only for the first bulk read of a very large ledger export.
Privacy: the company's books go only to its own Claude account, never to us and never to the PE firm through this pack. Use Team or Enterprise, or turn model training off, before you add real numbers.

2. BEFORE THE FIRST RUN
First ask what the CFO is most worried the PE owner will ask about this month, and record it. Then ask, one at a time:
{{COMPANY}} and its fiscal year end. {{MONTH}} the month being reported. {{CURRENCY_UNIT}} for example USD 000s. {{SPONSOR_TEMPLATE}} the PE owner's reporting template and KPI definitions. {{CREDIT_AGREEMENT}} the credit agreement with its definitions. {{DEADLINE}} the business day the package is due. {{VARIANCE_RULE}} when a variance needs commentary (default: over 5% and over 250 in {{CURRENCY_UNIT}}). The named CFO who signs the package.
A missing item gets a plain default, labelled ASSUMED.

3. STOP RATHER THAN GUESS
- A folder path pasted into the Claude app: this is a Claude Code job. Say so and stop.
- A figure needs a document you do not have (the credit agreement, a bank statement, a KPI export): ask once, name it, mark it OPEN.
- The sponsor's definition and the company's definition of a KPI differ: use the sponsor's and show the difference.
A stop blocks only the outputs that need the missing input. Everything else still runs.

4. LABELS ON EVERY FIGURE
REPORTED (the ledger, statement or export, with the account or page) · CALCULATED (show the arithmetic) · ASSUMED (who set it) · MARKETING (a claim with no document behind it, such as an unrealised synergy: it makes a question, never a number in a covenant) · NOT IN SOURCE.

5. THREE FLAG TAGS
- CHANGES THE DECISION: a covenant moves to RED, liquidity falls below the floor, or a figure in the package does not tie. It goes on page one.
- WORTH A QUESTION: a variance or KPI move over {{VARIANCE_RULE}} with no evidence yet.
- EXPLAINED BY CONTEXT: one line under "Checked, normal". Once closed, it stays closed.

6. LOOKS WRONG, IS NORMAL
- Revenue under budget because a shipment moved into next month | timing | not normal without the delivery note or invoice dated next month.
- A seasonal month far from the yearly average | seasonality | not normal when last year's same month was different.
- Budget phasing that does not match real seasonality | the budget was spread evenly | not normal when the full year is also off.
- A one-off cost the board already approved | approved | not normal without the approval in minutes or email.
- FX moving a foreign subsidiary's figures | translation | not normal when the local currency figures also moved.
- Management EBITDA higher than covenant EBITDA | add-back caps in the credit agreement | not normal when the agreement has no caps.
- Covenant tracked monthly, tested quarterly | early warning | not normal when a quarter end figure differs from the tracked one.

7. STANCE
A neutral finance colleague who has sent many sponsor packages. Do not dress up the month. The PE owner trusts a package that shows the bad news first and ties to the books.

8. HANDOFF (every unit ends with this)
Read (and not read) · Outputs · Checks: pass, fail or not run · Open items, with the document needed · Next unit · Sign-off needed from the named CFO.
Click to copy
TRY THIS FIRST: A 5 MINUTE TEST ON FAKE DATA
Run units 06, 08 and 12 on this sample in chat; inputs from units not in this test are given directly below, and steps with no data here are NOT RUN. Compare your result to the answer key. If one figure does not match, stop and find out why first. One document is missing on purpose, so you see the pack stop instead of guess.

SAMPLE: Kestrel Components, fiscal year ends 31 December, October 2026, USD 000s. VARIANCE_RULE over 5% of budget and over 250.

A. Management accounts (ledger export, page 1): October revenue actual 7,850.00, budget 8,400.00. Order SO-1182 for 600.00 was in the October budget and shipped on 3 November; its delivery note dated 3 November is in the folder.

B. LTM to October (ledger export, page 2): reported EBITDA 9,600.00. Management add-backs: restructuring 900.00, sponsor monitoring fees 300.00, run-rate synergies 900.00 (from the board-approved synergy plan, all expected within 12 months). Management "adjusted EBITDA" in last month's board deck: 11,700.00.

C. Credit agreement (section 1.1 and 7.1): Consolidated EBITDA = EBITDA plus restructuring costs, sponsor fees and run-rate synergies expected within 12 months, but all add-backs together may not exceed 15% of EBITDA before add-backs. Total net debt = term loans + revolver drawn + finance leases - unrestricted cash. Maximum total net leverage 4.25x, tested quarterly.

D. Balances at 31 October (lender statement and bank statement, page 1): term loan 42,000.00, revolver drawn 3,000.00, finance leases 1,200.00, unrestricted cash 2,900.00.

E. The sponsor template asks for backlog and customer churn from the CRM. The CRM export is not in the folder.

ANSWER KEY
| Check | Expected | Working |
| Revenue variance | -550.00, -6.5%, EXPLAINED BY CONTEXT (timing) | 7,850.00 - 8,400.00. Over both thresholds, but the 600.00 order shipped 3 November with a dated delivery note. |
| Add-backs allowed | 1,440.00, not 2,100.00 | Cap 15% x 9,600.00 = 1,440.00. Claimed 2,100.00 is over the cap. |
| Covenant EBITDA | 11,040.00 | 9,600.00 + 1,440.00. Not the 11,700.00 management figure. |
| Total net debt | 43,300.00 | 42,000.00 + 3,000.00 + 1,200.00 - 2,900.00 |
| Net leverage | 3.92x, headroom 7.7%, RED | 43,300.00 / 11,040.00 = 3.92x. 1 - 3.92 / 4.25 = 7.7%. EBITDA could fall only 851.76 before a breach (11,040.00 - 43,300.00 / 4.25). |
| The trap | Reject 3.70x, 12.9%, AMBER | That uses the 11,700.00 management EBITDA. Leaving out the leases gives 3.81x, 10.3%, the second trap. |
| Tag | CHANGES THE DECISION, page one | Headroom under 10% before the quarter end test. |
| Backlog and churn | OPEN: ask for the CRM export | Blocks the KPI lines only. Every check above still runs. |

A run that reports 3.70x or AMBER, flags the revenue miss as a problem, or fills in backlog or churn, has failed.
Click to copy
<unit name="tools-setup">
Follow the shared rules in prompt 01.
What it does: suggests tools for the jobs in this pack, then installs only the ones the CFO approves, on the company's own accounts.
Use when: after prompt 02 passes, before the first real month. Skip it if exports are enough, which is the normal case.
Needs: the "Needs" lines of every unit in this pack, and the systems the company already uses: the accounting system, the bank, the CRM, payroll.
Method:
1. See what is already connected. In Claude Code, run `claude mcp list`. In the Claude app, look up the current steps in Anthropic's own help pages with your web search, then ask what the company's Claude already shows as connected.
2. For each need, search the web yourself for an MCP server or connector published by the vendor the company already uses, or listed by Anthropic. Prefer: official publisher, read-only access, sign-in by OAuth, updated in the last 6 months.
3. Show one table: need · tool · publisher · official page URL · read only or read and write · how far it reaches · what it costs on the company's own plan (write "not stated" if the page does not say) · last update (write "no date shown" if none).
4. For each tool the CFO approves, open its official page and follow its own steps. A server with a command or URL: copy the command word for word, never from memory. In Claude Code the shape is `claude mcp add --transport http <name> <url>` for a remote server. A connector added in the Claude app: give the steps from the official help page. A page with no command or steps: mark it ASK VENDOR.
5. Install one at a time. Make one small read-only test call and compare it to the system's own screen.
Rules: use only the company's accounts and credits. Never ask for a key in chat. Start every tool read-only. Never connect anything that can post to the ledger or move money.
<trap>Giving the PE owner's team access to the company's Claude or systems through a connector. The package is sent; the books stay with the company.</trap>
Stop: no official page means do not install it. Mark that need EXPORT and carry on.
Output: the table, what was installed, each test result, and the handoff. Next: sponsor-template-map.
</unit>
Click to copy
<unit name="sponsor-template-map">
Follow the shared rules in prompt 01.
What it does: maps every trial balance account and KPI source to the PE owner's template and definitions, once, so every month uses the same map.
Use when: first, then only when the chart of accounts or the template changes.
Needs: {{SPONSOR_TEMPLATE}} with its KPI definitions, the trial balance with account names, and the KPI source exports.
Method:
1. List every line in the sponsor template and its definition, word for word.
2. Map each trial balance account to one template line. Every account maps exactly once; the mapped total equals the trial balance total.
3. For each KPI, name the source system, the export, and the calculation the sponsor defines.
4. Where the company's own definition differs from the sponsor's, write both and the difference.
5. Save the map as one file the company keeps.
<trap>Mapping an account by its name. "Other income" in the ledger may be a reclassified cost credit. Check the account's postings before mapping it.</trap>
Stop: no sponsor template: map to a standard P&L, balance sheet and cash flow, label it ASSUMED, and ask for the template by name.
Output: the map, unmapped accounts, definition differences, then the handoff. Next: monthly-close-check.
</unit>
Click to copy
<unit name="monthly-close-check">
Follow the shared rules in prompt 01.
What it does: proves the month's books are closed and tied before anything goes into the package.
Use when: every month, first.
Needs: the final trial balance, bank statements for every account, the bank reconciliations, and the debt statements.
Method:
1. The trial balance nets to zero and matches the ledger.
2. The balance sheet balances.
3. Every cash account in the ledger ties to its bank statement, after reconciling items. List any reconciling item older than 30 days.
4. Every debt balance ties to the lender or agent statement.
5. LTM equals the sum of the last 12 actual months, never budget months.
<trap>Calling the books closed while the bank reconciliation still has unexplained items. Every later number inherits them.</trap>
Stop: a bank or lender statement missing: that balance is OPEN and the package says so on page one.
Output: the close checklist with pass, fail or open, then the handoff. Next: management-accounts.
</unit>
Click to copy
<unit name="management-accounts">
Follow the shared rules in prompt 01.
What it does: builds the P&L, balance sheet and cash flow in the sponsor's template, with actual against budget and prior year, and the commentary.
Use when: every month, after the close check.
Needs: the map from unit 04, the tied trial balance, the budget, last year's same month.
Method:
1. Month, year to date and LTM, in {{CURRENCY_UNIT}}, through the map.
2. Variance against budget and prior year for every line.
3. For each variance over {{VARIANCE_RULE}}, one line of cause with the evidence, tested against the normal list. A cause with no evidence is WORTH A QUESTION.
4. The cash flow ties: opening cash + cash flow = closing cash in the balance sheet.
<trap>Writing "timing" with no document. Timing needs a dated invoice, delivery note or contract showing the next month.</trap>
Stop: no budget: show actual against prior year only, and say so.
Output: the three statements, the variance table, the commentary, then the handoff. Next: kpi-pack.
</unit>
Click to copy
<unit name="kpi-pack">
Follow the shared rules in prompt 01.
What it does: computes every KPI the sponsor asks for, exactly as the sponsor defines it.
Use when: every month.
Needs: the KPI definitions from unit 04 and the source exports (CRM, operations, payroll, AR and AP ageing).
Method:
1. Compute each KPI from its source with the sponsor's formula. Show the arithmetic.
2. Show the trend for 13 months.
3. A KPI that moved over {{VARIANCE_RULE}} gets one line of cause.
4. Any change to a definition since last month is listed at the top.
<trap>Quietly changing a definition, like counting churn by customers one month and by revenue the next. The trend line breaks and nobody notices.</trap>
Stop: a source export missing: that KPI is OPEN with the export named. The others still run.
Output: the KPI table with trends, causes, definition changes, then the handoff. Next: covenant-compliance.
</unit>
Click to copy
<unit name="covenant-compliance">
Follow the shared rules in prompt 01.
What it does: computes every financial covenant exactly as the credit agreement defines it, with headroom, and prepares the compliance certificate inputs.
Use when: every month as tracking, and at each test date.
Needs: {{CREDIT_AGREEMENT}} (definitions, covenants, add-back rules and caps, cure rights), the LTM figures from unit 06, and the debt and cash balances from unit 05.
Method:
1. Quote each definition with its section: consolidated EBITDA, permitted add-backs and their caps, total net debt, and each ratio.
2. Build covenant EBITDA: EBITDA + each permitted add-back, then apply the cap. An add-back the agreement does not permit is MARKETING.
3. Build net debt exactly as defined: every debt type the agreement counts, minus only the cash it allows.
4. Each ratio, the limit, the headroom (1 - ratio / limit for a maximum), and how far covenant EBITDA could fall before a breach.
5. Flag: headroom over 20% GREEN, 10% to 20% AMBER, under 10% RED and CHANGES THE DECISION.
6. Recompute every ratio a second time from the components before stating it.
A synergy counts only if the agreement permits it and a document supports it (a board-approved plan); without the document it is MARKETING and stays out.
<trap>Using management adjusted EBITDA. Add-back caps in the agreement usually make covenant EBITDA lower, and a RED covenant shows as AMBER.</trap>
Stop: no credit agreement: every covenant is OPEN. Nothing is computed from last month's deck.
Output: the covenant table with the working, certificate inputs on test dates, then the handoff. Next: thirteen-week-cash.
</unit>
Click to copy
<unit name="thirteen-week-cash">
Follow the shared rules in prompt 01.
What it does: rolls 13 weeks of cash from the tied bank balance and shows liquidity against the floor.
Use when: every month for the package, weekly if liquidity is tight.
Needs: tied cash from unit 05, AR and AP ageing, payroll and tax dates, debt service from the agreement, committed capex, and the revolver availability.
Method:
1. Week 1 opening equals tied cash at month end.
2. Inflows by week, each CONFIRMED or ESTIMATED with the basis. Outflows by week, each COMMITTED or DISCRETIONARY.
3. Closing by week, liquidity = cash + undrawn revolver available under the agreement.
4. Flag the first week liquidity falls below the floor the CFO set.
<trap>Counting the undrawn revolver as available when the covenant is RED. A lender may block a draw if a breach is coming.</trap>
Stop: no AR ageing: inflows are ESTIMATED from last quarter's collections, and the package says so.
Output: the 13 week table, the liquidity line, then the handoff. Next: value-creation-tracker.
</unit>
Click to copy
<unit name="value-creation-tracker">
Follow the shared rules in prompt 01.
What it does: tracks each value creation initiative the PE owner agreed with management: owner, status, and EBITDA impact with evidence.
Use when: every month.
Needs: the agreed plan (the 100 day plan or value creation plan), last month's tracker, and evidence for each claimed impact.
Method:
1. One row per initiative: owner, due date, status, EBITDA impact claimed, evidence.
2. An impact counts as REALISED only with evidence in the books (a cost line that fell, a price increase on invoices). Otherwise it is PLANNED.
3. Late initiatives first, with the new date and the reason.
<trap>Counting a synergy as realised because a contract was signed. It is realised when it shows in the ledger.</trap>
Stop: no agreed plan: say so and list the initiatives management names, labelled ASSUMED.
Output: the tracker, realised against planned, late items, then the handoff. Next: board-pack.
</unit>
Click to copy
<unit name="board-pack">
Follow the shared rules in prompt 01.
What it does: drafts the board slides from the tied package.
Use when: every month, or before each board meeting.
Needs: the outputs of units 05 to 10.
Method:
1. Page one: the three things the PE owner must know, bad news first, with every CHANGES THE DECISION item.
2. Then: results against budget, KPIs, covenants and liquidity, value creation, asks of the board.
3. Every figure on a slide carries the unit it came from.
<trap>A slide figure typed in by hand that no longer matches the package after a late change. Pull every figure from the package.</trap>
Stop: a unit not run: its slide says NOT RUN and names the missing input.
Output: the slide text and the source line for every figure, then the handoff. Next: proof-check.
</unit>
Click to copy
<unit name="proof-check">
Follow the shared rules in prompt 01.
What it does: recomputes the numbers the PE owner will rely on from the source documents, before reading the package, and blocks it from going out on a break.
Use when: last, every month, before the package goes to the PE owner.
Needs: the trial balance, bank and lender statements, the credit agreement, and the package.
Method:
1. Recompute covenant EBITDA, net debt and each covenant ratio from the documents.
2. Recompute closing cash from the bank statements.
3. Recompute LTM revenue and EBITDA from the 12 actual months.
4. Only then compare with the package and the board slides. Any difference marks the package BLOCK: do not release it until the difference is fixed and the named CFO signs.
<trap>Reading the package first and then "confirming" it. Recompute first, then compare.</trap>
Stop: a document missing: that check is NOT RUN, and the package says so on page one.
Output: the checks with the arithmetic, PASS or BLOCK, then the handoff. Next: send-checklist.
</unit>
Click to copy
<unit name="send-checklist">
Follow the shared rules in prompt 01.
What it does: prepares the package to send and drafts the cover note. It never sends anything.
Use when: after proof-check passes.
Needs: the signed-off package and {{DEADLINE}}.
Method:
1. List every file in the package, in the sponsor template's order.
2. Draft a short cover note: the month, the three page-one points, open items with dates, and the CFO's name.
3. Check the deadline: on time, or late with the reason.
<trap>Sending a package with an OPEN item and no date for when it will close. Every open item gets a date.</trap>
Stop: proof-check not passed: no cover note is drafted.
Output: the file list, the cover note draft, then the handoff. The CFO sends it.
</unit>

From a working build to an operating system.

For PE firms to hand to every portfolio company: the monthly package for the sponsor, with management accounts, KPIs, covenants from the credit agreement and 13 week cash, tied before it is sent.

Path A · free

Run the build independently

The setup rail and every prompt above are free and stay free. The cost is your time, and the risk of wiring it wrong on live data.

Back to the prompts
Path B · done with you

Connect it to your operation

The kit builds one company's package. We wire it for a whole portfolio: each company's accounting system feeding the same template every month, the proof check run before anything is sent, and the packages landing in the fund's monitoring in one format. Reply "wire it" for a 30 minute slot.

Book a build call
data safety

Before you use live numbers

  • • Run last quarter's numbers first. Live data is not a test bed.
  • • Nothing here uploads to us. It runs in your own Claude account, on your own machine.
  • • A named human reviews and signs every output before it reaches a board, lender, or client.
  • • Mask account numbers and names to the minimum the task needs.
the fine print

Straight answers on ownership

Prompt set authored by consultance.ai. Each company's books stay in its own Claude tenant; we never see it, and the pack sends nothing to the PE firm. It builds and checks the package; the company's lawyers and lenders own the reading of the credit agreement, and the named CFO signs. The worked example is synthetic. Not legal, accounting or investment advice.

Bring this workflow into your operation.

Book a build callBack to the library

Want this wired into your stack instead of running it yourself? That is our AI deal desk and finance automation service.

Newsletter

New builds, as they ship

One short note when a new build ships: what it does, who it is for, and how to run it in your own Claude.

Free. Three short welcome emails over your first three days, then at most one email a week. Unsubscribe in one click.

More like this

Related builds

All builds
Finance and data
Finance and data

Accretion Dilution Merger Model

For deal teams and corp dev building the buy-side merger model: 12 prompts that run accretion or dilution, the funding mix, goodwill, synergies, and the breakeven price where the deal stops adding to EPS, in an afternoon instead of a two-week associate build.

Setup guide
Finance and data
Finance and data

Valuation First Pass Pack

For CFOs, boards and corp dev teams: check the DCF against the comps, rebuild comps, precedents and sensitivities, set the offer against every range, and draft the pages a board reads first.

Setup guide
Finance and data
Finance and data

AI Deal Diligence Prompt Pack

For PE deal teams and corp dev: read a data room and draft the IC memo in Claude with 11 prompts. Reads every contract, ties the financials to source, flags concentration and change of control, and reconciles before the memo. Replaces the associate grind and a chunk of the third party diligence engagement.

Setup guide
Get the free kitBook a call

Share with your workflow owner.

Bring the relevant team into the conversation with the build and setup guide.

Forward by email
in one line

What is Portfolio Company Reporting Kit?

Portfolio Company Reporting Kit is a finance and data build in the consultance.ai AI Build Library. For PE firms to hand to every portfolio company: the monthly package for the sponsor, with management accounts, KPIs, covenants from the credit agreement and 13 week cash, tied before it is sent. It fits Portfolio company CFOs and controllers who build the monthly reporting package for their private equity owner, and PE operating partners who want every company to send a tied package on time. Setup difficulty is Medium, with 4 plain-English steps.

What does Portfolio Company Reporting Kit do?

For PE firms to hand to every portfolio company: the monthly package for the sponsor, with management accounts, KPIs, covenants from the credit agreement and 13 week cash, tied before it is sent.

Who is Portfolio Company Reporting Kit for?

It fits Portfolio company CFOs and controllers who build the monthly reporting package for their private equity owner, and PE operating partners who want every company to send a tied package on time.

How hard is Portfolio Company Reporting Kit to set up?

Medium to set up — one guided setup instruction covering 4 plain-English steps, plus 13 ready-to-run prompts on the resource page.

How would consultance.ai build this out?

The kit builds one company's package. We wire it for a whole portfolio: each company's accounting system feeding the same template every month, the proof check run before anything is sent, and the packages landing in the fund's monitoring in one format. Reply "wire it" for a 30 minute slot.

What are the licensing terms?

Prompt set authored by consultance.ai. Each company's books stay in its own Claude tenant; we never see it, and the pack sends nothing to the PE firm. It builds and checks the package; the company's lawyers and lenders own the reading of the credit agreement, and the named CFO signs. The worked example is synthetic. Not legal, accounting or investment advice.

Connect this build to your workflow.

Discuss how Portfolio Company Reporting Kit fits your systems, controls, and team. We define the integration, review process, and deployment requirements with you.

This build comes from our AI consulting and AI implementation practice — see the full AI in finance guide and how we work with CFO teams.

Book an audit