What is Due Diligence Request List?

Definition

A Due Diligence Request List is a structured list of documents, data, explanations, and evidence requested from a company or counterparty during a due diligence review. It establishes what information the review team needs to assess financial performance, operations, legal matters, tax positions, commercial relationships, technology, and other areas relevant to a transaction or business decision.

The list functions as a working framework between the requesting and responding parties. Each request can have an owner, due date, status, priority, and supporting documentation. A well-designed list helps reviewers obtain consistent evidence while giving the target organization a clear understanding of what must be provided.

Table of Contents

How a Due Diligence Request List Works

The process typically begins by defining the purpose and scope of the diligence exercise. The review team then organizes requests by workstream and identifies the information needed to test assumptions, validate financial results, understand obligations, and evaluate business performance.

Requests are commonly submitted through a secure data room or document-sharing environment. The target assigns responsible stakeholders, uploads relevant materials, and responds to clarification questions. Reviewers examine the submissions, identify gaps, and issue follow-up requests where additional evidence is needed.

The list should remain a controlled record throughout the review. Status categories such as requested, in progress, provided, under review, clarification required, and complete can make progress visible and help teams focus on unresolved matters.

Key Categories of Requests

  • Financial: Request audited and management financial statements, trial balances, general ledger details, budgets, forecasts, debt schedules, working capital data, and cash flow information.
  • Tax: Collect tax returns, assessments, correspondence, exemptions, indirect tax records, and documentation supporting jurisdictional positions.
  • Legal: Review material contracts, litigation, intellectual property, corporate records, licenses, permits, and regulatory matters.
  • Commercial: Examine customer concentration, sales pipelines, pricing arrangements, market information, major contracts, and revenue dependencies.
  • Operations and technology: Request information about systems, processes, infrastructure, cybersecurity controls, personnel, and key operational dependencies.
  • Procurement and suppliers: Collect sourcing information, approvals, supplier agreements, purchasing records, and spend documentation.

For procurement-related diligence, a purchase requisition can help establish how internal demand moves into sourcing and approval workflows, while a purchase order provides evidence of authorized commitments, supplier terms, and procurement controls.

Financial and Accounting Evidence

Financial requests should be designed to connect reported results with underlying records. Reviewers may request reconciliations, journal entries, revenue schedules, accounts receivable and payable aging, inventory reports, fixed asset registers, accrual schedules, and supporting contracts. These documents help validate whether reported financial performance reflects the underlying economics of the business.

Month-end accounting evidence can be particularly important. Requests concerning accrual discovery, estimation, booking, reversal, GRNI, cut-off, and expense recognition should capture the supporting calculations and gl coding used to record the relevant amounts. This creates a clearer audit trail between operational activity and reported financial results.

Tax documentation also deserves specific attention. Review teams may examine jurisdiction rules, nexus, exemptions, VAT or GST treatment, and invoice-level sales tax validation to identify potential overcharges or audit exposure. The request list should specify the periods, entities, jurisdictions, and supporting evidence required rather than using broad requests that create ambiguity.

Managing Data, Systems, and Evidence

A due diligence request list becomes more effective when every request has clear ownership and a defined evidence standard. The requesting team should specify whether it needs an original agreement, report extract, reconciliation, management explanation, or other form of documentation.

Where financial systems are relevant, the Integrations List page can provide context on how Hyperbots integrates with leading ERP systems such as SAP, Oracle, and QuickBooks for secure data exchange and process automation. Understanding system connectivity can help diligence teams identify where source information resides and how financial data moves between applications.

Consistent naming conventions, version control, access permissions, and document indexing also improve traceability. These practices make it easier to connect a finding in the diligence report to the specific evidence supplied in response to a request.

Common Request Tracking Practices

A request should be specific enough for the recipient to understand exactly what is required. Instead of requesting “financial information,” a stronger request might specify monthly management accounts for a defined period, supporting trial balances, reconciliation schedules, and explanations for material variances.

Useful tracking fields include request number, category, description, responsible owner, priority, requested date, response date, status, reviewer, and follow-up notes. A structured Request List creates visibility into outstanding information, while an Information Request List provides a broader framework for organizing information needed across multiple diligence workstreams.

Each individual Due Diligence Request should also be traceable to the question it is intended to answer. This prevents unnecessary document collection and helps reviewers understand why a particular record matters to the transaction or business assessment.

Best Practices for Building the List

  • Start with the decision objective: Align every major request with valuation, transaction structure, financial assessment, compliance, or operational analysis.
  • Use clear ownership: Assign each request to a responsible person or function on both the requesting and responding sides.
  • Define periods and entities: Specify fiscal years, reporting periods, legal entities, jurisdictions, and business units where relevant.
  • Prioritize material items: Identify requests that directly affect earnings, cash flow, working capital, debt, tax exposure, or transaction terms.
  • Track follow-ups: Record clarifications and additional evidence requests against the original item to preserve context.
  • Close requests with evidence: Mark an item complete only when the supplied information answers the underlying diligence question.

Summary

A Due Diligence Request List provides the operational structure for gathering and tracking evidence during a financial, commercial, legal, tax, or operational review. By organizing requests by workstream, assigning ownership, defining evidence requirements, and tracking responses, it helps diligence teams develop a complete and traceable understanding of the business. A disciplined request list ultimately supports stronger financial analysis, transaction decisions, and business performance evaluation.