1

When sending an EHF Billing 3.0 Invoice, one must supply information about the customer and the supplier. The invoice is sent along with a Standard Business Document Header (SBDH) that specify sender and receiver of the document.

Does the sender equivalent to the AccountingCustomerParty? And the receiver to AccountingSupplierParty?

And is it necessary to query the SML/SMP for all registrants?

pekaaw
  • 2,309
  • 19
  • 18

1 Answers1

0

The PEPPOL BIS Billing 3.0 syntax binding contains information on how to understand the different parts of the invoice document.

klakegg
  • 181
  • 1
  • 8
  • I have been studying this in details the last 4 months, and the syntax for Payment Request two months before that. Still, this does not answer the question about any relationship between Billing 3.0 syntax and SBDH sender/receiver. And it does not say if one should query the SML register before sending to the assumed participants, say if their configuration is not longer valid. – pekaaw Apr 30 '20 at 10:41
  • @pekaaw I also have to generate and send EHF invoices via peppol networks, how did you do these creation, validation and sending of invoices? what did you use? any github link or anything, it's a very unknown tech stack for me – Juliyanage Silva Feb 11 '22 at 14:40
  • 1
    @JuliyanageSilva I'm afraid I have no good answer for you, and I wish I knew this tech stack. We use a PEPPOL access point implementation called Oxalis from . It is a java implementation, so we have a separate server running this endpoint, and another api to generate an EHF based on a simpler dataset, as well as a validation api we use before sending. I can only wish you luck. – pekaaw Feb 11 '22 at 14:55
  • @pekaaw thanks for the info, so you wrote generating and sending by yourselves? – Juliyanage Silva Feb 11 '22 at 15:07
  • 1
    @JuliyanageSilva I created an internal service where I wrote an api for generating EHF xml with or without SBDH according to the syntax documentation referred to in this answer. A collegue created another internal service with two api endpoint. One for sending EHF, which works as a wrapper around Oxalis. The other one for validation, which works as a wrapper around another library called vefa validator . – pekaaw Feb 11 '22 at 15:42
  • @pekaaw sorry I have another question, did you ran oxalis in windows or linux? the guide seems only for linux, if it is windows did you find a guide for that? – Juliyanage Silva Feb 16 '22 at 15:30
  • 1
    @JuliyanageSilva I did not install this myself, but I can see that it is a Java application running on a TomCat server on Windows. – pekaaw Feb 18 '22 at 11:15
  • @pekaaw thanks mate, there are some issues as in it's highest natural habitat as usual, let's see – Juliyanage Silva Feb 18 '22 at 11:19