Electronic Signature
Features
Other
Send Assigned Number Efficiently

Send Assigned Number with SignNow's Secure eSignature Solution

Get rid of paper and automate digital document managing for higher efficiency and countless possibilities. eSign anything from your home, fast and feature-rich. Discover a greater manner of doing business with airSlate SignNow.

See how it works!Click here to sign a sample doc

Award-winning eSignature solution

What send assigned number Does and Why It Matters

The send assigned number feature generates a unique identifier for each outbound document or envelope at the moment it is sent, creating a persistent reference for tracking, audit, and reconciliation. This identifier can be embedded in the document metadata, visible in the signNow activity feed, and returned by API calls to link records across systems. Using an assigned number reduces manual lookup, improves searchability in cloud storage, and simplifies matching signed documents with backend records for reporting and compliance purposes.

Why assign a number to each sent document

Assigning a unique send number improves traceability, streamlines audits, and reduces errors when reconciling documents across systems and teams.

Why assign a number to each sent document

Common tracking and control challenges

Duplicate filenames and scattered storage locations make locating the correct signed record time consuming and error prone.
Manual logging of sends increases administrative overhead and introduces transcription mistakes during reconciliation.
Cross-system workflows lack a consistent identifier, complicating automated updates between CRMs, ERPs, and document repositories.
Regulatory and audit requests can be delayed when documents lack a verifiable, persistent reference number.

Representative user profiles

Contract Manager

A contract manager uses send assigned number to maintain a searchable index of executed agreements. They rely on the identifier to link signed documents to contract lifecycle systems, verify signing order, and expedite audit responses with minimal manual search.

IT Administrator

An IT administrator configures the assigned number format and exposes it via APIs and webhooks. They use the identifier to correlate signNow events with CRM or ERP records and to troubleshoot workflow failures across integrated systems.

Teams and roles that rely on assigned numbers

Organizations that need consistent document lifecycle controls use assigned numbers to simplify tracking and evidence collection.

Legal and compliance teams requiring reliable audit references for regulatory reviews and litigation support.
Operations and finance teams reconciling signed agreements against invoices and internal systems.
IT and integration teams mapping document events to system records for automation and monitoring.

Assigned numbers provide a lightweight, system-neutral identifier useful across departments and technical stacks.

Core capabilities that support send assigned number

Several signNow features work together to make assigned numbers practical: metadata storage, audit trails, integration points, configurable formats, secure retention, and API access.

Configurable format

Define prefixes, separators, and sequencing rules to create identifiers that align with internal numbering schemes and external system requirements.

Persistent metadata

Assigned numbers are stored in document metadata fields so they remain available after signing and during archival for programmatic retrieval.

Audit trail linkage

Every assigned number is recorded in the transaction audit trail to provide an evidentiary chain for compliance, showing creation, modification, and finalization events.

API access

REST API endpoints expose assigned number values for integration with CRMs, ERPs, and document stores, enabling automated reconciliation and reporting.

Search and filters

Search by assigned number in the signNow UI to quickly surface active or completed documents without relying on filenames or dates.

Webhook notifications

Configure webhooks to deliver event payloads that include the assigned number when documents are sent, signed, or completed for downstream processing.

be ready to get more

Choose a better solution

Integrations and templates that use assigned numbers

Assigned numbers integrate with templates and third-party tools so identifiers are consistent across repetitive workflows and external systems.

Google Workspace

Use assigned numbers with Google Docs templates so each generated document receives a unique identifier that syncs back to Google Drive filenames and metadata for easy retrieval.

CRM integration

Push the assigned number into CRM records at send time to maintain a single reference between customer records and signed agreements, simplifying reconciliations and audits.

Dropbox and storage

When documents are saved to cloud storage, the assigned number is included in the filename or metadata to make later searches and retention policy application straightforward.

Document templates

Predefined templates can embed placeholders for assigned numbers so every template-generated sending action produces a traceable identifier without manual entry.

Creating and using your assigned send number online

Overview of how assigned numbers are generated, stored, and referenced through signNow's web interface and APIs.

