Can a requisition be signed electronically?

Yes. Under the ESIGN Act (15 U.S.C. ch. 96) and UETA, electronic signatures are valid for most business documents provided intent, consent, attribution, and record retention are present.

Do requisitions require notarization or witnesses?

Ordinarily no. Standard internal requisitions do not require notarization or witness signatures unless tied to a legal instrument that specifically requires them.

What happens if vendor details are incorrect?

Incorrect vendor information causes payment delays, potential backup withholding for tax identification issues, and may require purchase order cancellations and reissuance.

How long should I retain requisition records?

Retain requisitions for the contract term plus at least three years; IRS guidance sets a minimum three‑year period (IRC §6501(a)) and HIPAA requires six years for health records.

Can a requisition be amended after approval?

Yes, but amendments should follow a formal change control process that records who authorized changes and why; material changes often require reapproval.

How do integrations affect approval accuracy?

Integrations reduce manual entry errors by mapping fields and validating GL codes; ensure mapping rules are tested to prevent incorrect account charging.

Electronic Signature
Templates
Finance
Purchase Order Requisition

Purchase Order Requisition

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

Purchase Order Requisition

Requisition Details

Requisition No.: Date: Department:

Requestor / Originating Unit

Vendor / Supplier

Vendor Name Vendor Contact & Details

Shipping & Billing

Ship To (Location) Bill To

Required by: Delivery Location Reference:

Procurement Details & Budget

Procurement Method: Competitive Bid Existing Contract Sole Source Emergency

Budget / Account Code Justification for Purchase

Itemized Requisition

Description	Quantity	Unit Rate	Amount

Subtotal:

Tax:

Shipping / Handling:

Total:

Payment & Terms

Payment Method: Check ACH Credit Card Wire Transfer

Payment Terms Notes / Delivery Instructions

Certification & Administrative Conditions

I certify that funds are available and budgeted for this purchase and that the goods or services requested are necessary for official use. Approval of this requisition constitutes authorization to obligate the organization to a purchase order consistent with applicable procurement policy and any authorized contract terms.

The vendor will be required to deliver goods or services in accordance with the purchase order. Receipt and inspection by the receiving department is required prior to acceptance. Nonconforming goods or services are subject to replacement, repair, credit, or return at the vendor's expense. Fraudulent statements or intentional misrepresentations may result in administrative action or penalties.

Certifications (check all that apply)

Funds available / Encumbrance authorized Procurement policy requirements met Required approvals obtained

Terms & Conditions (internal use)

Approval Routing

Routing Instructions: After Requestor signature, submit to Approving Authority. Procurement will not issue a purchase order until required approvals and budget verification are complete.

Requestor Printed Name:

By:

Date:

Approving Authority Printed Name:

By:

Date:

What a Purchase Order Requisition Is and When It’s Used

A Purchase Order Requisition is an internal procurement document that formally requests approval to buy goods or services. It records required items, quantities, estimated costs, preferred vendors, and accounting codes, and it initiates the purchasing workflow so procurement, accounts payable, and budget owners can review and authorize the commitment before a purchase order is issued to a supplier.

Why a Clear Requisition Matters

A well‑formed requisition reduces order errors, speeds approvals, supports audit trails, and creates a single record linking budgets, approvals, and vendor fulfillment — improving transparency across procurement and finance teams.

Who Prepares and Reviews Purchase Order Requisitions

Typical participants include the requestor, department approvers, procurement staff, and accounts payable; each plays a distinct role in validation and routing.

Requestors (department staff) — Create the requisition, assemble vendor quotes, and enter item details, SKU numbers, and cost centers for review.
Approving managers — Verify budget availability, business purpose, and compliance with procurement policy prior to sign‑off and routing.
Procurement / Purchasing — Confirm vendor selection, negotiate terms if needed, assign PO numbers, and convert approved requisitions into purchase orders.

Clear role definitions shorten approval cycles and reduce rework by ensuring each party knows the information they must supply or verify.

Step‑by‑Step: Completing a Purchase Order Requisition

Follow these steps to prepare a complete requisition that can be approved and converted to a purchase order without delays.

01

Create Request: Enter requester, department, and business purpose.
02

List Items: Specify description, quantity, unit price, and SKU.
03

Attach Quotes: Upload vendor quotes, certifications, or scopes of work.
04

Route for Approval: Send to manager and procurement for final authorization.

Typical Workflow Settings for Requisition Routing

Configure workflow fields so approvals, notifications, and purchase order creation proceed without manual handoffs.

Field	Configuration
Approval workflow	Two‑step manager followed by procurement review
Auto‑numbering	Enabled for unique requisition IDs
Accounting validation	Require valid GL code before routing
Notifications	Email alerts to approvers and requestor

