E-invoice Center end-to-end scenario

The business application of the Seller generates invoice data and sends it to StreamServer. StreamServer creates an invoice and sends it via the signing filter to the TrustWeaver On Demand service. The on-demand service creates a legal, digitally signed e-invoice and returns the e-invoice to StreamServer.

StreamServer sends the signed e-invoice through the archive filter. The filter archives the e-invoice in the Seller’s archive. Depending on the local legal requirements, the archive is either the Collector storage or a third-party archiving system.

Note:

If the Collector storage is used, the e-invoice is first sent to the StreamServer runtime repository, from where it is further transferred to the Seller’s archive by an Archiver application.

The Seller validates the signed e-invoice on behalf of the Buyer. The Buyer is then not required to validate the e-invoice upon reception. To achieve this, StreamServer sends the signed e-invoice via the validation filter to the TrustWeaver On Demand service. The on-demand service validates the e-invoice and returns the signed and validated e-invoice to StreamServer.

StreamServer sends the signed and validated e-invoice to the Buyer. To ensure that the e-invoice is not manipulated during transmission, the Seller and the Buyer must use a secure connection. The Buyer registers and archives the e-invoice in the Buyer’s archive.

Figure 1

Creating legal e-invoices