What's New: E-Documents (2024 release wave 1)

Overview

The session covers the e-documents architecture: a core app, a third-party access point integration app, and part of the functionality that stays in the base app to avoid breaking existing partner localizations. It describes the format and integration interfaces, helper code units, and the localization roadmap.

Demos use a Contoso demo module. They show a sales invoice exported through a Peppol e-document service via background workflow, with audit logs. They also show an incoming purchase e-document matched to purchase order lines in a matching page, including cost variance handling and the resulting purchase order update. Copilot-assisted matching is mentioned but is covered in a separate session.

Key points

• The e-documents core app is separate from the base app. Some parts stay in the base app to avoid breaking existing partner-based localizations. Together with the third-party connector app, the aim is more than 80% of the features needed.
• The Peppol format (captioned as ‘PayPal B3’/‘pebble’) ships as a code solution based on existing XMLports and as a data exchange definition. Before this, no format was included and partners had to build their own.
• Localizations delivered: Denmark (Peppol and OBL) and Belgium (Peppol). Planned: German, Spanish and Australia/New Zealand, and the legacy Italy and Mexico functionality will be upgraded. Timing depends on enforcement in each country.
• The third-party access point integration app covers authentication, communication and messaging. It currently supports only one access point, with more planned, and it can be extended.
• Purchase order matching links incoming e-documents to existing purchase orders, or creates new ones based on vendor setup. It supports one-to-one, one-to-many and many-to-one matching. The matching page works like bank reconciliation, and Copilot matching is covered in a separate session.
• Cost differences are allowed when matching, with a notification. Applying to the purchase order updates cost, discount, quantity to invoice, vendor invoice number and document date. Posting is still a separate step.
• Sending a sales e-document needs a document sending profile with e-documents enabled on the customer. The Peppol format needs a reference number. Processing runs in background jobs, every step is logged, and retention policies and error handling are provided.

Features

AL objects mentioned

As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.

• other “Contoso Demo Tool” at 14:13
• other “E-Document Services” at 15:11
• other “Data Exchange Definition” at 15:32
• other “Sales Invoice Export” at 16:13
• other “E-Document P Invoice Import” at 16:33
• other “Supported Document Types” at 16:53
• other “Document Sending Profile” at 17:54
• other “E-Documents” at 19:27
• other “E-Document Matching Page” at 22:59
• other “Precision Grind Home” at 23:55
• other “Smart Grind Home” at 26:08
• interface “document format interface” at 28:50
• interface “integration interface” at 28:50
• codeunit “e document helper code units” at 29:10

Not found in BC28-30: interface “document format interface”, interface “integration interface”, codeunit “e document helper code units”.

Quotes

• 1:10 “we deliver e doent core app but if you can see this light blue in a Bas app yes some part of e doents”
• 2:11 “in general we are looking to have more than 80% of all features you will need in documents”
• 6:02 “we deliver P format support why because of your feedback when we created first framework we didn’t support any format”
• 7:38 “currently we are supporting only one access point but we are planning to add more access points there”
• 8:39 “we deliver localization for Denmark both formas obl and P so you can choose both of them um in Danish um uh environment”
• 8:59 “we are planning additional localizations I cannot say exactly when uh it depends of enforcement from country to country”
• 10:31 “when it comes to purchase process it becomes uh much more complicated and what we can see more and more countries enforcing uh electronic”
• 11:32 “now with the new new release you can match without any problem actually what you can do if there is um no purchase order”
• 13:33 “before enable you need to have because there dependency you need to uh first enable comma module and Warehouse module after that you need”
• 16:13 “this is one of the formats that we provide for you out of the box for free”
• 19:07 “for this service we will pick it up and run this workflow”
• 20:08 “be locked so that you can easily audit what is going on with a e”
• 21:47 “that there is a link to one of your existing purchase orders and we automatically link it”
• 23:15 “if you have seen bank reconciliation matching before this is built around the same concept”
• 25:15 “we do allow you for you to do a matching where the cost is not”
• 27:09 “system will automatically collect all this information from incoming document to uh do vendor document number they update all lines”
• 27:29 “this is not even blocker so now you can use everything as a standard is used earlier in busy Central together with e documents”
• 27:49 “we want to encourage you to extend this function ality maybe some additional features even we will continue to invest”
• 29:10 “there are some set of e doent hel helper code units so you can find a lot of interesting information a lot of important”
• 29:30 “if you build your own extension on top you get the co-pilot feature as well natively it will work”
• 30:50 “everything is running in background job so it’s not disturbing it’s not requiring anything from from those people that are are invoicing”
• 31:22 “we lock everything and again this is because that you can all audit what is happening with the E document so there is a”
• 32:42 “the things I just mentioned they are here in in blue then we have our two interfaces both for import export that’s one interface”

Disclaimers in the video

• 7:38 coming-later: currently we are supporting only one access point but we are planning to add more access points there
• 9:19 coming-later: we are planning additional localizations I cannot say exactly when uh it depends of enforcement from country to country but minimum what we are planning in next two week um we have uh planed German localization Spanish localization and Australian New Zealand localization
• 9:51 coming-later: we already have um from previous um uh times we have some Legacy e documents in voice hisory documents in Italy and Mexico so we are planning in following period to upgrade Italian and Mexican functionality
• 17:14 other: today we don’t have a a service integration you can see it’s set to no integration normally when you have a a service in a production environment you would have set up some kind of uh service
• 22:38 preview: if you’re interested in the new copilot stuff we’re doing I think personally it’s very cool I would definitely recommend you to watch another session we have called e invoicing with co-pilot
• 34:03 coming-later: introducing to e invoicing matching with co-pilot great session uh this part about matching what magot is playing but this time with copilot fully automated
• 34:24 subject-to-change: we updated um uh new session with Danish bookkeeping Act features because there are some new things in the meantime happened from uh previous pre previous uh wave

Presenters (as heard): Manos, Alexander, Magnus.