What qualifies as a PO exception?

A deviation from the original purchase order terms such as quantity, price, delivery date, or supplier that requires documented business justification and authorization.

Who must approve an exception?

Approval typically requires the requesting manager, procurement lead, and an accounts payable or finance approver; high-value exceptions may need executive sign-off per policy.

Can the form be signed electronically?

Yes. Electronic signatures are acceptable under ESIGN and UETA when intent, consent, signer attribution, and record retention are present and an audit trail is maintained.

Are notarization or witnesses required?

Most internal PO exceptions do not require notarization, but changes that amount to contract amendments may trigger state-specific notarization or witness rules; verify with legal counsel.

What supporting documents should be attached?

Include invoices, revised quotes, vendor emails, change orders, and any approvals that substantiate the exception and show vendor acceptance where applicable.

How long should the form be retained?

Retain according to your document retention policy; tax-related records follow IRS minimums (IRC §6501(a)) and healthcare records must meet HIPAA retention (45 CFR §164.530(j)).

Electronic Signature
Templates
Finance
Purchase Order Exception Form

Purchase Order Exception Form

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

What the Purchase Order Exception Form Is and When It Applies

A Purchase Order Exception Form documents a planned deviation from an existing purchase order or procurement policy. It records the PO number, exception reason, affected line items, dollar amounts, and required approvals so the organization can process goods or services despite a mismatch, timing issue, or policy exception. The form creates a permanent record for accounts payable, procurement, and audit teams and supports downstream actions such as vendor invoice payment, contract amendment, or internal corrective steps while preserving traceability for compliance and financial control purposes.

Why a Formal Exception Form Matters for Procurement Controls

A standardized Purchase Order Exception Form reduces payment errors, clarifies authorization, and documents the business justification for nonstandard spend. It supports auditability and consistent decision-making while preserving vendor relationships and reducing disputed invoices.

Who Typically Completes and Reviews a PO Exception

Assign clear ownership for submitting, reviewing, and archiving the exception to ensure timely resolution and traceability.

Procurement officers who assess compliance, alternatives, and policy impact before approval.
Accounts payable staff who match the exception to invoices and release payments when authorized.
Requesting department managers who provide the business justification and confirm receipt of goods or services.

Typical Signers and Their Responsibilities

Procurement Manager

Responsible for evaluating whether the exception is justified, identifying alternative sourcing, and confirming policy mitigation steps; signs to authorize procurement deviation and records approval metadata for audit.

Accounts Payable Lead

Verifies invoice/PO reconciliation, confirms approval chain completeness, and signs to permit payment release while retaining the form in financial records for compliance and audit purposes.

Essential Data Fields to Capture

PO Number: Unique purchase order identifier

Exception Reason: Concise description of deviation

Vendor Name: Registered vendor or supplier

Amount Impacted: Dollar value affected

Approver Name: Authorized approver identity

Attachments: Supporting invoices or emails

Risks and Consequences of Improper Exceptions

Delayed Payment: Vendor may be unpaid, risking disruption

Audit Finding: Incomplete records can trigger audit exceptions

Contract Breach: May violate supplier agreement terms

Tax Reporting: Incorrect records can affect reporting

Duplicate Orders: Risk of paying twice for same goods

Compliance Violation: Internal policy or regulatory breach

Common Preparation Mistakes to Avoid

Entering the wrong PO number, which prevents correct invoice matching and delays payment reconciliation.
Missing required approvals or signature lines, creating audit-resolvable exceptions and payment holds.
Submitting mismatched amounts or currencies without clear conversion notes or supporting documentation.
Failing to attach supporting emails, quotes, or revised SOWs that justify the exception and show vendor consent.

Step-by-Step: Completing the Purchase Order Exception Form

Follow these sequential steps to document, approve, and route a PO exception for processing and recordkeeping.

01

Identify PO: Enter the exact PO number and verify line items
02

Describe Exception: Summarize why the order deviates from policy
03

Collect Approvals: Obtain signatures from procurement and finance
04

Attach Evidence: Include invoices, emails, or change orders

