8 Reports You Can Send a Buyer Without Naming Anyone

Short answer

Eight reports can answer a buyer's real questions without naming a single customer, employee, or supplier, and the list is shorter and more useful than most owners expect. Concentration, margin, labor cost, contract risk, and pipeline all have name-free versions that are completely truthful. The work is in the accounting system, not in the judgment call, and it takes an afternoon once.

Most owners treat early disclosure as a nerve problem. Send it or do not send it. Trust the buyer or do not.

It is almost never a nerve problem. It is a reporting problem. An owner sends the named customer list on day four because the named customer list is the only revenue-by-customer report their system can produce, and the buyer asked a fair question that the report happens to answer. Nobody made a decision to over-disclose. The system made it for them.

A coded schedule is a financial report in which each counterparty is replaced by a label that stays attached to that same counterparty in every period you produce. Once those exist, the awkward conversation disappears, because you are no longer choosing between answering the question and protecting the relationship. You answer the question completely and you name nobody, and the buyer gets a better file than the one they asked for.

The No-Names Standard

Every counterparty schedule in your monthly reporting pack should exist in two versions produced by the same process, one with names and one with stable codes, and the coded version should be the default export.

Two requirements make that real, and skipping either one is worse than not doing it at all.

The first is persistence. The code map has to live in the accounting system, on the customer or vendor record, not in a spreadsheet somebody rebuilds each time a buyer asks. Customer C in March has to be the same company as Customer C in June. A buyer who spots a code that moved between periods does not conclude you were careless. They conclude the file was assembled to produce an impression, and every other schedule you sent gets re-read in that light.

The second is footing. Every coded schedule has to add up to the same total as the named version and to the corresponding line on the profit and loss statement. A coded file that does not foot is the worst of both outcomes: you gave up the information and you damaged your credibility doing it. This is the same discipline as the reconciliations covered in the tie-outs a buyer runs on your books, applied to a report rather than to an account.

Here is the build cost, on the assumptions stated in this sentence and nothing else. Assume 180 active customers and a bookkeeper who can tag a customer record with a code at roughly 40 records an hour. That is four and a half hours, once, after which every future export is coded automatically. Those are illustrative assumptions and not a benchmark for your business. The shape of the answer holds anyway: this is an afternoon of work that removes a decision you would otherwise make badly, under time pressure, with a buyer waiting.

The 8 reports, ordered by how early a buyer asks

The eight are ordered by how early in a conversation a buyer asks for them. The first three usually come up before anyone has put a number in writing, which is exactly when an owner is least prepared and most eager to look cooperative.

1. Revenue by customer, by month, with customers shown as codes

Revenue by customer is the first report a buyer asks for and the one owners most often send with names attached, because concentration is the first risk any buyer needs to size. A coded version answers it completely. Show each customer as a code, revenue by month for 36 months, first invoice date, and whether the relationship is under contract or at will. A buyer can compute concentration, tenure, churn, and trend from that file and cannot call anyone. Add an industry tag per code if your customers span sectors, since that answers the diversification question too. The takeaway: concentration is a shape, and a shape does not require names.

2. Gross margin by customer code and by service or product line

Margin by customer is the second question, because a buyer wants to know whether your largest accounts are also your best ones or whether you are busy at a discount. The coded revenue file becomes a margin file by adding direct cost per code and per line. What this exposes internally is often more useful to the owner than to the buyer: most owners have never seen margin by account, and the exercise routinely finds a top-five customer running below company average. Find that now, while you can still do something about it, rather than during diligence when it becomes a negotiating point. The takeaway: build this report for yourself first and the buyer version is a byproduct.

3. An anonymized payroll census by position

A payroll census by position gives a buyer everything they need about labor cost without producing a recruiting list. One row per position, not per person: role, department, tenure band, full-time or part-time, compensation, and whether that position is covered by a written agreement. Totals have to foot to wage expense in the general ledger, including payroll taxes and benefits as separate lines so a buyer can rebuild fully loaded cost. This answers bench depth, wage inflation exposure, and whether the business is thin in a critical function. Whether a buyer has agreed not to approach your people is a clause in the specific agreement you signed, so ask your attorney what yours contains. The takeaway: a buyer needs your labor cost structure, not your roster.

4. Supplier concentration as a percentage, without the agreements

