WorkflowFund Accounting & Administration

Distribution Waterfall Calculation

Every distribution waterfall run on its own from the LPA and checked tier by tier, before a dollar of carry is paid

See one case, screen by screen ↓
Watch with transcript →

Built forFund finance managersFund controllersFund CFOsInvestor relations teamsChief compliance officers

The Problem Today

Fund finance re-performs the administrator's waterfall by hand, or not at all, so overpaid carry can surface years later.

4.5 days
for one simple European distribution, by hand our estimate
$18T
in private funds run by SEC-registered advisers published

Re-performed by hand each time

  • Fund terms
  • Side letter
  • Ledger
  • Admin model
  • Conventions hide the errorsA wrong day count or compounding rule pays the GP more
  • Investors can now re-checkThe ILPA carried interest reconciliation now reaches LPs

The Solution

  1. Terms read into a tableAgreement, amendments and side letters; each term cited to its clause
  2. The waterfall run on its ownReturn of capital, preferred return, catch-up and split, from the ledger
  3. Two models, tier by tierCompared with the administrator's model; each gap traced to its cell
  4. Checked, then signedThe controller checks, the GP CFO signs, then notices are released

Built-in controls

  • Carry recipients never approve their own funds
  • Agents recommend; people pay, sign and send
  • Each amount cites its source

What You Get

Fewer distributions are reopened at audit or in an investor's review, and notices still go out inside the notice period.

  • Carry errors corrected before paymentA compounding error traced to a formula cell in the model
  • Clawback seen while it's smallInterim carry tested each quarter against the whole fund
  • Risky payments heldAn expired tax form or new bank details holds the payment
In short

What is Distribution Waterfall Calculation?

Distribution Waterfall Calculation is distribution waterfall software for private fund finance. A distribution waterfall, or carried interest waterfall, decides how each distribution is split between the LPs and the GP: return of capital, preferred return, GP catch-up, then the carried interest split. Seven agents read the LPA and side letters, run each waterfall on their own, explain each gap with the administrator's model tier by tier, allocate to each LP and draft the notices; the fund controller checks and the GP CFO signs.

AI in asset management: a buyer's guide to agentic AI for investment managers →

Updated

The problem

A distribution waterfall re-performed by hand, or not re-performed at all

Every closed-end private fund runs its distribution waterfall at each distribution: return of capital, then the preferred return, then the GP catch-up, then the carried interest split, with different terms in each LPA, amendment and side letter. Most managers keep these calculations in spreadsheet models, often the fund administrator's, and fund finance checks them by re-performing the model by hand: several hours for a simple European fund and days for an American waterfall with write-downs, all inside the notice period the LPA sets. Sometimes nobody re-performs it at all.

The errors sit in the conventions: whether unpaid preferred return compounds, the day count, the write-downs left out of a deal-by-deal waterfall, a management fee offset applied after instead of before the waterfall, an IRR hurdle dated at quarter end. Each one moves money between the LPs and the GP. A carried interest overpayment surfaces at audit, in an LP's review or as a clawback years later, and the SEC has cited private fund advisers for overcharging carried interest. From 2026 LPs receive the ILPA carried interest reconciliation and can re-perform the numbers themselves.

typical$705Bmore private equity assets under administration at the 12 largest administrators in one year: more waterfalls run by someone else, still the GP's liability
typical$18Tof private fund assets managed by more than 5,000 SEC-registered advisers, each closed-end fund running a waterfall at every distribution
typical60daysafter quarter end: ILPA's suggested delivery for a direct fund's quarterly report, now with a consolidated carried interest reconciliation LPs can re-perform
Where a distribution's working days go, from the administrator's model to signed noticesestimated
By hand4.5 days
With the solution1.6 days
  • Finding this fund's terms in the LPA and side letters0.5 → 0.1 d
  • Re-performing the administrator's model tier by tier1 → 0.1 d
  • Tracing a gap and agreeing it with the administrator1 → 0.6 d
  • Allocating to LPs: side letters, transfers, tax forms0.5 → 0.1 d
  • Controller's check and the GP CFO's signature1 → 0.6 d
  • Notices, payment file and evidence0.5 → 0.1 d

Estimated split for a simple European whole-fund distribution, by hand and with the solution. The working solution's quarterly report shows a median of 1.6 days from the administrator's model to signature; the split itself is not yet measured.

