What is a BIN versus an EIN?

A BIN is a business identifier used by specific agencies or institutions and may be distinct from an EIN. Confirm the exact identifier the recipient requires before submitting documentation to avoid mismatches.

Can I submit the request with an electronic signature?

Yes, when the recipient accepts electronic records. Ensure the eSignature meets ESIGN and UETA criteria: signer intent, consent to e-records, attribution, and retrievability.

What supporting documents are most often requested?

Common attachments include the formation certificate, EIN confirmation letter, government ID for the signer, and a corporate resolution or operating agreement when signatory authority is not obvious.

How do I avoid common rejections?

Use exact-match names, clear readable scans, and confirm signer authority. Validate the recipient’s notarization or witness requirements before finalizing the submission.

Who must sign the request for a corporate entity?

An authorized officer or an agent with signed, documented authority such as a corporate resolution or power of attorney must sign; include capacity language in the signature block.

How long should I retain completed BIN requests?

Follow the highest applicable retention rule: at least three years for tax purposes (IRC §6501(a)), six years for HIPAA where applicable (45 CFR §164.530(j)), and longer if state law requires it.

Electronic Signature
Templates
Legal
Legal Request for BIN

Legal Request for BIN

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

LEGAL REQUEST FOR BIN

This Legal Request for BIN (the "Request") is entered into as of by and between Requesting Party: , organized as Entity Type: Corporation LLC Sole Proprietor Other with principal place of business at , and Issuing Party: , with principal place of business at .

RECITALS

WHEREAS, Requesting Party desires that Issuing Party assign or register a Business Identification Number ("BIN") to Requesting Party for use in business administration, financial reporting, or regulatory identification; and

WHEREAS, Issuing Party has processes, systems, and authority to issue, reserve, or register BINs under applicable internal policies and applicable law; and

WHEREAS, the parties wish to set forth the terms under which Issuing Party will issue and Requesting Party will accept and use the BIN.

NOW, THEREFORE, in consideration of the mutual covenants and agreements set forth below, the parties agree as follows:

1. DEFINITIONS

1.1 "BIN" means the Business Identification Number assigned by Issuing Party to identify Requesting Party in Issuing Party's records and systems for purposes stated in this Request.

1.2 "Confidential Information" means nonpublic information disclosed by either party relating to the BIN, the request hereunder, or business operations that is designated confidential or would reasonably be understood to be confidential.

2. REQUEST FOR BIN

2.1 Request. Requesting Party hereby formally requests issuance of a BIN by Issuing Party with the following requested parameters: Proposed BIN or format: ; Intended primary use: .

2.2 Supporting Documentation. Requesting Party shall deliver to Issuing Party the following documents at the time of submission:

2.3 Acceptance. Issuing Party shall evaluate the request and notify Requesting Party in writing of acceptance, rejection, or request for further information within a commercially reasonable period. Issuing Party's issuance of a BIN shall be effective upon written notice of assignment.

3. REPRESENTATIONS AND WARRANTIES

Requesting Party represents and warrants that: (a) it is duly organized and validly existing under the laws indicated; (b) the execution, delivery, and performance of this Request have been authorized by all necessary corporate or other organizational action; and (c) all information and documents provided in connection with this Request are true, complete, and not misleading in any material respect.

4. USE, RESTRICTIONS AND MANAGEMENT OF BIN

4.1 Permitted Use. BIN shall be used solely for the purposes described in Section 2.1 and in compliance with applicable laws and Issuing Party policies.

4.2 Prohibited Use. Requesting Party shall not transfer, sell, license, or otherwise assign the BIN except with Issuing Party's prior written consent. Any unauthorized use constitutes a material breach.

5. CONFIDENTIALITY

Each party shall treat as Confidential Information all nonpublic information disclosed in connection with this Request and shall not disclose such information except (a) to its employees, agents, or professional advisors who have a need to know and are bound by confidentiality obligations, or (b) as required by law provided the disclosing party gives prior written notice and assists in any protective measures.

6. FEES AND COSTS

If applicable, fees for issuance, reservation, or maintenance of a BIN shall be as mutually agreed in writing. Requesting Party shall pay any reasonable costs incurred by Issuing Party in connection with evaluating or processing the request. Indicate proposed fee arrangement, if any:

7. COMPLIANCE WITH LAW

Each party shall comply with all applicable laws, rules, and regulations in performing its obligations under this Request. Requesting Party shall not use the BIN in any manner that would cause Issuing Party to be in violation of any applicable law.

8. INDEMNIFICATION

