Frequently asked questions - Electronic Document Exchange

Have a question? You’re in the right place.

Frequently asked questions - EDE

Have a question? You’re in the right place.

This page is designed to give you clear, straightforward answers to the questions we hear most often. Whether you’re curious about Electronic Document Exchange by August Bridge or our other services, our FAQ is here to provide the answers.  

If you can’t find what you’re looking for, our team is just a message away to provide you with more detail or walk you through a specific challenge. 
Please feel free to contact us, and we will make sure you get the answers you need.  

Electronic Document Exchange by August Bridge

Electronic Document Exchange by August Bridge (EDE) is a platform made up of two parts: a Peppol gateway (Access Point capability) and a Microsoft Dynamics 365 FSCM integration. Together, they connect your organisation to the Peppol network so you can exchange structured e-documents (for example invoices aligned with Peppol BIS Billing) from your standard ERP posting process.

Learn more: EDE

EDE is designed for finance organisations that run Microsoft Dynamics 365 FSCM and need a practical, supported path to structured e-invoicing because of mandates, customer requirements, or process efficiency goals.

Learn more: Home and EDE

Following the pre-onboarding discovery – which confirms countries, legal entities, trading partners, and invoice scenarios – a typical onboarding proceeds through these phases:

  1. Participant verification and registration (participant identifiers)
  2. Configuration using Electronic Reporting templates and mappings
  3. Testing with sample documents and acknowledgements
  4. Go live
  5. Hypercare

Learn more: EDE and Webinar

Most onboarding projects take 2 to 6 weeks, depending on the speed of participant verification, the number of entities and trading partners, and the testing cycles required.

Learn more: EDE

You will usually need:

  1. Company verification details (VAT ID, Chamber of Commerce ID, or similar)
  2. Countries in scope and the first trading partners to onboard
  3. Invoice scenarios (sales invoices, credit notes, and any special cases)

Learn more: EDE

Most organisations only need limited customisation. The majority of work is configuration in Electronic Reporting templates and mappings, plus a small set of data-specific refinements.

Learn more: EDE

Yes. Many organisations start with one country or one legal entity, stabilise the process, then expand in waves to additional entities and trading partners.

Learn more: EDE

Available on AppSource, EDE is built for and integrated with Microsoft Dynamics 365 FSCM.

After setup, finance users continue to post invoices in Microsoft Dynamics 365 FSCM as normal. EDE uses posted invoice data to create Peppol-compliant e-invoices and transmit them through the Peppol network as a certified Access Point.

Delivery status and exceptions can be monitored so teams can address rejections and resend corrections without leaving Microsoft Dynamics 365 FSCM.

Learn more: EDE

EDE is built around the concept of source tables for posted invoices and uses Electronic Reporting for structured message creation and execution. The resulting message is then routed through the Peppol exchange model via the Access Point layer.

Learn more: EDE

Invoice data created and posted in Microsoft Dynamics 365 FSCM is transformed by the EDE integration into a Peppol-compliant e-invoice and securely transmitted via the Peppol Access Point of August Bridge.

Using the Peppol 4-corner model, the process follows these steps:

  1. EDE creates the structured e-invoice from posted invoice data.
  2. August Bridge validates and sends the document from its certified Access Point.
  3. The recipient’s Access Point is discovered, and the document is routed accordingly.
  4. The recipient’s provider delivers the document into the recipient’s accounting system and returns acknowledgements where available.

Learn more: Peppol and EDE

No. EDE works from the posted invoice context. What typically changes is ensuring required reference fields and master data are present before posting.

Learn more: Webinar

EDE covers Peppol connectivity and standards-aligned exchange. Some organisations also use additional solutions for clearance models, non-Peppol networks, AP automation, or country-specific requirements. If you use multiple solutions, define clear responsibilities for message creation, routing, acknowledgements, and exception handling.

Learn more: Webinar

No. EDE handles structured exchange through the Peppol network and uses Microsoft Dynamics 365 FSCM Electronic Reporting for structured message creation. Separate output tools are only needed if you require PDFs, document packs, or additional customer communication formats.

Yes. EDE supports enforced or fallback e-mail delivery for scenarios where structured invoices need to be delivered without Peppol. Using Microsoft Graph API and Entra ID App registration, EDE can support sending e-mails from the customer’s own tenant, providing a controlled and recognisable delivery model for supported scenarios where Peppol is not the applicable route or is not available for the recipient.

Yes. EDE supports PDF conversion so Peppol documents that do not have a visual representation can be converted into a readable PDF. This gives users a human-readable view for faster review and makes structured exchange activity easier to understand in day-to-day operations, including when reviewing supported document activity through the portal.

Yes. EDE supports manual processing using Print management configuration at document, customer, or transaction level. This allows specific operational or exception-based scenarios to be handled in a controlled way and gives organisations more flexibility where standard automated processing is not sufficient on its own.

EDE supports standards-aligned exchange through the Peppol network. It provides:

  1. participant onboarding and identifier setup
  2. standards-aligned message creation and validation support
  3. routing and delivery handling through the Peppol model
  4. operational handling support (status visibility and exception support)