How a PO Exception Moves Through Your Workflow

A clear routing path speeds resolution and keeps stakeholders informed at each step of the approval process.

Submission: Requester files the completed form and attachments
Procurement Review: Procurement evaluates alternatives and policy impact
Finance Approval: Accounts Payable confirms budget and releases payment
Archive: Form and audit trail retained in records

Key Sections of a Professional PO Exception Form

A well-structured form groups related information so reviewers can quickly confirm justification, approvals, and financial impact before payment or contract change.

Header

Includes company name, form title, submission date, and the PO number so reviewers immediately identify the exception context and record metadata.

Request Details

Captures the requesting department, requester name, contact details, and the date the exception was discovered to establish responsibility and timeline.

Exception Description

A clear, concise rationale that explains the deviation, the affected line items, and whether the vendor agreed to the change in scope or price.

Financial Impact

Explicit dollar amounts, tax treatment, currency, and account codes so accounting can post adjustments without reconciliation ambiguity.

Approvals

Designated signature blocks for procurement, department head, and accounts payable with printed names and dates to prove authorization.

Attachments & Notes

Space to list and store supporting documents such as revised quotes, email approvals, or change order references for auditability.

Configuring an Electronic Workflow for Exceptions

Set up a consistent electronic routing path and field rules to automate approvals and prevent omission of required information.

Field	Configuration
PO Number Field	Required, validation against ERP
Attachment Field	Required for >$1,000 exceptions
Approval Order	Requester → Procurement → Finance
Authentication	Email + optional SMS code

Digital Tools and Integration Considerations

Ensure the chosen platform can export signed records, maintain tamper-evident audit trails, and map approvals back into your accounting system for reporting and retention.

File Formats: PDF, DOCX, and XML supported
Integrations: Connects to ERP and cloud storage
Authentication: Email, SMS, and SSO options

Timelines and Typical Processing Deadlines

Set clear internal deadlines to keep exceptions from delaying payment, procurement, or vendor performance.

Submit Immediately:

Requester should submit the exception within 1 business day of discovery

Procurement Review Deadline:

Procurement typically responds within 3 business days

Finance Approval Deadline:

Accounts Payable approval within 5 business days if complete

Payment Hold Period:

Payment may be held until approvals and documentation are complete

Record Update:

Update PO system and ledger within the same accounting period

Key Milestones from Discovery to Resolution

Track milestone stages so each exception completes within defined SLAs and to provide a clear audit trail.

01

Discovery

Issue is identified and logged by requester

02

Submission

Requester submits form with attachments and initial details

03

Review

Procurement and finance analyze risk and cost impact

04

Resolution

Approval granted or corrective steps assigned and recorded

eSignature Pricing and Feature Comparison for Exception Workflows

Simple pricing and capability differences can affect solution selection; signNow is listed first in the table as a point of comparison with other market options.

	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
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently Asked Questions About PO Exception Forms

Answers to common questions on form validity, signatures, approvals, and recordkeeping to help avoid rework and audit findings.

Need help? Contact support

What qualifies as a PO exception?
A deviation from the original purchase order terms such as quantity, price, delivery date, or supplier that requires documented business justification and authorization.
Who must approve an exception?
Approval typically requires the requesting manager, procurement lead, and an accounts payable or finance approver; high-value exceptions may need executive sign-off per policy.
Can the form be signed electronically?
Yes. Electronic signatures are acceptable under ESIGN and UETA when intent, consent, signer attribution, and record retention are present and an audit trail is maintained.
Are notarization or witnesses required?
Most internal PO exceptions do not require notarization, but changes that amount to contract amendments may trigger state-specific notarization or witness rules; verify with legal counsel.
What supporting documents should be attached?
Include invoices, revised quotes, vendor emails, change orders, and any approvals that substantiate the exception and show vendor acceptance where applicable.
How long should the form be retained?
Retain according to your document retention policy; tax-related records follow IRS minimums (IRC §6501(a)) and healthcare records must meet HIPAA retention (45 CFR §164.530(j)).

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now