Can the form be signed electronically?

Yes. Electronic signatures meet US legal standards under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states when intent, consent, attribution, and record retention are demonstrated.

Is notarization required?

Not typically for a Finance Addbacks Form, but specific lenders or jurisdictions may require notarization; check counterparty requirements and state rules before execution.

Who should sign the form?

An authorized officer such as the CFO or controller should certify figures; preparers may sign a separate preparer block to document responsibility.

What supporting documents are necessary?

Attach ledger extracts, invoices, bank statements, and reconciliations for each addback. Lack of documentation is the most common reason for rejection.

What happens if amounts change post-signature?

Prepare an amendment or corrected form with versioning and a new signature; record reasons for change to maintain auditability and avoid covenant disputes.

How long should the signed form be retained?

Retain for at least 3 years plus the active term; follow IRS retention guidance (IRC §6501(a)) and industry-specific rules such as HIPAA six-year retention when applicable.

Electronic Signature
Templates
Finance
Finance Addbacks Form

Finance Addbacks Form

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

FINANCE ADDBACKS FORM

Entity and Contact

Company / Entity: Department / Cost Center: Prepared by (Name):

Contact Phone:

Contact Email:

Reporting Period: From to . Total company reported period amount (for reference):

Certification and Purpose

Certification of Accuracy: The preparer certifies that each addback listed below is true, complete and presented in accordance with the company's addback policy and applicable accounting standards. These adjustments are intended solely for non-GAAP performance presentation, and do not constitute tax return positions. Supporting documentation shall be retained and made available for audit. Material changes to reported results arising from these addbacks require written approval by the Controller or Finance Director.

Supporting documentation attached:

Yes Pending Not applicable

Itemized Addbacks

#	Description	Category	Reason for Addback / Business Rationale	Amount	Tax Effect	Account Code	JE Req'd
1
2
3
4
5
6

Subtotal of Addbacks:

Total Tax Impact:

Other Adjustments:

Total Addbacks:

Classification and Accounting Treatment

Classify each addback according to the company's addback policy. Check all that apply to the aggregated submission:

Non-recurring Recurring One-time Extraordinary Pro-forma

Cash item Non-cash item Requires Controller approval

Notes, Supporting Details and Internal Controls

Notes / Terms & Conditions:

Audit and Retention: All supporting documentation and working papers supporting the addbacks will be retained for a minimum of seven years in accordance with company record retention policy and will be made available for internal or external audit review upon request. The preparer and approver acknowledge responsibility for the accuracy of the associated GL postings should adjusting journal entries be executed.

Preparer (Print Name):

By:

Date:

Approver (Print Name):

By:

Date:

What the Finance Addbacks Form Is and when it's used

The Finance Addbacks Form records adjustments to a company's reported operating income for purposes such as valuation, loan covenant calculations, or transaction diligence. Typical addbacks restore non-recurring, non-cash, or discretionary expenses to produce normalized EBITDA or cash flow for lenders, acquirers, and internal management review. The form identifies each addback line item, its rationale, the numerical adjustment, the supporting schedule or attachment, and a certification by an authorized signer attesting to accuracy and documentation.

Why a clear Finance Addbacks Form matters

A well-prepared Finance Addbacks Form creates a transparent, auditable record of adjustments that stakeholders rely on for credit decisions, purchase price allocations, and covenant testing. It reduces disputes by linking each addback to source documents and a named approver.

Typical users and reviewers

The Finance Addbacks Form is completed and reviewed by finance and deal teams, then circulated to external reviewers such as lenders, auditors, and acquirers.

CFO teams and controllers who prepare and certify addback line items, reconciliations, and supporting schedules.
Buy-side analysts and private equity associates who verify adjustments during diligence and model integration.

Accurate completion shortens review cycles and reduces requests for follow-up documentation from external parties.

Step-by-step: preparing and circulating the form

Follow this sequential checklist to prepare, verify, and distribute a Finance Addbacks Form so it is audit-ready and accepted by counterparties.

01

1. Draft: List each addback with description and amount
02

2. Attach: Upload supporting schedules and source documents
03

3. Certify: Authorized officer signs and dates the form
04

4. Distribute: Send to lenders/parties with audit trail

Common online workflow settings for the form

Standard configuration options help ensure consistent routing, authentication, and storage across deals and periods.

Field	Configuration
Template Name	Use a standardized template per deal type
Conditional Fields	Show fields only when relevant (e.g., tax vs. non-tax)
Signer Order	Set sequential signing: preparer → CFO → external reviewer
Authentication	Email + SMS code or KBA for higher assurance

Where to send or file the completed form

A clear routing plan avoids version confusion and supports audit trails for lenders and acquirers.

Upload: Store original with version identifier in deal repository
Send to Lender: Transmit signed copy to lender contact or counsel
Provide to Auditor: Include attachments and reconciliations for audit review
Archive: Save signed PDF plus audit trail in records system

Technical and integration considerations for eSubmission

Verify the eSignature platform supports your file formats, authentication level, and records retention before sending the form to counterparties.