Supplier concentration by percentage of cost of goods sold answers the dependency question without exposing your unit costs. Show each supplier as a code, spend by month, category, and whether you have an alternate source qualified for that input. That tells a buyer exactly what they need to assess: how exposed you are if one supplier fails or reprices. What it does not tell them is what you pay per unit, which combined with your prices would map your margin by line for anyone who later decides not to buy the business. The executed agreements are a later conversation. The takeaway: dependency is a percentage and your input pricing is not, so send the percentage.

5. A contract summary schedule instead of the contracts

A contract summary schedule answers the revenue durability question in one page: contract count, total contracted value, weighted average remaining term, renewal dates by quarter, how many agreements require consent on a change of control, and how many are terminable within 30 days. Counterparties appear as the same codes used in the revenue file, so a buyer can tie the two together. Whether any specific contract actually transfers depends on that contract's language rather than on any general rule, so the schedule should flag the consent question rather than answer it. Build it once and keep it current monthly. The takeaway: buyers need the terms in aggregate long before they need the documents.

6. Accounts receivable aging with customers coded

A coded receivables aging shows collection quality without showing who owes you what. Standard buckets, coded customers, days sales outstanding by month for at least 24 months, and a separate line for anything written off. This is one of the fastest credibility reports you can send, because a clean aging with a stable days sales outstanding trend answers a question buyers usually have to dig for. It also has to tie to the receivables control account on your balance sheet, and if it does not, fix that before you send either version. The takeaway: collection discipline is visible in the shape of the aging, and the shape does not need names.

7. Pipeline summary statistics instead of the pipeline

A pipeline summary gives forward visibility as statistics: total open value, opportunity count, distribution by stage, weighted value using your own historical conversion rates, and your realized win rate on bids from the prior 24 months. No prospect names, no individual bid amounts. This matters most in construction, trades, and professional services, where the open bid list is the business and the names in it are being actively competed for right now. The historical win rate is the part that carries the weight, because it converts the pipeline from a claim into a calculation a buyer can check against what actually closed. The takeaway: forward visibility is a statistic, and your bid list is not a statistic.

8. Referral and channel concentration by coded source

Referral concentration answers where new business comes from without naming the people who send it. Show new customers and new revenue by coded source per year, the percentage from the top three sources, and the commission or fee arrangement expressed as a rate rather than as a party. In a professional services or trades business this is frequently the single most concentrated relationship in the company and the one least visible in the financial statements, because a referral source appears nowhere on the profit and loss statement. Most owners have never quantified it. The takeaway: if you cannot produce this report today, the gap is a reporting gap before it is a disclosure question.

What to do with the named versions

Keep them, keep them current, and keep them out of the first export. The named version of every report above still gets produced by the same process on the same day, because a deal that reaches a signed letter of intent will need all of it, and a named file assembled under deadline is how errors get introduced into a record a buyer is actively verifying.

The decision about which version goes out and when is a process decision rather than an accounting one, and the sell-side advisor running your process should own it. Texas Exit Advisors covers that side in detail in which documents to hold back and when each one opens.

What the accounting function owes that process is simple: both versions, every month, footing to each other and to the general ledger, ready before anyone asks. An owner who has that never has to choose between looking cooperative and protecting a relationship, because the cooperative answer is already the safe one.

The short version

Over-disclosure is usually a reporting failure wearing the costume of a judgment failure. The owner who sends the named customer list on day four is not careless. They are working with the only report they have.

Build the coded versions once, tie them to the general ledger, keep the codes stable across periods, and the eight reports above answer nearly every early buyer question truthfully and completely. The named versions stay in the system for the buyer who earns them.

Where Thryve fits

Thryve Accounting & Advisory builds the reporting pack that produces both versions as a byproduct of a clean monthly close, so the coded schedules are current on the fifteenth of every month rather than assembled in a weekend after a buyer has already asked twice. That work includes the customer and vendor coding structure in your accounting system, the schedules themselves, the footing checks that keep them credible, and the add-back documentation that sits behind the earnings number the reports support.

If a buyer has already called, or if you are eighteen months out and want the reporting built before you need it, we can start with a look at what your current system can and cannot produce.

Last reviewed: September 2026. This is general information, not legal, tax, or accounting advice for your specific situation. The customer-coding arithmetic runs on assumptions stated in the sentence that carries it and is an illustration, not a benchmark. What your non-disclosure agreement permits and requires is set by the specific agreement you signed rather than by any general rule, so read it with your attorney. Whether a given customer contract transfers on a change of control depends on that contract's language.