Business Document to PwC
What a Business Document to PwC Is and when it’s used
Why a clear submission matters for PwC engagements
A well-prepared Business Document to PwC speeds review, reduces requests for supplemental materials, preserves an auditable signature trail under ESIGN (15 U.S.C. ch. 96) and UETA, and helps satisfy tax and regulatory recordkeeping obligations.
Who typically prepares and approves these submissions
Responsibility for preparing and signing a Business Document to PwC varies by engagement type and internal delegation of authority.
- Chief Financial Officer or Controller certifies financial accuracy and signs management attestations.
- Accounting or reporting manager assembles schedules, reconciliations, and source documents for submission.
- External tax advisor or legal counsel reviews specialized language and may sign engagement-specific declarations.
Define signatory authority in company policy and retain delegation documents with the submission to support PwC's review and any subsequent audit trail requests.
Authorized signers and their roles
CFO
The Chief Financial Officer commonly has authority to sign audit- or tax-related submissions and formal attestations. Where corporate bylaws require it, the CFO’s signature should be supported by board authorization or a written delegation of authority retained with the file.
Authorized Representative
An authorized representative (for example, Controller, VP Finance, or other designee) may sign routine submissions when a delegation exists. Include the delegation document so PwC can verify the signer's authority during review or audit procedures.
Step-by-step: preparing a Business Document to PwC
-
01Assemble: Gather financials, schedules, exhibits and source files.
-
02Validate: Reconcile totals, confirm footnotes, and verify cross-references.
-
03Authorize: Obtain required approvals and signatures according to delegation policy.
-
04Deliver: Submit via PwC intake method with clear file names and metadata.
Configuring an online submission workflow
| Field | Configuration |
|---|---|
| Template | Create reusable template with required fields and attachments |
| Authentication | Choose email link, SMS code, or stronger signer verification |
| Routing | Define signer order and conditional approvers |
| Notifications | Enable reminders and completion receipts |
Typical delivery paths to PwC and internal routing
-
PwC Secure Portal: Upload signed package to the PwC secure intake portal
-
Encrypted Email: Send password-protected attachments per PwC guidance
-
SFTP / FTPS: Use firm-designated secure file transfer protocols
-
Physical Delivery: Provide hard copies when specifically requested by engagement team
Digital signing and file-format considerations
Use common, non-proprietary formats and platforms that preserve audit trails and file integrity.
- Accepted Formats: PDF/A, PDF, DOCX recommended
- Authentication Options: Email, SMS code, or stronger MFA
- Integrations: Ensure compatibility with Salesforce, NetSuite, or secure cloud
Confirm with the PwC engagement contact before using new platforms; retain signed originals or certified electronic copies in a secure archive.
Timelines and typical submission deadlines
Internal Lead Time:
Provide materials at least 10 business days before scheduled fieldwork
Tax Filing Support:
Supply requested data within dates required for preparer deadlines
Response to Requests:
Respond to PwC follow-ups within 3–5 business days when possible
Extension Planning:
Allow extra time when filings require external confirmations or notarization
Real-Time Updates:
Notify PwC immediately of material changes or restatements
Common preparation mistakes to avoid
- Submitting inconsistent numbers between schedules and financial statements creates delays and additional audit requests.
- Missing or unsigned attestation pages force PwC to seek re-execution and can delay opinion or reporting timelines.
- Uploading unsupported file formats or poorly named files increases reviewer time and the risk of misplaced exhibits.
- Failing to document signatory delegation or authority can require legal confirmation and extend the review cycle.
Key risks if the submission is incorrect or incomplete
Real examples of electronic submissions used in practice
Tech Data — Bob Dutkowsky
Tech Data standardized submission packages for external reviewers to reduce turnaround time and ensure consistency.
- Bulk templates and integrated workflows were used to scale external reporting.
- As a result, the team reported improved internal and external customer service while accelerating speed to revenue and simplifying reconciliation across systems.
Xerox — Kodi-Marie Evans
Xerox integrated document templates with its ERP system to ensure mapping consistency for external reviews.
- API-driven attachments preserved source formatting.
- This approach provided flexibility to deliver the right documents and formats to reviewers and reduced manual data entry during PwC engagements.
How the Business Document to PwC differs from similar submission types
| Criteria | Audit Package | Informal Data Package |
|---|---|---|
| Purpose | audit support | ad hoc questions |
| Formality | high | low |
| Required Signatures | usually no | |
| Retention Expectation | long-term | short-term |
eSignature vendor comparison for submitting documents to PwC
| 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 | Varies by offer | Varies by offer | Varies by offer | Varies by offer |
| Bulk Send | Yes (Business Premium) | Yes | Yes | Yes | Varies |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes (BAA available) | Yes (BAA available) | Yes (BAA available) | No | No |
Frequently asked questions about Business Document to PwC submissions
-
Can PwC accept electronically signed documents?
Yes. Electronic signatures executed in compliance with the ESIGN Act (15 U.S.C. ch. 96) and applicable state UETA provisions are generally valid. Confirm any firm-specific authentication or notarization preferences with the engagement lead.
-
When is notarization required?
Notarization is required only where a document’s legal effect depends on notarization or when PwC or third parties request it. State notary rules differ; use RON where accepted and when a remote notarization is permitted.
-
How should signer identity be verified?
Use email plus SMS code, government ID checks, or knowledge-based authentication as appropriate. Stronger verification reduces risk of later disputes and supports compliance with 21 CFR Part 11 for regulated records when required.
-
What if an error is discovered after signing?
If a signed submission contains an error, prepare an amendment or corrected page, obtain the same authorized signatures, and provide a cover letter explaining the correction to PwC for the engagement record.
-
How long should signed submissions be retained?
Retain signed originals or certified electronic copies per applicable law. For tax records, follow the IRS minimum of three years from filing (IRC §6501(a)); healthcare records follow HIPAA retention periods.
-
What formats minimize processing issues?
Provide finalized, non-editable PDFs (PDF/A when possible) with bookmarks and a clear file-naming convention. Include an index or cover sheet listing included schedules to aid PwC review.