Standard Business Central Features This App Uses

E-Invoice Platform is built on standard Business Central rather than beside it. This article is the inventory: which standard pages it changes, which standard data it writes, which it only reads, which frameworks it plugs into, and where data leaves Business Central. Consult it when you are reviewing the app before installing, answering a security question about it, or working out why something standard behaves differently since it was installed.

For what you must configure before the app works, see What Business Central Must Have in Place. For what stays behind when you remove it, see Remove the App Cleanly.

Fields added to standard tables

Two standard tables get new fields. Both are removed when the app is uninstalled with Delete Extension Data turned on.

Table	Field	Purpose
Customer	Peppol Endpoint	The address invoices are delivered to
Vendor	Peppol Endpoint	The address used when exchanging documents
Vendor	Receive To Confirmed, Receive To Set By, Receive To Set On	Records whether a person actually chose Receive E-Document To, or whether it is only Business Central's default

Standard pages the app changes

Nineteen page extensions, all adding actions or fields rather than changing existing behavior.

Area	Pages
Customers	Customer Card, Customer List
Vendors	Vendor Card, Vendor List
Sales	Sales Invoice, Sales Credit Memo, Posted Sales Invoice, Posted Sales Invoices, Posted Sales Credit Memo, Posted Sales Credit Memos
Purchases	Purchase Invoice, Purchase Credit Memo, Posted Purchase Invoice, Posted Purchase Invoices, Posted Purchase Credit Memo, Posted Purchase Credit Memos
Role centers	Business Manager Role Center, Accountant Role Center, User Setup

The unposted sales and purchase documents get a Peppol readiness box; the posted ones get a status box and the send action. The two role centers get the E-Invoicing tile band, with every tile off by default.

Standard data the app writes

This is the list that matters for a review. Everything here is written only as the result of an action somebody took.

Standard data	When it is written	Triggered by
Customer and Vendor	The Peppol Endpoint field is filled	Fill Peppol Endpoints, or assigning a vendor to an incoming document
Customer and Vendor	Name, address, post code, city, country and VAT number are overwritten	Get Official Data, and only for the fields you select
Vendor	Receive E-Document To is set	Choosing a supplier default on the recognition list
Vendor Bank Account	An account is created, and optionally made preferred	Approving a supplier bank account, according to Approved IBAN Action
Unit of Measure	New units are created	Add Missing Units
Document Attachment	Supplier PDFs are attached to the purchase document	An incoming document carrying an embedded attachment
Service Participant	A sender's Peppol identity is registered against a vendor	Answering yes when assigning a vendor
E-Document Service	Supplier recognition is selected on the service	Apply Supplier Recognition to Services
E-Document Service, Job Queue Entry	Deleted	Prepare for Uninstall, after you confirm

Nothing in this list happens on a schedule without a person having switched it on.

Standard data the app only reads

The app's own permission sets grant read-only access to these, and it never writes them:

Text-to-Account Mapping and Purchases & Payables Setup — to work out in advance which incoming lines will not resolve to a G/L account.
Approval Entry and Purchase Header — to report what happened to a document sent for approval.
E-Doc. Data Storage — to read the raw document an e-document arrived with.

Two consequences worth noting. The app does not create or change text-to-account mappings; it only tells you which descriptions resolve to nothing. And because it holds read-only access to Purchase Header, reopening a stuck document goes through Business Central's own routines rather than writing the status directly.

It also reads, through your own permissions: Company Information, VAT Posting Setup, Report Selections, and bank accounts.

Standard frameworks the app plugs into

Framework	How
E-Document	Registers as a receiving connector on the Service Integration enum, and supplies its own vendor resolution on the E-Doc. Proc. Customizations enum
Document Attachment	Supplier PDFs go through the standard framework, so external file storage works unchanged
Approval workflow	Purchase documents are sent for approval through Business Central's own approval routines
Guided Experience	Registers the setup page, so it appears in Manual Setup and under Set up this app
Isolated storage	Holds the API secret, so it can never be projected by a page or API

Three event subscriptions, and no more:

E-Doc. Import → OnAfterProcessIncomingEDocument — the one public hook that fires on both import processes, used for supplier recognition, attachments and approval routing.
Guided Experience → OnRegisterManualSetup — registers the setup page.
Vendor → OnAfterValidateEvent on Receive E-Document To — records who set the value and when, so an unconfirmed default is distinguishable from a real decision.

Where data leaves Business Central

Destination	What goes there	When
`app.recommand.eu`	The documents you send, and requests to read the inbox	Whenever you send or receive
`directory.peppol.eu`	The identifier or name you are searching for	Directory lookups and endpoint checks
`ec.europa.eu`	A Belgian enterprise number	Only when Look Up Official Data (VIES) is on
Application Insights	Diagnostic events, marked as system metadata	On a handful of failures during import

The VIES host is contacted only if you switch that setting on, which is why it ships off. The telemetry carries document identifiers and failure reasons, not document contents.