Since September 1, 2026, all businesses in France that pay value-added tax (VAT) must be able to receive electronic invoices through an approved platform. This means that large companies and mid-sized businesses must also start issuing electronic invoices. Small businesses and micro-enterprises will have until September 1, 2027, to comply with this requirement. A PDF invoice attached to an email still looks like an invoice but no longer meets the standards of the new system. Many small businesses have already moved away from paper documents but have not yet fully adopted the electronic invoicing system required by the government. The reform applies to all VAT-paying businesses, including those that use reduced tax rates or do not invoice their customers. The first requirement—being able to receive electronic invoices—has already taken effect. This applies to invoices from French suppliers subject to VAT, such as telecom companies, energy providers, and large IT service providers. The second phase, which involves issuing electronic invoices, will apply to small and medium-sized enterprises (SMEs) and micro-enterprises starting September 1, 2027. These businesses will need to send their business-to-business (B2B) invoices in a structured format through an approved platform. A well-formatted PDF will not be enough to meet the new standards. The challenge is not just about installing another software but building a reliable system connecting the client, the invoice, the payment, and the accounting firm. It is important to check the billing software already in use: is it an approved platform, or is it connected to one? Can it handle customer and supplier invoices, credits, deposits, and payment statuses? These questions are more important than the software's user-friendliness. Companies must assign someone to manage this system, such as a manager, an administrative assistant, or a financial officer, or partially delegate it to the accounting firm. While the reform speeds up document circulation, it does not solve issues like data errors, missing purchase orders, or commercial disputes. The chosen platform must be on the official list of approved platforms published by the French tax administration, DGFiP, and its status must be verified at the time of subscription. For companies that already use an enterprise resource planning (ERP) system or robust business software, a single platform may be sufficient to ensure compliance. However, many small businesses need more: the ability to create quotes, convert them into invoices, track payments, follow up on non-payments, match expenses, and send documents to their accounting firm. In such cases, electronic invoicing can help reduce duplicate work rather than adding complexity to an already complicated system. Three platforms are worth considering for SMEs and small businesses starting with few tools or looking to simplify their setup: Tiime, which is ideal for entrepreneurs who want to centralize all financial processes in one place; Pennylane, which is better suited for SMEs that want invoicing to be the entry point for broader financial management; and Qonto, which integrates electronic invoicing with professional banking, payments, and pre-accounting features. Before choosing a platform, companies must ensure five key points: that the platform is officially approved, compatible with their existing software, capable of handling the required invoice formats, able to process specific operations, and that data can be exported or reversed if needed. A solution that works from day one should also allow the company to retrieve its information if it changes accounting firms, ERPs, or platforms. When the standard is fully implemented, several issues can arise. One common mistake is assuming that a valid XML file means a compliant invoice. However, compliance is not just about the XML structure but about adhering to the rules of the profile, checked through a Schematron validation. These rules ensure semantic coherence, such as which information must be included together and how amounts should be calculated. A file might pass all syntax checks but still be rejected due to a business rule that is not clearly communicated. The typical sign of this issue is when a company believes everything is working correctly until it is validated by the system. The format of the invoice determines what can be expressed. A paper invoice allows for any information written on it, but an electronic invoice has specific limitations. For example, a 10% discount on a line item is a common practice, but the BASIC profile used in France does not allow for specific fields to record the percentage or its base at the line level. This means the discount rate must be entered in a free text field, which is readable by humans but not by machines. This is not a flaw in the software but a limitation imposed by the standard itself, which changes the way invoices are structured from a container to a strict format that must be followed. Producing a compliant invoice is not the same as transmitting it. This is a common confusion that can be costly for small businesses. Two distinct roles exist behind the term "compliant": one is the creation of a valid Factur-X file, and the other is the transmission of that file via an approved platform to the customer and the administration. A software can be excellent at creating the file but not transmit it at all, while an approved platform transports whatever it receives, whether compliant or not. Both are necessary, but few companies clearly distinguish between them. When choosing a provider, it is more important to ask whether they handle the creation or the transmission, rather than simply asking if they are compliant. Once an invoice is issued, it becomes immutable. An issued invoice cannot be changed or deleted. Any corrections must be made through a credit note, which leaves both documents intact. This has always been a rule for accountants, but it has now become a technical constraint enforced by the system. Many invoicing tools allow users to reopen and edit an invoice that has already been sent, which is no longer acceptable. This change has deeper technical implications: if an invoice cannot be deleted, the numbering must never have gaps. Deleting a draft requires rolling back the counter, and an invoice canceled by a credit note must never be paid again to avoid double-counting revenue. These are rules that must be maintained in the database, not just team conventions.