We were at Chargebee’s Beelieve Roadshow in Paris last week, and one comment kept coming up: “Every country we sell in does eInvoicing differently. Keeping up with compliance across markets is a pain.” If you're using Chargebee, you can connect it with Invopop and handle all of those markets from one connector, with the workflow you want for each one. Invopop's Chargebee app imports every new invoice and credit note automatically and runs it through that workflow, converting it into the format that country legally requires and filing it with the right tax authority. Updates and error messages come back into Chargebee in the comment section of the invoice or credit note, so nothing gets lost. You can also have it notify you in Slack or email when something needs a look. Getting started is simple: connect Invopop with Chargebee, select your country apps, and start issuing legally compliant eInvoices. 👇 Álvaro made a full video on how to set it up. eu1.hubs.ly/H0zcmKw0

🇪🇸 The work for B2B eInvoicing in Spain has begun. Businesses above €8 million in annual volume of operations need to start eInvoicing on 6 October 2027. Everyone else follows on 6 October 2028. Preparing means more than the invoices you send. You also have to receive structured invoices from your suppliers, and report what happens to them: whether you rejected the invoice, and the date you paid it in full. That brings accounts payable and treasury into the project. Where do your payment dates live? Can you connect them to the right invoice and report them within four working days of payment? The AEAT has also started publishing the first technical documentation for the public invoicing solution. It is an early version, but teams operating in Spain can begin planning and building now. We wrote a guide explaining the deadlines, the exchange routes, and the reporting duties, plus how they fit alongside VERI*FACTU and SII. eu1.hubs.ly/H0z6szK0

If you run a vertical SaaS, this will sound familiar: eInvoicing isn't your obligation, but your customers expect you to handle it anyway. Mews' promise is a single platform for hotel operations, and eInvoicing is part of it. Complying in every mandated market meant patchwork: find a local provider, negotiate a contract, build another integration. Three to four months before a hotel could issue a legal invoice. Mews embedded Invopop instead. One integration with our API, and their customers can now send and receive eInvoices that comply with local regulation. Development time per market went from 12 weeks to 5. Belgium was first. Mews is now live in 5 countries with Invopop. We sat down with Patricio Roffo, Director, Product and Engineering at Mews, to hear how they turned eInvoicing from a pain point into a growth lever. Watch the interview 👇 eu1.hubs.ly/H0y-2nC0

NetSuite offers native eInvoicing. For a lot of companies it's the obvious place to start. We keep hearing from teams who did, and how they found it harder to navigate than expected. Most problems don't show up on day one. They show up when regulations change, volumes grow, or a new market gets added, and edge cases start hitting production. Invopop's NetSuite connector is built for exactly that: every country you operate in, the exceptions included, and workflows that adjust to how you work. It connects directly to NetSuite, so your finance team continues to manage everything from one place. 🔌 More than 85 companies already invoice from NetSuite with Invopop, across the 30+ countries we support today, with more in development. 📘 To help you work through the choice between the native route and a separate provider, we wrote a guide: what each one involves, and the questions worth asking before you commit. eu1.hubs.ly/H0yVX1Q0

🇪🇸 Spain published the Ministerial Order this morning, the last piece of the B2B eInvoicing mandate. What it means: — The clock started: the obligation has been coming since Ley Crea y Crece in 2022, but the deadlines couldn't start running until this order existed. It takes effect tomorrow, 6 October, and that's the date everything counts from. Companies with turnover above €8M get twelve months, so 6 October 2027. Everyone else gets twelve more, 6 October 2028. — You send and you receive: every business has to issue invoices to its business customers in a structured electronic format aligned with the European standard EN 16931, and be able to receive them from its suppliers the same way. Being mostly a buyer doesn't exempt you. — The buyer reports the payment: when you receive an invoice, you report to AEAT whether you rejected it, the date you paid it in full, and the payment due date. That's how Spain plans to measure late payment, which is what Ley Crea y Crece was written to tackle. — Everything reaches AEAT: choosing a private platform doesn't keep you out of the public one. If you don't invoice through the SPFE, the free public platform AEAT is building, you send AEAT a faithful copy of every invoice at the moment you issue it. The repository is not optional. – This is not VERI*FACTU: two separate obligations, and complying with one does not cover the other. VERI*FACTU governs your billing software and the records it keeps. This governs the invoices you exchange with other businesses and the payment data that follows them. The two do meet in one place: the eInvoice carries a field for the VERI*FACTU QR where that applies. lnkd.in/e-GB8wfC We're preparing a guide to help you navigate it. Questions in the meantime? Drop them below 👇

One month of mandatory e-invoicing in France. The ministry's numbers are good: 5 million invoices exchanged in the first two weeks, more than €15 billion, and 70% of VAT-declaring businesses with a reception solution chosen, figures it had modelled for the end of October. Signed up isn't the same as reachable. Three things we're seeing across the companies we work with in France. 1️⃣ Poor registrations — Buyers listed in the annuaire who still can't receive. France doesn't mandate Peppol, but most plateformes agréées use it to exchange with each other, so a buyer needs both an annuaire entry and a live address on the network. The directory says yes, the network says no, the invoice doesn't land. The sender gets an error, but the fix is on the buyer's side. 2️⃣ Misconfigured senders — France's statuses travel back to whoever issued the invoice, so your endpoint has be able to receive statuses as well as send. We've seen companies issuing fine while nothing can reach them, which means a rejection goes out by email and the status never closes the loop. You find out your invoice was refused when somebody tells you. 3️⃣ Businesses migrating PA — Companies that picked a platform, ran real volume through it and hit a wall in production are now moving. If you're changing where you receive, that's an annuaire change, and the network routing has to stay in step with it, so for weeks your addressing sits half in one place and half in the other. You run two setups at once and reconcile by hand. No business will be penalised in 2026, so none of this is expensive yet. An invoice that doesn't arrive is still one nobody books, pays or deducts on time. Two things worth doing: check how you appear in the annuaire, since that entry is what your suppliers resolve against. And check your own endpoint accepts statuses, not just sends invoices. Full guide to the French mandate: invopop.com/blog/e-invoicing…

Belgium has confirmed plans to introduce mandatory B2B e-invoicing starting in July 2024 DM us to learn more about it!! invopop.com/blog/belgium-con…

🎉Invopop it’s part of YC's W23 batch! 🎉 Thanks to our customers, investors, and team for helping to make this possible. ycombinator.com/launches/Hu5…

💥 Last Thursday the “Crea y Crece Law” was published in Spain.💥 All Spanish companies will be obliged to issue electronic invoices in their B2B relations Read more and how we can help here 👇🏼 invopop.com/posts/2022/elect…