Establishing secure connection…Loading editor…Preparing document…

Oklahoma Income Tax Declaration for Electronic Filing

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

Oklahoma Income Tax Declaration for Electronic Filing

(for Form 512, 512-S, 513, 513-NR or 514)

Do not send to the Oklahoma Tax Commission. Keep Form EF for your records.

For calendar year 2024 or tax year beginning , 2024 and ending , 20

1 TAX RETURN INFORMATION (Whole dollars only. Complete lines A and B. Enter the applicable amounts from the return, if any.)

Form 512: A. Oklahoma taxable income (Form 512, line 1)

B. Refund or balance due (Form 512, line 16 or 20)

Form 512-S: A. Nonresident share of taxable income (Form 512-S, line 1)

B. Refund or balance due (Form 512-S, line 16 or 20)

Form 513: A. Taxable income of fiduciary (Form 513, line 23)

B. Refund or balance due (Form 513, line 36 or 40)

Form 513NR: A. Taxable income of fiduciary (Form 513-NR, line 25)

B. Refund or balance due (Form 513-NR, line 40 or 44)

Form 514: A. Nonresident share of income (Form 514, line 1)

B. Refund or balance due (Form 514, line 14 or 18)

2 DECLARATION OF OFFICER, PARTNER, MEMBER OR FIDUCIARY

If a balance due return is being filed, I understand that if the Oklahoma Tax Commission (OTC) does not receive full and timely payment of the tax liability, the entity will remain liable for the tax liability and all applicable interest and penalties.

Under penalties of perjury, I declare I have compared the information contained on the return, with information I have provided to my Electronic Return Originator (ERO), and the amounts described in Part One above, agree with the amounts shown on the corresponding lines of the Oklahoma income tax return. To the best of my knowledge and belief, the return is true, correct, and complete. I consent the return, including this declaration and accompanying schedules and statements, be sent to the OTC by my ERO.

In addition, by using a computer system and software to prepare and transmit my return electronically, I consent to the disclosure to the OTC of all information pertaining to my use of the system and software and to the transmission of my tax return electronically.

3 DECLARATION OF ELECTRONIC RETURN ORIGINATOR (ERO) AND PAID PREPARER

I declare I have reviewed the above taxpayer’s return and the entries on Form EF are complete and correct to the best of my knowledge. (EROs who are collectors are not responsible for reviewing the taxpayer’s return; however, they must ensure Form EF accurately reflects the data on the return.) I have obtained the taxpayer’s signature on Form EF and have provided the taxpayer with a copy of all forms and information to be filed with the OTC, and have followed all other requirements described in the Federal Publication for Modernized e-File. If I am also a Paid Preparer, under penalties of perjury I declare I have examined the above taxpayer’s return and accompanying schedules and statements, and to the best of my knowledge and belief, they are true, correct and complete. This Paid Preparer declaration is based on all information of which I have any knowledge.

ERO Must Retain Form EF - Unless Requested Do Not Submit This Form to the Oklahoma Tax Commission.

Enter text✕

What the Oklahoma Income Tax Declaration for Electronic Filing Is

The Oklahoma Income Tax Declaration for Electronic Filing is a taxpayer statement used to authorize electronic submission of a state income tax return and to confirm required information and consents. It records taxpayer identity, tax year, filing status, and consent to accept electronic communications and signatures, and it documents acceptance of e-filing procedures under federal and state e-signature laws. The declaration streamlines submission to the Oklahoma Tax Commission and creates an auditable record that supports attribution, intent, and retention for compliance and dispute resolution.

Why a Formal Electronic Filing Declaration Matters

A clear declaration documents intent and consent to use electronic records and signatures, reducing ambiguity for parties and examiners while aligning with ESIGN and UETA principles.

Why a Formal Electronic Filing Declaration Matters

Who Typically Prepares or Signs This Declaration

Each signer must verify identity and consent; for representatives, the declaration should include authority statements that tie the representative to the taxpayer.

  • Individual taxpayers using online filing services or OTC e-file portals.
  • Certified public accountants and enrolled agents submitting returns on clients' behalf.
  • Payroll teams or third-party filers transmitting multiple employee returns.

Stepwise Workflow to Complete and Submit the Declaration

