Download signNow app
4.7 / 5 rating on

Wh 347 Form

Use a Fillable Wh 347 0 template to make your document workflow more streamlined.

What the Wh 347 Form is used for

The Wh 347 Form is the document identified by that name on this page; its issuing agency, filing purpose, required fields, and signature rules should be confirmed from the form itself or its instructions before submission. signNow can help a sender upload the file, detect fillable fields, assign fields to named signers, collect an electronic signature, and preserve the completed document with an audit trail. The legal effect of signing depends on the form’s governing authority and any state or agency filing rule. Do not treat electronic completion as proof of acceptance by an agency.

Who can prepare and sign this form

Businesses

Use signNow to prepare the Wh 347 Form for review, signature, and controlled storage when the recipient accepts electronic records.

Operations teams

Use a reusable Wh 347 Form template when authorized staff send the same document repeatedly and need consistent field placement.

Features that support Wh 347 Form workflows

signNow organizes preparation, signing, audit evidence, and storage around the specific Wh 347 Form file you upload.

Field preparation

Upload the Wh 347 Form once, then use detected or placed fields to reduce repeated manual formatting before sending.

Signer routing

Assign each Wh 347 Form field to a specific signer so responsibilities remain clear during completion.

Electronic signing

Collect signatures through a browser or mobile workflow when electronic signing is permitted for this document.

Audit trail

Keep the completed Wh 347 Form and its signing history together for later review and retrieval.

Reusable template

Reuse an approved Wh 347 Form template without rebuilding field locations for every transaction.

System connections

Connect signed Wh 347 Form records to supported storage or business systems for organized downstream processing.

How to prepare Wh 347 Form

Follow the document-specific instructions first, then use signNow to prepare, route, sign, and retain the completed Wh 347 Form.

  • Upload form:

    Upload the exact Wh 347 Form file to signNow.
  • Check fields:

    Review detected fields and add missing signature or date fields.
  • Assign signers:

    Assign every field to the correct Wh 347 Form signer.
  • Send form:

    Send the prepared document through the approved signing workflow.
  • Store records:

    Download the completed form and preserve its audit trail.
be ready to get more
Get legally-binding signatures now!
  • Best ROI. Our customers achieve an average 7x ROI within the first six months.
  • Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
  • Intuitive UI and API. Sign and send documents from your apps in minutes.

How the Wh 347 Form workflow works

The workflow moves from the original Wh 347 Form file to assigned fields, signer completion, and a retained completion record.

  • Upload document: The sender uploads the Wh 347 Form and reviews its pages.
  • Prepare fields: signNow detects fields or lets the sender place them manually.
  • Route document: The sender routes assigned fields to each signer.
  • Complete and sign: The signer completes required fields and signs electronically when permitted.

Recommended Wh 347 Form setup

Use the document instructions and governing record category to configure authentication, signing, evidence, retention, and access.

SettingRecommended configuration
Authentication methodEmail verification with SMS OTP
Signature typeTyped or drawn electronic signature
Audit trailEnabled with completion certificate
Document retentionThree years from filing under IRC §6501(a)
EncryptionTLS 1.2/1.3 and AES-256

What the Wh 347 Form audit trail records

The audit trail adds evidence around the signing event without replacing the Wh 347 Form’s own filing instructions or agency requirements.

01

Authenticate signer:

Records the signer’s email or configured authentication event.
02

Capture timestamp:

Captures signing time and each recorded document action.
03

Hash document:

Associates the completed Wh 347 Form with integrity evidence.
04

Seal record:

Preserves the signed file and completion history against unnoticed changes.
05

Record actions:

Links the signer’s field actions to the document event log.
06

Export evidence:

Allows authorized users to retrieve or export the audit trail.

Security controls for Wh 347 Form

Transport encryption:

TLS 1.2/1.3 in transit

Storage encryption:

AES-256 at rest

Security certification:

SOC 2 Type II certified

Information security:

ISO 27001 certified

U.S. e-signature law:

ESIGN and UETA compliant

Protected health information:

HIPAA compliant with BAA

Rules that can limit electronic signing

Agency acceptance

Confirm agency acceptance first.

Wet-ink requirement

Electronic signature may be rejected.

Notarization required

Missing notarial act can invalidate filing.

Excluded documents

Excluded documents remain outside ESIGN.

Privacy and disclosure issues to avoid

  • A sender can expose taxpayer, employee, patient, or business information by granting document access more broadly than the Wh 347 Form requires.
  • A signer may complete the Wh 347 Form without seeing the electronic-record consent disclosure required for a consumer-facing transaction under 15 U.S.C. §7001(c).
  • Unassigned or duplicated fields can leave required Wh 347 Form information blank while making the document appear complete.
  • Deleting the signed file without its completion record can weaken the evidence needed to attribute the Wh 347 Form signature.

Retention periods for Wh 347 Form records

Choose retention based on the record’s legal category and business purpose, not solely on the Wh 347 Form label.

01

Three years for federal tax records

IRS recordkeeping rules under IRC §6501(a) generally require three years from filing.
02

Six years for major understatements

IRC §6501(a) extends the period to six years when income understatement exceeds 25 percent.
03

Six years for HIPAA records

HIPAA-covered records require six years from creation or the last effective date under 45 CFR §164.530(j).
04

Later of three or one year

Employment records connected to Form I-9 follow three years after hire or one year after termination, whichever is later, under 8 CFR §274a.2.
05

Three years for payroll records

FLSA payroll records require three years under 29 CFR §516.5 when the signed form supports payroll documentation.

Wh 347 Form troubleshooting questions

Use the document’s own instructions first, then check these signNow workflow, acceptance, authentication, and retention issues.

Upload the original Wh 347 Form again, then inspect detected fields and compare them with the document instructions. Add missing fields manually before routing the file to signers.

Business includes legally binding eSignatures, templates, and audit trails at $8 per user monthly with annual billing. Confirm the current plan and document requirements before sending.

ESIGN and UETA generally recognize electronic signatures when intent, consent, attribution, and record retention are established. The form’s issuing agency may still require another submission method.

Use assigned fields, signer authentication, timestamps, and the completion record to establish attribution. For consumer-facing records, provide the disclosure required by 15 U.S.C. §7001(c).

Keep the completed Wh 347 Form with its audit trail and follow the record category’s controlling rule. IRC §6501(a), HIPAA, employment, and payroll rules impose different periods.

If the workflow includes protected health information, signNow states that HIPAA compliance requires a business associate agreement. Confirm that requirement before routing the Wh 347 Form.

ROI at a Glance

Key performance indicators that demonstrate SignNow's proven track record.

28M+Documents signed
13+Years in business
4.6/5Average G2 rating

BE READY TO GET MORE

Get this form now!

If you believe that this page should be taken down, please follow our DMCA take-down process.