Integrations: Salesforce | NetSuite | Google Workspace | Box
File Formats: PDF | DOCX | XLSX
Auth Options: Email link, SMS code, KBA, SSO

Use integrations to automate storage and recordkeeping; select authentication that matches the transaction risk and counterparty requirements.

Typical timelines and review expectations

Expect different turnaround targets depending on transaction stage; set realistic internal SLAs to avoid bottlenecks.

Internal Drafting:

3–5 business days to assemble and reconcile source data

Internal Approval:

2–7 business days for CFO or controller certification

External Review:

7–14 calendar days for lender or buyer questions

Integration Adjustment:

30 days post-close for model updates

Final Archival:

Archive immediately after execution with audit trail

Common preparation errors to avoid

Using subjective language for addbacks (e.g., 'management discretion') without objective support increases dispute risk and slows approval.
Omitting source documents or ledger references forces reviewers to request additional substantiation and delays the transaction.
Mixing period ranges (e.g., accrual vs cash months) without reconciliation leads to inconsistent EBITDA adjustments.
Failing to certify or route the signed form to the correct authorized officer can render the adjustment unenforceable for covenant testing.

Immediate risks of incorrect or unsigned forms

Incorrect Amounts: Covenant breach risk

Missing Signatures: Enforceability questions

Wrong TIN: 24% backup withholding

Late Submission: Contractual penalty exposure

Unverifiable Addbacks: Due diligence holdbacks

Intentional Misstatement: Regulatory or fraud exposure

Essential components of a professional Finance Addbacks Form

A complete form combines clear identification, standardized calculations, and certifying signatories so third parties can reproduce and accept adjustments.

Header

Entity name, reporting period, preparer contact, and version number for change control and auditability.

Addback Description

Concise explanation of why the item is non-recurring or non-operational, with objective criteria for inclusion.

Calculation

Line-by-line math showing gross-to-net adjustments, rounding rules, and references to accounting policies.

Supporting Schedules

Attached source documents, ledger extracts, and reconciliations cross-referenced to each addback line.

Certifications

Signed statement by an authorized officer attesting to accuracy and completeness of supporting evidence.

Version Control

Version date, approver initials, and archival location to prevent confusion across deal participants.

Practical examples of use in transactions

These scenarios illustrate common contexts where a Finance Addbacks Form clarifies adjusted earnings for decision-makers.

Private Equity Example

A buy-side team compiles addbacks to normalize EBITDA across three quarters

Each addback links to a supporting invoice or ledger extract
The form reduced back-and-forth with sellers and shortened purchase price adjustment negotiations by enabling direct verification.

Bank Underwriting Example

A commercial lender requests addbacks to assess covenant compliance

Borrower provides reconciled schedules and bank statements
Lender relies on the certified form plus audit trail to finalize covenant calculations and funding conditions.

Who typically signs and certifies the form

CFO / Controller

Chief financial officers or controllers certify addbacks as part of financial representations; they review supporting schedules and ensure adjustments align with accounting policies and board-approved estimates.

Buy-Side Analyst

A buy-side analyst or deal accountant prepares the schedules and provides the reconciliations; they may sign preparer blocks and annotate source document links for reviewer confirmation.

Practical tips for accurate and efficient completion

Follow these practices to reduce review cycles and improve acceptability to external parties.

Standardize Line Items

Use a consistent chart of addback categories across periods so reviewers can compare like-for-like adjustments.

Attach Source Documents

Include invoices, bank statements, or ledgers and cross-reference them to each addback line for rapid verification.

Use Audit Trails

Capture signer identity, timestamps, and IP addresses for each execution to support enforceability and due diligence.

Maintain Version History

Keep prior versions accessible and note changes to avoid contradictory representations during negotiations.

eSignature pricing and capability snapshot for executing the form

Compare basic pricing and capability criteria across common eSignature vendors. signNow appears first in the table per vendor ordering rules.

	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 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

Frequently asked questions about the Finance Addbacks Form

Answers to common execution, acceptance, and retention questions related to completing and signing the Finance Addbacks Form.

Need help? Contact support

Can the form be signed electronically?
Yes. Electronic signatures meet US legal standards under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states when intent, consent, attribution, and record retention are demonstrated.
Is notarization required?
Not typically for a Finance Addbacks Form, but specific lenders or jurisdictions may require notarization; check counterparty requirements and state rules before execution.
Who should sign the form?
An authorized officer such as the CFO or controller should certify figures; preparers may sign a separate preparer block to document responsibility.
What supporting documents are necessary?
Attach ledger extracts, invoices, bank statements, and reconciliations for each addback. Lack of documentation is the most common reason for rejection.
What happens if amounts change post-signature?
Prepare an amendment or corrected form with versioning and a new signature; record reasons for change to maintain auditability and avoid covenant disputes.
How long should the signed form be retained?
Retain for at least 3 years plus the active term; follow IRS retention guidance (IRC §6501(a)) and industry-specific rules such as HIPAA six-year retention when applicable.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now