How Requisition Submission and Conversion Typically Flow

Requisitions move from request creation through approvals to PO issuance; each step adds validation to prevent downstream issues.

Prepare Request: Assemble item details, vendor info, and attachments.
Manager Approval: Confirm budget and business justification for the purchase.
Procurement Review: Validate vendor, negotiate terms if needed, and approve supplier selection.
Issue PO: System converts approved requisition into a purchasable order.

Distribution and eSubmission Options

Requisitions can be shared by internal systems, email, or integrated eProcurement platforms; choose a method that preserves attachments and audit metadata.

Integrations: Salesforce, NetSuite, Microsoft 365, Google Workspace
File formats: PDF, DOCX, and CSV supported for exports
Delivery methods: Email, API push to ERP, or portal upload

Common Timelines and Processing Expectations

Timelines vary by organization, supplier lead times, and approval SLAs; document expected response times to set clear expectations.

Internal approval SLA:

Standard 3–7 business days depending on approver availability

Expedited requests:

Temporary 24–48 hour approval tracks for urgent needs

Vendor acknowledgment:

Suppliers typically confirm POs within 1–5 business days

Order fulfillment:

Delivery schedules follow supplier terms and lead times

Invoice submission:

Vendors should submit invoices upon shipment per PO terms

Common Mistakes That Delay Procurement

Missing or incorrect vendor tax ID, address, or payment details causing AP rework and backup withholding risk.
Vague item descriptions and missing SKUs that lead to incorrect shipments and return cycles.
Absent or incorrect accounting codes that prevent proper budget encumbrance and delay approval.
Lack of required attachments (quotes, certifications) prompting hold for procurement verification and supplier qualification.

Risks of Inaccurate or Incomplete Requisitions

Contract disputes: Ambiguous terms can lead to supplier disagreement

Payment delays: Invoice mismatches cause late payments and fees

Budget overruns: Incorrect coding hides true spend levels

Compliance exposure: Procurement rules or grant conditions may be violated

Operational downtime: Delayed supplies can interrupt projects

Audit findings: Insufficient records can trigger audit exceptions

Security and Compliance Considerations

Encryption (Transit): TLS 1.2/1.3

Encryption (At rest): AES‑256

Audit Trail: Timestamps and action logs retained

HIPAA: BAA required for PHI workflows

SOC 2: SOC 2 Type II available

21 CFR Part 11: Compliant controls available

eSignature Vendor Pricing and Feature Comparison

Basic pricing and feature distinctions relevant to signing and routing Purchase Order Requisitions across common eSignature providers.

	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 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
Envelope Cap	No cap	100 envelopes/user/year	Varies	Varies	Varies

Real‑World Examples of Requisition Workflows

Examples show how organizations combine approvals, integrations, and eSignatures to shorten procurement cycles and improve traceability.

Tech Data — Enterprise Procurement

Tech Data standardized requisitions across business units to reduce manual review time.

Integration with ERP automated PO creation for approved requests.
The change improved internal customer service and reduced time to revenue by shortening approval handoffs and minimizing invoice mismatches.

Xerox — NetSuite Integration

Xerox linked requisition creation to NetSuite so procurement could validate inventory and vendor terms.

Automated field mapping prevented coding errors.
This approach ensured accuracy, enabled faster PO issuance, and maintained consistent records for audit and vendor payment reconciliation.

Frequently Asked Questions About Purchase Order Requisitions

Answers to common questions about preparation, approvals, eSigning, retention, and integration with purchasing systems.

Need help? Contact support

Can a requisition be signed electronically?
Yes. Under the ESIGN Act (15 U.S.C. ch. 96) and UETA, electronic signatures are valid for most business documents provided intent, consent, attribution, and record retention are present.
Do requisitions require notarization or witnesses?
Ordinarily no. Standard internal requisitions do not require notarization or witness signatures unless tied to a legal instrument that specifically requires them.
What happens if vendor details are incorrect?
Incorrect vendor information causes payment delays, potential backup withholding for tax identification issues, and may require purchase order cancellations and reissuance.
How long should I retain requisition records?
Retain requisitions for the contract term plus at least three years; IRS guidance sets a minimum three‑year period (IRC §6501(a)) and HIPAA requires six years for health records.
Can a requisition be amended after approval?
Yes, but amendments should follow a formal change control process that records who authorized changes and why; material changes often require reapproval.
How do integrations affect approval accuracy?
Integrations reduce manual entry errors by mapping fields and validating GL codes; ensure mapping rules are tested to prevent incorrect account charging.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now