How it works

Each distribution waterfall run from the LPA and compared tier by tier

What comes in
Data inEach distribution · LPAs, side letters, ledger, administrator models
Agents at work
Terms agentLPA to term table
Then
Model agentindependent run
Clawback agentwhole-fund test
Then
Diff agenttier by tier
Then
Allocation agentevery LP
Notice agentLP notices
Evidence agentevidence pack
A person decides
Controller and GP CFOcheck, sign, release
What comes out
Carry traced to the LPA
Notices to every LP
Every decision on the record
One case, step by step

One fund's distribution, two models apart on the preferred return

A Delaware private equity fund with $1.4 billion of commitments from 214 LPs and a European, whole-fund waterfall has sold a portfolio company and is distributing $48,000,000 on a set date, with notices due a week before. Here is how the controller, the agents and the GP CFO work it through, screen by screen, in the working solution.

A worked example on sample data. Names, IDs and figures on the screens and in this section come from the demo.

  1. 01Tuesday morning

    What needs the controller today, one next step each

    Fund controller

    The controller checks each distribution before it goes to the GP CFO. The Today screen shows 23 open distributions worth $478.6M, 5 differences to decide ($1.78M between the independent runs and the administrator models), 11 notices due by Friday and 1 clawback exposure not covered. At the top of Needs you: the fund's distribution, check the corrected waterfall. Beside it, what the agents did overnight, each line cited.

    Diff agent, early that morning: “The administrator agreed to the $412,000 correction; model v3 matches.”

  2. 02The queue

    Each distribution, grouped by what it needs

    Fund controller

    Distributions lists 23 open distributions, one per vehicle, in three groups: needs a decision, with the agents or an administrator, and with the controller. Each row shows the amount, the notice date, the independent run against the administrator's model and who holds it. The controller can filter by strategy, waterfall type (European, American, IRR promote, deal-level, MOIC-tiered, incentive allocation), administrator and notice date. This distribution reads “Agreed in model v3 · $412,000 corrected to the LPA”.

    An opportunistic credit fund: “Administrator model missing”. The independent run is ready and the request is drafted.

  3. 03Before any run

    The LPA as a cited term table

    Terms agent

    The fund's waterfall terms sit in term table v4, prepared by the fund finance manager and approved by the controller earlier in the year, read by the Terms agent from the agreement, 3 amendments and 61 side letters. Each term cites its clause with a confidence: a European (whole-fund) waterfall, an 8% preferred return compounded annually at each year-end, Actual/365, a 100% GP catch-up until the GP has 20% of profits and an 80/20 carried interest split. The §9.5 in-kind valuation read at 86%, below the 95% line, so a person confirms it, and it is flagged for fund counsel with the question already drafted; proposed Amendment No. 3 waits for the checker.

    Below 95% confidence a person confirms the term; an ambiguous clause goes to counsel instead of a guess.

  4. 04A week before the notices

    The waterfall, run on its own from the LPA

    Model agent

    The Model agent ran the distribution from the approved term table and the capital ledger alone. The $48,000,000 pours through four buckets: return of capital $36,374,871 (§9.1(a)), preferred return $8,937,129 at 8% compounded yearly (§9.1(b)), and $2,688,000 of GP catch-up, 100% to the GP until it has 20% (§9.1(c)). The 80/20 carried interest split is not reached. The clawback gauge beside it shows $2.69M of carry paid against $247.5M of whole-fund carry at the last quarter-end NAV: no exposure.

    The Model agent does not read the administrator's model or overwrite a run: what-ifs are separate scenarios.

  5. 05Six minutes later, then Tuesday

    Two models, two tiers apart, and the §9.1(b) arithmetic

    Diff agent, with the fund controller

    Six minutes after the run, the Diff agent opened the administrator's model v2, received by file drop, read every formula and compared it tier by tier. Return of capital agrees; the preferred return is $412,000 lower and the GP catch-up $412,000 higher, $3,100,000 where the LPA allows $2,688,000. On Tuesday morning the controller asks in the thread beside the waterfall, “Show the §9.1(b) arithmetic”: unpaid preferred return of $6,055,242 at the last year-end, plus $148,553 accrued on a December capital call, makes a base of $6,203,795 that compounds into this year, and 8% × 303/365 of it is $412,000. Each figure links to its clause, ledger entry or cell.

    Diff agent: “The administrator's 'Pref'!F18 leaves the base out. §9.1(b) puts it in.”

  6. 06The next two days

    The clause beside the formula, and the query

    Fund finance manager

    The difference in plain words: what the agreement says, §9.1(b), beside what the administrator's model does, 'Pref'!F18 = C18*0.08*D18/365, a simple accrual on capital only. The fund finance manager accepted the independent run with reason code R1, the Diff agent drafted the query, and the controller approved sending it. The next morning the administrator replied: model v3 compounds per Section 9.1(b). The look-across found the same formula in a distribution from the fund's Luxembourg parallel: $91,600.

    The Diff agent does not edit the administrator's model or send a query without approval.

  7. 07Minutes later

    214 LPs, five exceptions, two payments held

    Allocation agent

    The Allocation agent split the distribution across 214 LPs, and the LP totals tie to the tiers to the dollar. Five exceptions: an insurer's W-8BEN-E expired last month, and a health foundation changed its bank details through the portal, so both payments are held. A German pension LP's side letter sets its carry at 15%, shown in the German original beside the English; a university endowment's transfer and a county retirement system's excused call are applied.

    The Allocation agent does not pay or change LP bank details: the foundation stays held until the call-back to the contact on file confirms them.

  8. 08Checked, then signed

    The controller checks; the GP CFO signs the correction

    Fund controller, then the GP CFO

    The controller checks $48,000,000, $45,312,000 to the LPs and $2,688,000 of GP carry; the check confirms the controller did not prepare it and holds no carry in the fund, and the controller records reason code R1, Independent run follows the LPA. The GP CFO then sees who prepared and who checked, that the CFO holds no carry in the fund and that each tier cites its clause, and signs with a passkey: “Signed on the independent run: §9.1(b) compounds annually. Catch-up $2,688,000, in place of $3,100,000.” The payment file goes to the treasury payment system with 212 LP payments, $43,481,577, and 2 held, and the evidence pack is sealed.

    “I approve this distribution and the carry it pays, as officer of the General Partner.”

  9. 09Released

    212 notices released; two stay held with their payments

    Investor relations manager

    The Notice agent drafted all 214 notices with the tier breakdown, the payment date and the account ending, and courtesy translations where an LP asked. The investor relations manager previews the German pension LP's distribution notice with the German translation beside the English, then releases 212 notices to the investor portal. Release was locked until the signature; the two held LPs are excluded.

    The Notice agent does not send: notices release only after the GP CFO signs.

  10. 10Each quarter

    The whole-fund GP clawback test

    Clawback agent, then the Chief Compliance Officer

    The Clawback agent tests each main fund that has paid interim carry, each with its parallel funds and AIVs, at the last quarter-end NAV; this fund, with this distribution, shows no exposure. A real estate fund with an American (deal-by-deal) waterfall has paid $14,200,000 of carry against $9,600,000 the whole fund supports. After tax at 41% under §12.6 and $1,894,000 of escrow under §12.4, $820,000 is not covered, so it is escalated to the GP CFO and the CCO with an LPAC note drafted; the CCO accepts the escalation or edits the note.

    The Clawback agent does not move or release escrow, and does not contact LPs.

