When Someone Wants to Buy You, Be Ready That Week

• A complete due-diligence package, with statements, ledgers, agings and evidence, produced as a snapshot of one moment in time and carrying a seal anyone can check.

• A due-diligence package is a saved template you generate on demand, held for a second person's release, sealed, and put on the register like any other pack.

• For a buyer, the package can carry trailing-twelve-month EBITDA, a net-debt bridge and working-capital analysis, alongside customer and vendor concentration, related-party transactions and red flags.

• Releasing a package is a two-person act on the record: one person requests the period, a second names the reviewer and approves it, and only then can it be published — with every step, and who took it, kept beside the package it released.

Statements, trial balance, ledger detail, agings, bank reconciliations, fixed assets, the chart of accounts, the journal listing, the supporting documents, the control attestations. A buyer’s analyst wants trailing-twelve-month EBITDA, a net-debt bridge and working capital, and wants to know who your biggest customers are and whether anyone related to you is on the vendor list. All of it is one template, generated from the books as they stand.

• A delivered package is frozen at a point in time and given a unique seal, so what the recipient holds can be checked against what was sent rather than taken on trust.

• A package refuses to seal if the balance sheet does not balance or the books' tamper-evident record shows a break. It would rather not exist than exist wrong.

• A delivered package can be re-verified byte for byte against what was issued, at the moment someone is about to rely on it.

A package is a snapshot of one moment. It carries a seal a recipient can check, it is registered when it is issued, and it can be re-verified later against exactly what was sent. If the books cannot produce a package that is right, no package is produced. A buyer who asks “is this the version you sent last month?” gets a fact, not a recollection.

• A published package is filed into the Documents hub under the full diligence checklist tree, with a checklist and a completeness manifest, ready to share as a scoped, expiring link.

• A supporting document is tied to the transaction it supports inside the record itself, so a transaction cannot be deleted out from under its own evidence.

• 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 evidence you attached during the year is the evidence that ships in the package at the end of it. A published package lands in the Documents hub under the full checklist a diligence team works from, each document filed under the caption it substantiates, with a manifest that says what is present and what is not. Share it as a link that expires and records what was opened, and what the buyer holds cannot change under them.

• Every figure on every statement opens into the journal entries behind it, and from there into the invoice, bill or payment that caused them.

• Every report takes an as-of date, so you can reproduce what the books said on the day you reported them rather than only what they say now.

• A package states which of its figures came from your other system and which were prepared here, so a reader never has to guess where a number was born.

The diligence question is always the same: where did this come from? A figure on the income statement opens into the entries behind it and from there into the invoice, and the package can be regenerated as of the date it was first sent. If some of the books live in another system, the package says which figures came from there.

• 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.

• Audits, reviews, agreed-upon procedures and diligence exercises are tracked as engagements, each with a period, a team, its own materiality and its own request list.

• 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.

A sale is not one package. It is a buyer’s review that runs for months, sends a second request list after the first, and asks for the March numbers again in June. Track it as an engagement: what has been delivered to this buyer, whether each copy still stands, and what they are still waiting on. When two buyers are looking at once, each has its own register.