Identification
Legal business name, DBA, EIN, and entity type so reviewers can confirm tax and corporate identity against public records and payer systems.
A well-prepared Business RDQ Document reduces downstream review time, lowers legal and financial risk, and creates an auditable record for compliance obligations under ESIGN and UETA. It clarifies responsibilities, supports tax and regulatory reporting, and standardizes data collection across stakeholders.
The Business RDQ Document is used by compliance, procurement, legal, finance, and business development teams to verify the facts and authorizations necessary to do business.
Responses should come from an authorized representative with the knowledge and authority to bind the organization; follow your internal signature policy.
Responsible for confirming regulatory answers and attestations on behalf of the business, ensuring statements reflect current controls, and coordinating any required follow-up documentation or remediation.
Person with delegated authority to bind the company (e.g., CFO or Director). Signs attestations, confirms tax identifiers, and accepts legal terms; their signature triggers reliance on the document by counterparties.
Legal business name, DBA, EIN, and entity type so reviewers can confirm tax and corporate identity against public records and payer systems.
Name, title, contact details, and evidence of signing authority; this allows reliance on attestations and links the response to a responsible person.
Yes/no and narrative fields for conflicts of interest, litigation, regulatory actions, sanctions, and insurance coverage that materially affect the relationship.
Tax classification, W-9 data when required, backup withholding status, payment terms and remittance instructions to reduce tax and payment processing delays.
Attestation language for truthfulness, data accuracy, and consent to electronic records consistent with ESIGN and applicable state law.
Signing timestamps, IP address, and audit record to support non-repudiation, regulatory review, and internal governance procedures.
| Field Mapping | Map RDQ fields to your CRM and document template |
|---|---|
| Signer Order | Sequential or parallel routing options |
| Authentication Method | Email link, SMS code, or KBA |
| Attachments | Require specific file types and size limits |
| Retention Rules | Auto-archive signed RDQs to records system |
Use an eSignature platform that supports required authentication, audit trails, and integrations to your core systems.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial, no credit card | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
Provide on request; needed before payment setup
Recipient: Jan 31; IRS electronic: Mar 31
Retain 3 years after hire or 1 year after termination
Enter MM/DD/YYYY; many obligations begin that date
Supply current certificate before work begins
Optica used a standardized RDQ to collect vendor disclosures rapidly
A real estate operator used an RDQ to gather contractor attestations on insurance and tax status