Skip to content

Fund admin · Fund · Quarterly

Data check before LP reporting

Your LP report is built on data that agrees everywhere: books, cap table, calls and marks.

PlanData check before LP reporting

  1. Audit the fund’s records

    Held

    Operator looks for missing fields, stale drafts, problems in the chart of accounts and entries without a category.

    Operator
  2. Cross-check the books

    Held

    Reads the books against the cap table, every capital call against its booking, and the fund’s values against the latest marks.

    API action
  3. List the exceptions

    Held

    Operator lists every exception with its type, its owner and a proposed fix.

    Operator
  4. Set the missing categories

    Held

    Sets the proposed category on each uncategorized entry, all behind one approval.

    API actionper entryAccountant approves all in one go
  5. Link calls to their bookings

    Held

    Links each unbooked capital call to its booking entry. One approval covers them all; a match that is edited comes back on its own.

    API actionper callAccountant approves all in one go
  6. Fix or explain the rest

    Held

    Each remaining exception goes to its owner, with reminders until it is fixed or explained.

    Personper exception
  7. Sign the review

    Held

    The accountant signs the review. You see exception counts by type; the admins see the records.

    PersonAccountant approves

The plan as it runs: each step waits for the one before it, and stops at its gate until the owner approves.

At a glance

Who runs it, and when

Who runs it
Fund admin
What starts it
Each quarter end, after the hard close and before the LP report is drafted.
How often
Quarterly
Vehicle
Fund

Ask Operator

Start it in a sentence

Ask Operator in chat. It drafts the plan for your fund, and nothing runs until you release it.

  • You

    Run the pre-reporting data check on Fund II.

  • You

    Does everything agree before we draft the Q3 report?

  • You

    Find the data problems in the client’s fund.

The outcome

Every exception has an owner and an end state, every call is linked to its booking, and the accountant has signed the review.

What it proves

  • Runs the cross-checks admins otherwise do by hand, on live records.
  • Gives every exception an owner and a proposed fix.
  • Fixes the simple ones in a few grouped approvals; an edited fix comes back on its own.
  • Hands the rest to their owners, with reminders until each is fixed or explained.
  • Shows you counts by type, and the admins every record.

Run it on your fund

Talk to the team about running this playbook on your own fund.