Requesting Party shall defend, indemnify and hold harmless Issuing Party and its officers, directors, employees and agents from and against any claims, liabilities, losses, damages, costs and expenses (including reasonable attorneys' fees) arising out of Requesting Party's misuse of the BIN, breach of representations, or infringement of third-party rights.

9. LIMITATION OF LIABILITY

Except for claims arising from willful misconduct or gross negligence, neither party shall be liable to the other for consequential, incidental, punitive, or special damages. The aggregate liability of either party for any claim arising under this Request shall not exceed the greater of (a) fees paid pursuant to Section 6 in the twelve (12) months preceding the claim, or (b) $.

10. TERM AND TERMINATION

This Request shall commence on the Effective Date and continue until terminated by either party upon thirty (30) days' prior written notice. Issuing Party may suspend or revoke the BIN immediately for cause, including material breach or unlawful use.

11. NOTICES

All notices under this Request shall be in writing and delivered to the addresses below by hand, certified mail, or nationally recognized overnight courier. Requesting Party notice address:

Requesting Party Notice Address Issuing Party Notice Address

12. AMENDMENTS; WAIVER

No amendment, modification, or waiver of any provision of this Request shall be effective unless in a written instrument signed by duly authorized representatives of both parties. No failure or delay in exercising any right shall operate as a waiver.

13. GOVERNING LAW; VENUE

This Request 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 submit to the exclusive jurisdiction of the courts located in that state for disputes arising hereunder.

14. ENTIRE AGREEMENT; SEVERABILITY

This Request constitutes the entire agreement between the parties with respect to its subject matter and supersedes all prior discussions and agreements. If any provision of this Request is held invalid or unenforceable, the remaining provisions shall remain in full force and effect.

15. COUNTERPARTS

This Request may be executed in counterparts, each of which shall be deemed to be an original and all of which together shall constitute one and the same instrument.

16. AUTHORIZED CONTACT

Requesting Party Contact Issuing Party Contact

CERTIFICATION

By signing below, the authorized signatories each certify under penalty of perjury that they are authorized to execute this Request on behalf of the respective party, that the information provided herein is true, accurate, and complete, and that they will comply with the terms and conditions set forth in this Request.

Requesting Party:

By:

Date:

Issuing Party:

By:

Date:

What a Legal Request for BIN Is and when it’s used

A Legal Request for BIN is a formal document submitted to a government agency, financial institution, or registry to obtain, verify, or update a Business Identification Number (BIN). The BIN identifies an entity for licensing, banking, tax reporting, vendor onboarding, or compliance checks. The request typically lists the business legal name, entity type, formation data, authorized signatory details, and supporting evidence. In many workflows the request may be executed and transmitted electronically under U.S. e-signature law (ESIGN/UETA) and must include clear signer attribution and record-retention provisions.

Why a clear Legal Request for BIN matters

A precise request reduces processing delays, prevents mismatches with tax and banking records, and makes subsequent verifications simpler.

Organizations and roles that commonly complete this request

Typical filers include new businesses seeking a BIN, legal or accounting teams preparing entity records, banks onboarding commercial accounts, and third-party vendors validating supplier identities.

Accounting and finance teams: Prepare supporting tax documents and ensure TIN/BIN alignment for reporting.
Legal and compliance teams: Verify formation documents, authorized signatories, and governing-state selection.
Banks and payment processors: Use requests to confirm KYC data and open accounts or link merchant services.

Who completes the form depends on the recipient: state agencies, federal partners, banks, or private registries will dictate required signers and evidence.

Representative signer profiles

Owner — CEO

A business owner or CEO typically signs when assigning the BIN to a newly formed entity or correcting primary identity data; their signature confirms legal authority and triggers record updates with tax and banking partners.

Corporate Counsel

In regulated or multi-entity situations corporate counsel or an authorized officer signs to confirm corporate resolutions, attest to formation documents, and ensure the BIN request aligns with governing-state filings and internal policies.

Essential compliance and security elements to include

Authentication: Email, SMS code, KBA

Transport Security: TLS 1.2 / TLS 1.3

Data Encryption: AES-256 at rest

Audit Trail: Timestamp and IP

Regulatory Standards: ESIGN, UETA compliance

Sensitive Data: HIPAA BAA where applicable

Core components of a professional Legal Request for BIN

A complete request groups identity, authority, and supporting evidence into clearly labeled sections so reviewers can verify identity and issue or update a BIN without follow-up.

Requester

Full legal name and contact details for the submitting party, including phone, email, and physical address; this identifies who can answer follow-up questions and receive confirmations.

Entity Details

Business legal name, DBA (if any), entity type (LLC, Corp, Sole Proprietorship), state of formation, and formation date as shown on formation or tax filings.

Requested BIN Action

Clear description of the action requested: new BIN issuance, verification of existing BIN, correction of BIN data, or BIN transfer between records.

Authorized Signatory

Name, title, and authority basis (e.g., corporate resolution or operating agreement) for the person signing the request.

Supporting Documents

Attach formation documents, EIN notice, driver’s license or passport for authorized signer, and any vendor agreements requiring the BIN.

Signature and Date

Signature block with printed name, role, date, and preferred delivery method; indicate whether eSignature is used and include consent language if consumer-facing.

Step-by-step: preparing and submitting the request

Follow these sequential steps to complete and send a Legal Request for BIN with minimum rework.

01

Collect entity records: Gather formation certificate, EIN confirmation, and any operating agreement excerpts.
02

Confirm signatory authority: Verify meeting minutes or corporate resolution authorizing the signer.
03

Complete the form: Fill required fields exactly as official records show.
04

Sign and submit: Apply authorized signature, attach documents, and send to the designated recipient.

Configuring a digital workflow for BIN requests

Set up a repeatable template and validation rules to reduce errors and accelerate approvals.

Field	Configuration
Authentication	Email link with optional SMS code
Field validation	Enforce exact-match formatting for names and dates
Conditional fields	Show extra fields when correction or transfer selected
Notifications	Auto-notify requestor and compliance after completion

Typical submission and processing flow

A clear process path helps requestors and reviewers know what to expect after submission.

Prepare request: Complete form and attach evidence
Submit to recipient: Send to agency, bank, or registry email/address
Verification: Recipient reviews documents and may request clarification
Completion: BIN issued, updated, or a correction workflow is opened

Digital submission: formats and integrations to prefer

Use common, machine-readable formats and integrate with core systems to reduce manual data entry and errors.

File formats: PDF, DOCX acceptable
Integrations: Salesforce, NetSuite, Google Workspace
Authentication: SMS, email, or KBA

Connecting the request template to accounting, CRM, or document storage reduces duplicate entry and preserves an auditable record.

Timelines and deadlines to watch when exchanging identity data

Some BIN-related actions have explicit deadlines (tax or reporting) while others are processed on agency timelines; follow recipient instructions closely.

W-9 / TIN requests:

Provide on request; no fixed filing deadline

1099-NEC reporting:

Recipient deadline: Jan 31 (per IRS)

1099-MISC filing:

Paper to IRS: Feb 28; electronic: Mar 31

Income tax returns:

Form 1040 due Apr 15 (extensions available)

I-9 retention:

Retain 3 years after hire or 1 year after termination (8 CFR §274a.2)

Key milestones from preparation to retention

Track these stages to ensure complete documentation and ongoing recordkeeping.

01

Document preparation

Assemble formation records, EIN, and ID for signer

02

Submission

Send request and attachments to designated recipient

03

Agency verification

Recipient validates evidence and confirms BIN action

04

Record retention

Store completed request per retention rules

Common mistakes that delay BIN requests

Mismatched names or entity types between the request and formation documents, causing identity verification failures and rework requests.
Missing or low-quality supporting documents (scans unreadable, partial pages), which force recipients to request clearer evidence or certified copies.
Unauthorized signer or missing capacity evidence, such as absent corporate resolution or power of attorney documentation for the signer.
Improperly formatted dates, incomplete addresses, or P.O. boxes used where a physical address is required for service or validation.

Consequences of incorrect or incomplete BIN requests

Reporting penalties: Incorrect 1099 data can trigger IRC §6721 penalties

Banking delays: Account holds or onboarding denials

Compliance risk: KYC failures and regulatory scrutiny

Contract disruption: Vendor payments withheld pending verification

Reputational harm: Trust issues with partners and customers

Audit exposure: Extended documentation requests from authorities

Example eSignature pricing and capabilities for BIN workflows

Compare typical vendor starting prices and capability signals; choose a provider that supports HIPAA if handling protected health information.

	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
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently asked questions about Legal Requests for BIN

Answers to common points of confusion when preparing, signing, and submitting a BIN request.

Need help? Contact support

What is a BIN versus an EIN?
A BIN is a business identifier used by specific agencies or institutions and may be distinct from an EIN. Confirm the exact identifier the recipient requires before submitting documentation to avoid mismatches.
Can I submit the request with an electronic signature?
Yes, when the recipient accepts electronic records. Ensure the eSignature meets ESIGN and UETA criteria: signer intent, consent to e-records, attribution, and retrievability.
What supporting documents are most often requested?
Common attachments include the formation certificate, EIN confirmation letter, government ID for the signer, and a corporate resolution or operating agreement when signatory authority is not obvious.
How do I avoid common rejections?
Use exact-match names, clear readable scans, and confirm signer authority. Validate the recipient’s notarization or witness requirements before finalizing the submission.
Who must sign the request for a corporate entity?
An authorized officer or an agent with signed, documented authority such as a corporate resolution or power of attorney must sign; include capacity language in the signature block.
How long should I retain completed BIN requests?
Follow the highest applicable retention rule: at least three years for tax purposes (IRC §6501(a)), six years for HIPAA where applicable (45 CFR §164.530(j)), and longer if state law requires it.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now