Complete the declaration in sequence, verify all entries, confirm consent language, and then apply an electronic signature before submission.

  • 01
    Prepare Document: Gather ID, TIN, and return details before starting.
  • 02
    Enter Required Fields: Complete name, TIN, tax year, filing status, and contact info.
  • 03
    Confirm Consent: Read ESIGN disclosure and indicate consent as required.
  • 04
    Sign and Submit: Apply e-signature, date, and send via approved e-file channel.

Typical Digital Workflow Settings for eSubmission

Configure the e-file workflow to capture consent, identity evidence, and a tamper-evident signed PDF with an audit trail.

Field Configuration
Consent Checkbox Requires affirmative opt-in before enabling submit
Authentication Level Email plus SMS code for representative filers
Audit Trail Capture IP, timestamp, and signer email
Signed Output Generate PDF with embedded audit certificate

How Electronic Filing and Declaration Flow Typically Works

A standard flow ensures the declaration is captured, the return packaged, authentication logged, and the completed record archived.

  • Upload Return: Prepare tax return files and attach to package
  • Add Declaration: Insert completed declaration to accompany return
  • Authenticate Signer: Use email link or SMS code to verify identity
  • Transmit to OTC: Send via approved e-file gateway with receipt

Technical and Platform Considerations for eSubmission

Ensure the platform you use documents consent, retention, and signer attribution to meet ESIGN and state requirements.

  • File Formats: PDF and DOCX supported
  • Integrations: Works with accounting and payroll systems
  • Access Controls: Role-based permissions

Key Filing and Reporting Deadlines to Note

Timely declaration and filing align with federal and state tax deadlines; missing dates can trigger penalties and processing delays.

Individual Return Due:

April 15 each year (Form 1040 deadline)

Extension Deadline:

October 15 with approved Form 4868 extension

1099-NEC Deadline:

January 31 to recipients and IRS

1099-MISC Electronic:

March 31 if filing electronically to IRS

W-9 Provision:

Provide upon payer request; no fixed due date

Penalties and Risks of Incomplete or Incorrect Declarations

Late Information Return: Penalties per form
Incorrect TIN: Backup withholding may apply
Intentional Disregard: Higher uncapped penalties
I-9 Paperwork: Civil fines possible
Audit Exposure: Increased IRS scrutiny risk
Data Breach: Privacy and regulatory consequences

Security and Compliance Essentials for Electronic Declarations

Transport Encryption: TLS 1.2/1.3
Data at Rest: AES-256 encryption
Certifications: SOC 2 Type II and ISO 27001
Health Data: HIPAA compliant with BAA
Legal Frameworks: ESIGN and UETA compliance
Audit Trail: Detailed signer metadata retained

Electronic Signature Versus Digital Signature: Key Differences

Understand the technical and legal distinctions so you can choose the appropriate signature type for compliance and non-repudiation needs.

Criteria Electronic signature Digital signature
Definition broad legal category pki-based cryptographic
Legal acceptance esign/ueta valid esign/ueta valid
Non-repudiation audit trail evidence strong certificate chain
Typical use everyday forms high-assurance regulated filings

Comparing eSignature Pricing and Key Features for Declarations

Vendor pricing models vary; signNow appears first for parity and includes widely used compliance features. Confirm plan details with each provider before purchase.

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 vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Practical Tips for Accurate and Efficient Declarations

Follow these best practices to reduce errors, avoid penalties, and create defensible electronic records for Oklahoma state filings.

Verify Identity Documents
Compare the taxpayer name and TIN to government ID and Social Security records before signing to avoid mismatches and backup withholding triggers.
Use Clear Consent Language
Include an explicit ESIGN-style consent statement if the form is consumer-facing so electronic acceptance meets 15 U.S.C. ch. 96 standards.
Capture Robust Audit Trails
Log IP address, timestamps, authentication method, and signer email to support attribution and rebut potential disputes.
Retain Reproducible Copies
Store signed PDFs with embedded audit certificates in a secure repository for the IRS minimum retention and any longer state or industry periods.

Frequently Asked Questions and Troubleshooting

Answers to common questions about legal validity, signature methods, errors, and recordkeeping for the Oklahoma Income Tax Declaration for Electronic Filing.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users