Check every prerequisite before the money moves.

What it does

The agent works through a fixed checklist against every payment on a single capital distribution. Each check can be turned on or off independently, and if a check fails the agent stops right there rather than continuing to the remaining checks. It is the distribution counterpart to the Call Notice Agent, which gates a capital call before its notices are sent.

1. Gets ready. Sets up separate buckets to collect KYC issues, payment issues, document issues and bank-detail issues.
2. Checks KYC (toggle: Check KYC). Every payment's linked investor must have a KYC record, and it must be marked verified. A missing or unverified KYC fails this step for that payment.
3. Checks that the payable amount has been computed (toggle: Check Net Payable). Every payment must have a net payable amount that is present and not zero.
4. Checks that notices have been generated (toggle: Check Docs Generated). The agent first confirms the fund has a Distribution Template document uploaded at all; if not, this fails the whole step for every payment on the distribution, with the message “Upload a Distribution Template under Fund > Documents.” If the template exists, it then checks each payment has at least one generated notice document attached.
5. Checks that documents are approved (toggle: Check Docs Approved). Every notice document on every payment must be approved; anything still pending approval fails this step.
6. Checks bank details (toggle: Check Bank Details). Every payment's investor must have a bank account number on file in their KYC record.
7. Marks the distribution ready to pay. This confirmation step is only reached if every enabled check above has passed.
8. Saves the report, finalised as either Ready or Blocked depending on whether any step failed.

Because the agent stops at the very first failing step, later steps are never run on a blocked check — their entries in the report stay “Pending” until you fix the blocker and run the agent again.

What it needs

Configuration fields

What it reads directly

• The distribution's payments, each with their linked investor — through the capital commitment and KYC record — and their attached documents.
• The fund's documents, specifically whether a Distribution Template exists. This is a fund-level prerequisite checked once per run, not separately for each payment.

Setup warnings

The agent's General tab shows a yellow warning banner whenever setup is incomplete. For this agent the banner flags:

• Any of the five check toggles that has never been set. Set each one explicitly to Yes or No — an explicit No is respected and not flagged.
• All checks turned off. The agent would mark distributions “ready to pay” without verifying anything.
• Any fund with no Distribution Template uploaded. The notices-generated check will block every payment on that fund's distributions until a template exists under Fund → Documents.

Resolve everything in the banner before trusting a “Ready” result.

Turning it on

• Where to toggle it. Admin → Edit Entity → Support Agents. Requires the Company Admin role.
• AI key. Not required. This agent is entirely rule-based — none of its checks call AI, and it works with no AI key configured at all.
• If the agent is turned off for your entity, the Run Readiness Check action is hidden entirely from the distribution's page.

Running it

From the distribution's own page — the typical way to use it:

1. Open the distribution's show page.
2. From the action menu, choose Run Readiness Check. It only appears when the agent is turned on for your entity.
3. A confirmation popup explains what the agent does, then runs it against just that distribution.
4. Because you are targeting one distribution, a live step-by-step progress panel appears on the distribution's page as each check completes.

From the agent's own page: open AI → Support Agents → Distribution Readiness and click Run Now on the General tab to run the check against every distribution in your entity at once. Batch mode shows no step-by-step panel for an individual distribution.

There is no way to select several specific distributions at once. Your only batch option is the generic Run Now on the agent's own page.

Scheduling

Not available. This agent has no Schedule tab — it is on-demand only, by design. Run it manually before releasing each distribution's payments; there is no recurring automated check running in the background.

Where the output goes

• The distribution's own page — the live step panel shows real-time progress while the check runs, and stays visible afterwards showing the final outcome of each step.
• The agent's General tab — a “View Report” link to the most recent report for the agent overall. Since the agent checks one distribution at a time, “most recent” simply reflects whichever distribution was checked last.
• The Execution History tab — every past run across all distributions, with status, start time and duration. Any row opens the full report.

Reading the result

Each step's outcome is recorded as Success, Failed, Skipped or Pending — pending meaning it was never reached because an earlier step blocked the run. Each failed step includes:

• A plain-language message explaining what went wrong, often with a direct next step: re-run fee calculation on the distribution, click Generate Docs on the distribution page, approve each document before releasing payment, update KYC records before releasing payment.
• A count and list of the specific payments or investors that failed, each with a name and the reason.

The distribution is marked Ready if it reaches “Ready to Pay” with no failed steps, and Blocked if any enabled check fails, with the report noting which step stopped the run. A blocked distribution's payments should not be released until the flagged investors or documents are corrected and the agent is run again.

Where it can fail

• The agent stops at the first problem it finds. Unlike agents that collect every issue before reporting back, this one stops dead at the first failed check. If KYC fails for one investor, you learn nothing about net-payable, document or bank-detail issues for any payment until that KYC issue is fixed and the agent is run again. Plan to iterate.
• No Distribution Template uploaded for the fund. The notices-generated check fails for the entire distribution, not just one payment, if the fund has no document tagged as a Distribution Template. Easy to miss if you have only ever generated notices by hand.
• A payment's amount is exactly zero. The agent treats a zero net payable exactly like a missing one. A genuinely zero payment — say, fully offset by fees — is still flagged as a blocker asking you to re-run fee calculation. There is no way to mark a payment as intentionally zero; the only option is to turn off Check Net Payable for that run.
• KYC exists but has not been marked verified. The agent distinguishes “no KYC on file” from “KYC exists but is not verified” in its messaging, but both block the same way. A KYC that is complete but has simply not had its Verified box ticked will block the payment.
• Bank details are only checked on the KYC record. The check looks at the bank account number stored on the investor's KYC record, not at any separate banking module your entity might use. Bank details entered elsewhere but never synced onto the KYC record are reported as missing.
• The notices-generated check is not picky about what counts as a notice. It checks whether any non-template document is attached to the payment, not that the document is a real distribution notice. A stray, unrelated attachment can make the check pass with no real notice present — and a genuine notice mistakenly tagged as a template is excluded and flagged as missing.
• The approval check does not notice if no documents exist. It only looks at documents that already exist and are not templates. If the notices-generated step was turned off and no notices exist at all, the approval check passes trivially: “Docs Approved: Success” does not mean approved documents exist, only that none of the zero existing ones are pending.
• A distribution with no payments attached sails through as Ready. Every payment-based check reports success when there is nothing to check. This can mask a setup mistake, like forgetting to add the payments in the first place.
• Running it twice on the same distribution at once. A manual run from the distribution's page and a batch Run Now from the agent's page can both target the same distribution simultaneously. Both write to the same report, and whichever finishes last wins.
• Turning off every check. With all five toggles off, the agent sails through to “Ready to Pay” having validated nothing. The report says Ready, but that reflects your configuration rather than actual readiness. The agent's page shows a warning banner whenever it is in this state.

Questions we get asked