1. AGENDA BE Bis MEETING

2. Agenda 2017.08.03 1. Welcome. 2. Who is who.
3. The new workgroup/forum/standard proposal and discussion.
4. Validation and distribution of a schematron to increase quality and interop.
5. Registration of the schematron at Peppol/EU level.
6. The new European Norm on e-Invoicing to be rolled-out in 2018.
7. Migration path of the current standard towards this new norm.
8. Peppol in Belgium in a B2B context.
9. Results of the workgroup active under the umbrella of the Federal Government.
10. Adaptations based on the feedback from the market.
11. Q&A and suggestions
12. Closing

3. Extra agenda 2017.08.24 1. Discussion answers questionnaire. XLS
2. Organization format. PPT
3. Formal decision(s) of the way to move forward. Discussion and conclusion
Format
Your engagement
New mailing list if appropriate
4. Tasklist Slide 15
5. Decision process Slide 16
6. Extension on Peppol or CIUS on E.N. Slide 17
7. Timeline E.N. Slide 18
8. Candidate for hosting next meeting
9. Closing

4. The new workgroup/forum/standard proposal
1. Continue with e-FFF but
2. Name BE Bis, e-FFF, Peppol in Belgium
One name or split due to broader context of use of BE Bis / e-FFF
3. Format and budget
Role the CodaBox (mail address, site, schematron, etc…) until other decision
Formal protocol signing or not
No formal legal entity
Foundation / NPO
Under umbrella of
IAB/IEC – BIBF/IPCF, Agoria, VBO/FEB
Budget and (type of) membership fee if any
Documentation open to anyone
Versioning, planning, communication,

5. Validation and registration of format
Remarks on the schematron if any
Use of as from today
Registration and changes depending on name and governance decision
Formal registration or not
Conformant statement adaptation
Modify owner (and specification)
New specification
Migrate CustomizationID and AdditionalDocumentReference
Timeframe parallel / hard migration
Quality label

6. Membership / meetings
Participation demanded by DAV/ASA, IAB/IEC, (BIBF, IPCF), FEDICT, VL.O.
Meetings
IAB/IEC
Alternating organisation on voluntary bases

7. Adaptations CashCredit CashDiscount Roundings4 StandardExchange
Identification
To be used preferably in the EndpointID, PartyLegalEntity and PartyIdentification
<cbc:CompanyID schemeID="BE:CBE"> </cbc:CompanyID>
To be used in the PartyTaxScheme
<cbc:CompanyID schemeID="BE:VAT">BE </cbc:CompanyID>

8. TC434 / EN 16931 List of syntaxes which comply with EN 16931-1
Based on the assessment, the list of the limited number of syntaxes, which comply with EN [1] shall include:
• UN/CEFACT Cross Industry Invoice XML message as specified in XML Schemas 16B (SCRDM - CII)
• UBL invoice and credit note messages as defined in ISO/IEC 19845:2015
leaves no room for Contracting Authorities to choose which ones to accept between the syntaxes that are included in the list that will be published in the Official Journal, further to Art 3 of the Directive. Art 7 clearly says that electronic invoices corresponding to the standard and to any syntax in the published list will have to be received and processed by Contracting Authorities and Contracting Entities in the EU. Any derogation from this rule would violate the Directive.

9. TC434 / EN 16931
The core invoice model shall include elements that allow the trading parties to represent any invoice transaction according to the EU VAT directives and should support the following types of business processes:
P1: Invoicing of deliveries of goods and services against purchase orders, based on a contract;
P2: Invoicing deliveries of goods and services based on a contract;
P3: Invoicing the delivery of an incidental purchase order;
P4: Pre-payment;
P5: Spot payment;
P6: Payment in advance of delivery;
P7: Invoices with references to a despatch advice;
P8: Invoices with references to a despatch advice and a receiving advice;
P9: Credit notes or invoices with negative amounts, issued for a variety of reasons including the return of empty packaging;
P10: Corrective invoicing (cancellation/correction of an invoice);
P11: Partial and final invoicing;
P12: Self billing.

10. TC434 / EN 16931
Accounting
Recording a business transaction into the financial accounts of an organization is one of the main objectives of the invoice. According to financial accounting best practice and VAT rules every Taxable person shall keep accounts in sufficient detail for VAT to be applied and its application checked by the tax authorities. For that reason, an invoice shall provide for the information at document and line level that enables booking on both the debit and the credit side.

11. TC434 / EN 16931 In scope for the core invoice model:
R45 information to determine the requirements of the applicable VAT legislation in force and the calculation and reporting thereof;
R46 information on the date the VAT is liable at document level;
R47 the necessary elements for national legal VAT requirements that apply for invoices issued to national and foreign Buyers, such as the legal registration status of the Seller;
R48 information to support the following VAT use cases:
Invoices for supplies for which VAT is charged;
Invoices for supplies for which VAT is not charged based on an exemption reason;
Invoices for supplies for which the Seller’s goods and services are exempt from VAT at line level;
Invoices for supplies that are issued under reverse charge;
Invoices for exempt intra-community supplies for which an intra-community acquisition must be done;
Invoices for supplies outside the scope of the Directive 2006/112/EC [2] (non-VAT invoices);
R49 the total VAT amount at document level;
R50 total taxable amount per VAT rate at document level;
R51 any additional information required to support the exemption evidence in case VAT is not charged based on an exemption reason at document and at invoice line level;
R52 the legal registration number and the VAT registration number of the Seller and Buyer and the VAT registration number of the Tax representative of the Supplier;
R53 the official postal address of the Buyer, Seller and Tax representative of the Supplier and their place of business and registered office;
R54 the invoice currency and the VAT accounting currency at document level if different from the invoice currency;
R55 codes for exemption reasons at document and invoice line level.

12. TC434 / EN 16931
In whatever manner the human readable presentation is created, it is important to bear in mind that since the fundamental process for producing an electronic invoice compliant with the European standard is based on invoice creation, processing and delivery in a structured format required by Directive 2014/55/EU, the human readable presentation is only a companion for human processes and cannot be a substitute for the structured e-invoice itself. The structured invoice will invariably be considered to be the reference instance and the instance for process automation, as required under Directive 2014/55/EU. However, the human readable version may be used in the event of manual processing or when a readable version is clearly required. In the event that a human readable presentation, it s present and contain all the information present in the structured e-invoice.

13. TC434 / EN 16931 Electronic invoicing - Part 5
Guidelines on the use of sector or country extensions in conjunction with EN , methodology to be applied in the real environment
6.9 Validation
For consistent implementation and operation of an extension specification it is necessary to express its rules with processable artefacts.
Examples of such artefacts are xml schemas and schematron. The type of artefacts selected depends on the syntax that is used in the implementation.

14. Gap Peppol and EN 16931Main findings
Significant number of gaps found
46 gap on business terms.
9 syntax gaps
20 attribute gaps
16 cardinality gap
138 rule gaps
Effect of gaps
191 minor.
35 average
3 major

15. Tasklist Creation of the organization Governing body
Bookkeeping / budget
Website and forum
Documentation
Schematron
Validation governance

16. Decision process Founding (Fixed) members Joining members
Supporting (members)
Decisions level 1
Changing articles of the association
Banning members
Decision by 2/3 majority
Decisions level 2
Changing the format
Decision by 50 % + 1

17. Extension on Peppol or CIUS on E.N.
E.N. UBL
UBL.BE
Peppol
E.N. UBL
UBL.BE
Peppol

18. Timeline E.N. implementation
01/01/2018
30/06/2018
31/12/2018
Start development
Roll out
ERP
Start development
Roll out
Accounting