Number Transfer Agreement
What a Number Transfer Agreement covers
Why using a formal Number Transfer Agreement matters
A clear, signed agreement reduces disputes, records authorization for carriers, protects against unauthorized transfers, and documents consideration and obligations. It provides a single source of truth for billing, regulatory audits, and downstream service changes.
Who normally completes a Number Transfer Agreement
Use the agreement whenever a documented authorization is required by a receiving carrier, when ownership changes, or when financial or regulatory recordkeeping obligations follow the transfer.
- Telecom carriers and porting teams handling inter-carrier transfers and authorization verification.
- Businesses and nonprofits moving phone lines or account numbers during mergers, vendor changes, or asset sales.
- Resellers, brokers, and service providers recording ownership changes and billing responsibility shifts.
Step-by-step: completing and submitting the agreement
-
011. Verify authority: Confirm signer has legal authority to transfer the number.
-
022. Populate details: Enter number, account, port code, and effective date accurately.
-
033. Sign and authenticate: Collect required signatures and choose appropriate signer authentication.
-
044. Submit to carrier: Send agreement and carrier forms to receiving and losing providers.
Recommended digital workflow settings
| Field | Configuration |
|---|---|
| Authentication | Email + SMS code or organization SSO for high-assurance signers |
| Routing order | Sequential routing: transferor then transferee then carrier contact |
| Template locking | Lock number and account fields to prevent accidental edits |
| Archive destination | Save signed PDF to secured cloud storage with audit trail |
Typical end-to-end process for e-submitting the agreement
-
Upload document: Add the executed agreement and any carrier-specific forms
-
Assign signers: Add contact emails and define signing order
-
Authenticate signer: Use SMS or higher-assurance methods where required
-
Deliver to carrier: Send signed package and confirm carrier receipt
Platform and format considerations for eSubmission
Use an eSignature provider that produces an audit trail and secure, exportable signed PDFs so carriers and auditors can verify signature events and document integrity.
- File formats: PDF or PDF/A; many carriers require a tamper-evident PDF
- Integrations: Salesforce, NetSuite, Microsoft 365, Google Workspace supported
- Authentication: Email + SMS code, SSO, and advanced signer verification
Typical timelines and processing expectations
Internal review time:
Allow 1–3 business days for legal and admin review
Carrier processing:
Processing commonly completes in 1–5 business days; confirm with carrier
Cutover scheduling:
Schedule effective date during low-traffic hours to reduce disruption
Confirmations:
Request written receipt or confirmation from both carriers
Record retention:
Keep signed records per company retention policy and regulatory rules
Key milestones from preparation to completion
Draft and verify
Prepare agreement and confirm all identifying data with transferor
Signatures collected
Obtain signatures from authorized representatives of each party
Carrier submission
Send signed package to losing and gaining carriers
Service cutover
Carrier executes port and transfers service responsibility
Common preparation errors to avoid
- Mismatched account names between the agreement and carrier records cause port denials and back-and-forth delays.
- Omitting the port authorization code or entering an expired PIN frequently leads carriers to reject the request.
- Using informal or unsigned authorizations results in carriers refusing to process transfers for compliance reasons.
- Failing to confirm billing responsibility and effective date creates disputes over charges after the transfer.
Potential risks and consequences of an incorrect agreement
Real-world examples of Number Transfer Agreement use
Optica Ventures — COO
Optica automated their transfer forms for portfolio companies to speed signings and reduce errors.
- They used standardized templates and audit trails for every transfer.
- The standardized process cut turnaround time, improved recordkeeping for audits, and reduced carrier rejections by eliminating inconsistent account data.
Tech Data — CEO
Tech Data centralized number transfers into a single workflow to support vendor changes.
- They integrated signing, storage, and carrier submission.
- Centralization ensured consistent authorization, simplified carrier submissions, and provided a single, auditable source of truth for regulatory and billing reconciliation.
Practical tips for accurate and efficient completion
Frequently asked questions about Number Transfer Agreements
-
Can this be signed electronically?
Yes. Electronic signatures meeting the ESIGN Act (15 U.S.C. §7001) and state UETA standards are generally enforceable. Ensure intent, consent, attribution, and retrievable records are documented to satisfy legal validity tests.
-
Is notarization required?
Not typically for telecom porting, but certain states or carriers may require notarized authorization for specific instrument types. Check the receiving carrier and state law; when in doubt, obtain notarization or RON and retain the certificate.
-
What if a carrier rejects the transfer?
Common causes include mismatched account names, incorrect port codes, or missing authorization. Resolve by supplying corrected data, updated authorization, and carrier-specific forms; log carrier correspondence for audit trails.
-
Who must sign the agreement?
An authorized representative with authority over the account or asset must sign. For corporate parties, this often includes officers with signatory authority or a person designated by corporate resolution.
-
How do I revoke or cancel a transfer?
Revoke in writing and provide notice to both carriers and the other party before the effective date; document the withdrawal and obtain written acknowledgment to avoid unintended porting.
-
How long should records be retained?
Retain signed transfers for the contract term plus applicable statutory periods: IRS records 3 years (IRC §6501(a)), HIPAA records 6 years (45 CFR §164.530(j)), and extended state-specific requirements where applicable.