Impact Numbers Deserve an Auditor Too, and Moko Runs Its Fund Closes That Way

Every quarter, the investors in a development fund receive two kinds of numbers. The first kind describes money: what the fund is worth, what each partner owns, what was called and what was paid back. Those figures pass through a trial balance, a reconciliation and, eventually, an auditor who signs an opinion. The second kind describes the world: homes occupied, loans made to small businesses, acres moved onto regenerative practices. Those figures often pass through a spreadsheet kept by whoever on the deal team had time that week.

Both sets of numbers arrive with the same letterhead. Only one of them has been checked against anything.

For the people who put money into community development finance institutions, affordable housing partnerships and farmland funds, the second set is frequently the reason they invested at all. A pension committee or a foundation board approves an allocation to an impact vehicle because of what it is supposed to do. When the outcome figures are softer than the financial ones, the investor is left trusting the part of the report that matters most to them and was examined least.

Two calendars, two standards

The problem is usually structural before it is ethical. A fund’s financial close runs on a fixed calendar with a cutoff date, a reviewer and a deliverable. Impact reporting tends to run on a separate track. The deal team gathers occupancy figures or loan counts when the property managers and borrowers send them, someone formats an appendix, and it goes out a few days or weeks after the net asset value statement. Sometimes it covers a slightly different period. Sometimes the numbers are estimates that were meant to be replaced and never were.

None of this requires bad faith. It only requires two processes owned by two groups with two deadlines. The financial side has decades of practice behind it, from double-entry books to audit trails. The impact side mostly has good intentions and a shared drive.

That gap matters more in development finance than almost anywhere else. A small CDFI or a regional housing fund may have a handful of institutional investors who each read the outcome section closely, and a single unsupported claim about jobs or units can follow a manager into the next fundraise.

One close, one reviewer

Moko, a fund administrator that works with impact vehicles, starts from a blunt premise: the impact scorecard should go through the same close as the books. On the firm’s combined financial and impact reporting service, the NAV statement and the scorecard share one cutoff date, one reviewer and one delivery to limited partners. There is no separate appendix that turns up the following week.

The mechanism is a matching rule. Before a close begins, the manager and Moko agree which scorecard lines the fund owes its investors and which source file feeds each one. A line for occupied units points to a rent roll. A line for loans closed points to a loan register. During the close, each figure is checked against its named file. If a line cannot be tied to a source document for that period, it is left off the pack. The site puts it plainly: estimates do not get a stamp.

That rule produces reports that are occasionally shorter than a manager would like. It also produces reports where every outcome figure has a paper trail an auditor could follow, which is the standard investors already apply to the financial pages.

The books come first

The financial side is ordinary fund administration done carefully. Moko keeps the NAV calculation and fund accounting, maintains capital accounts for each partner, and prepares capital call and distribution notices on the manager’s calendar. Before it runs a NAV, it wants the trial balance, an investment roll-forward reconciled to the prior close, capital activity through the cutoff, a partner roster checked against subscription documents, and dated fair-value marks. Its own summary of the logic is hard to argue with: without clean capital accounts, the outcome sheet is decoration.

Engagements follow three steps. The firm scopes the vehicle by mapping its NAV dates, investor pack and impact metrics. The manager signs an engagement agreement with defined fees and deliverables. Then the close calendar runs, with calls processed and reports shipped on the same cycle.

The limits are stated just as clearly. Moko does not originate impact data; the fund and its investees still have to collect it. It does not hold assets or wire capital. It does not give legal or tax advice, does not sign the audit opinion, and does not promise returns or outcomes. The general partner keeps the decisions and signs the notices. Moko signs its own administrative checklist, counsel handles filings, and the auditor signs the opinion.

For development finance, the practical change is modest and specific. An investor reading a Moko pack can ask where any outcome figure came from and get a file name back, the same answer they would get about a cash balance.

Business Correspondent