M&A Due Diligence: Financial Records and Legal Risk

Set the Acquisition Scope

Define what the buyer proposes to acquire before issuing the document request. Record whether the transaction concerns shares, selected assets or a business. Identify every entity and jurisdiction involved. Describe what must remain available after completion, such as premises, customer contracts, intellectual property or working capital.

Agree the financial periods, materiality thresholds and reporting deadline with the buyer. Include issues that deserve escalation regardless of value, such as disputed ownership or access to customer data. Record excluded entities, unavailable records and any reliance on sampling so the final report matches the agreed work.

Allocate the legal, accounting and tax workstreams separately. Give technical, employment, privacy and valuation questions to specialists where the target requires them. Commercial due diligence examines the business assumptions behind the purchase, including customer concentration and demand. Its findings can change which contracts and receipts the legal and financial teams investigate.

Name one coordinator who can resolve overlaps. Also identify who can authorise access to bank statements, employee information and commercially sensitive records. Agree confidentiality arrangements and restricted access before the seller supplies that material.

Build the Document Request and Issue Register

Build an M&A due diligence checklist that records why each document is needed and what question its reviewer must answer. Use the following categories as a starting point, then tailor them to the proposed acquisition.

Acquisition records checklist

For every request, record its identifier, purpose, seller contact, reviewer and due point. Add the response status and source location, then link any unresolved question to an issue entry. Distinguish “received” from “reviewed” and “resolved”. An uploaded contract closes the document request only after someone checks that it answers the request.

For a technology company, extend the M&A technology due diligence checklist to outsourced development and dependencies on third-party systems. Ask who owns the code and which rights let the target use it. Allocate system reliability and security testing to the technical team, while lawyers examine the supporting rights and obligations.

Assess legal due diligence software by following one request through its full history. Can the team connect the request to the received source, reviewer, open issue and seller’s response? Check access restrictions, version history and export of a usable handover. Legal and financial reviewers still decide what the records establish and whether a response resolves the issue.

Review Ownership, Contracts and Liabilities

Review ownership and obligations against the transaction structure, then identify anything that could prevent transfer or change the purchase economics. Begin with the correct legal entities. The Australian Securities and Investments Commission (ASIC) provides searchable registers, including company extracts and officeholder information. Compare the relevant extract with the company’s own records and transaction documents.

Read each material contract’s assignment and change-of-control provisions. A share acquisition and an asset acquisition can trigger different clauses in the same agreement. Record the clause, affected party, required action and consequence if consent is refused. Keep the detailed contract review with the lawyer responsible for that workstream.

Search the Personal Property Securities Register (PPSR) using the organisation search guidance. The correct identifier depends on the organisation. The search only returns registrations against the identifier entered, and the guidance explains situations requiring additional searches. Retain the search criteria and certificates with the diligence file.

Investigate a registration against the underlying security documents and secured party’s response. Record which assets it concerns and the release arrangements proposed for completion. A registration alone does not give the outstanding debt balance.

Review related-party arrangements for payments, guarantees, loans and terms that may end when ownership changes. Link a claimed liability to its contract, correspondence or other source. Keep management’s explanation in a separate field from the evidence supporting it.

Treat regulatory approvals as a separate legal workstream based on the actual buyer, target and transaction. Assign responsibility for deciding which regimes apply and recording any approval conditions. The request list must reflect that assessment before the team advises that completion can proceed.

Test Financial Claims Against Source Records

Test financial claims by reconciling the relevant bank movements with the ledger and the documents explaining each transaction. Start with account ownership and statement coverage. Missing accounts or periods change what the financial reviewer can conclude about the supplied records.

Trace sales receipts to customer records and receivables. Separate customer payments from loan proceeds, internal transfers and refunds. Match debt-service payments to facility statements, and investigate differences between actual payments and the repayment schedule. For related-party transfers, identify both ends where records permit and request the agreement or ledger entry explaining the payment.

Hypothetical Cash-Receipt Reconciliation

Assume management describes $240,000 of bank credits for a review period as customer receipts. The supplied statement credits reconcile as follows.

The arithmetic reconciles: $180,000 + $40,000 + $20,000 = $240,000. Only $180,000 is supported as customer payments in this illustration. The accountant must determine the accounting treatment and whether other records explain any further revenue. Bank credits alone do not establish sales revenue or profit.

If a transfer remains unexplained, retain its amount, description and source page, then request the receiving record or supporting agreement. A transaction exception identifies a question for investigation. A finding of fraud requires evidence of the alleged conduct beyond an unusual payment. Use asset tracing where the review needs to follow disputed money beyond the initial transfer.

FinTrace saves the financial team hours of statement conversion and review by consolidating supplied PDFs into a searchable ledger and source-backed findings report. It flags suspicious transactions and follows transfers across accounts, with the PDF filename and page behind each finding. Forensic accountants can use those outputs to focus on interpretation and the acquisition’s financial questions.

Refer accounting treatment to the accounting workstream, tax consequences to tax advisers and value implications to the valuation specialist. Keep each specialist’s conclusion distinct from the observed bank movement.

Report Issues That Change the Deal

Report each red flag through the assertion tested and the decision it affects. An issue entry needs the supporting evidence, remaining uncertainty, commercial consequence and proposed response. Add its owner and the point by which the buyer needs an answer.

For the hypothetical reconciliation, a useful entry would say that management’s $240,000 customer-receipt assertion includes a matched $40,000 internal transfer and $20,000 loan advance. It would identify the supporting files and ask the accounting team to assess the effect on the buyer’s financial assumptions. The report must preserve the difference between the verified receipt classification and any unresolved effect on the deal.

Connect proposed responses to the issue they address. An unresolved consent may call for a completion condition. A verified historical exposure may inform a proposed indemnity, while uncertainty about an assertion may affect warranty negotiations. Financial findings may support a price adjustment or a revised purchase structure. The buyer may stop if the remaining exposure exceeds its tolerance.

The transaction lawyer must assess each response against the evidence and negotiated agreement. Record who accepts the remaining risk and why, including any dependency on further documents. Generic clause wording cannot settle whether a proposed remedy addresses this acquisition’s issue.

Close Outstanding Work Before Completion

Close the diligence file by checking every request and issue against the agreed acquisition scope. Give each unresolved item a named workstream owner, required response and escalation point. If access remains restricted, describe the unanswered question and the buyer’s decision about proceeding with that gap.

Check that the retained file contains the reviewed source versions, search certificates and material responses. Reconcile the final issues report with the completion checklist so required consents and release arrangements have someone responsible for obtaining them. Carry continuing obligations into the post-completion action list, including their owner and evidence of completion.

The handover must let the next reviewer find the evidence and understand the decision without reconstructing the data room. Before advising the buyer to proceed, confirm that each material issue is resolved, addressed in the transaction or expressly accepted by the authorised decision-maker.