Is this your project? I'd love to see a link to the source. My problem with all of these nice invoicing tools is that they are way too localized. Most often U

Is this your project? I'd love to see a link to the source. My problem with all of these nice invoicing tools is that they are way too localized. Most often US-centric. Invoices must adhere to strict rules in many countries. And lots of countries have rather different business rules. VAT, obviously. But invoice numbering. Dating. What info must, or must not be included and so on and so forth. The EU has some effort done and underway to normalize this across the EU member states, but that's far from done and will problably never finish. Some examples: In the Netherlands, we must use an incrementing number scheme, that must never have holes and be stable. So after invoice myFoo-24-whatevs-1337 you must issue myFoo-24-whatevs-1338 (and not myFoo-24-whatevs-1336 or myFoo-24-whatevs-1339). This requires state somewhere. Its horrible. But its the law. In france, you must include your RCS or RM registration number depending on your type of org. You must add your TVA number if you are VAT registered. You must have an incrementing number similar to above. You must add dates for the invoice and some other dates in certain cases. And you must add all sorts of info regarding conditions and penalties for late payments. It is complex. But it is the law. Repeat the above for every country in the EU. And then for every other country in the world. This doesn't touch on all the various VAT and other tax rules and line-items that must, may, may not and so fort be applied. My point being: It's nice to have invoice-generation-apis or simple invoicing apps. But unless they clearly target a country and niche and use-case, they will quite likely produce invoices that are not compliant and may get you in trouble with authorities or tax laws. Where "niche" is e.g. freelancer software devs or webshop-owners. And where use-case is e.g. "only issued to consumers in my own country".