Eshop integration with myDATA AADE: workflows, prerequisites and testing

Integrate the store with myDATA AADE around a defined workflow and the installation's available interface. An Eshop-to-myDATA workflow starts with actual document issuance, not simply pressing the purchase button. Link the order, payment, fulfilment, issued document and confirmed submission response.

An Eshop-to-myDATA workflow starts with actual document issuance, not simply pressing the purchase button. Link the order, payment, fulfilment, issued document and confirmed submission response. The accountant and ERP administrator decide the appropriate procedure and channel. Technically, we recommend distinct states for pending, issued, submitted and rejected events, without assuming one online order always corresponds to one document or one shipment.

AADE publishes distinct technical interfaces for ERP users, electronic invoicing providers, and digital goods movement. Its version page provides version 2.0.2 and corresponding schemas. This distinction determines the technical design. An online order is not itself a fiscal document. The accountant and ERP administrator determine the appropriate procedure. We do not describe eightweb as a certified provider or offer tax advice.

A store accepts prepayment and fulfils the purchase in two shipments. The commercial procedure determines which documents are issued and when. The connector links each actual document to the order and stores the response from the correct submission channel. If a response is lost, reconcile state before submitting again. A return or cancellation must not be treated as deletion of history. The technical team implements the approved procedure while accounting assessment remains with the responsible business professionals.

An important failure scenario occurs when a technical failure occurs after data has been accepted but before its response is stored locally. Keep the external reference and confirmed destination ID before retrying. Separate access failure, business rejection and an unknown outcome. An operator must be able to inspect the relevant record and resolve its status without replaying completed steps. Agree which fields may appear in logs and who handles unresolved cases.

Test partial fulfilment, a business rejection, and matching a response to the actual document. For each case record the expected source data, destination record and customer-visible state. Include one denied-permission case and one interrupted response. Re-run a previously confirmed event and check that its business effect is unchanged. The acceptance record should identify the responsible team and the evidence required to close any discrepancy.

The initial discovery should confirm: Invoicing flow approved by accountant/ERP owner; Appropriate myDATA channel, credentials, and test environment; Current schema and documented rejection handling. Before launch, document the mapping for Order → agreed document issuance → ERP/provider → appropriate submission → Response → reconciliation and pending-item review. Assign responsibility for access renewal, monitoring and correction. A change to product configuration or the agreed business rule should trigger targeted regression checks. Begin with this defined workflow; add another channel only after its ownership and acceptance cases are clear.