How is usage typically measured?

Usage is measured against the agreed metric—named users, concurrent users, active instances, or transactions. The agreement must define collection method, sampling, and rounding; ambiguity here causes disputes.

Can a true-up be signed electronically?

Yes. Electronic signatures are enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided intent, consent, attribution, and retention are satisfied.

What happens if we disagree with the vendor’s report?

Follow the contract’s dispute process: provide a written challenge within the dispute window, supply supporting data, and escalate to the agreed neutral reviewer or arbitrator if unresolved.

Do audits require onsite access?

Not always. Many agreements allow remote verification via secure data exports or credentialed access; specify acceptable audit methods and data privacy protections in advance.

How should sensitive data be handled in reports?

Mask or aggregate personally identifiable and protected health information when possible. If PHI is shared, include HIPAA BAAs and minimize exposed fields.

What records should we keep?

Keep signed agreements, reports, calculation worksheets, and correspondence for at least the retention period specified—commonly 3–7 years—and longer where regulations require it.

Electronic Signature
Templates
Miscellaneous
License True-Up Agreement

License True-Up Agreement

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

LICENSE TRUE-UP AGREEMENT

Effective Date: Agreement No.:

Parties

Licensor (Company granting license) Licensor Address Licensee (Entity acquiring license) Licensee Address

Recitals

WHEREAS, Licensor is the owner or authorized licensor of certain software, services, or other licensed products described herein (the "Licensed Products"); and

WHEREAS, Licensee currently uses or has previously licensed the Licensed Products and has represented license usage counts to Licensor; and

WHEREAS, the parties desire to reconcile and, if applicable, adjust license quantities and payments by means of this License True-Up Agreement (the "Agreement") pursuant to the terms set forth below.

Definitions

For purposes of this Agreement, capitalized terms shall have the meanings given in this section: "Reporting Period" means the period listed below; "Reported Licenses" means the number of licenses Licensee reported to Licensor for the Reporting Period; "Audited Licenses" means the number of licenses determined by an audit or reconciliation; "True-Up Amount" means the amount owed by Licensee for any under-reported licenses as calculated in accordance with Section Payment Terms.

Scope of Work

The parties agree that Licensor shall perform the reconciliation activities and Licensee shall provide required records in accordance with this Agreement. The scope of reconciliation, reporting requirements, and any remediation activities are described below.

Scope of reconciliation and obligations

License and Reporting Details

License Type(s): Per Seat Per User Enterprise

Reporting Period Start: Reporting Period End:

Reported Licenses: Audited Licenses:

Payment Terms

Unit Price per License:

True-Up Calculation: If Audited Licenses exceed Reported Licenses, Licensee shall pay Licensor the product of (Audited Licenses minus Reported Licenses) multiplied by the Unit Price (the "True-Up Amount"). If Audited Licenses are less than Reported Licenses, any credit shall be addressed in accordance with the adjustments provision below.

True-Up Amount (calculated)

Payment Schedule: Licensee shall pay the True-Up Amount within days of receipt of Licensor's invoice reflecting the True-Up Amount. Partial payments are not permitted unless otherwise agreed in writing.

Late Payment: Any undisputed amount not paid by the due date shall accrue interest at % per month (or the maximum permitted by applicable law, if lower), from the due date until paid.

Adjustments, Credits and Disputes

Adjustments: If Audited Licenses are less than Reported Licenses, Licensor shall provide Licensee a credit equal to the difference multiplied by the Unit Price. Such credit shall be issued as an invoice credit to be applied against future invoices within twelve (12) months following issuance.

Dispute Description (if Licensee disputes audit results)

If Licensee timely notifies Licensor in writing of a dispute within days of receiving the audit report, the parties shall cooperate in good faith to resolve the dispute. Absent manifest error, Licensor's audit findings are binding.

Term and Termination

Term Start Date: Term End Date:

Either party may terminate this Agreement for convenience upon days' prior written notice. Termination shall not relieve Licensee of obligations to pay any accrued True-Up Amounts or amounts due under this Agreement.

For material breach, the non-breaching party may terminate if the breaching party fails to cure within days after written notice specifying the breach.

Confidentiality

Each party shall treat as confidential and shall not disclose to any third party any non-public information of the other party disclosed in connection with the reconciliation and audit process, including license counts, pricing, audit reports, and business practices ("Confidential Information"), except as required by law. Confidential Information shall be used solely for the purposes of performing obligations under this Agreement. Confidentiality obligations shall survive termination of this Agreement for a period of three (3) years.

Audit Rights

Licensor shall have the right, on no less than ten (10) business days' prior written notice and during Licensee's regular business hours, to audit or engage an independent auditor to audit Licensee's records solely to verify compliance with license terms and the accuracy of Reported Licenses. Audits shall be conducted no more than once per twelve (12) month period except where a prior audit reveals material noncompliance. If an audit reveals an under-reporting of more than five percent (5%), Licensee shall reimburse Licensor for reasonable third-party audit costs.

Governing Law and Remedies

