Trust needs a record another person can follow.

A useful record lets someone other than the original decision-maker understand what was promised, what changed and what actually happened. It supports trust by making an explanation checkable without requiring the owner to take over every decision.

Trust, Money, and Control considers a painful failure of trust in PCH’s history. The lasting operating question reaches beyond the dispute: how can a company see its own activity when one person holds the relationships and supplies the account of what they produced?

Several agreeing totals may still be one view.

Suppose a hypothetical equipment-rental operation compares its booking report with a monthly summary assembled from that report. The numbers may agree perfectly. A rental omitted from the original bookings will also be missing from the summary. Agreement between the two does not establish that every rental was recorded.

The book connects different kinds of evidence instead: an agreement, the use of an asset, a customer payment and the company’s receipt. Each answers a different question. A deposit may establish that money arrived without identifying the full customer obligation. An asset being used does not establish whether the use was authorized.

Start by identifying where the account comes from and which events could remain outside it. Two reports produced from the same incomplete source should not be mistaken for two independent checks.

Follow one event from outside the summary.

Continue the invented equipment-rental example. A return note shows a machine coming back on Monday, but the booking list has no entry explaining where it went. The note was made when the yard received the machine, for a different purpose from preparing the sales report. It gives the reviewer a question the sales report could not supply.

It does not yet establish a missing sale. The machine might have gone for a repair, been used under an authorized arrangement that was recorded elsewhere, or been attached to the wrong reference. The next step is to find the reason for that movement and connect it to the relevant agreement or other record. Calling it misconduct before doing that would replace a missing explanation with an accusation.

The book makes these distinctions in a rental setting. The table applies them to the invented example. Keep the question each record can answer beside the questions it leaves open.

A second case begins differently: the booking exists, but the receipt is lower than the original price. An authorized reduction, a documented payment charge or an unfinished payment could explain that gap. Finding one explanation does not resolve the first case, where the event itself was absent from the booking list. A company needs a way to notice both incomplete events and differences within recorded events.

Right total, wrong booking

Matching totals can conceal a different problem: the money is present but attached to the wrong transaction. Consider a separate invented case with two equipment bookings, A and B. Each requires a $420 deposit. Both customers pay, and both deposits reach the company in full on the same day.

The original transfer confirmations preserve the booking reference supplied with each payment. They identify these associations:

Booking A

$420 paid with transfer reference P-71.

Booking B

$420 paid with transfer reference P-72.

The company’s receipt records contain both transfer references and the full $840. The booking ledger also shows $420 paid against each booking, but its links are reversed: A points to P-72 and B points to P-71. Those links were entered separately from the original transfer records.

A check of the total deposits passes. A check that each booking shows the required amount passes too. Neither check establishes which payment belongs to which booking. Looking for another $420 on the same date cannot distinguish them.

Later, Booking A’s customer cancels. The invented agreement permits the full deposit to be returned for this cancellation. No refund has been sent. In this company’s process, the person preparing the refund starts from the payment reference attached to the booking. Following A’s current link would select the payment made for B.

The useful check is now specific. Compare A’s booking reference with the original transfer confirmation, then connect P-71 to the company’s receipt record. Do the same for B and P-72. The evidence establishes an association error while confirming that both deposits arrived. It has not found missing cash.

Record the original references that support each match, rather than simply replacing one unexplained link with another. The deposit amounts do not need changing to repair the association. The person preparing A’s refund needs the correct payment identified before continuing; the refund remains a separate unfinished action.

For an ordinary transaction with repeated amounts, ask whether another person could follow that connection without choosing whichever payment looks closest. Following the reference may reveal an error, a missing piece of evidence or a legitimate difference that still needs explaining. A plausible match should not become a confirmed one merely because it makes the report balance.

The total can remain $840 throughout this review. What changes is whether the next person can tell which $420 belongs to which booking.

Ordinary exceptions need a place to go.

Real customers change plans. A booking may require a substitution, a permitted discount or a refund. If the process can record only the original, uncomplicated transaction, sensible service decisions start to look like unexplained differences.

A clear exception record can protect an employee as well as the company. Someone who issued an authorized refund should be able to show the authorization and its completion. A missing payment should remain a question about that payment until the evidence supports a conclusion. Treating every difference as a character test makes it harder to report ordinary problems.

That fairness also requires action. A discrepancy can sit in a report until everybody recognizes it and nobody remembers who is supposed to resolve it. Assign the discrepancy to someone who can investigate it, with a clear next step.

Give freedom a visible boundary.

Chapter 10 supplies the other half of this discussion. Employees need enough information and authority to help customers while the founder is unavailable. Keeping every approval with the owner would exchange a visibility problem for a capacity problem.

That calls for a clear division between a person preparing the account, a person examining an important difference and a person allowed to resolve it. In a small team, some roles will overlap. Name where they overlap and choose a check that brings another view of the event. A second signature on the same unsupported total adds less than an actual explanation somebody else can verify.

The absence walkthrough takes the next question further: can the person with responsibility reach a decision and complete it while the founder is away? Here, the test is whether their account of what happened can stand without their memory filling every gap.

Choose the scale of the check deliberately. A small routine adjustment and the receipts of an entire branch do not create the same exposure. If every minor exception acquires a long approval chain, the business can lose the responsiveness it meant to protect. The question is where another view materially improves confidence in the account, while leaving people able to do their work.