Can this form be signed electronically?

Yes. Electronic signatures are legally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted; ensure intent, consent, attribution, and retention requirements are met.

When is notarization required?

Notarization is required only when specified by contract, internal policy, or state law. For remote notarization, verify the state's RON rules and identity-proofing requirements.

What if the vendor's TIN is missing or incorrect?

An incorrect or missing TIN can trigger backup withholding and reporting issues; request a corrected W-9 and note that backup withholding may apply until corrected.

How do I revoke or cancel a submitted request?

Revoke by submitting a written cancellation with request ID to treasury and all approvers; document the revocation in the audit trail and follow internal dispute procedures.

What supporting documents are required?

Common attachments include invoices, contracts, PO numbers, and tax forms (W-9). Attach all materials used to justify the funding amount to speed validation.

How long until tokens are issued?

Issuance timing depends on verification and approval stages; typical end-to-end processing is 3–10 business days depending on documentation and approval complexity.

Electronic Signature
Templates
Miscellaneous
Funding Token Request Form

Funding Token Request Form

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

Funding Token Request Form

Parties

Requestor Name: Requestor Entity Type:

Individual Corporation LLC Other

Requestor Address: Contact Email: Contact Phone:

Funder Name: Funder Entity Type:

Individual Corporation LLC Other

Funder Address: Funder Contact Email: Funder Contact Phone:

Recitals (WHEREAS)

WHEREAS, Requestor requires funding in the form of blockchain-native tokens and has requested that Funder provide an allocation of tokens identified as (symbol: ), and the parties desire to set forth the terms for the issuance and delivery of tokens.

WHEREAS, Funder agrees to provide the requested tokens subject to the conditions, representations, and operational milestones described in this Funding Token Request Form and the exhibits incorporated by reference herein.

WHEREAS, the parties intend that this document constitute a binding agreement for the issuance, distribution and any associated funding obligations, subject to the terms and conditions set forth below.

Scope of Work

The Requestor shall use the funding tokens for the activities described below. The Requestor must provide periodic progress reports and allow reasonable verification of token usage by the Funder.

Payment Terms

Funder will provide funding in tokens and/or fiat equivalent as set forth below. All amounts and schedules are subject to verification of compliance with representations and milestone completion.

Funding Amount (if applicable): Token Allocation / Delivery Method:

Lump-sum transfer on execution Delivered by milestone Tranches over time

If milestone or tranche, describe schedule: Late Fee / Remediation (if applicable):

Term and Termination

This Agreement commences on the Start Date below and continues until the End Date or until earlier termination in accordance with this section.

Start Date: End Date:

Notice Period for Termination:

Either party may terminate this Agreement if the other party materially breaches its obligations and fails to cure within the notice period above. Termination shall not relieve either party of obligations accrued prior to termination, including any token delivery, return or remediation obligations.

Confidentiality

Each party (the "Recipient") shall hold in strict confidence all non-public information disclosed by the other party (the "Discloser") in connection with this Agreement, including token economics, technical designs, financial terms and due diligence materials ("Confidential Information"). The Recipient shall not disclose Confidential Information except to its employees, advisors or contractors who have a need to know and who are bound by confidentiality obligations no less protective than those herein.

Confidentiality obligations survive termination for a period of three (3) years from the date of disclosure, except with respect to trade secrets, which remain protected for as long as they qualify as trade secrets. Confidential Information does not include information that: (a) is or becomes publicly known through no wrongful act of Recipient; (b) was rightfully in Recipient's possession prior to disclosure; or (c) is independently developed by Recipient without breach of this Agreement. If Recipient is compelled by law to disclose Confidential Information, Recipient shall provide prompt written notice to Discloser and cooperate to seek a protective order or other appropriate remedy.

Representations and Warranties

