What should a buyer request, and why?
Start with the deal, entities, services, jurisdictions and access limits. Give each request a decision to test. Files alone cannot show which question is resolved.
The buying hub frames the process; the diligence guide develops investigation. Name evidence, reviewers and response standards. Check whether the answer supports the intended decision.
Record the team, date and scope. Keep files in the approved repository. Match access to purpose, with personal detail limited to the authorized reviewer.
These items propose a workflow. Actual lender, legal, tax, regulator and technical reviews may need other periods or records. Obtain their instructions first.
Which fields turn requests into a usable register?
Give requests stable IDs linked to questions. One file can serve several items. Record scope and version rather than request duplicate uploads.
| Field | Entry to make | Review consequence |
|---|---|---|
| Request ID | Unique reference and category | Follow-up remains traceable |
| Decision | Question the evidence must answer | Prevents collecting without purpose |
| Scope | Entity, dates, service line, and population | Avoids mismatched comparisons |
| Format | Readable file and relevant source settings | Supports analysis and reproduction |
| Recipient | Authorized reviewer and access limit | Protects sensitive records |
| Response criterion | What would answer the question | Separates receipt from adequacy |
| Follow-up | Owner, open issue, and next date | Keeps unresolved dependencies visible |
Use missing, received, clarification needed, accepted for this purpose, outdated or blocked. A readable file can still cover the wrong entity or dates.
Acceptance is purpose-specific. A statement may prove one receipt but leave revenue recognition or the wider period unresolved. Keep that limit visible.
Which eight evidence requests should be specified?
- Request a financial reconciliation package.
State entities and periods needed by the reviewers. Get statements, returns, ledgers and bank or merchant support, with comparable interim dates where relevant. Ask for reconciliation and unexplained differences. A seller's summary can guide the inquiry. It cannot replace proof connecting reported earnings with source transactions, necessary roles and the adjustments proposed for review.
- Request defined job and contract populations.
Define completed and open jobs, services, costs, payer concentration, deposits and continuing promises. Put dates and status definitions beside totals. Obtain relevant contracts through controlled access. A total without its included records cannot show consistent treatment of work, credits or duties. Explain exclusions and review the same population before comparing revenue and future completion cost.
- Request payroll and worker-control facts.
Specify payroll dates, roles, pay, tax records and time or payment proof. Review real supervision, schedules, tools and financial control within personal-data limits. Federal tax, wage, state and coverage tests need separate review. A payment label cannot settle them all. Give counsel the actual work facts and keep conclusions scoped to the test applied.
- Request operating-authority evidence.
List firms, credential holders, qualifier ties, trades, jurisdictions, registrations and permits. Get required notices, accepted approvals and the future continuity route. Track missing regulator responses separately from uploaded licenses. A current certificate cannot authorize a new person or entity by itself. Check the actual scope and effective date before the buyer relies on the proposed role.
- Request asset and premises records.
Get titles, leases, liens, maintenance, equipment, stock and property-use records. Match them to purchased assets. Assign title, condition, consent and environmental questions to appropriate specialists. Depreciation or an equipment list can identify an item. It cannot prove ownership, clearance, condition or unrestricted transfer. Record missing proof and the operating consequence before accepting asset readiness.
- Request systems and data-control evidence.
Get report definitions, filters, account owners, user roles, provider contracts and access or retention limits. Test evidence flow with authorized samples. Keep passwords out of the request list. A readable export may answer a reporting question. It cannot prove that the whole system or customer database transfers, or that the buyer may lawfully use every record.
- Request financing-purpose evidence separately.
Name the lender, category, dates, equity sources, valuation and independent QoE needs. Get scope and reliance instructions through the authorized team. Separate seller-readiness work from lender-benefit reports. A proposed funding schedule is not loan approval. Track the lender's accepted evidence and remaining conditions before assuming that the buyer has funds available to close.
- Request a targeted response to each exception.
For mismatched balances, dates, consents or roles, state the exact open question. Name the reviewer, required proof and next dependency. A reply alone cannot close it. Preserve original files and corrections so later decisions remain traceable. Record whether the response answers the stated purpose and which related comparisons need further review before acceptance.
Which primary sources help scope these requests?
IRS Publication 583 explains transaction support. It gives no universal acquisition period or request list. Ask the reviewer what evidence this decision needs.
The IRS worker guidance covers real control and relationships for federal tax. It cannot settle all wage, state, unemployment or insurance tests. Assign separate reviews.
California's entity-change guidance illustrates that state's routes. Check actual jurisdictions. One process cannot authorize every branch, person or service in a multi-state deal.
The FTC guide supports limited access and secure handling. Neither a request nor an NDA creates automatic rights to every personal record.
EPA's inquiry guidance has defined property scope. The property guide develops that review. Identify premises, lender purpose and specialist before deciding required evidence.
How should lender requests remain distinct from general diligence?
Current SBA policy separates acquisition categories. Initial Acquisition and Business Expansion have a mandatory lender-benefit QoE trigger at $3 million defined Business Purchase Price, with stated exceptions. Ask the lender which category and review apply.
Measure that defined basis before equity and financing; exclude appraised owner-occupied commercial real estate. The required report must be independent and not prepared by or for the seller. Preserve those conditions when asking for report evidence.
The SBA acquisition guide covers wider rules. Get lender category, scope, records and reliance instructions. A seller report cannot satisfy every independent lender-benefit requirement.
Valuation and property records have specific purposes. Use separate IDs for buyer review and lender conditions. Acceptance for one question cannot resolve every use.
What does a worked exception follow-up look like?
Assume a hypothetical export has 600 jobs and the seller summary has 500 completed jobs. Ask whether 100 records are canceled, open or another status. Either count could be correct for its stated scope.
Request same-date data, status definitions and a reconciled count. Seek a traceable population explanation. Another unexplained screenshot cannot answer which jobs the first total included.
Reopen revenue review if filters differ. A corrected count cannot settle all earlier conclusions. Check changed records, their totals and which reviewer must reassess the comparison.
Use the financial guide to interpret results and fleet guide for asset follow-up. Preserve each specialist's accepted scope and remaining limits.
How should the request cycle progress?
- Agree the decision, scope, authorized recipient, and required evidence.
- Issue the request through the transaction's approved process.
- Mark receipt and verify that the file opens and covers the intended population.
- Have the assigned reviewer assess adequacy and record exceptions.
- Accept the stated purpose or assign a targeted follow-up with a next date.
The buyer licensing guide assigns authority questions. Actual lender, contract, agency and adviser dependencies govern timing. A presumed duration cannot guarantee proof or approvals.
How should the list be printed and used?
Print checks and use a separate register for IDs, versions, recipients, status and findings. Record scope and date. Link decisions to the exact proof reviewed.
Print keeps explanations together where practical and removes navigation. Leave sensitive proof in controlled files. The request sheet's scope and notes can also be confidential.
Which mistakes make a request list ineffective?
Avoid purposeless requests, mismatched dates, receipt mistaken for acceptance and unsupported resolution of conflicts. Check the question before changing status. Name the next reviewer for open limits.
A financing request cannot establish approval. Make missing proof and its closing effect clear. Assign the follow-up to someone, with a due date based on the actual requirement.