Skip to main content
Active Voice
Nov 19, 2026 12:57 AM UTC
Question

Custom Envelope Fields - Limiting/Cleaning Sender Input

Setup:

I’m A DocuSign Admin, and my organization uses a Custom Envelope Field to collect a 5 or 6 digit account number that DocuSign Connect then sends to our Document repository where that number is used to route the documents into the correct account. 

 

 Issue:

Sometimes staff will have a typo in the CEF such as a letter, period, or leading space on the account number.

This causes the file to not be routed correctly by our repository.    

 

Question:

Is there a way to force the CEF to allow numbers, or to have Docusign Connect clean the CEF so it does not pass non-number data entry into our repository? 

1 reply

Community Moderator
Nov 19, 2026 2:58 PM UTC

Hi ​@Office_Tech732,

 

Thank you for reaching out to the Docusign Community!

 

We understand that you would like to restrict the Custom Envelope Field (CEF) to accept only numeric values and prevent invalid entries from being passed through Docusign Connect to your document repository.  We apologize for any inconvenience this issue is causing, and I’ll be happy to help.

 

Custom Envelope Fields are designed to capture envelope-related information. Docusign documents CEFs as either free-text fields or lists of predefined values; number validation applies to recipient document fields, which are a different feature. It does not automatically validate or clean the field values before transmitting them to an external system.

 

As a possible workaround, you may consider the following approaches:

  • If the valid account list is manageable: change the CEF to a list so senders select an allowed value.
  • If the list is too large or changes often: validate in the sending workflow or in the receiving integration before routing. Require ^\d{5,6}$ (exactly 5 or 6 digits; no spaces or punctuation), and reject or flag invalid values.
  • Avoid silently stripping non-digits. Removing a character could turn a typo into a different, valid account number and route the document incorrectly. Trim whitespace only if your business rules explicitly allow that.

 

Link for reference: EnvelopeCustomFields Resource

 

For dynamic account numbers, implementing validation before the envelope is sent would be the recommend approach to help prevent incorrect routing.

 

We hope these suggestions help clarify the available options.

 

Feel free to click the “Best Answer ✅” button below the post. That helps others in the Community find trusted answers faster.

 

Best regards,

Noralynn | Docusign Community Moderator

 

 

Translate