Each party represents and warrants that it has full power and authority to enter into this Agreement and perform its obligations; that it will comply with applicable laws, including anti-money laundering, economic sanctions and export control laws; and that its execution will not violate any agreement or obligation to which it is a party.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the jurisdiction specified below, without regard to conflict of laws principles. The parties consent to the exclusive venue of the courts located in that jurisdiction for any dispute arising out of or relating to this Agreement.

Governing Law / Jurisdiction:

Entire Agreement

This Funding Token Request Form, together with any exhibits, schedules and the parties' mutually executed written attachments, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, representations and understandings, whether written or oral. No amendment to this Agreement is effective unless in writing and signed by duly authorized representatives of both parties.

Additional Provisions

The parties acknowledge that the issuance and transfer of tokens may be subject to blockchain-specific constraints, network fees, delays and third-party custodian requirements. The Requestor and Funder will cooperate in good faith to complete transfers and satisfy on-chain and off-chain conditions precedent.

Requestor Printed Name:

By:

Date:

Funder Printed Name:

By:

Date:

What the Funding Token Request Form Is

A Funding Token Request Form is a standardized document used to request issuance, transfer, or allocation of funding tokens or voucher credits within an organization or between contracting parties. It records requester identity, token type, funding amount, purpose, and required approvals so finance, treasury, or operations teams can validate, authorize, and track token disbursements. Organizations commonly combine this form with supporting attachments, identity verification, and an audit trail to ensure traceability and meet internal controls and regulatory requirements when funds or tokenized assets move.

Why a Clear Request Form Matters

A concise Funding Token Request Form reduces processing delays, creates a verifiable audit trail for approvals, and documents authorization to disburse funds or tokenized credits. Consistent forms help teams meet internal control requirements and simplify reconciliation.

Who Typically Completes the Form

Teams that commonly prepare or sign Funding Token Request Forms include treasury, accounts payable, procurement, vendor finance, and program managers responsible for disbursing funds or credits.

Treasury and Finance teams handling disbursements and reconciliation.
Procurement or vendor managers requesting supplier credits or tokenized payments.
Legal or compliance reviewers for high-value or contractually sensitive requests.

The form also moves through legal review and authorized signatories for higher-value requests or where contractual terms require executive approval.

How to complete and submit the form

Simple sequential steps to prepare, verify, and submit a Funding Token Request Form.

01

Prepare: Populate all required fields and attach supporting documents.
02

Verify identity: Confirm requester details and authority to request funding.
03

Obtain approvals: Route to designated approvers in the required order.
04

Submit: Send to treasury/finance via the authorized channel with audit trail.

Essential sections to include in a professional form

A complete Funding Token Request Form groups identification, transaction details, approvals, and evidence to support rapid validation and accurate accounting.

Header

Document title, unique request ID, creation date, and version or revision number so requests are uniquely identifiable and auditable.

Requester Details

Full legal name, department, contact information, and employee or vendor ID to ensure requests can be validated against company records.

Token Details

Token name/type, amount, currency, and any serial or reference IDs required to map issuance or ledger entries precisely.

Business Purpose

Concise description of intended use, project code, or GL account to facilitate approval, compliance checks, and accounting coding.

Approvals

Designated approver names, roles, and signature fields with required sequence and thresholds for escalations or multiple approvers.

Supporting Documents

Attachments such as invoices, contracts, W-9 or tax forms, and identity verification records that justify the request and support audit needs.

Key data elements required on the form

Full Legal Name: Exact legal name

Entity Identifier: EIN or vendor ID

Account Reference: Internal account or ledger code

Token Type: Token or credit identifier

Funding Amount: Amount with currency

Contact Email: Valid contact address

Configuring the online workflow

Configure notification, authentication, and routing settings to match internal control requirements before enabling the form for use.

Field	Configuration
Authentication	Email + SMS code or SSO
Conditional Fields	Show extra fields for high-value requests
Notifications	Email alerts for each approval stage
Integrations	ERP, accounting, and document storage

Technical formats and system requirements

Use platforms that support PDF, DOCX, and secure eSignature workflows and that integrate with your ERP or ticketing system.

