Standard BI Publisher

</aside>

BI Publisher runs the invoice print UBE and produces the invoice PDF and the Report Definition source XML. The Report Definition must run in Burst mode so that each invoice is processed separately.

Required setup:

Invoice UBE versions (R42565 / R03B505 / R48506 / R48507) linked to the Report Definition.
Report Definitions with an RTF template and a Burst definition.

Steltix Document Control

</aside>

Document Control picks up the burst output through the BIP Delivery hookup and runs RQ46DC21 to create the enhanced source XML, which contains the additional data an eInvoice requires. It then applies the XSL template to create the eInvoice output.

Required setup:

Document Control setup: eInvoice Accounts and BIP Delivery.
Cross Reference setup: eInvoice Xrefs.

eInvoicing Monitor

</aside>

The eInvoicing Monitor holds the eInvoice output (XML, and JSON where the broker requires it) with the invoice PDF embedded as Base64, and shows the status of every eInvoice. From here, eInvoices can be sent manually, regenerated, and investigated.

Required setup:

Report Template (XSL) created in P95600 and linked in Document Control.
Meta data setup (KCO / DCT / DOC) in Document Control.
If required, JSON output turned on in Document Control.

Broker API / eMail functionality

</aside>

This component sends the eInvoice to the receiver, either by API to a broker, which delivers it over the Peppol network or a government portal, or by e-mail directly to the customer. This part is customer-specific: the orchestrations and setup depend on whether the eInvoice is sent via a broker or directly to the customer.

Required setup:

Broker API orchestration.