This Agreement shall be governed by and construed in accordance with the laws of the state of without regard to its conflict of laws principles. The parties agree that monetary damages may be an inadequate remedy for breach of confidentiality or obligation to provide accurate records and that equitable relief may be sought in addition to any other remedies.

Indemnification and Limitation of Liability

Each party shall indemnify and hold the other harmless from third-party claims arising from its grossly negligent or willful breach of this Agreement. Except to the extent required by applicable law, neither party shall be liable for consequential, special, or punitive damages arising out of this Agreement; however, each party's liability for direct damages related to an uncured material breach shall not be limited with respect to the True-Up Amounts or amounts adjudicated in favor of the non-breaching party.

Entire Agreement

This Agreement, together with any referenced schedules or exhibits executed by the parties, 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 or waiver shall be effective unless in writing and signed by authorized representatives of both parties.

Notices

Licensor Notice Contact Licensee Notice Contact

Miscellaneous

Severability: If any provision of this Agreement is held invalid or unenforceable, the remaining provisions shall remain in full force and effect. Waiver of any breach shall not constitute waiver of subsequent breaches.

Additional Provisions or Notes

LICENSOR

Printed Name:

By:

Date:

LICENSEE

Printed Name:

By:

Date:

What a License True-Up Agreement Is and When It Applies

A License True-Up Agreement is a contractual mechanism used to reconcile actual software license usage with prior license counts or payments. It typically sets a look-back or audit period, defines the basis for measuring usage (for example, named users, concurrent users, or active installations), and establishes how under- or over-usage is converted into additional fees or credits. The agreement often includes reporting requirements, inspection or audit rights, a calculation method for additional charges, timing for payment, and dispute-resolution procedures. Organizations use true-ups to align ongoing usage with commercial license terms without renegotiating the base license agreement.

Why the License True-Up Agreement Matters for Compliance and Cost Control

A true-up agreement provides predictability for both vendor and licensee by defining measurement methods, timelines, and remedies for variance. It reduces surprise invoice disputes and supports audit defensibility while enabling accurate budgeting for incremental license costs and ensuring compliance with the licensor's usage terms.

Typical Parties Who Draft, Review, and Sign a True-Up

Organizations on both sides of a software license transaction rely on true-up agreements to maintain accurate entitlements and financial records.

Licensee IT and procurement teams responsible for tracking user counts or deployments and authorizing payments for supplemental licenses.
Software vendors and contract managers who need audit rights, clear billing formulas, and mechanisms to enforce license compliance.
Legal counsel or compliance officers who review definitions, reporting cadence, dispute resolution, and governing law to limit exposure.

The agreement is most useful where usage fluctuates, where licenses are metered by activity, or where audits are an anticipated enforcement tool.

Who Signs and What Roles They Represent

Authorized Signatory

A company officer or delegated procurement lead signs for the licensee; the signatory must have authority under the organization’s internal approval policy to bind the entity to payment and audit terms.

Vendor Representative

A vendor account manager or contracting officer signs for the licensor; that person must be authorized to accept payments, enforce audit remedies, and escalate disputes per the master license agreement.

Core Elements to Include in a Professional License True-Up Agreement

A comprehensive true-up should state measurement methods, reporting cadence, audit rights, calculation formulas, payment terms, and dispute resolution. Each element reduces ambiguity and facilitates straightforward enforcement.

Measurement Basis

Define whether the metric is named users, concurrent users, active devices, CPU cores, or transactions and how transient usage is counted.

Reporting Cadence

State required reports (monthly/quarterly/annual), submission method, required fields, and who receives the reports.

Audit Rights

Specify inspection procedures, frequency, notice periods, allowed third-party auditors, and data access limitations for privacy/security.

True-Up Formula

Provide arithmetic for converting measured overages to fees, any tiered pricing, rounding rules, and minimums or caps.

Payment Terms

Set due dates, invoicing format, interest on late payments, and whether pre-existing credits apply to true-up balances.

Dispute Resolution

Include timelines to contest reconciliations, escalation steps, and governing law or arbitration provisions.

Step-by-Step: Completing a License True-Up Reconciliation

Use this sequential checklist to gather data, compute usage variances, and complete reconciliation paperwork accurately.

01

Collect Records: Export usage logs and license reports for the true-up period.
02

Apply Measurement Rules: Normalize usage to the agreed metric and apply rounding rules.
03

Calculate Overage: Subtract licensed entitlements from measured usage to determine excess units.
04

Issue Invoice or Credit: Prepare the true-up statement, apply credits, and issue invoice per payment terms.

Typical True-Up Workflow from Reporting to Payment

The following flow shows common handoffs and checkpoints used in true-up processes.

Reporting: Licensee or vendor produces usage report per cadence.
Verification: Parties reconcile counts and correct obvious errors.
Audit (if requested): Vendor exercises audit rights under agreed notice and scope.
Settlement: Vendor issues invoice; licensee pays or disputes within defined timeframe.

How to Complete and Submit a True-Up Electronically