File types: PDF, DOCX, HTML, Excel
Integrations: Salesforce, NetSuite, Google Workspace
Authentication: SSO, SMS code, KBA options

Where to send the completed form

Identify the canonical submission route to avoid processing delays and ensure the request enters the correct approval queue.

Treasury Queue: Direct submission to treasury ticketing system for validation
ERP Entry: Upload to accounting system for GL coding
Vendor Portal: If vendor-initiated, upload to vendor management portal
Document Repository: Archive signed form in secure DMS for audit

Typical timelines and processing expectations

Standard internal SLAs and external timing considerations to set requester expectations and meet compliance windows.

Internal SLA:

Initial review within 2 business days

Verification Window:

Identity and documentation checks in 3–5 business days

Approval Cycle:

Approvals typically completed in 1–3 business days

Funding Effective Date:

Funds or tokens issued after final approval

Tax Reporting:

Retain vendor tax info for year-end reporting

Key milestones from request to issuance

A linear milestone view helps teams monitor request status and identify bottlenecks during processing.

01

Request Submitted

Form completed and supporting docs attached

02

Documentation Verified

Identity, tax, and contract checks performed

03

Approval Completed

Required signatories approve the request

04

Tokens Issued

Treasury or token service executes issuance

Common mistakes that cause rejections

Missing or incorrect tax identifiers that trigger backup withholding or vendor validation delays.
Incomplete approval chain or absent authorized signer for the requested dollar threshold.
Incorrect token type or ledger reference causing misallocation of funds or credit.
Unsupported file formats or large attachments that fail automated ingestion processes.

Risks and potential penalties

Payment Delays: Delays in vendor payment or project funding

Backup Withholding: 24% backup withholding risk (incorrect TIN)

Contract Dispute: Unauthorized disbursement can trigger disputes

Compliance Violation: Internal control failures increase audit exposure

Data Exposure: Improper sharing of PII risks breach

Form Rejection: Missing notarization or signatures may void request

Best practices to speed approval and reduce errors

Adopt consistent templates, strong authentication, and clear approval rules to minimize manual review and rework.

Standardize templates

Use a single approved template with required fields enforced; eliminate optional fields that commonly lead to incomplete submissions.

Require authentication

Apply SSO or multi-factor authentication for requesters and approvers to ensure attribution and reduce fraud risk.

Attach evidence

Always include invoices, contracts, or Purchase Orders to justify amounts and expedite finance validation and ledger coding.

Log the audit trail

Capture timestamps, IP addresses, and signer identity with every transaction for compliance and dispute resolution.

eSignature vendor comparison for form processing

Common vendor pricing and feature differences relevant to high-volume form processing and secure electronic signatures for funding requests.

	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	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
Envelope Cap	No cap	100 envelopes/user/year	Varies	Varies	Varies

Frequently asked questions and troubleshooting

Answers to common questions about validity, notarization, TIN issues, revocation, and processing expectations for the Funding Token Request Form.

Need help? Contact support

Can this form be signed electronically?
Yes. Electronic signatures are legally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted; ensure intent, consent, attribution, and retention requirements are met.
When is notarization required?
Notarization is required only when specified by contract, internal policy, or state law. For remote notarization, verify the state's RON rules and identity-proofing requirements.
What if the vendor's TIN is missing or incorrect?
An incorrect or missing TIN can trigger backup withholding and reporting issues; request a corrected W-9 and note that backup withholding may apply until corrected.
How do I revoke or cancel a submitted request?
Revoke by submitting a written cancellation with request ID to treasury and all approvers; document the revocation in the audit trail and follow internal dispute procedures.
What supporting documents are required?
Common attachments include invoices, contracts, PO numbers, and tax forms (W-9). Attach all materials used to justify the funding amount to speed validation.
How long until tokens are issued?
Issuance timing depends on verification and approval stages; typical end-to-end processing is 3–10 business days depending on documentation and approval complexity.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now