Who it’s for

The controller, GP CFO, fund finance, investor relations and compliance

Five roles on one distribution waterfall, each with the work by hand and the work now.

Fund controller
The checker
Before
Ticks and ties the administrator's spreadsheet against a shadow model, with the evidence spread across email threads and file versions.
Now
Opens each distribution with both models compared tier by tier and each gap explained, and checks with a reason code.
GP CFO
Signs each distribution that pays carry
Before
Approves distributions by email, after a review that lives in email threads and file versions.
Now
Signs with each dollar of carry traced to the LPA, and the maker, the checker and the carry check on the same screen.
Fund finance manager
The maker
Before
Re-types the administrator's spreadsheet to rebuild each tier by hand.
Now
Prepares instead: decides each explained difference with a reason code, and the query to the administrator is already drafted.
Investor relations manager
Releases notices
Before
Finds an expired tax form or changed bank details after the notices are out.
Now
Sees each LP exception held before payment, and releases signed notices in bulk with their courtesy translations.
Chief compliance officer
Clawback and the carry conflict
Before
Hears about clawback exposure at year end or at wind-down, from a separate spreadsheet.
Now
Gets each quarter's whole-fund test, and any exposure not covered by escrow arrives with a drafted LPAC note.
The agents

Terms, model and diff agents that keep two calculations independent