Most organizations complete true-up agreements using PDFs or a contract lifecycle platform, then collect signatures electronically for auditability and speed.

Document Format: PDF or DOCX
Authentication: Email or SMS code
Integrations: CRM/ERP connectors

Use an eSignature platform that provides audit trails, role-based access, and secure storage to preserve evidentiary records and simplify future reconciliations.

Configuring an Online True-Up Workflow

Standard configuration items help automate reporting, approval, and signature collection for recurring true-ups.

Field	Configuration
Report Upload	Automated SFTP or API ingest
Approval Flow	Two-step approval: finance then legal
Signer Authentication	Email + optional SMS code
Record Retention	Store signed PDFs for required retention period

Required Data and Common Fields in the Agreement

Party Names: Full legal names

Effective Dates: Start and end

Measurement Unit: Metric type

Reporting Cycle: Monthly/Quarterly/Annual

Pricing Schedule: Unit price / tiers

Signature Blocks: Authorized signatories

Common Mistakes When Preparing a True-Up

Failing to define the measurement unit clearly, leading to inconsistent counts between parties.
Using ambiguous rounding or pro-ration rules that create calculational disputes.
Neglecting to specify required supporting reports or formats, causing delays in verification.
Omitting timelines for dispute resolution and payment, which increases collection risk.

Risks and Contractual Consequences of an Incorrect True-Up

Back Charges: Vendor may invoice for unpaid license fees or interest

Audit Escalation: Repeated discrepancies can trigger broader audits

Contract Termination: Material breaches may permit termination

Financial Exposure: Unexpected liabilities affecting budgets

Compliance Impact: Noncompliance can void indemnities or warranties

Dispute Costs: Legal and forensic review expenses

Typical Timelines and Deadlines to Track

True-up processes follow preset filing and payment windows; missing these can create late fees or limit dispute remedies.

Report Submission Deadline:

30–60 days after period end

Vendor Review Period:

15–30 days to validate reports

Invoice Issuance:

Within 30 days of reconciliation

Payment Due:

Net 30 commonly used

Dispute Window:

10–20 days to raise disputes

Key Milestones in a License True-Up Cycle

A sequential view of milestones helps stakeholders prepare required exports and approvals on time.

01

Period Close

Collect and freeze usage data for the reporting window.

02

Report Delivery

Submit formatted usage reports to the vendor per agreement.

03

Reconciliation

Vendor and licensee compare counts and resolve discrepancies.

04

Settlement

Issue invoice and process payment or credit adjustments.

eSignature Vendor Comparison for True-Up Execution

Comparison of common vendor starting prices and key capabilities relevant to executing and storing License True-Up Agreements. signNow is listed first per comparison guidelines.

	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

Practical Examples: How Organizations Use True-Up Agreements

Real-world scenarios show common variations in measurement methods and settlement approaches.

Optica Ventures

A mid-market SaaS buyer reconciled named-user counts quarterly

point: vendor accepted CSV exports
As a result, both parties reduced disputes by standardizing a single source of truth and agreed a capped back-charge for a 12-month look-back period to limit exposure.

Tech Data

A large reseller used automated reports from its entitlement system

point: bulk true-up invoices issued annually
The process sped invoicing, improved cash flow predictability, and minimized manual audit labor across the finance team.

Practical Tips for Accurate and Efficient True-Up Management

Follow these practices to minimize disputes and administrative overhead during annual or periodic reconciliations.

Standardize Exports

Automate generation of usage reports in an agreed CSV or PDF format to prevent formatting disputes and reduce manual reconciliation time.

Define Edge Cases

Explicitly state whether trial accounts, terminated users, or inactive service instances count toward entitlements to avoid after-the-fact disagreements.

Agree on Sampling

For very large customer bases, agree in advance on sampling or statistical methods to bound audit scope and cost.

Keep an Audit Trail

Maintain signed reconciliation statements, calculation worksheets, and communications for the retention period to support future audits.

Frequently Asked Questions About License True-Up Agreements

Answers to common questions about measurement, enforcement, and electronic execution of true-up agreements.

Need help? Contact support

How is usage typically measured?
Usage is measured against the agreed metric—named users, concurrent users, active instances, or transactions. The agreement must define collection method, sampling, and rounding; ambiguity here causes disputes.
Can a true-up be signed electronically?
Yes. Electronic signatures are enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided intent, consent, attribution, and retention are satisfied.
What happens if we disagree with the vendor’s report?
Follow the contract’s dispute process: provide a written challenge within the dispute window, supply supporting data, and escalate to the agreed neutral reviewer or arbitrator if unresolved.
Do audits require onsite access?
Not always. Many agreements allow remote verification via secure data exports or credentialed access; specify acceptable audit methods and data privacy protections in advance.
How should sensitive data be handled in reports?
Mask or aggregate personally identifiable and protected health information when possible. If PHI is shared, include HIPAA BAAs and minimize exposed fields.
What records should we keep?
Keep signed agreements, reports, calculation worksheets, and correspondence for at least the retention period specified—commonly 3–7 years—and longer where regulations require it.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now