Running the waterfall is only half of a distribution. Before any cash leaves the fund, the allocations have to reconcile to your general ledger: the same total, split the same way, traceable back to a source you can show. When the waterfall output and the GL disagree, you end up explaining why the investor statement differs from the books instead of talking about the deal.
Start with the tie-out that matters most
The first control most fund accounting teams run is easy to state and easy to get wrong: the sum of every investor allocation should equal the fund-level distribution total. If the fund paid out $1,000,000, the per-investor amounts plus the GP's share should add back to exactly $1,000,000, not $999,998 after rounding drifts across twenty LPs. Investor-level totals that fail to match fund-level totals are a common source of reconciliation breaks, and they tend to surface late, after the notices are already out.
Where reconciliation breaks actually hide
Most breaks do not come from the waterfall math. They come from the capital activity around it: a distribution notice that was never posted, a transfer with the wrong effective date, a side letter adjustment applied in the model but not in the ledger. Capital activity is where investor-level errors typically enter, and a single misposting there can create statement issues that are painful to unwind. A short pre-allocation checklist helps: confirm every notice is posted, that cash movements match the postings, and that transfers are mapped to the right investor before the allocation runs.
Make the waterfall side defensible
Reconciliation moves faster when the waterfall side of the tie-out is a figure you can stand behind. That means a per-tier, per-investor breakdown you can trace, not a spreadsheet tab that has changed since last quarter with no record of what moved. Treating the waterfall as controlled and versioned, rather than a model someone edits in place, is what lets you reconstruct any past distribution when an auditor or an LP asks for support. WaterfallOne is a waterfall calculation engine that produces that breakdown as a locked record for each distribution, so the figure you reconcile against the GL is the same one you can walk through line by line in the audit trail.
Illustrative: a distribution's per-investor and GP allocations sum back to the single ledger entry.
Reconciliation rarely fails because the pref was wrong. It fails because the two sides of the tie-out were built in different places and quietly drifted apart. Keep the waterfall output traceable and locked, and the GL reconciliation becomes a quick sign-off instead of a late-night search for a missing two dollars. For more on the support reviewers expect, see what auditors want in distribution records.