How AI runs distribution waterfall calculations
By Team DwellFi
A wrong distribution number does not look wrong.
It looks like a finished number. Formatted correctly, tied out to the fund's cash position, signed off by someone who trusts their own process. Then it pays the wrong LP the wrong amount, and nobody finds out until the LP's own accountant calls asking why their check does not match their side letter.
That is the failure mode nobody talks about when they talk about waterfall automation. Everyone assumes the risk is the math: the tiers, the catch-up provisions, the clawback mechanics, the carry calculation itself. It is not. A competent analyst can model all of that in an afternoon. The risk lives one layer down, in the inputs nobody double-checks because double-checking them is tedious, and tedious is where errors live.
This is the specific problem we built DwellFi's waterfall engine to close. Not a faster calculator. A system that reads the fund's own governing documents before it computes anything, so the inputs stop being the weak point.
Where the risk actually lives
Every waterfall calculation depends on three things being right before a single number gets computed: the current LPA, not last quarter's version sitting in someone's downloads folder. The side letters that actually govern this specific LP, all of them, not the two someone remembered to pull. The historical distributions that feed the next tier, pulled correctly and in the right order.
Get any one of those wrong and the arithmetic downstream is still perfectly correct. Tiers apply cleanly. Catch-up triggers fire on schedule. Carry comes out to the decimal.
The output is confidently, professionally wrong.
This is the part that makes waterfall errors so dangerous. They do not surface as an error message. There is no red flag, no failed validation, nothing that tells the analyst to look again. There is just a number, formatted the way a correct number is always formatted, and it pays someone the wrong amount.
How DwellFi runs the calculation differently
The fix is not a better spreadsheet template. Templates assume someone has already extracted the right inputs and typed them in correctly, which is exactly the step that fails.
DwellFi reads the source documents directly, before a single number gets computed. It goes into the LPA and identifies the tier structure on its own. It reads every side letter attached to the fund and applies the LP-specific terms that actually govern this investor, not a generic set of assumptions. It runs the distribution against those inputs. Then it writes down its reasoning, one step at a time, so the logic is visible rather than buried inside a black-box calculation.
Because DwellFi reads the documents instead of relying on someone's memory of what they say, it does not forget the side letter that only applies to one LP out of forty. Because it pulls the current version every time, it does not silently run the calculation against an LPA that was amended two quarters ago.
That is the entire mechanism, and it is the core of how the platform is built. Read everything, every time, and show the work.
What DwellFi actually produces
The output is a distribution schedule, the same thing you would get from any waterfall tool. What is different is what comes with it: DwellFi generates a memo alongside the schedule that shows exactly how each figure was derived, and every number in that memo traces back to the specific clause it came from.
That distinction matters more than it sounds like it should. A partner who receives a bare number has to trust it. A partner who receives a number with a clause reference behind every line item can hand the whole thing to an LP or an auditor without reconstructing anything first. The defensibility is built into the output instead of bolted on afterward by someone reverse-engineering their own work three weeks later.
I have watched analysts spend an entire evening rebuilding the logic behind a number they generated themselves, because the original working file got overwritten and nobody wrote down which side letter applied to which LP. That evening disappears entirely when the derivation is documented at the moment the calculation runs, not reconstructed after the fact.
Speed or accuracy: pick one, or don't
People ask this question like it is a trade-off. It is not, but if you force the choice, accuracy is the one that matters.
Yes, DwellFi is faster. A request that used to consume an evening now comes back before the analyst has finished their coffee. But speed was never really the constraint. The constraint was that a tired analyst working late does not always catch the side letter that only applies to one LP out of forty, and a system that reads every governing document does not get tired.
DwellFi does not skip a provision because it is 11 pm and the deadline is tomorrow morning. It does not reach for last quarter's LPA out of habit because that is the file that was already open. It reads what is actually current, every time, because reading everything is the only mode it operates in.
That is the kind of accuracy you can put in front of an auditor. It is the only kind that counts when the calculation on the screen determines who gets paid and how much.
Does DwellFi hold up against real fund complexity
This is the real test of any waterfall tool, and it is where most of them quietly fail. European waterfalls behave differently from American ones. Hurdle rates stack in ways that are specific to a single fund's structure. GP catch-up provisions vary. Clawback mechanics are rarely identical from fund to fund, and LP-specific side letter terms exist precisely because every LP negotiated something slightly different.
DwellFi handles all of it, because it never forces a fund's structure into a preset shape to begin with. A configured template hopes the shape is close enough. DwellFi reads the governing documents directly, so a European waterfall gets modeled as a European waterfall, a fund with three side letters carrying three different hurdle rates gets modeled that way, and a clawback provision that only triggers under one specific condition in one specific fund still gets applied correctly. Every fund's structure is encoded in its own documents, written by lawyers who were paid specifically to make sure those terms said exactly what the fund wanted. DwellFi reading those documents instead of forcing them into a template is how the platform respects what they actually say instead of approximating it.
Where this leaves the partner
None of this replaces judgment. A partner still reviews the output, still signs off, still owns the number that goes out the door. What changes is what they are reviewing. Instead of checking someone's arithmetic and hoping the inputs were right, they are reviewing a fully sourced derivation where every figure already points back to the clause that produced it.
That is a different job. It is a faster one, and it is a safer one, and it is the only version of this process that survives contact with an LP's own counsel asking hard questions.
This is the capability we built DwellFi around: read the documents, run the calculation, show the work. If you run distributions on any complexity of fund structure and want to see what a fully sourced waterfall calculation looks like against your own documents, we would be glad to walk you through it.