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

What the Integration Does

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.

Reviews

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.

Signed documents can also be stored in SharePoint automatically. If your company already uses SharePoint as a document repository, the integration connects to it so that completed envelopes land in the right location without any manual steps.

This is configured separately in Setup SharePoint, which is part of the same NAV SEAL DocuSign setup area.

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.

The integration is available as a Business Central app. To connect it to your DocuSign account you need two values from DocuSign: your User ID and your API Account ID. These are available from the DocuSign Developer or Production portal depending on your environment.

From there, setup in Business Central is done through the DocuSign Setup page. A Developer Environment flag lets you point the app at a DocuSign Sandbox so you can test the full flow before going live in production.

Full setup documentation, step-by-step guides, and video walkthroughs are available in the NAV SEAL knowledge base.

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.