Practical FAQ guide · Published October 25, 2026

How to Reconcile Conflicting Business Acquisition Records Before Making a Decision

A business acquisition review often contains several descriptions of the same fact. A presentation may show one customer count, an operating report another and a seller conversation a third. The discrepancy may reflect timing, definitions, scope or an actual error. This guide proposes an evidence-conflict register that helps a buyer and advisers investigate differences without silently choosing the most attractive number. It is a document-review method, not a valuation, financing recommendation or substitute for professional diligence.

Use the method within the access and confidentiality arrangements governing the transaction. Record only information the team is authorized to review and share. The examples below are fictional and do not describe a completed acquisition. The purpose is to identify what is known, what conflicts, who should clarify it and which decisions depend on the answer. A well-organized register does not prove a business is worth buying; it makes unresolved questions harder to overlook.

What counts as a conflict between acquisition records?

A conflict exists when two records appear to make incompatible statements about a material fact. The first task is to confirm that they are actually describing the same thing. One report may count active accounts at month-end while another includes every account billed during the year. Those figures can differ without either being wrong. Record the definitions before describing the difference as a misstatement.

Distinguish a missing record from a contradictory record. A missing lease schedule creates an evidence gap; two incompatible lease schedules create a reconciliation question. Both may matter, but they require different requests. The register should preserve that distinction and avoid allegations about intent. Its role is to guide investigation and decisions using documented facts, not to turn every ambiguity into an accusation against the seller.

Where should a buyer start?

Choose a small set of decision-relevant facts rather than comparing every sentence in the data room. Start with the business model, ownership scope, customer relationships, operating dependencies and records your advisers identify as important. Write the question in plain language. For example: Which customer accounts are included in the seller's description of recurring revenue? A clear question makes the document request more precise.

The SBA's buying-an-existing-business material encourages examining the business and its records as part of diligence. That broad principle does not tell a buyer how to resolve a particular discrepancy. Use the source as background, then work with qualified advisers on the transaction's actual facts. This guide's register is an original organizational aid; it is not an SBA-approved checklist or a representation that every required review is covered.

What belongs in the evidence-conflict register?

Use fields for issue ID, decision question, record A, record B, source locations, applicable dates, definitions, apparent difference, clarification owner, requested evidence, response and resolution status. Add the decision that depends on the answer. Without that last field, the register can become a list of interesting inconsistencies that nobody knows how to prioritize.

Keep document identifiers stable even when files are renamed. Record the version or delivery date and the location of the relevant passage, table or row. Do not paste sensitive source material into an unrestricted spreadsheet simply for convenience. The register should help authorized reviewers find evidence in its approved location. If the review platform changes, retain enough information to understand which version supported the question and whether it was later superseded.

How do you determine whether dates explain the difference?

Compare the period each record covers, its preparation date and the date the underlying information was effective. These are different attributes. A report prepared in April can describe March activity; a presentation delivered in June can reuse an earlier snapshot. Ask for the source period rather than assuming that the newest filename contains the newest facts.

Build a short timeline when timing may explain the conflict. Note intervening events such as a new customer, an ended contract or a reporting change, using supporting records rather than inference. If the difference is explained by dates, preserve the explanation and specify which period is relevant to the decision. Do not delete the issue merely because one number is newer; a historical change may itself matter to the buyer's understanding of operations.

How do definitions create apparent contradictions?

Words such as customer, recurring, backlog and active can carry different meanings across reports. Ask who produced each report and which inclusion rules were used. A count of legal customer entities differs from a count of service locations. A list of signed work differs from a forecast of likely work. The reconciliation begins by describing those categories accurately.

Write the definition beside each figure. If no definition is available, mark it unknown and request one. Avoid inventing a definition that makes the figures match. A clean spreadsheet is not a useful outcome if it conceals an unsupported assumption. The team may need to restate figures using a common definition, but the adviser responsible for the analysis should determine the appropriate treatment and preserve the original data.

What is a worked example involving customer counts?

Imagine a fictional service business. Its presentation lists 120 customers, while an operating export contains 95 accounts marked active. The buyer records both sources and asks what each count includes. The seller explains that the presentation includes accounts served at any point during the prior year, while the export shows accounts active on a specific date. The explanation identifies a definition and timing difference; it does not by itself establish retention or future revenue.

The next question is what decision the buyer was trying to make. If the concern is workload at transfer, current service commitments may be relevant. If the concern is customer continuity, the adviser may request a different analysis. The register should link the clarification to the appropriate follow-up instead of claiming that the original discrepancy is evidence of fraud or that the larger number is the correct investment assumption.

How should a clarification request be written?

State the two records, their locations and the apparent difference. Ask for the definition, period and underlying evidence needed to reconcile them. A neutral request might say: These files show different account counts. Please identify the inclusion rules and dates for each and provide the source supporting the current active-account schedule. Avoid a broad message saying the numbers do not add up without identifying what needs explanation.

