On October 12, 2026, BBC News reported that Deloitte helped falsify documents used to evade tax on Roman Abramovich’s wealth. The account says backdated paperwork also removed yachts and mansions from accounts. The full BBC News report on falsified documents concerns affairs far larger than those of an ordinary American firm. Its useful lesson, however, fits any enterprise: a record is only as trustworthy as the method used to create, approve and preserve it.
Most small businesses do not need an elaborate compliance department. They do need a simple way to establish what was requested, who approved it, when the approval occurred and whether the finished work matched the agreement. That file should be strong enough to survive staff turnover, a disputed invoice or a question raised months later.
Keep the original request
Begin each substantial purchase or project with a dated request. State the business purpose, expected result, rough budget and person responsible. Attach the first estimate or proposal instead of replacing it when a new version arrives.
The point is not to produce paperwork for its own sake. It is to preserve the path of the decision. A folder containing only the final invoice cannot show whether the scope grew, the price changed or someone approved a substitute.
Number every revision
Give each proposal, drawing or specification a version number and date. The filename can be plain: Project Name, Revision 2, October 12, 2026. When a revision arrives, keep the old one and add the new one.
Ask the vendor to identify what changed. A short change note is enough: dimensions revised, material substituted, installation date moved or electrical work excluded. That practice prevents two people from approving different documents that happen to share the same title.
Make approval an affirmative act
Silence should not count as approval. Require the responsible person to write that a particular version is approved, with a date. If the business has spending limits, record the person whose authority covers the amount.
For a physical project, approval should identify more than appearance. It may need to cover measurements, materials, colors, mounting, access, cleanup and the division of responsibility for permits or property consent. Those details belong in the record because they determine what the vendor is actually being paid to deliver.
Ask vendors how they preserve the trail
A capable vendor should be able to explain how estimates, proofs, revisions and installation details move from the first conversation to completion. Ask who controls the current version, who records customer approval and what document governs the crew in the field.
The questions apply whether a firm is choosing an accountant, printer, contractor or sign installer. A business comparing custom outdoor signs in O'Fallon, for example, should retain the chosen specifications and approved proof alongside the invoice and completion photographs. The file should show the work ordered, not merely the product category purchased.
Separate discovery from evidence
Traffic figures can show that people and automated systems reached a publication. They cannot prove why those visits occurred. The American Packet records 2,719 page views, 1,284 visitors, 1,488 search crawls and 3,706 AI crawls. There is no query or lead data confirming an interest in signage.
That distinction matters in every business record. A count is not an explanation. Website visits do not establish purchase intent, just as a calendar entry does not prove that work was completed. Label each item for what it actually shows.
Protect sensitive records
Not every document belongs in the general project folder. Tax information, health details, account credentials and personnel records require tighter access. A business compiling local resource information, including PTSD treatment near St. Peters, Missouri, should not mix an employee’s private circumstances into ordinary vendor notes or shared marketing files.
Access should follow responsibility. The people who must review a proof may not need banking information. The person paying an invoice may not need confidential background material. A short access list is easier to defend than a shared folder open to everyone.
Close the file without erasing its history
At completion, add the final invoice, proof of payment, warranties, photographs and a note identifying unresolved items. Mark the project closed, but do not rewrite earlier documents or alter their dates to make the sequence look cleaner.
An honest file may contain mistakes, rejected drafts and changed minds. That is not a weakness. It is evidence that the record reflects events as they happened. For a small business, that dependable chronology is one of the cheapest safeguards it can maintain.