Substantially revised and editorially reviewed September 8, 2026. The original publication date is not documented.
This is an evaluation checklist for customer and vendor certificate workflows. It does not promise that a product performs every listed step. Confirm the supported module, jurisdiction, integration and permitted action in the demonstration and agreement.
The Role of Exemption Certificates in Indirect Tax Compliance
An exemption or resale certificate can support the treatment of a qualifying transaction when the applicable conditions are met. A document label alone does not establish an exemption. For example, California Regulation 1668 addresses the form, timing and good-faith acceptance of resale certificates. Check the rule for the relevant jurisdiction and transaction rather than applying one national validity test.
A useful evaluation tests what happens after upload: how the document is reviewed, which transactions it can support and what an authorized status change affects. Keep those questions separate from storage and extraction.
There are two distinct categories with different workflows:
- Sales-Side Exemption Certificates — received from customers.
- Purchase-Side Exemption Certificates — issued to vendors.
If your business has both workflows, evaluate each explicitly; a sales-side repository does not establish purchasing-side coverage.
Sales-Side Exemption Certificates: Intake, Validation, Monitoring, and Compliance
Sales-side certificate management begins with certificates received from customers. AI can assist extraction and flag incomplete or inconsistent records. A reviewer must still confirm the applicable requirements and the basis for the claimed treatment.
1. Centralized Repository with Research Visibility
Ask how the selected workflow preserves and retrieves these fields:
| Key Data | Typical Fields |
|---|---|
| Customer Identity | Entity name, address, tax ID, contact information |
| Certificate Metadata | Document type, applicable jurisdiction, exemption reason, expiration date when applicable |
| Validity Details | Signature status, form version, jurisdictional compliance |
| Lifecycle Tracking | Upload date, renewal history, replacement versions |
Inspect whether the fields remain linked to the original document and whether missing or uncertain values are visible.
2. Document Checks and Tax Review
Use a representative upload sample to test which checks the workflow supports and which require a reviewer:
- Is this document actually an exemption certificate?
- Does it contain the required fields for the applicable state or jurisdiction?
- Does it include valid exemption reason codes?
- Does the document meet the applicable signature and date requirements?
- Is there an applicable expiration, revocation or changed-facts issue?
Test extraction and document classification against a sample reviewed by your tax team. The workflow should make missing facts and uncertain classifications visible, with a recovery path for an incorrectly rejected document.
3. Data Extraction and Structuring
For supported extraction, compare the output with the original document. Relevant fields may include:
- Customer ID or name
- Issuing state and multistate applicability
- Exemption reason (resale, manufacturing, direct-pay, agricultural)
- Effective and expiration dates where applicable, with missing and not-applicable values distinguished
- Certificate number
- Signatory identity
If an integration uses these fields, demonstrate the mapping, review step and permitted downstream change. An extracted value should not silently become an approved exemption.
4. Version Control, Lifecycle Awareness, and Accessibility
Validity and renewal requirements depend on the jurisdiction and certificate type. For example, California Regulation 1668 states that a resale certificate remains effective until revoked in writing. Changes in the purchaser or covered transactions can still require review. Configure supported requirements; do not manufacture an annual expiration for every certificate. The system should:
- Track all historical versions without losing any prior certificate.
- Preserve the reviewed status and effective scope of each version instead of activating a replacement solely because it is newer.
- Allow users to view documents, metadata, and expiration status.
- Associate certificates with transactional history to determine exposure if invalid.
5. Notification and Renewal Automation
Where expiration or periodic review applies, evaluate whether the configured workflow can:
- Initiate reminders to internal tax personnel or directly to customers.
- Send secure upload links for certificate replacements.
- Distinguish expired, revoked, missing and awaiting-review records under the applicable rule.
- Track remediation efforts for audit readiness.
6. Secure Customer Upload Portals
If the product offers customer upload links, test their access scope, expiration and connection to the intended account. Demonstrate how a submission enters review and how an incomplete or mismatched document is handled. Confirm whether notices are drafts or sent messages and which permissions control sending. Receipt of a file is not confirmation of an exemption.
7. E-API Connectivity and System Integration
For each integration you need, request a demonstration of the specific supported action:
| Integration to evaluate | Action to demonstrate where supported |
|---|---|
| ERP / Billing | Apply authorized changes based on reviewed certificate scope and transaction facts |
| Tax Engines | Apply certificate status to transaction-level tax decisions |
| Compliance Systems | Support return preparation and audit documentation |
| Customer Portal | Provide upload tracking and renewal status |
Record unsupported integrations as open requirements rather than assuming a feature in one module is available in another.
Purchase-Side Exemption Certificates: Preparation, Authorized Delivery and Tracking
On the purchasing side, confirm the documentation required for the claimed treatment before providing it to a vendor. Requirements differ by exemption and jurisdiction. Texas, for example, explains that a sales tax permit number or copy of a permit does not replace a resale certificate. Texas Comptroller: Resale Certificates.
Key Capabilities for Purchase-Side Certificate Management
1. Governed Selection of Supported Form References
Ask the provider to show the form source, jurisdiction, review date and supported use. A stored form alone does not establish freshness or applicability. Confirm how a reviewer checks the proposed form, exemption basis and transaction context before using it.
2. Reviewable Data and Contextual Fields
Relevant fields such as company name, address, registration numbers, and exemption basis can be prepared for review where the workflow supports them. A qualified user must confirm identity, authority, applicability, and form completeness.
3. Authorized Completion and Delivery
Demonstrate which of these steps the purchased workflow supports, which occur elsewhere and which require separate authorization:
- Completion and signature outside or inside an explicitly approved signing workflow
- Secure sending to vendors directly through the system or downloadable delivery
- Recording delivery or receipt evidence when supplied; sending alone is not proof of receipt
- Ongoing monitoring of expiration dates, form changes, or vendor requests
4. Integration into Procurement and Accounts Payable
For the purchasing workflow, test the supported connection to each required function:
| Function to evaluate | Evidence or action to demonstrate |
|---|---|
| Vendor Master Files | Link certificates to suppliers and qualified purchases |
| Accounts Payable | Flag incoming invoices where tax was incorrectly charged |
| Procurement / ERP | Trigger certificate creation based on contract terms or purchase categories |
| Audit Defense | Retrieve the document, reviewed scope and transaction links supporting a position |
Record the Demonstrated Coverage
Document the tested product version, jurisdiction, integration and user role. List the unresolved requirements and the evidence needed to close them. A successful upload or field extraction does not prove correct tax treatment, successful delivery, vendor acceptance or complete audit support.
Test Both Sides Before Choosing Software
Demonstrate a customer certificate, a purchase-side certificate and an incomplete document. Confirm that the original evidence, jurisdiction, scope, review status and permitted downstream action remain visible. Use the certificate software evaluation checklist for the detailed acceptance questions, and the tax-exempt purchasing overview when comparing the vendor-facing workflow.