Group related questions only when they depend on the same source. A long request mixing customer counts, equipment ownership and employment matters can delay answers because different people hold the information. Give the seller or intermediary a clear response format and track unanswered items. Keep the request within the transaction process and access arrangements rather than contacting employees, customers or suppliers independently without appropriate authorization.

Who should decide which discrepancies matter?

The buyer should coordinate the register with the advisers responsible for financial, legal, tax and operational review. The person who notices an inconsistency may not be qualified to determine its significance. Record the observation, affected decision and proposed reviewer. Avoid assigning a definitive legal or accounting conclusion based on a document comparison alone.

Use practical priority descriptions rather than invented precision. An issue may block a current decision, require specialist review or be an explanatory difference with no immediate action. Those categories should reflect actual transaction needs. A small numerical discrepancy can be important if it concerns an essential operating permission, while a larger apparent difference may be explained by scope. Let evidence and the responsible review process guide the next action.

What if the seller provides a new file instead of an explanation?

Save the new version with its delivery date and ask what changed. A replacement file can resolve a question, but it can also make the historical comparison harder to understand. Identify which rows, periods or definitions differ and whether the prior file should be treated as superseded. Do not silently overwrite it in the working folder.

Record the explanation alongside the new source. If the response does not answer the question, keep the issue open. A fresh filename is not resolution evidence. The team should be able to explain why the current record is used and which decision it supports. If a later adviser reviews the issue, they should not have to reconstruct the sequence from scattered emails or assume that every version represented the same scope.

How should conflicting contract descriptions be handled?

Separate a summary of a contract from the contract itself and from a legal interpretation. A seller presentation may use shorthand that omits conditions, expiration or required consent. Record the exact document versions and ask the qualified legal reviewer to assess the relevant provisions. This guide does not determine transferability, enforceability or the meaning of a specific agreement.

The register can still help the team coordinate. List the operating dependency, the documents received, the unresolved question and the person responsible for the legal review. Track whether the operating plan assumes an outcome that has not been confirmed. Do not mark an issue resolved merely because a salesperson or assistant paraphrases the agreement confidently. The substantive conclusion should come from the appropriate review and be recorded in terms the transaction team can use.

How can AI assist without becoming the decision-maker?

An assistant can extract candidate differences, organize source references and propose clarification questions from authorized materials. Require it to distinguish direct statements from interpretations. Ask for the relevant passage or row location and review the output. It may compare documents incorrectly when tables, units or definitions change, so a polished reconciliation should remain a draft until checked.

Do not ask the model to decide whether the acquisition is safe, identify a guaranteed adjustment or infer missing financial data. Keep calculations reproducible outside a narrative answer. When sources are incomplete, the assistant should label the limitation rather than supply a plausible explanation. Its useful role is to make questions and evidence easier to inspect, not to replace the buyer's advisers or certify the seller's records.

What prompt helps identify document conflicts?

Use a task such as: Compare only the supplied records for statements about the named decision question. Return source IDs, dates, definitions, matching facts, apparent differences and unanswered questions. Do not assume differences are errors. Do not choose a preferred figure without supporting evidence. Keep legal, tax and financial interpretations in a separate specialist-review column. List passages that could not be read reliably.

Test the instruction using a fictional pair of records with a known timing difference and a genuinely unresolved contradiction. Check whether the output preserves both categories. Save failure examples for later review when the prompt or tool changes. A prompt that produces more confident conclusions is not necessarily better; the task needs careful uncertainty and traceable source locations.

What should a reconciliation meeting accomplish?

Choose the decisions that need clarification and circulate the corresponding issue rows in advance. During the meeting, confirm definitions, identify missing sources and assign the next evidence request. Do not use the time to read every data-room file aloud or debate an unsupported interpretation. Keep the distinction between a factual clarification and a negotiated transaction term visible.

End with an issue-by-issue status and owner. A participant saying that a matter should be fine is not the same as receiving the requested evidence. Record commitments accurately and return the relevant rows to the responsible adviser. The meeting succeeds when it reduces ambiguity and advances defined reviews, even if some questions remain open. It should not manufacture consensus to keep a timetable looking on track.

How do you avoid requesting the same information repeatedly?

Maintain one request identifier and link related issue rows to it. Before sending a question, check whether a prior response, source delivery or adviser workstream already addresses it. Duplicate requests create confusion when different people receive different versions of the answer. A shared request log helps the team coordinate without giving everyone access to information they do not need.

When a response is incomplete, refer to the original request and specify what remains unanswered. Avoid restarting the conversation with a broader, less precise question. If the transaction uses an intermediary or formal communication channel, follow it. Coordination is part of diligence quality: a buyer can be thorough without generating disorganized demands that obscure which facts are genuinely unresolved.

What does a resolved issue look like?

A resolved row explains the difference, identifies supporting evidence, records who reviewed it and states the effect on the relevant decision. It can conclude that the difference was definitional, that a source was corrected or that an assumption must change. Resolution is not always agreement with the seller's original presentation. It is a documented conclusion reached through the appropriate review.

