Document Header
Identify the document as a Price Change Notification Form and include version or reference numbers to link it to sales orders or contracts for traceability.
A formal notice reduces contractual ambiguity, supports consistent billing, and documents consent or acknowledgement. It limits disputes by capturing the effective date and rationale, and it preserves a record that can be produced to auditors, regulatory reviewers, or in customer service escalations.
Use the form to centralize approvals and to create a single authoritative record that downstream teams can reference.
Identify the document as a Price Change Notification Form and include version or reference numbers to link it to sales orders or contracts for traceability.
Name the parties precisely using legal entity names and account numbers so the notice unambiguously identifies the contract, account, or service affected by the price change.
Provide both the old price and the new price with units, measurement basis (per month, per user), taxes, and any conditional pricing elements clearly stated.
State the exact effective date in MM/DD/YYYY format and specify whether the date applies to new orders, renewals, or all invoices following that date.
Briefly explain the reason for the change (e.g., cost increases, feature changes) and list any transitional terms such as grandfathering or pro rata billing adjustments.
Include the sender’s contact details, required approver name and title, and a signature block or e-signature field plus instructions for customer acknowledgement.
| Field Name and Recommended Configuration | Value |
|---|---|
| Authentication Method | Email link plus optional SMS code for higher assurance. |
| Template Usage | Use a locked template to prevent unapproved language changes. |
| Delivery Confirmation | Enable read receipts and delivery timestamps. |
| Storage Location | Save final PDF to contract repository and ERP mapping. |
Ensure the platform provides tamper-evident signed PDFs, an auditable action log (IP, timestamp), and connectors that push executed notices into billing and contract systems.
Follow the notice period required by the contract; this overrides typical practices.
Commonly use 30 to 60 days notice for recurring billing adjustments.
One-time fee increases may apply immediately if contract permits and notice requirement is met.
Utilities or telecom rates may require regulator filings or specific public notice.
Align effective date with billing cycles to avoid proration disputes.
| 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, no card required | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| 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 by plan | Varies by plan | Varies by plan |
The pricing manager or commercial lead typically prepares the notice, documents the rationale with supporting cost or margin analysis, and routes the filled form for finance and legal approval before dispatch.
A delegated officer in legal or finance signs to confirm contract compliance and accounting treatment; their signature signals internal approval to apply new rates in billing systems.