mandatoryfull document
Your company
Authorised users create, approve or view the full document.
Internal permissions should follow actual need.source04
electronic invoicing
One invoice can have several readers
The map separates the regulated chain from access added by management software, accountants, banks, finance and AI assistants.
Snapshot taken on 22 August 2026. No upload, no tracker and no data transmission.
- auditable model
- v1.0.0
- actor categories
- 13
- zero collection
- local
ACCESS MAP
Who can see your invoice?
Enable the services you use. The map separates the mandatory chain from access added by software, accountants, banks or an AI assistant.
Potential access chain
8 visible actors5 with the full document2 with data or technical access
optionalfull document
Software, ERP or compatible solution
It processes the full document when used to create, import or synchronise the invoice.
It may be separate from the approved platform that actually carries the flow.sourceoptionalfull document
Accountant
They may access invoices and accounting data under the engagement and workspace permissions.
This access is not automatic in every product.sourcemandatoryfull document
Sender approved platform
It receives or creates the invoice, runs checks, routes it and extracts tax data.
The visible brand may rely on a support platform.sourcemandatorypotential technical access
Infrastructure and any subcontractors
They may have potential technical access to service data.
Technical access does not mean routine human reading.sourcemandatoryrouting only
Central directory
It identifies the customer platform and receiving address.
Its purpose is routing, not invoice content.sourcemandatoryfull document
Recipient approved platform
It receives the full document and makes it available to the customer.
One PA may hold both roles when both companies use the same operator.sourcemandatoryfull document
Customer company
It views the invoice, may refuse it and processes payment.
Purchasing, approval and accounting rights may be separated.sourcemandatorystructured data
Tax authority
It receives the structured file, statuses and, where relevant, transaction and payment data.
This is not necessarily the PDF or complete file exchanged between platforms.sourceoptionalstructured data
Bank or payment service
It may receive data needed for matching, settlement and cash management.
Bank integration does not prove automatic use for credit scoring.sourceoptionalstructured data
Credit or factoring
A partner may receive data defined by a financing journey activated by the customer.
The dataset and any automated decision must be documented product by product.sourceoptionalpotential technical access
Product integrated AI
It may read a document or its data for OCR, categorisation, search or assistance.
Provider, location, retention and training rules must be checked.sourceoptionalpotential technical access
Connected external AI assistant
Data required for the request may be sent to the provider chosen by the user.
Revocation stops new transfers without guaranteeing deletion of data already received.sourceMethod and limitations
This map describes access categories. It does not replace your provider contract, DPA or audit.
// what the tool shows
Possible access
The result distinguishes full documents, structured files, routing and technical access. It also identifies mandatory and optional branches.
// what it cannot know
Your real architecture
Only your contract, DPA, subprocessor list and account permissions can identify the exact organisations and people accessing your data.