Some issues remain unresolved when a decision must be considered. Record that status honestly and route it to the buyer and advisers. Do not rename unresolved as accepted merely to close the spreadsheet. The decision-maker needs to understand the remaining uncertainty and determine its treatment through the transaction process. This guide does not prescribe whether to proceed, renegotiate or stop; it supports an informed discussion of those choices.

How should a buyer handle changing assumptions?

Keep an assumption register linked to the evidence-conflict log. Record the current assumption, source, decision owner and conditions that would change it. If new information arrives, update the working analysis through the responsible process and preserve the reason for the change. Do not let a spreadsheet cell change silently while presentations continue to repeat the earlier conclusion.

Distinguish an analytical input from a verified fact. A planning assumption can be useful when labelled and tested appropriately, but it should not become a seller representation by repetition. When the team discusses an outcome, state which inputs remain uncertain. The register is particularly useful when several advisers work at different times because it shows which version of the business description each analysis relied on.

How does the register connect to transition planning?

Some discrepancies reveal operating dependencies that matter after a purchase: a process known only to the owner, a supplier arrangement described informally or an incomplete equipment list. Record the dependency and the review owner without assuming that the transaction will close. If the buyer proceeds, the verified findings can inform a transition plan through the appropriate advisers and agreements.

Do not copy every diligence issue into a day-one checklist without interpretation. Some are historical, some are resolved and some require negotiated treatment rather than an operational task. Link the transition item to the source conclusion and name the person responsible for implementing it. This preserves context and prevents a vague note such as check supplier issue from becoming the only instruction passed to the new operating team.

What should the first weekly review measure?

Review open decision-blocking questions, aging requests, received evidence awaiting review and rows marked resolved without closure evidence. Count consistently, but do not treat fewer open rows as proof of a better acquisition. A team can close issues prematurely, and a careful review can discover new questions. Discuss the substance and effect on decisions alongside the counts.

Record which workstreams were not reviewed and which advisers still need to respond. A dashboard should not imply complete diligence when it covers only selected operating records. Use the meeting to remove coordination obstacles and clarify responsibility. The purpose of measurement is to keep the review usable, not to create a performance target that encourages people to suppress uncertainty or convert every question into a green status.

FAQ: Does a discrepancy prove the seller is dishonest?

No. Differences may reflect dates, definitions, scope, preparation errors or incomplete context. Investigate and document the explanation before drawing conclusions. At the same time, do not accept an unsupported explanation simply because it sounds plausible. The register should preserve the evidence and unresolved questions in neutral terms so the appropriate reviewers can assess them.

If the circumstances raise a concern about misrepresentation or another legal issue, consult the relevant adviser through the transaction process. An AI comparison or this editorial guide cannot determine intent or legal liability. The useful first step is a precise description of the conflicting records and why the answer matters to a decision, followed by an authorized request for clarification.

FAQ: Should the buyer use the highest or lowest figure?

Neither is a universal rule. First establish what each figure measures, which period applies and which source supports the question being analyzed. Choosing the lower number may look conservative while still being conceptually wrong. Choosing the higher number may conceal a scope difference. The responsible analyst or adviser should determine how a verified figure enters the analysis.

Keep original figures, restatements and planning assumptions separate. If the evidence cannot support a common definition, record the limitation and request the missing information. Do not average conflicting numbers merely to produce a tidy answer. A reconciled explanation is more useful than a single value that has lost its source, conditions and relationship to the actual decision.

FAQ: Can this process replace a quality-of-earnings review?

No. The register organizes questions and evidence; it is not a professional accounting engagement or a substitute for specialist diligence. It does not verify earnings, tax treatment, contracts or valuation. Use it to prepare better questions and coordinate the work the buyer and advisers determine is necessary for the particular transaction.

Keep the scope statement visible when sharing the worksheet. Someone receiving a completed register should not assume every financial or operating issue has been examined. Record which areas the team covered, which were excluded and where professional conclusions are documented. Clear scope helps a useful organizational tool remain useful without being promoted into a certification it was never designed to provide.

FAQ: When is outside implementation support relevant?

Consider process support when the team repeatedly loses track of requests, versions or responsibility despite having appropriate professional advisers. Bring a sample issue register, the communication workflow and the specific coordination problem. Separate document organization from substantive legal, accounting and tax judgments so that each provider's responsibility remains clear.

Elixir Consulting Group is the author's consulting firm. A link to its operations service is contextual information about potential process support, not an independent endorsement or a promise that it can resolve every acquisition issue. Review scope directly. You can use the blank register internally and with your existing advisers without engaging an additional service. The right next step follows the unresolved task, not the existence of another link.

Use the editable worksheet

Download the blank evidence-conflict register. Add your own authorized records. Empty fields are not conclusions, and the template does not replace the responsible review.

Sources and editorial scope

Primary sources checked October 25, 2026. The proposed workflow, worksheet and fictional examples are original editorial material; linked organizations do not endorse this method. Review current guidance and the circumstances of your business.

This guide was prepared with AI assistance and checked for source attribution, internal consistency and publication requirements. It does not claim professional review or a demonstrated client outcome.