Download signNow app
4.7 / 5 rating on

Information Concerning Claims For Treaty Based Exemptions Schedule 91

Use a Information Concerning Claims For Treaty Based Exemptions Schedule 91 2011 template to make your document workflow more streamlined.

What Schedule 91 is and does

Information Concerning Claims For Treaty Based Exemptions Schedule 91 is a tax-document workflow used to collect information supporting a claim that treaty rules may affect U.S. withholding. The recipient supplies the requested identifying, residency, and treaty-claim details; the payer reviews them before applying any exemption or reduced rate. Schedule 91 is not itself a guarantee of eligibility, and the available ground truth does not identify an issuing agency, filing deadline, or universal threshold for this form. With signNow, the PDF can be uploaded, fields reviewed, routed for signature, and preserved with an audit trail.

Who uses Schedule 91

Tax departments

Tax professionals and payer teams use Schedule 91 to collect treaty-based exemption information from non-U.S. recipients before applying withholding decisions. They review the recipient’s answers, preserve supporting records, and route the completed document for authorized approval.

International recipients

International contractors, vendors, and beneficial owners use Schedule 91 to state treaty-related claims for a U.S. payer. They complete the requested fields, confirm the information, and return the signed record for the payer’s review and retention.

How Schedule 91 moves through signNow

A Schedule 91 workflow moves from document preparation to recipient review, signature capture, and auditable storage without changing the form’s substantive tax information.

  • Upload form: Add the Schedule 91 PDF to signNow.
  • Check fields: Review detected fields and add required fields.
  • Send securely: Route the form to the designated recipient.
  • Store record: Capture signatures and retain the completed record.

Recommended Schedule 91 workflow setup

Use a controlled signing workflow that preserves recipient attribution, payer review, and the completed Schedule 91 record.

SettingRecommendation
Authentication methodSMS verification for recipients
Signature typeElectronic signature with consent
Audit trailEnabled with completion certificate
Document retentionThree years from filing (IRC §6501(a))
EncryptionTLS 1.2 or 1.3 and AES-256
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.

Authentication options for Schedule 91

PKI support:

PKI can support certificate-based signatures.

X.509 certificates:

X.509 certificates identify certificate-based signers.

Two-factor authentication:

Two-factor authentication strengthens recipient access.

SMS OTP:

SMS OTP verifies a supplied phone number.

ID verification:

ID verification can strengthen signer attribution.

Audit evidence:

Audit trails connect actions with timestamps.

Platform requirements for Schedule 91

Complete Schedule 91 in Chrome, Firefox, Safari, or Edge on Windows and macOS. signNow mobile apps support iOS and Android, while TLS 1.2 or 1.3 protects transmitted form data.

  • Browser support Chrome, Firefox, Safari, and Edge on Windows or macOS.
  • Mobile devices iOS and Android devices support mobile signing.
  • Connection security TLS 1.2 or 1.3 secures browser connections.

Use a supported browser and a current Windows, macOS, iOS, or Android device when preparing Schedule 91. Organizations can add managed-device controls, SSO provisioning, API access, and certificate settings according to their internal records and authentication policies.

Find and fill out the correct information concerning claims for treaty based exemptions schedule 91 2011

airSlate SignNow helps you fill in and sign documents in minutes, error-free. Choose the correct version of the editable PDF form from the list and get started filling it out.

VersionsForm popularityFillable & printable
Canada T2 - Schedule 91 20144.8 Satisfied (3079 Votes)
Canada T2 - Schedule 91 20114.8 Satisfied (87 Votes)

Integrations for Schedule 91 workflows

Connect Schedule 91 routing with Salesforce, NetSuite, Microsoft 365, Google Drive, or Box to move signed records into the systems used for payer review and retention.

Salesforce
Procore
Zapier
Microsoft Teams
Hub spot
Box
Microsoft

Best practices for completing Schedule 91

Accurate recipient information, controlled routing, and complete signing evidence help payers review Schedule 91 without confusing a valid signature with a valid treaty claim.

Review treaty information before approval

Confirm the recipient’s identity, tax residence, and treaty-related answers before approving the completed Schedule 91. Compare entries against payer records and request clarification when information is incomplete or inconsistent. Do not treat a signature alone as proof that the exemption applies.

Separate recipient and payer fields

Use signNow’s field placement tools to make every required Schedule 91 response visible and unambiguous. Separate recipient fields from payer review fields, and prevent accidental changes to explanatory text or instructions before sending.

Preserve consent and signing evidence

Capture recipient consent to electronic records when the workflow is consumer-facing. Retain the signed PDF, completion certificate, and audit trail together so the record shows intent, attribution, timestamps, and the final document version.

Restrict access to tax records

Limit Schedule 91 access to personnel handling withholding and tax documentation. Use role-based permissions, controlled sharing, and a documented review process before forwarding treaty-related information to another department or payer system.

Legal standing of Schedule 91 records

A completed Schedule 91 may be retained as an electronic business record when the signer shows intent, consents where required, can be attributed, and the record remains reproducible under ESIGN, 15 U.S.C. ch. 96, and applicable state law such as UETA. Electronic signing does not establish treaty eligibility.

Why teams look for DocuSign alternatives

What the Schedule 91 audit trail records

The audit trail documents signing evidence around Schedule 91, giving reviewers a chronological record separate from the recipient’s substantive treaty answers.

01

Authenticate signer:

Email, SMS, or configured authentication identifies the recipient before signing.
02

Capture timestamp:

signNow records the signing event’s date and time.
03

Hash document:

The completed document receives integrity evidence for later comparison.
04

Seal record:

The signed record is sealed against unnoticed content changes.
05

Link events:

The audit trail links recipient actions to the document.
06

Export evidence:

Authorized users export the completed PDF and audit evidence.

Privacy pitfalls for Schedule 91

  • Schedule 91 may expose tax residence, identification, and payment information when shared with unauthorized recipients or stored in open folders.
  • Missing electronic-record consent can weaken the process when a consumer-facing workflow requires ESIGN disclosure and access procedures.
  • Broad administrator permissions can allow unauthorized viewing, editing, or forwarding of completed treaty-claim records.
  • Separate storage of the PDF and audit trail can make later review of signer intent and document integrity harder.

Schedule 91 troubleshooting

Resolve document, recipient, authentication, compliance, and retention questions before relying on a completed Schedule 91 record.

Upload Schedule 91 as a readable PDF, then review signNow’s detected fields before sending. If fields are missed, place text, date, checkbox, and signature fields manually. The Business plan includes templates and audit trails for recurring payer workflows.

Use signNow’s recipient authentication settings to require an SMS code or stronger verification where your organization needs it. Authentication supports attribution evidence, but the payer remains responsible for confirming treaty eligibility and reviewing the completed information.

The Business plan includes legally binding eSignatures and audit trails at $8 per user monthly with annual billing. Paid plans include 100 signature invites per user annually, with overage fees applying when the allowance is exceeded.

signNow documents ESIGN and UETA compliance, but those laws do not decide whether a treaty claim is substantively correct. The payer should review Schedule 91 under applicable IRS rules and preserve the completed record for its tax process.

For healthcare workflows involving protected health information, signNow states that HIPAA compliance requires a BAA. Schedule 91 should not contain unnecessary health information; restrict access and apply the organization’s retention policy.

Export the completed Schedule 91 and its audit trail after signing. Business Premium adds bulk send for repeated distribution, while Enterprise adds advanced signer authentication and integrations for larger controlled workflows.

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.