The agents run the waterfall from the LPA on their own and compare it tier by tier with the administrator's model; the controller checks, the GP CFO signs.

Terms agent

Reads LPAs, amendments and side letters in any language into a cited term table: waterfall type, preferred return rate, compounding and day count, catch-up, split, GP commitment, offsets, write-downs, clawback, escrow and side-letter economics, each with its clause and page.

  • Never changes an approved term
  • Never guesses an ambiguous clause: below 95% confidence a person confirms, and an ambiguity goes to counsel
Model agent

Runs each distribution waterfall independently from the approved term table and the capital ledger, per LP and per tier, with day counts and compounding; what-ifs on request.

  • Never reads the administrator's model
  • Never overwrites a run: a what-if is a separate, labeled scenario
Diff agent

Compares the independent run tier by tier with the administrator's model, reads its formulas, explains each gap in plain words with the clause, the cell and the arithmetic, drafts the query and looks across other vehicles.

  • Never edits the administrator's model
  • Never sends a query without the controller's approval
Clawback agent

Tests interim carry each quarter against a whole-fund hypothetical liquidation at NAV for each vehicle that has paid carry, with the after-tax limit, escrow and guarantees, and drafts the LPAC note for an exposure not covered.

  • Never moves or releases escrow
  • Never contacts LPs
Allocation agent

Allocates each distribution to each LP, with commitment shares, excused investors, side letters, transfers, tax forms and bank detail checks.

  • Never pays
  • Never changes LP bank details
Notice agent

Drafts each LP notice with the tier breakdown, the payment date and the account ending, with courtesy translations where the LP asked.

  • Never sends
  • Notices release only after the GP CFO signs
Evidence agent

Builds the hash-chained record of each run and the evidence pack per distribution and per period: inputs, terms with citations, both models, differences, decisions, signatures, notices and the payment file.

  • Never edits a record
Fund Controller and GP CFO

Check, sign, release.

Ask in plain words

Carry at risk, a held payment or a notice date: ask beside the waterfall

Ask about any distribution, tier, investor or fund, or say what to do. The answers come with their sources, and the agents act only with your approval.

Why is the fund's carry $412,000 lower than the administrator's?

Section 9.1(b) compounds the preferred return at each year-end. The administrator's rebuilt model accrued this year on capital only, in 'Pref'!F18, leaving $6,203,795 out of the base. 8% × 303/365 × $6,203,795 = $412,000 more for the LPs and less catch-up for the GP: $2,688,000 in place of $3,100,000. The administrator agreed this morning.

How much carry have we paid this year, and is any at risk?

$46.2M of carry paid this year. One exposure is not covered: a real estate fund, $2,714,000 after tax against $1,894,000 in escrow, so $820,000. Two other funds, one real estate and one direct lending, are on watch.

Which notices are at risk of missing their date?

11 notices are due by Friday. Two need attention: an infrastructure fund is due today and waits for the GP CFO's signature; an opportunistic credit fund has no administrator model yet, and its independent run is ready.

Prepare the evidence pack for this distribution

The pack holds the term table with each clause cited, the independent run, the administrator's models v2 and v3, the $412,000 difference with its arithmetic, the fund finance manager's decision (R1), the query and the reply, the check, the signature, the 214 notices, the payment file and the hash chain.

The screens

The waterfall, the clause beside the formula and the clawback test

From the working solution, on its sample data. Pick one to see it large.

