BDM58

Use a Bdm58 2016 template to make your document workflow more streamlined.

What BDM58 is and how it works

BDM58 is a U.S. form identified by its code, but the available information does not establish its issuing agency, purpose, filing deadline, or required fields. To complete it accurately, obtain the authoritative BDM58 instructions, upload the current document to signNow, review any automatically detected fillable fields, assign signer and date fields, and send it through the appropriate workflow. signNow can capture electronic signatures, completion evidence, and an audit trail; it cannot determine whether a specific agency accepts electronic filing or replace the form’s official instructions.

Organizations completing BDM58

Teams that use BDM58 should first confirm the form’s issuing authority, purpose, required fields, and signature instructions. signNow can support completion and e-signature workflows, but it does not determine which person must file the form or whether an agency accepts electronic delivery.

Authorized signers and reviewers

A finance, operations, legal, or administrative team can upload BDM58, assign fields, send it to the responsible signer, and retain the completed file. The exact audience depends on BDM58’s underlying program or transaction, which should be confirmed from the source form or governing instructions.

Business types that may use BDM58

The right BDM58 workflow depends on the form’s official purpose, the responsible signer, and the organization’s recordkeeping obligations.

Solo practitioners can use BDM58 when they control the source document, verify the required fields, and need one auditable signing workflow without paper handling.
Small business finance or operations teams can route BDM58 to designated signers, preserve completion evidence, and connect records to accounting or cloud-storage systems.
Enterprises can standardize BDM58 through templates, role-based access, integrations, and stronger authentication while aligning retention with the form’s underlying regulatory or business record.

Complete BDM58 in signNow

Use the authoritative BDM58 instructions first, then prepare, route, sign, and preserve the completed electronic record.

Upload BDM58:
Upload the current BDM58 file.
Check fields:
Review detected fields against the source.
Assign signers:
Assign each signer and required field.
Send and store:
Send BDM58 and store completion evidence.

be ready to get more

Get legally-binding signatures now!

Start free trial

Request a call

Best ROI. Our customers achieve an average 7x ROI within the first six months.
Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
Intuitive UI and API. Sign and send documents from your apps in minutes.

Authenticate signer:

The audit trail records the signer’s identity and authentication event.

Capture timestamp:

Each BDM58 signing action receives a recorded date and time.

Record document integrity:

The completed document is associated with an integrity record.

Seal history:

The signing history becomes tamper-evident after completion.

Create certificate:

The certificate of completion links actions to the signed BDM58.

Export audit trail:

Authorized users can retrieve or export the completed audit record.

Setting	Recommendation
Authentication method	Email verification with SMS OTP
Signature type	Electronic signature with signing intent
Audit trail	Capture completion certificate and action history
Document retention	Apply the rule for BDM58’s record category
Encryption	AES-256 at rest and TLS 1.2/1.3 in transit

Find and fill out the correct bdm58

airSlate SignNow helps you fill in and sign documents in minutes, error-free. Choose the correct version of the editable PDF form from the list and get started filling it out.

Versions	Form popularity	Fillable & printable
NZ BDM58 2016	4.8 Satisfied (13886 Votes)
NZ BDM58 2014	4.7 Satisfied (172 Votes)

Security for BDM58 records

Data at rest:

Encrypted with AES-256

Data in transit:

Protected by TLS 1.2/1.3

Security certification:

Certified under SOC 2 Type II

Management certification:

Certified under ISO 27001

Electronic signatures:

Supports ESIGN and UETA

Healthcare protection:

HIPAA compliance requires a BAA

Connect BDM58 to business systems

Route completed BDM58 records into CRM, ERP, cloud-storage, and collaboration systems while preserving the signed-document workflow.

Record-keeping practices for BDM58

A defensible BDM58 file includes the signed document, its completion evidence, controlled access, and retention decisions tied to the underlying record category.

Export the signed record package

Export the completed BDM58 and certificate of completion after signing, then preserve the audit trail with the same matter or transaction record. Record the export date, responsible administrator, and repository location so the electronic record can be reproduced during review.

Map retention to the record type

Apply the retention period tied to BDM58’s actual purpose. Tax records generally use three years from filing under IRC §6501(a), while HIPAA records use six years under 45 CFR §164.530(j); confirm which rule applies before deletion.

Limit access to sensitive information

Restrict access to BDM58 files containing taxpayer, health, payment, or other sensitive information. Use role-based permissions, review sharing settings, and remove access when a user changes responsibilities or leaves the organization.

Protect the original signed file

Keep the original completed document separate from later working copies. Preserve the signed PDF, completion certificate, and audit history together, and document any permitted amendment through a new controlled transaction rather than silently editing the signed file.

BDM58 record retention schedule

Retention depends on what BDM58 documents; apply the governing federal or state rule rather than assuming the form itself sets a period.

Three years from filing

Retain tax-related BDM58 records three years from filing under IRC §6501(a), unless another rule applies.

Six years for understatement

Retain records six years when 25% or more income was understated under IRC §6501(a).

Six years for HIPAA records

Retain healthcare records six years from creation or last effective date under 45 CFR §164.530(j).

Three years for payroll

Retain payroll records three years under 29 CFR §516.5 when BDM58 supports covered payroll documentation.

Thirty years for exposure records

Retain OSHA exposure records 30 years under 29 CFR §1910.1020 when BDM58 documents covered exposure information.

Risks when BDM58 is mishandled

Incomplete submission

Missing required information

Evidence weakness

Unclear signer attribution

Privacy exposure

Unauthorized disclosure

Filing rejection

Wrong delivery method

BDM58 signing and troubleshooting

These answers address field detection, signer identity, electronic consent, plan selection, legal effect, and record preservation for BDM58 workflows.

Upload the source PDF again and inspect the detected fields before sending. signNow’s Business plan includes templates and audit trails, but field detection should be checked against the original BDM58 because an electronic workflow does not correct missing or misplaced form information.

Use the signer’s email address and add SMS authentication when stronger attribution is needed. signNow records signing events in an audit trail, while ESIGN and applicable state law require intent, consent, attribution, and a reproducible electronic record.

A Business subscription includes legally binding eSignatures and audit trails. Business Premium adds bulk send, while Enterprise adds advanced signer authentication; choose the plan based on BDM58 volume and identity-control requirements.

For a consumer-facing BDM58 transaction, provide the required electronic-record disclosure and demonstrate access to the electronic format under 15 U.S.C. §7001(c). Obtain consent before relying on the electronic record, unless an applicable exception applies.

ESIGN generally gives electronic signatures legal effect in interstate commerce, and UETA governs most intrastate transactions. These laws do not confirm that a specific agency accepts BDM58 electronically, so verify the form’s filing instructions separately.

Export the signed BDM58 and its certificate of completion from signNow, then store them under the retention rule governing the underlying record. ESIGN and UETA require accurate reproduction, but they do not establish one universal retention period.

28M+Documents signed

13+Years in business

4.6/5Average G2 rating

BE READY TO GET MORE

Get this form now!

If you believe that this page should be taken down, please follow our DMCA take-down process.