Every Party Who Needs Your Numbers, Managed

• A pack can carry any of 40 sections: the four statements and their notes, the trial balance, agings, a covenant compliance certificate, a borrowing-base certificate, an investor update letter, KPI and cohort metrics, a 13-week cash forecast, projected statements and more.

• One generation produces three ready-to-send packages, for management, your bank and your investors, each holding only what that audience should see.

A lender wants the statements, the agings, the certificates and nothing narrative. An investor wants the letter, the metrics and the cap table and nothing operational. Management wants all of it plus the detail. One generation produces each of those, from the same frozen numbers, so the three can never disagree with each other.

• Packs generate on the day of the month you choose and go out as expiring links to named recipients, with every delivery recorded: which period, when, and to whom.

• A pack bound for a bank can be held until a second named person releases it, so nothing that carries a certificate goes out on one click.

• A folder shared outside the company is scoped, expiring and logged — you can see what the recipient opened and when.

The monthly pack goes out on the fifteenth because you said the fifteenth, to the people you named, as a link that expires. If a template is set to require a second approver, the pack waits as a draft until that person releases it, and the schedule waits with it. Automation that skips the second signature is not automation, it is a shortcut.

• Covenant compliance certificates are computed from the books, for leverage, debt service coverage, current ratio and net worth, against the terms in force for that period.

• Borrowing-base certificates are computed from live AR and inventory against your facility's own advance rates and ineligibility rules.

• An amended covenant or advance rate never rewrites a past certificate. Each period certifies against the terms that applied then, so a re-issued certificate says what the original said.

• Projected covenant headroom shows whether you will still comply twelve months out, using the same formulas as the certificate itself.

A covenant certificate is a promise with a number in it, and the number has to come from the books rather than from the spreadsheet where it was last massaged. Here the leverage, coverage, current-ratio and net-worth tests are computed from posted activity, against the terms that applied in that period, and the headroom projection tells you in March about a problem in December.

• Every pack you issue is recorded with a unique seal, so you can say exactly what you sent, when, and prove it has not changed since.

• Reissuing a statement supersedes the earlier one on the record instead of replacing it, so a recipient holding the old version can still be told exactly what changed.

• Every night, every pack you have delivered is re-checked against the books. If the numbers underneath it have moved, that pack is flagged and you are told, before your lender notices.

• A link you send freezes exactly what it points at: the files, and the version of each, as of the day you shared it. A later upload cannot change what a recipient already holds.

The question that ages a finance team is not “what did we send?” but “is what we sent still true?” Every pack is registered with a seal when it goes out, and every night each delivered pack is re-checked against the books underneath it. When a late entry moves a number a bank already holds, you find out first, and the re-issue supersedes the old copy on the record rather than quietly replacing it.

• For each lender review, investor round or prospective buyer, one register shows what you delivered, whether each copy still stands, and what is still outstanding.

• Client requests are tracked as a list with owners and states, so "what are we still waiting on" is a query rather than an email thread.

• Every document view and download is recorded on a tamper-evident log, so who saw what is a matter of record rather than of trust.

A lender’s annual review, an investor’s round, a buyer’s look. Each is an engagement that persists across months, accumulates requests, and ends. For each one, a single register answers what was delivered, whether each copy still stands, what is still outstanding, and who opened what. The relationship stops living in an inbox.

A recipient checks a delivered package on their own computer, with a tool that travels inside the package, installs nothing and contacts no one.

A recipient does not have to take the pack on trust or ask us about it. Every package carries a small program that recomputes each file’s fingerprint on their machine and reports whether anything has changed; it contacts nothing. What it cannot establish is that we sealed an honest package to begin with — the Verifiable Books page states that limit plainly, and describes the second thing every package now carries that closes it: a timestamp signed by an authority we do not control.