TodayThe fund controller's day: open distributions, differences to decide, notices due and clawback watch, with one next step each and what the agents did, each line cited.
DistributionsEach open distribution grouped by what it needs, with the independent run against the administrator's model, the notice date and filters by waterfall type.
The distribution waterfallThe distribution poured through return of capital, preferred return, GP catch-up and the carried interest split, each tier with its LPA clause, the clawback gauge and the agents' thread.
Asking the agentsThe distribution waterfall with the independent run against the administrator's model tier by tier, and the controller's question to the agents: the §9.1(b) preferred return calculation, cited to clause, ledger and cell.
The clause beside the formulaWhat the LPA says beside what the administrator's model does, the arithmetic, the query to the administrator and the look-across to other vehicles.
Investor allocationThe distribution allocated to 214 LPs with side letters, transfers and excused investors, and the five exceptions, two payments held.
The GP CFO signsWho prepared and checked, the carry check, the reason code and the GP CFO's signature with a passkey.
LP distribution noticesEach LP's distribution notice with the tier breakdown and a courtesy translation beside it, released to the investor portal after the signature.
GP clawbackInterim carry paid against what the whole fund supports at NAV for each vehicle that pays carry, with escrow, the after-tax limit and a drafted LPAC note.
The term tableThe fund's waterfall terms read from the LPA, each cited to its clause with a confidence, a proposed amendment, a question for counsel and the side letters.
Audit trailEach run, difference, decision, signature and notice, by person, agent or integration, hash-chained, with the evidence pack export.
Quarterly reportThe quarter in plain numbers: distributions run, carry paid, differences found by cause, control health and the ILPA carried interest fields.
Waterfall rulesTolerance per tier, the notice clock, approval chains, the second signer, escrow release and rounding, all settings, each change approved by the controller.
Governance

Carry conflicts blocked and three signers on each distribution waterfall

Each amount cites its sourceEach tier, difference and LP amount links to its LPA clause and page, its capital ledger entry or the administrator's cell, and each agent statement shows its plan, the sources it read and its confidence.
Maker, checker and signer are different peopleFund finance prepares, the fund controller checks, the GP CFO signs and investor relations releases. Each decision carries a reason code and a comment, and a distribution over $100,000,000 needs a second signer, the COO.
Carry recipients never approve their own fundsAnyone who holds carry in a fund, from the carry plan register imported nightly, is blocked from preparing, checking or signing its distributions. The check runs at each decision, is shown on the sign-off, and a blocked attempt goes on the record.
Agents recommend; people pay, sign and sendThe agents do not pay, sign, send a notice or a message to an administrator, change a term or move escrow. The Model agent does not see the administrator's model, so the two calculations stay independent.
A hash-chained audit trail and evidence packsEach run, difference, decision, signature and notice is recorded with who, what, when, why and the evidence, each entry chained to the one before. One export gives the evidence pack for the auditor, the LPAC or an SEC exam, kept seven years after a fund ends, beyond the five years of Rule 204-2.
Versioned agents, data kept in its regionA new agent version runs in parallel on last quarter's distributions before it goes live, and the controller approves the result. Each vehicle's data stays in its own region, and EU investor data in an EU region; entitlements are by fund, and LP bank and tax details are masked except for investor relations.
Configuration

Tolerances, the notice clock and the signers for each distribution

The rules each distribution waterfall is checked against are settings. The platform administrator proposes a change, the controller approves it, and each version is on the audit trail.

SettingDefaultChoose from
Difference tolerance per tier$1,000 or 0.01% of the distribution, whichever is lowerPlatform administrator proposes; controller approves
Notice clock5 business days before paymentPlatform administrator proposes; controller approves
Distributions paying carryMaker → controller → GP CFOMaker, checker and signer are always different people
Distributions over $100,000,000Second signer: COOPlatform administrator proposes; controller approves
Escrow releaseGP CFO and CCOPlatform administrator proposes; controller approves
Query to an administratorController approves before sendingPlatform administrator proposes; controller approves
Administrator model missing at T−2Controller may check on the independent run alone (policy 4.2)Platform administrator proposes; controller approves
RoundingTo the dollar, largest remainder across LPsPlatform administrator proposes; controller approves
Connections

The capital ledger, fund documents and administrator models it reads

Fund accounting platformcapital ledger, NAV and carry ledger
Document managementLPAs, amendments and side letters, in their original language
Fund administrator file dropsthe administrator's waterfall model and draft notices, for each distribution
Investor registerLPs, commitments, transfers, excused investors, tax forms and the carry plan register
Investor portalLP notices, released after the signature
Treasury payment systemthe payment file after signature, with held LPs left out
What it changes

Carry gaps fixed before payment, and one exception list to decide

Each figure carries its label: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
100%
of distributions recalculated independently from the LPA, tier by tier, before the notice goes out
each distribution
tier by tier, before the notice
target
$0
of carry paid beyond the LPA, as a design goal: each gap found before payment
Todayfound at audit or clawback
With agentsfound before payment
target
1list
of exceptions to decide, in place of a model review of several hours
Todayre-perform the model by hand
With agentsdecide each explained gap

