Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think the same thing about invoicing... especially given the different hoops every company makes you jump through to make your invoice compliant.


Italy actually has a standard for electronic invoicing, and most companies are required to use it ("Fattura Elettronica"). It works by having a centralized portal to which invoices are submitted.

Of course, being a SERIOUS, CORPORATE standard it needs to be overly complex, based on XML and SOAP and WebServices and whatnot: https://www.agenziaentrate.gov.it/portale/documents/20143/23...


Don't they kind of do that at larger organizations with EDI? Or is it still nonstandard between organizations?


EDI is only semi-standardized; in my experience usually each pair of trading partners requires a separate effort (usually the bigger partner imposes the requirement and the smaller one has to make changes). Some difficulties include:

* There are multiple protocols for exchanging EDI documents (AS1, SMTP, FTPS, SFTP...)

* There are multiple standards for the documents themselves (EDIFACT, X12, GS1 XML...)

* There are partner-specific business rules that need to be set up (this partner needs an ASN, that partner requires invoices to be for only one PO each, the other partner can only accept invoices which use their ERP’s internal codes...)

Some of these problems can be papered over with a “VAN” that can translate between standards, but I have yet to see one business send a non-PDF invoice to another without a lot of fuss.


Good overview. I wrote about this in a bit more detail on our blog recently: https://www.stedi.com/blog/what-makes-edi-so-hard




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: