Your organization may already have a well-documented policy for creating electronic documents and managing digital transactions. But what happens when you receive an electronic document created and signed by parties outside your organization? What is your standard for accepting that digital document or relying on an electronic signature?
You’ll want to look to industry best practices if you haven’t already. It’s normally a better bet to have your own internal policy set before imposing one on third parties.
Design transaction profiles that reflect your organization’s own risk mitigation standards
Develop customized assessment tools to apply your criteria to incoming transactions
Provide policy communication tools to cultivate professional levels of trust and expectations with transaction partners and regulators
The end result should be that your organization has the tools necessary to readily recognize and evaluate any externally-generated electronic record for compliance with your standards, without having to run to Legal first.
- 5 FAM 140 ACCEPTABILITY AND USE OF ELECTRONIC SIGNATURES
- CMS Signature_Requirements_Fact_Sheet_ICN905364
- FHA Changes Electronic Signatures Policy
- FAA DOT Notice of policy clarification 2016-09069
- Electronic Signature Policy for lenders – KY housing authority
- GSA Order 2162.1 (2010) – Digital Signatures
- LDWholesale – Electronic Signatures acceptance
- Norther KY U – APPROVED_ElectronicSignature7-2-16
- New esignature Guidance for IRS efile
- Miami Valley Youth Soccer Assn – Electronic signature policy
- SAMPLE ELECTRONIC SIGNATURE POLICY
- Oconee County (SC) Electronic Signature Ordinance