DocuSign eSignature Integration for Business Central — Send, Sign, and Store Without Leaving BC

The app connects Business Central to DocuSign through the official DocuSign API. When a user is ready to collect a signature on a document, they click a Send to DocuSign button directly on the BC page. The document is packaged as an envelope, sent to the recipient, and tracked from that point on — all from within Business Central.
The signed PDF is stored automatically once the recipient completes the signature. No manual download, no back-and-forth by email, no filing in a shared folder that only two people know about.

What companies did before DocuSign Integration

Most companies that run Business Central still handle signatures the old way. A document gets posted, exported to PDF, emailed out, printed at the other end, signed by hand, scanned, and emailed back. Then someone saves it somewhere and hopes they can find it later.
It works. But it is slow, it depends on the customer having a printer, and there is no audit trail inside Business Central.
The NAV SEAL DocuSign eSignature Integration changes that. Documents go out for signature directly from BC pages you already know. The signed document comes back automatically. And everything is logged — status, timestamps, envelope IDs — without leaving Business Central.

The DocuSign button comes pre-configured on the most common sales and purchase document pages in Business Central:

  • Sales Quote, Sales Order, Sales Invoice, Blanket Sales Order
  • Sales Return Order, Sales Credit Memo
  • Purchase Quote, Purchase Order, Purchase Invoice, Blanket Purchase Order
  • Purchase Return Order, Purchase Credit Memo

If your company uses custom pages, the integration supports adding the DocuSign button there as well — without modifying base application objects.

When sending a document for signature, you add recipients directly inside Business Central. For each recipient you can define their role — whether they need to sign, approve, or simply receive a copy of the document.

If more than one person needs to sign, you can set a signing order. This controls the sequence in which recipients receive the envelope. The first person signs, then the next receives their notification, and so on. A diagram in the setup makes it easy to see the order before sending.

Recipients can also be configured with additional authentication steps if your process requires it.

The integration includes a Job Queue Entry that runs automatically in the background. Once activated from DocuSign Setup, it polls DocuSign at set intervals to retrieve updated statuses and download completed envelopes.

This means your team does not need to manually check whether a document has been signed. Business Central updates itself. The signed document appears on the record when the recipient is done.

Setting up the Job Queue takes a single click inside DocuSign Setup. Once active, it disappears from the setup options and can be managed from the standard Business Central Job Queue Entries page instead.

If your approval process requires a document to reach Status = Released before it can go out for signature, that can be enforced from DocuSign Setup. With the option enabled, Business Central will return an error if a user tries to send a document that has not yet been released.

This is useful for companies where documents go through an internal review or approval step before customer-facing communication is allowed.

Every envelope sent through the integration is tracked in Business Central. Two views give you full visibility:

DocuSign Envelopes shows all envelopes regardless of document type or status. From here you can navigate directly to the source document in Business Central or to the log entry for that envelope.

DocuSign Envelope Logs provides a detailed activity log — what happened, when, and to whom. Both lists are accessible directly from DocuSign Setup, or by searching from anywhere in Business Central.

This means that when a customer asks whether a contract was sent, or when it was signed, the answer is already in BC. There is no need to go into DocuSign’s own portal to check.

When Business Central sends a document to DocuSign, it uses a report to generate the PDF. The integration lets you configure which report — and which layout — is used for each document type through DocuSign Report Parameters in setup.

This is important if you use custom report layouts, branded document templates, or specific Word layouts for different document types. The signed copy the customer receives looks exactly like the document your team works from.

Setup is wizard-driven, so you do not need a Business Central administrator to get it running. From DocuSign Setup, a guided wizard walks you through each step: entering your DocuSign User ID and API Account ID, choosing between a DocuSign Sandbox and Production, and confirming the connection — with an explanation of what each field means as you go.

Once the wizard completes, the app is ready to use. There is no manual object configuration and nothing to set up outside the wizard itself. The Developer Environment option lets you test the full flow against a DocuSign Sandbox before going live in production.

Full setup documentation, step-by-step guides, and video walkthroughs are also available in the NAV SEAL knowledge base if you want to see the process before you start.

Sending a document for signature does not require knowing DocuSign’s own interface at all. Clicking Send to DocuSign on a Business Central document opens a guided wizard that walks the user through the process step by step — confirming the document, adding recipients, assigning their role and signing order, and reviewing everything before it goes out.

Each step only shows the fields relevant to that step, so a first-time user is not confronted with a wall of options. The wizard checks the required fields as you go — a recipient’s email, a signing order conflict — before the envelope can be sent.

The result is that anyone on the team can create and send a DocuSign envelope correctly the first time, without training or a reference guide to follow.

Every step of the signing process triggers a notification. Recipients receive an email as soon as a document is ready to sign, and your team is notified inside Business Central when a document is signed, declined, or voided — so nobody has to keep checking the DocuSign portal for status.

DocuSign’s built-in reminder and expiration rules carry through automatically. If a recipient has not signed after a set number of days, they receive an automatic reminder, and if an envelope sits unsigned too long, it can be set to expire so the document is freed up to be resent.

Reminder and expiration behavior is configured once in DocuSign Setup and applies across every document type, so there is nothing to set up on a per-transaction basis.

If you already have DocuSign templates set up — standard terms, signature blocks, routing rules — the integration can send envelopes using those templates instead of building the envelope from scratch on every send.

This is useful for document types where the layout and signing fields rarely change: a template keeps signature and initial field placement consistent, so your team is not repositioning fields by hand each time a document goes out.

Templates are selected per document type in DocuSign Report Parameters, alongside the report and layout settings, so different Business Central document types can point to different DocuSign templates.

Why It Matters

The manual signature process is not just slow — it creates gaps. Documents get lost, signed versions are stored in email threads rather than the ERP, and there is no reliable timestamp for when a customer actually accepted a quote or order.
The NAV SEAL DocuSign integration closes those gaps directly inside Business Central. The document goes out from BC, the status updates in BC, and the signed copy lands back in BC. Your team never needs to leave the system they already work in.