SDX

by Edward Jones

A secure document workflow built on the SDT Engine, used by financial advisors and their clients.

What it is.

Edward Jones built Secure Document Exchange (SDX) on the Botdoc SDT Engine API. SDX is the workflow Edward Jones financial advisors use to exchange sensitive client documents through a secure transport layer, without asking the client to register for a separate portal.

The public client-facing user guide for SDX is OLM-16043B-A and is published by Edward Jones. This page references only what Edward Jones has put in front of clients in that guide.

This is a Third Party Integration (TPI). Edward Jones built it on the SDT Engine, ships it under their own brand, and supports it inside their own client experience. Botdoc supplied the Engine; Edward Jones supplied the product. The TPI model is one of three commercial tracks Botdoc offers on the SDT Engine, alongside External Application Projects (EAPs that Botdoc builds and sells under our brand) and direct API integrations for developers building their own product on top of the Engine.

Why this was hard to do before SDT.

A regulated financial institution wanting a client-facing document exchange has historically had two choices: build a portal in-house (with the registration drop-off and the compliance review that implies) or buy a third-party portal product (with the same drop-off and a new vendor on the BSA exam). Either path means clients log in to something new.

The SDT Engine API lets the institution skip the portal entirely. Clients receive a one-click link. No registration. The institution's compliance posture lives in the transport layer rather than in a fragile new piece of customer-facing infrastructure that would also have to be examined, patched, and staffed against the customer support load it would generate. The result is a faster build, a lower ongoing-operations cost, and a client experience that does not punish the client for being a client.

What the SDT Engine made possible.

Building SDX on the SDT Engine API rather than on a portal-based secure file transfer product produced five specific outcomes for Edward Jones and their financial advisors. Each maps to a capability the SDT Engine exposes natively, and each removes a piece of infrastructure or customer friction that an in-house portal build would have created. The same five outcomes apply to any other regulated institution evaluating whether to build a TPI on the SDT Engine rather than buying or building a traditional secure-file-transfer stack.

• Financial-advisor document workflow: Advisors exchange sensitive client documents inside the institution's existing service workflow.
• Client side has no portal account: Clients pick up documents through a one-click experience, not a registration flow.
• Built on the SDT Engine API: Edward Jones owns the build and the experience. Botdoc supplies the transport underneath.
• Single API surface for the institution: One integration replaces what would otherwise be a secure email gateway plus a customer portal plus the help desk to staff it.
• Bank-grade transport built in: Compliance posture lives in the Engine, not in an additional control the institution has to maintain.

Want this for your clients?

Visit Edward Jones Secure Document Exchange →

Or scope a similar TPI build on the SDT Engine.

Find a time to meet with Botdoc

June 2026

Select a day in June

Now displaying available times for June 16th.

Meeting location

Google Meet

Meeting duration

30 mins

Now displaying start times for 30 mins blocks available on June 16th.

What time works best?

Showing times for June 16, 2026

UTC +00:00 Greenwich Mean Time

• 4:15 pm
• 4:30 pm
• 4:45 pm
• 5:00 pm
• 5:15 pm
• 8:15 pm
• 8:30 pm
• 8:45 pm
• 9:00 pm
• 9:15 pm