Transaction groups (business actions)

Business transaction groups

The action is part of the orchestration flow of documents between business partners. It is independent of its syntax e.g. EDIFACT, Peppol BIS3 or other.

Business transaction groups are the types of business transactions.

A business transaction group points to the action that should be performed on the core business document, while a business transaction refers to an implementation of a particular document syntax.

For example, SubmitInvoice can refer to transactions NESP4-2.0 SubmitInvoice or BISENUBL-3.0 SubmitInvoice.

These are the three most commonly used business transactions groups:

Profile key name	Internal transaction identifier
`SubmitInvoice`	The supplier issues an invoice to the customer to request payment for services or products provided. An invoice is used to specify the financial aspect following a business transaction.
`SubmitOrder`	The buyer places an order with a seller. The order specifies which goods or services the seller should deliver and might specify delivery conditions, discounts, and other pricing details
`CorrectWithCredit`	he supplier issues a correction credit note to the customer. For example, this happens when the products delivered do not satisfy quality standards or when there is an error in the despatch advice or the invoice.

Here is a list of all the business transaction groups that are configured on the messaging server:

Transaction group | Description

----------------- | ----------- AcknowledgeCatalogue | The buyer confirms that they have accepted the seller's catalogue. AcknowledgeOrder | The seller accepts or rejects an order that they have received from the buyer. CorrectWithCredit | The supplier issues a correction credit note to the customer. For example, this happens when the products delivered do not satisfy quality standards or when there is an error in the despatch advice or the invoice. CorrectWithDebit | The customer issues a correction invoice to the supplier, for example, in case when the despatch advice does not correspond to the products received or when the products do not satisfy quality standards. PunchOutCatalogue | The buyer sends to the seller a list of products or services that was created through the seller's procurement system or online catalogue. RequestQuotation | The customer requests a quotation from the supplier. SubmitCatalogue | The seller submits a catalogue to the buyer or a potential buyer. SubmitDocument | The sender transmits an additional document to the receiver. SubmitInvoice | The supplier issues an invoice to the customer to request payment for services or products provided. SubmitBillingResponse | The buyer sends to the seller an informative message regarding the status of the invoice or the credit note that the buyer's system is processing. SubmitMessageResponse | The receiver sends a message level response (MLR) in case the sender has requested feedback about the validation status of the message that they issued. The message level response contains details regarding the validation. SubmitOrder | The buyer places an order with a seller. SubmitOrderResponse | The seller accepts or rejects an order that they have received from the buyer. SubmitPackingNote | The seller sends a packing note or a despatch advice to the buyer. The document defines the delivery conditions and confirms that the items have been despatched. SubmitPaymentNotification | The customer sends a remittance advice to the supplier to notify them that their invoice or credit note has been paid. SubmitPaymentReminder | The seller submits a reminder to the customer that their payment is due. SubmitQuotation | The supplier sends a quotation to the customer for the items or services requested. SubmitUtilityStatement| The supplier issues a utility statement to the customer. The document accompanies an invoice or a credit note and provides details regarding utility services expenditure (electricity, gas, water, telephone).