“demo” = seen in the working solution, on its sample fund data · “target” = the design goal, measured in the live solution · “estimated” = our estimate, including the working-days split for a simple European whole-fund distribution; the 4.5 days is that split's by-hand rows, summed · “typical” = published figures (The Drawdown, Fund Admin Report 2025 — private equity assets under administration at the 12 largest administrators up $705 billion in a year; SEC Division of Examinations risk alert, January 27, 2022 — more than 5,000 registered advisers managing about $18 trillion of private fund assets; SEC OCIE risk alert, June 23, 2020, on overcharged carried interest; ILPA Templates Hub — Reporting Template v2.0 from Q1 2026, quarterly reports suggested within 60 days after quarter end for direct funds, deferring to the LPA). Names on the screens are sample data.

Questions

Distribution waterfall questions from GP finance and compliance

What is Distribution Waterfall Calculation?

Distribution Waterfall Calculation is distribution waterfall software for private fund finance. A distribution waterfall, or carried interest waterfall, decides how each distribution is split between the LPs and the GP: return of capital, preferred return, GP catch-up, then the carried interest split. Seven agents read the LPA and side letters, run each waterfall on their own, explain each gap with the administrator's model tier by tier, allocate to each LP and draft the notices; the fund controller checks and the GP CFO signs.

How is carried interest calculated in a distribution waterfall?

Each distribution fills the tiers in the order the LPA sets. In the sample private equity distribution waterfall, the fund's $48,000,000 returns $36,374,871 of capital, pays $8,937,129 of preferred return at 8% compounded annually, then $2,688,000 of GP catch-up at 100% until the GP has 20% of the profits; the 80/20 split is not reached. The Model agent runs this per tier and per LP from the approved term table and the capital ledger.

European vs American waterfall: does it handle whole-fund and deal-by-deal?

Yes. A European waterfall pays carry on the whole fund's result; an American waterfall pays it deal by deal. The sample firm's vehicles include European (whole-fund) and American (deal-by-deal) waterfalls, IRR promotes, deal-level co-investments, MOIC-tiered continuation funds and incentive allocation. The term table records each fund's type, and the differences it finds include write-downs left out of a deal-by-deal waterfall and IRR hurdles dated at quarter end instead of the actual cash-flow dates.

Is the preferred return compounded, and does the solution catch the wrong convention?

The LPA decides the preferred return calculation. The sample fund's §9.1(b) compounds 8% annually at each year-end, Actual/365; the administrator's model accrued the current year on capital only. The Diff agent read the formula, 'Pref'!F18, set it beside the clause and showed the arithmetic: $412,000 moved from the GP's catch-up back to the LPs, corrected before payment.

How does it track GP clawback?

Each quarter the Clawback agent tests interim carry against a whole-fund hypothetical liquidation at NAV for each vehicle that has paid carry, after the tax limit and escrow. In the sample, a real estate fund has paid $14.2M against $9.6M the whole fund supports; after tax at 41% and $1,894,000 of escrow, $820,000 is not covered, so it goes to the GP CFO and the CCO with a drafted LPAC note.

Does it help with the ILPA carried interest reconciliation?

The quarterly report shows the carried interest reconciliation fields of the ILPA Reporting Template v2.0 filled for each closed-end vehicle in the sample, with the open-ended funds marked not applicable, alongside the distributions run, carry paid and the differences found and corrected before payment. The numbers come from the audit trail.

Can anyone who earns carry approve the distribution that pays it?

No. Anyone who holds carry in a fund is blocked from preparing, checking or signing its distributions. The agents do not pay, sign, send a notice or a query, change a term or move escrow. Fund finance decides each difference with a reason code, the controller checks, the GP CFO signs with a passkey and investor relations releases the notices.

How is it set up, and does it run beside our current process first?

The Agentic Solution Engine builds and deploys it from your requirements and documents (your LPAs, side letters, the administrators' models and a sample of past distributions), and it goes live once each quality gate has passed. First-time setup connects your systems, reads your fund documents into term tables for approval and runs in parallel with your current process before go-live.

Re-run a past distribution
through the waterfall check.

We'll run Distribution Waterfall Calculation on your own LPAs and a sample of your past distributions.