Generation: Numbers are auto-generated at send time based on chosen format.
Embedding: Identifier is added to document metadata and activity logs.
Searchability: Use the identifier to locate documents in signNow or connected storage.
APIs: API endpoints return the assigned number for programmatic workflows.

Collect signatures

24x

faster

Reduce costs by

$30

per document

Save up to

40h

per employee / month

Quick steps to assign a number when sending

Simple steps show how to enable and apply send assigned number within a typical send workflow in signNow.

01

Open send flow: Start a new document send from the dashboard.
02

Enable identifier: Select the assigned number option in send settings.
03

Choose format: Set prefix, sequence, or custom template.
04

Send and record: Complete send; number is embedded and logged.

Audit trail steps for assigned-number transactions

Maintain a clear audit trail by recording each assigned-number lifecycle event and storing relevant metadata consistently.

01

Create event:

Assigned number generated

02

Send event:

Send recorded in audit log

03

Sign event:

Signer actions appended

04

Complete event:

Final status captured

05

Archive event:

Archive metadata preserved

06

Retrieve event:

API returns audit entries

be ready to get more

Why choose airSlate SignNow

Free 7-day trial. Choose the plan you need and try it risk-free.
Honest pricing for full-featured plans. airSlate SignNow offers subscription plans with no overages or hidden fees at renewal.
Enterprise-grade security. airSlate SignNow helps you comply with global security standards.

Start free trial

Recommended workflow settings for consistent numbering

Key configuration settings help standardize assigned number behavior across teams and integrations.

Setting Name	Configuration
Number Prefix and Suffix	OrgCode-YY
Auto-increment Format	Sequential six digits
Include in Metadata	Yes
API Exposure	Enabled
Webhook Payload	Includes assigned ID

Supported platforms and client requirements

signNow supports send assigned number functionality across major platforms and modern browsers for consistent behavior.

Web browsers: Chrome, Edge, Safari supported
Mobile apps: iOS and Android apps
APIs and SDKs: REST API and SDKs available

For mobile and API use, ensure you run the latest app version or client libraries; administrators should enable the assigned number configuration in account settings to make it available to users across devices.

Security and control elements for assigned numbers

Encryption at rest: AES-256 encryption applied

Encryption in transit: TLS 1.2+ connections

Access controls: Role-based permissions

Audit logging: Immutable event records

API authentication: OAuth 2.0 tokens

Data minimization: Identifier-only retention

How assigned numbers help in practice

Two brief use cases show how send assigned number simplifies workflows in different industries.

Financial Services

A bank attaches an assigned number to each loan disclosure before sending to customers to ensure consistent records across underwriting and servicing

Number appears in the signNow activity log and in the core banking system
This enables automated reconciliation between signed disclosures and loan accounts

Resulting in faster audits and fewer manual match-ups during compliance reviews.

Higher Education

A university issues student consent forms with an assigned number included in the document metadata to track approvals across departments

The identifier is written to the student information system via API
Departments can query signed records quickly for FERPA and accreditation requests

Leading to streamlined record retrieval and reduced administrative backlog.

Best practices for reliable assigned-number management

Follow these guidelines to keep assigned numbers consistent, searchable, and legally defensible across systems and processes.

Use a fixed prefix that denotes business unit or region

Assign a stable prefix reflecting organizational structure so identifiers immediately signal origin. This aids sorting, routing, and applying retention rules across departments and systems.

Keep numbering sequential and non-repeating across long windows

Avoid reuse of identifiers for archival and audit clarity; use sequence padding to support sorting and future scale without collisions.

Embed identifier in both document metadata and filename consistently

Write the assigned number into metadata fields and, where appropriate, into the visible filename so users and systems can locate records regardless of interface.

Expose the assigned number in API responses and webhook payloads

Ensure integrations receive the identifier at send and completion events so downstream systems can update status and reconcile records automatically.

Connect airSlate SignNow to your apps

Check out airSlate SignNow integrations

Data accuracy, security, and compliance

airSlate SignNow is committed to protecting your sensitive information by complying with global industry-specific

Learn more about security

Frequently asked questions about send assigned number

Common questions and answers to help troubleshoot assigned-number configuration, retrieval, and integration scenarios.

