The eInvoicing Implementation Guide
1 Audience
The intended audiences are:
BUSINESS ANALYSTS | APPLICATION DEVELOPERS |
Business Analysts: | Application Developers: |
+ Those involved in the identification of business requirements for solutions to support Accounts Receivable, Accounts Payable and the electronic transmission of the associated documents between businesses; or | + Those involved in the design, development, operation and implementation of software and Services for the exchange of electronic Documents or messages; or |
+ Those who analyse and document business or processes or systems, assessing the business model or its integration with technology. Analysts will need to understand which aspects of their business requirements the Implementation Guide addresses (and does not address). | + Those involved in the design, development, integration and operation of business applications dealing with invoicing. |
Audience Reading Guide | Section | BUSINESS ANALYSTS | APPLICATION DEVELOPERS |
---|---|---|---|
Overview | 2 | ||
Conformance | 3 | ||
Distribution Pacakage | 4 | ||
Terms and Definitions (Normative) | 5 | ||
Controlled Vocabulary | 6 | ||
Business Processes | 7 | ||
eInvoicing Profile | 8 | ||
Use of Identifiers | 9 | ||
Identfying Services for the Interoperability Framework | 10 | ||
Validation Artefacts | 11 | ||
Support Material | 12 | ||
Extensions to the Core Invoice | 13 |
Primary Audience | |
---|---|
Secondary Audience |
Business users (such as Accounts Payable or Accounts Receivable staff) do not need to use this specification to be able to participate in eInvoicing. Their business software providers may refer to the eInvoicing Semantic Model (Digital Business Council, 2016c) to ensure their application supports these requirements and may use this specification if they choose to implement the eInvoicing Profile for their applications, but it is also not a requirement for participation in the Council’s Interoperability Framework (Framework).