April 23, 2017
You are here : Support  >  Resources  >  On NESUBL  >  Basic Invoice Only
Basic Invoice only

If you would like general information on NES, the NES profiles and their meaning and purpose please visit our On NESUBL page. For information on UBL 2.0 visit our On UBL page.

This profile describes a process comprising only an electronic invoice. It is intended for situations where invoicing is electronic but where matching of the invoice to other electronic documents may not be practicable. As a result, the invoice is self-contained with respect to legal and fiscal requirements.

It is not a primary objective of this profile to facilitate automatic order matching and/or cost allocation; the profile assumes limited or no procurement data content and limited or no aligned and synchronized identifiers in the system to match the transaction.

Large parts of the invoice may be expressed as text rather than identifiers and codes e.g. the invoice may contain items (goods or services) with item identifiers and items with free text description.

This profile can be used with little or no integration to ERP systems. It may be introduced with minimum advance exchange agreement if coding schemes are not used.

This profile may cover invoice factoring arrangements.

Business benefits

These are the business benefits to the parties:
Customer Party
  • Reduced requirement for manual intervention; leads to fewer human keying errors.
  • Automatic invoice validation.
  • Potential for systematic application of invoice control.
  • Resource redeployment.
Supplier Party
  • Faster invoice transfers.
  • Acknowledgement of invoice receipt (at technical level).
  • Potential for shortened payment cycle and improved cash flow.

Business documents

The UBL 2.0 documents used in this profiles are:
  • Invoice

Business scenarios

The scenarios used in this profiles are:
  • Invoice accepted.
  • Invoice rejected.

Business activities

Activity description:
  • Supplier's accounting party creates and sends an invoice to customer's accounting party.
  • Customer's accounting party receives and processes the invoice.
  • Customer's accounting party accepts or rejects invoice in full. Acceptance of the invoice initiates a payment process. Rejection leads to an external resolution process. Notification of acceptance/rejection is external.
  • Implied, payment is external to this profile.
Activity diagram:

NES Profile #4: Basic Invoice Only