Assigned number not appearing in document metadata
Confirm that the assigned number option is enabled at the account or template level. If templates are used, check that the placeholder for the identifier is present and that the send flow applied the selected template during transmission.
API responses don’t include the assigned number
Verify that your API requests include the correct query parameters or fields to return metadata. Ensure the integration uses an updated API version and that the account configuration exposes the assigned number to API responses.
Duplicate assigned numbers observed
Check the sequence configuration and concurrency controls. If multiple send operations use the same seed without locking, adjust to a centralized increment or include a timestamp component to prevent collisions.
Assigned number format must match internal policy
Update the format settings to include required prefixes, separators, and padding. Test new formats on a sandbox account before applying to production to avoid retroactive inconsistencies.
How to search by assigned number across storage
Use signNow search by metadata, and ensure external storage sync writes the identifier to file metadata or filename. Index the identifier in downstream systems for rapid retrieval.
Handling legal evidence requests for assigned-numbered documents
Provide the document, audit trail, and assigned number metadata to demonstrate chain of custody. Confirm export formats preserve metadata and timestamp details for legal reviews.

Assigned-number capabilities: signNow compared with other providers

Comparison of common assigned-number features and how they are exposed across major eSignature platforms.

Feature	signNow (Recommended)	DocuSign	Adobe Sign
Assign ID on send
Include in metadata
API retrieval endpoint	GET /sends/{id}	GET /envelopes/{id}	GET /agreements/{id}
Webhook includes ID

be ready to get more

Get legally-binding signatures now!

Start your free trial

Retention and backup timelines for assigned-number records

Define retention and backup schedules that preserve the assigned number and accompanying audit records to meet legal and operational requirements.

Short-term retention policy:

90 days for active reconciliation

Standard archival period:

7 years for contractual records

Backup frequency:

Daily backups of metadata and audit logs

Disaster recovery retention:

90 days cold storage copies

Legal hold procedure:

Freeze retention on request

Risks from not using assigned send IDs

Regulatory fines: Noncompliance penalties

Lost evidence: Weakened auditability

Reconciliation delays: Payment disruptions

Operational errors: Misapplied documents

Customer disputes: Longer resolution times

Increased costs: Manual labor expenses

Pricing context for assigned-number features across vendors

A high-level view of entry pricing and trial availability for platforms that support assigned-number workflows.

Plan	signNow (Recommended)	DocuSign	Adobe Sign	PandaDoc	HelloSign
Entry Price	From $8/user/month	From $10/user/month	From $14.99/user/month	From $19/user/month	From $15/user/month
Free trial	7-day trial available	30-day trial available	14-day trial available	14-day trial available	14-day trial available
Core API access	Included in plans	Tiered API access	Included with subscription	Included in business plans	API in paid plans
Template library	Included	Included	Included	Included	Included
Webhook support	Included	Included	Included	Included	Included

Simplify complex workflows

Create, execute, and manage workflows of any complexity, electronically from virtually anywhere. Scalable eSignature capabilities allow you to share documents with the right people in the correct order and define roles for each recipient. Execute document workflows faster and easier than ever before.

Automate document management

Optimize complex signing processes with airSlate SignNow’s powerful features to enhance your business. Control your automated eSignature workflows to ensure they're running at peak performance with instant notifications and reminders.

Optimize in team collaboration

Bring teams together in a secure, shared environment. Manage documents, use form templates and notifications to create more efficient cross-organization collaboration. Free your employees from having to spend time on repetitive activities so that they can focus on valuable, business-critical tasks.

Integrate into your existing systems

Run your projects with industry-leading integration. Collect Salesforce, Microsoft Teams, and SharePoint all in one business flow. Connect your software to a single system for endless possibilities and more productiveness.

Stay compliant with best-in-class data safety

Feel confident knowing that your data is protected by the latest in encryption security. airSlate SignNow is GDPR and eIDAS certified and provides you transparence into your eSigning experience with court-admissible audit trails. Configure user authorization and roles to regulate who has access to what.

be ready to get more

Get legally-binding signatures now!

Start free trial