You retain responsibility for:

  1. invoice content accuracy
  2. transaction-specific VAT and legal decisions
  3. country-specific legal interpretation of mandates

Learn more: EDE and ViDA

EDE by August Bridge supports e-invoicing formats aligned with OpenPeppol-governed specifications, including Peppol BIS Billing. Some countries apply additional rules or profiles beyond the base specification.

Learn more: Peppol

As a certified Peppol Access Point, EDE is aligned with the EN 16931 standard through Peppol BIS Billing, which supports EU legislation and the upcoming ViDA requirements.

By standardising e-invoicing, Peppol helps align to evolving VAT and reporting expectations and makes digital document exchange more secure and efficient.

Learn more: ViDA and EDE

Yes. EDE supports sending and receiving Peppol e-invoices. Receiving scope depends on your scenarios and how you plan to process inbound documents in Dynamics.

Learn more: Webinar

EDE can support self-billing, but practical support depends on the full end-to-end scenario, including whether the receiving side supports the same approach.

Learn more: Webinar

EDE provides operational visibility focused on delivery status, acknowledgements (where available), and exceptions requiring action.

Learn more: Webinar

If an invoice fails validation or is rejected, it will not complete delivery as a successful transmission. You use the rejection or validation feedback to correct data or mappings, then resend.

Learn more: Webinar

Common reasons include:

  1. incorrect identifier scheme or formatting
  2. recipient is registered but not for the document type you are sending
  3. the recipient changed service providers and directory updates are still propagating

Learn more: Contact

No. Status messages are covered under the standard document transaction model.

Learn more: Contact

Operational support typically covers monitoring, exception triage, and guidance on corrective actions when documents fail validation or are rejected.

Learn more: Contact

In most cases, users continue to post invoices as normal. The main operational changes are:

  1. capturing required references (buyer reference, PO number) consistently
  2. reviewing delivery and rejection feedback
  3. correcting and resending when needed

Learn more: Webinar

Most teams:

  1. go live with an initial scope (country, entity, key partners)
  2. stabilise references, data quality, and exception handling
  3. expand in waves once operations are repeatable

Learn more: Webinar

The pricing model described includes:

  1. an onboarding fee
  2. a subscription per legal entity
  3. a bundle model across entities based on documents sent or received

Learn more: Contact

Key drivers include number of legal entities, countries in scope, document volumes, and special scenarios that require additional mapping or procedures.

The pricing model is based on successfully transmitted documents rather than raw API call volume.

You can review the August Bridge listing for validation and procurement via our Microsoft AppSource listing (Dynamics 365 for Operations and Supply Chain Management).

Learn more: Microsoft AppSource

Yes. August Bridge can provide a Data Processing Agreement (DPA) for Electronic Document Exchange by August Bridge and related processing upon request.

Learn more: Contact

Yes. August Bridge is ISO 27001 certified. The certification provides additional assurance that August Bridge operates under a formally governed security framework. This supports faster security approvals, reduced supplier risk concerns, and increased confidence when outsourcing critical business document processes. 

Learn more: Contact

At minimum, request the DPA and proof of August Bridge’s ISO 27001 certification. If you have specific internal requirements, include them in your request so August Bridge can confirm what additional documentation is available.

Learn more: Contact

Typically, the finance owner (process scope), IT/ERP owner (integration scope), and security/privacy stakeholders (due diligence and governance).

Learn more: Contact

The Customer Service Portal (CSP) is the client-facing service layer in EDE that gives users direct access to supported document exchange activity outside Microsoft Dynamics 365 FSCM. It brings together visibility, validation, participant information, and operational follow-up while Dynamics 365 FSCM remains the core business-process and posting context.

In practical terms, CSP gives clients a clearer place to review what has been sent or received, understand document status and validation outcomes, and work with tenant, participant, and network information without relying only on core transaction screens or manual checks in Microsoft Dynamics 365 FSCM. A dashboard-style view helps make supported exchange activity easier to understand, monitor, and manage as part of normal operations.

CSP is important because it turns the portal into a more practical service layer for day-to-day exchange activity. Instead of relying only on core transaction screens or manual follow-up in Microsoft Dynamics 365 FSCM, users gain a clearer operational view of document flows, validation results, participant information, and areas that may require attention.

CSP helps operational teams work with exchange activity more directly by improving visibility and reducing unnecessary manual follow-up. Users can identify issues that require review, understand validation outcomes, monitor document progress, and keep supported document flows moving with better day-to-day control.

CSP supports more direct access to tenant-related information, user account details, and supported portal-based administration according to the user’s role. This makes the administrative side of EDE more accessible while keeping registration-sensitive activities controlled where changes can affect network or participant setup.

CSP is especially useful when clients need a practical operational view of supported document exchange activity outside the core Dynamics screens. This includes situations where document and status visibility, validation review, tenant-related information, or clearer day-to-day monitoring of exchange activity matters to operations.

Yes. CSP shows participant registration details and supported document capabilities for network participants and trading partners, reducing separate external lookups when checking counterpart readiness and supported document types.

Yes. CSP provides a lower-effort route for raising support issues from within the portal, with much of the relevant issue context already prepared. This reduces effort for the client and gives August Bridge clearer information for quicker investigation and follow-up.