Business process design.

Before starting to configure the b+ dgtal eInvoice, the business processes to be deployed must be designed.

It is very important to define the different types of processes, and not to use the same process for all the processes to be deployed; i.e., if we are working on an e-invoicing project and we are designing the invoice reception process, it is advisable to design a separate process for:

• Invoices
• Debit notes
• Credit notes

The only scenario where it is recommended to use the same b+ dgtal eInvoice process for several types of processes is when they have exactly the same flow. However, if the client requires independent monitoring of each process, it is recommended that they are designed and deployed independently.

This is where the concept of the business unit is born.

It is recommended that each business process to be designed be assigned a single business unit.

It is recommended that the design of the business processes be carried out using the BPMN 2.0 notation and using a specialised tool for this purpose. SAP NetWeaver Developer Studio could be used to make these designs or any other specialised tool for this purpose, such as Bizagi.

For the design of these processes, it is recommended that the following be taken into account:

• Use standard BPMN 2.0 notation.
• Use exception events to model possible errors or exceptions that a process step may have.
• In cases where the flow is split, specify very well which event or condition must be fulfilled for the flow to be split.
• Clearly specify the possible termination events of the process.
• If there are external actors such as other systems where the flow interacts, it is recommended to use Lanes to model them in case they are part of the customer's infrastructure, or Pools in case they are outside the customer's infrastructure.

The following are examples of the design of the processes for invoice and credit/debit note receipt:

Invoice reception

Receipt of debit and credit notes (behave the same)