Brightfern E-Invoicing for WooCommerce
| 开发者 |
ombel
freemius |
|---|---|
| 更新时间 | 2026年10月6日 17:09 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Brightfern turns your WooCommerce orders into compliant, VAT-correct structured e-invoices for B2B and B2G sales, in whichever format the country you invoice actually requires — and checks each one before it leaves.
Four formats, one plugin
- Peppol BIS Billing 3.0 (UBL) — the European network standard, used across Belgium, the Netherlands and beyond.
- XRechnung (Germany) — the same UBL syntax with the German specification identifier and its own rules, including the buyer reference public bodies require.
- Factur-X (France) — a PDF/A-3 your customer can read, with the machine-readable CII invoice embedded inside it, for the domestic PPF/PDP flow.
- KSeF FA(3) (Poland) — the national clearance format, mandatory since February 2026. Not a variant of the others but a separate model written against the Polish VAT act, mapped directly and checked against the Ministry of Finance's own schema.
- It validates before it sends. A pre-flight gate checks the invoice against the rules for the chosen format, confirms the buyer is actually reachable on the network (SMP lookup), and validates their VAT number and name (VIES) — so you find out now, not days later when a portal rejects it. It also tells you when a format simply cannot express an order, rather than producing a file that gets refused at filing time.
- It also receives. Not just sending — Brightfern takes inbound e-invoices into a WooCommerce inbox and matches them to your orders. Being able to receive is mandatory for all French businesses from September 2026, even before they must issue.
- It doesn't lock you to one network. Brightfern is provider-agnostic: bring your own certified Access Point. No per-document markup, no lock-in.
- Gap-free invoice numbers. Its own sequential series (e.g. 2026-0001), a separate series for credit notes, a fresh series every year if you like — and a number is only used once an invoice actually passes the checks, so there are no gaps.
- A PDF invoice for every order, with your logo: attached to WooCommerce's customer e-mails, downloadable by the customer under "My account", and (for Peppol) included inside the e-invoice itself.
- A legal archive. Every issued and received invoice is written once to a protected archive that survives deleting the order, with a tamper-evident checksum chain.
- Built for your bookkeeping: an e-invoice column and bulk actions on the orders screen, a one-click period export (PDF + XML + a CSV overview) for your accountant, and an e-mail when an invoice is blocked, fails or is rejected.
- An inbox you can work through: received invoices with their lines, payment details and the supplier's own PDF, marked "processed" once booked.
- Free: generate the e-invoice (and credit notes) from an order in Peppol BIS UBL, XRechnung (Germany), Factur-X (France, a PDF/A-3 with the structured invoice embedded inside), or KSeF FA(3) (Poland), run the full validation + recipient + VAT checks, download the file, receive inbound e-invoices into the WooCommerce inbox — plus gap-free numbering, the PDF invoice (e-mail, "My account"), the archive, bulk actions and the accountant export.
- Pro: transmit outbound over Peppol, and file to Poland's KSeF — either straight to the Ministry of Finance (no intermediary, no per-document cost) or through your Access Point — with delivery and status tracking, including the official KSeF number once it is assigned.
安装:
- Install and activate the plugin (WooCommerce required).
- Go to WooCommerce → E-Invoicing and fill in your seller identity (legal name, VAT number, Peppol electronic address, address, IBAN).
- Choose your Access Point provider and enter its credentials (or keep Mock to try it offline).
- Pick the order status that should generate an invoice (default: Completed).
- (Receiving) Set a webhook secret and paste the shown webhook URL into your provider, or enable polling.
屏幕截图:
常见问题:
Do I need to be a certified Peppol Access Point?
No. You connect your own certified provider; Brightfern speaks to it through a provider-agnostic interface.
Which countries are supported?
Belgium (Peppol BIS UBL) is fully supported. Germany (XRechnung), France (Factur-X) and Poland (KSeF FA(3)) are supported — select the format under WooCommerce → E-Invoicing → Format. For Poland, generating and validating the FA(3) file is free and you can upload it to KSeF yourself; on Pro, Brightfern can file it through the KSeF API for you. For France, Brightfern produces the Factur-X PDF/A-3 and you submit it yourself — there is no automatic transmission to the French portal in this version.
Can it receive invoices, not just send?
Yes — that's a core feature. Received documents appear in a WooCommerce inbox and are matched to orders.
Does it check VAT numbers and get the VAT breakdown right?
Yes. Before you download an invoice, Brightfern validates the buyer's VAT number and registered name against VIES, and gets mixed VAT rates, discounts, reverse charge, intra-community supply and VAT-exempt small businesses right on the invoice itself — not just a flat total.
Which languages is the interface available in?
English, Dutch, French, German and Polish. It follows the site language, or the language set on your own user profile under Settings → General.
Are the invoice numbers gap-free?
Yes, by default. Brightfern keeps its own sequential series (format and padding configurable, e.g. {year}-{number} → 2026-0001), with a separate series for credit notes, and only hands out a number once the invoice passes the pre-flight checks. Sites that issued invoices before version 0.2.0 keep using the order number until they switch under WooCommerce → E-Invoicing → Invoice numbering; you can also continue an existing series from another system there.
Where are the invoices stored, and for how long?
Each issued and received invoice is stored on its order, and also written once to a protected archive folder in your uploads directory that is kept even if the order is deleted, and even when you uninstall the plugin. WooCommerce → E-Invoice export shows its integrity status. Keep backups: invoices must be retained for 7 years in the Netherlands and 10 in Belgium.
Do I need a Polish company to use KSeF?
Yes. The FA(3) format requires a Polish tax identifier (NIP) for the seller — that is the format's own rule, not a limitation here. Brightfern checks it before generating and tells you if it is missing.
更新日志:
0.2.0
- New: gap-free sequential invoice numbers with a separate credit-note series (configurable format, yearly series, continue from your previous system). A number is only used once an invoice passes the checks. Existing sites keep order numbers until they switch.
- New: a PDF invoice and credit note for every order, with your logo — attached to WooCommerce's customer e-mails, downloadable under "My account", and included inside Peppol / XRechnung e-invoices.
- New: a write-once legal archive of every issued and received invoice, with a tamper-evident checksum chain; kept when an order is deleted or the plugin is uninstalled.
- New: e-invoice status column and bulk actions (generate / send, download as ZIP) on the orders screen.
- New: WooCommerce → E-Invoice export: everything issued and received in a period as PDF + XML + a CSV overview for your accountant.
- New: an e-mail when an e-invoice is blocked, fails or is rejected.
- New: a readable inbox for received e-invoices — lines, due date, payment details, the supplier's PDF — with a "processed" status.
- New: "Check connection" on the settings page: tests your provider credentials and whether your own Peppol ID is registered.
- Fixed (Pro): the "is the buyer reachable on Peppol?" check never worked — Peppol changed how participants are looked up, and every lookup came back "unknown". It now uses the current lookup, and also really checks that the buyer accepts Peppol BIS invoices. Note: with "Block sending if the recipient is not registered on Peppol" switched on (the default), invoices to buyers who are not on Peppol are now held back as that setting describes, instead of being sent and failing at your Access Point.
- New: Belgian enterprise numbers (scheme 0208) are checked against the KBO/BCE checksum before sending, so a typo is reported with the exact field instead of a generic rejection from your Access Point.
- e-invoice.be: when e-invoice.be refuses an invoice as invalid, the specific rule it failed is now shown.
- e-invoice.be: a rejection the buyer sends back up to 14 days after delivery is now picked up — the invoice is marked rejected and an order note tells you why.
- e-invoice.be: the settings page now explains which webhook URL and event to set up.
- Fixed: the e-invoice.be provider added in 0.1.23 could not actually send or receive e-invoices. It has been rebuilt against e-invoice.be's API: sending, receiving (by webhook and by polling) and delivery status updates now work. If the receiving side has already rejected the invoice when delivery is first confirmed, that rejection is shown instead of "delivered"; a rejection the buyer sends days later is not picked up yet.
- Fixed: a received e-invoice that e-invoice.be announced but that could not be downloaded at that moment is now retried instead of being silently dropped, and the polling fallback now catches up on older received documents instead of only the newest ones.
- Fixed: during the 14-day Pro trial, Pro features stayed locked as if you were on the free plan.
- Fixed: when a Pro trial or licence had ended, invoices could still be sent automatically if the Pro build was still installed.
- The checkout VAT field, the order status messages and the provider names are now translated in Dutch, French, German and Polish, and the bundled translations now also load on WordPress 6.4–6.7.
- Pro now offers a 14-day trial (payment method required up front), so you can try sending before you are charged.
- Added e-invoice.be as an alternative Peppol Access Point provider, alongside Storecove — a lower-cost option for merchants sending a smaller invoice volume. Configure it the same way, under WooCommerce → E-Invoicing.
- Quieter logs: the duplicate-transmission lock now suppresses the expected database message it logs when two near-simultaneous requests legitimately contend for the same order, instead of printing it as if something were wrong.
- Fixed: the checkout VAT field fix in 0.1.20 was incomplete — a bare Polish, German or other non-Belgian VAT number of the same length as a Belgian one could still be wrongly treated as Belgian and blocked. It's now only recognized as Belgian on a valid checksum, or when the buyer typed "BE" themselves.
- Fixed: the checkout VAT field no longer treats every 9-10 digit number as Belgian — a Polish, German or other EU VAT number of that length is no longer blocked as an invalid Belgian one.
- Fixed a race condition where two near-simultaneous triggers for the same order could both pass the duplicate-transmission check and both send it.
- Fixed credit notes failing validation when the (optional) bundled schema was present, because they were checked against the invoice schema instead of the credit note one.
- Fixed a rare rounding mismatch on invoice lines whose unit price doesn't divide evenly, which could affect KSeF FA(3) filings.
- Pro: the hourly status-check pass no longer gets stuck re-checking the same handful of orders forever after a provider switch or an unresolvable order — it now works through the actual backlog.
- Fixed "Generate & send now" being able to leave an order with no recorded status at all when another request was already processing it, which could lead to a duplicate send on a later, unrelated status change.
- Fixed a received document with no provider reference being reported as lost instead of stored.
- Fixed: an explicitly configured Peppol address on an order (no company name or VAT number required) is now correctly recognized as a B2B transaction again.
- Fixed: a Belgian-looking VAT number typed without a country prefix that fails the checksum is now flagged with a warning instead of silently producing a made-up Peppol address.
- Pro: the provider's rejection reason (e.g. KSeF's "duplicate invoice") now reaches the order's status history instead of only the status change itself.
- Pro: KSeF status polling no longer adds extra delay to checkout/admin requests when the provider is temporarily unreachable.
- Belgium: Peppol electronic addresses are now derived using the correct scheme 0208 (KBO/BCE enterprise number) with real checksum validation, instead of the generic VAT-based scheme.
- Added a "VAT number / BTW-nummer" checkout field (classic checkout and the Checkout block), feeding the same VAT field Brightfern already reads from other plugins.
- Pro: an order with no company name and no VAT/KBO number is no longer treated as a B2B Peppol transaction — it now generates without transmitting, instead of hard-blocking on a missing Peppol address a private buyer never has.
- Clearer order-admin status messages (e.g. "Submitted. Awaiting delivery confirmation.", "Recipient or network rejected it: ...") instead of a bare status code.
- Pro: an invoice rejected by KSeF (for example, flagged as a duplicate) is now recorded as rejected instead of staying "pending" indefinitely.
- Pro: switching your e-invoicing provider no longer risks the hourly status check asking the newly-selected provider about an invoice that was actually sent through a different one.
- Pro: added a safety check that stops the KSeF (direct) provider from filing a document that was built for a different format.
- Pro: a bad response from KSeF's public-key service could previously block filing for up to 24 hours; it is no longer cached when that happens.
- Smaller reliability fixes to the hourly status-check pass: it now works through a backlog oldest-first, and a single failed check no longer gives up on the rest of that invoice's status poll.
- Pro: Poland's KSeF can now be filed automatically, instead of downloading the FA(3) file and uploading it in the Ministry's taxpayer application yourself. Two routes are available — directly to the Ministry of Finance (no intermediary and no per-document cost), or through Storecove if you already use them as your Access Point. Pick "Poland KSeF (direct)" under WooCommerce → E-Invoicing and paste in the authorization token you generate once at ksef.podatki.gov.pl.
- Pro: transmitted invoices that the network hadn't confirmed yet are now followed up automatically once an hour, so a KSeF invoice that takes a while to clear still gets its official KSeF number recorded on the order instead of an internal reference. Peppol delivery confirmations are picked up the same way.
- Provider API addresses are now restricted to https. A typo used to be able to silently downgrade the connection to plain http, which for KSeF also carries the credential used to file your invoices.
- Generating an invoice can no longer fail in a way that interrupts the order it belongs to: an unexpected error during transmission now fails just that invoice, with the reason recorded on the order.
- Fixed a data-loss edge case: a very large invoice (many line items) could fail to save under WooCommerce's High-Performance Order Storage without any visible error. Brightfern now detects this before it happens and fails the invoice with a clear message instead of silently losing it.
- Fixed a race condition where triggering invoice generation twice in quick succession for the same order (e.g. an automatic status-change trigger overlapping a manual "Generate now" click) could corrupt which document ended up stored.
- KSeF: line-level discounts are now included on the invoice (P_10), and the seller's tax id is clamped to the length KSeF actually allows.
- Fixed VAT numbers for Greek businesses being incorrectly flagged as invalid.
- Fixed the VAT breakdown being able to show the wrong sign for a shipping charge on some orders, and orders consisting only of fees or shipping (no product lines) failing to generate an invoice at all.
- Credit notes now double-check that the refunded amount matches what WooCommerce recorded before finalizing.
- Fixed a case where a failure to store a received e-invoice could go unnoticed instead of being reported so the sender's system retries.
- Fixed inbound invoice matching being able to attach a document to the wrong order in one of its two matching paths.
- Several smaller fixes: inbox order links under High-Performance Order Storage, a settings-save edge case, an empty inbound file being rejected safely instead of erroring, and more consistent Pro gating for Peppol-only checks.
- Pro: "Generate & send now" no longer re-transmits an invoice that was already sent and confirmed delivered — it now tells you to issue a credit note (or a new invoice) instead, since resending different content under the same invoice number isn't valid on Peppol or KSeF. Resending an invoice that failed or was blocked still works exactly as before.
- KSeF: the reason you give when refunding an order in WooCommerce now appears on the correction invoice itself, matching what already happened for Peppol, XRechnung and Factur-X.
- Added Poland's KSeF FA(3) as a Format option in Settings. Generating and validating it is free, same as the other formats: Brightfern produces the FA(3) XML and checks it against the Ministry of Finance's own schema, and you submit it in the taxpayer application to obtain the KSeF number. There is no automatic submission through the KSeF API in this version.
- Pre-flight now tells you before generating if KSeF cannot be used for an order: a seller without a valid Polish NIP, or a VAT rate that has no equivalent in the Polish rate scheme. Invoices in a currency other than PLN generate a warning, because FA(3) also expects the VAT restated in PLN.
- The Peppol recipient and electronic-address checks no longer run for Poland, the same fix already made for France — those documents never travel over Peppol, so the warnings were misleading.
- Added a Polish translation, alongside the existing Dutch, French and German. Set the site or user language under Settings → General (or your user profile) to switch.
- KSeF: long product names, SKUs and barcodes are now shortened to the lengths the Polish schema allows, instead of producing a file KSeF rejects. A buyer whose VAT field holds only a country code, and a correction invoice that cannot name the invoice it corrects, are handled properly too.
- Removed two files that were being packaged into the plugin by mistake: a copy of the plugin's own zip (shipped since 0.1.5) and a copy of the Composer tool. Together roughly 4.5 MB of dead weight that did nothing.
- Factur-X: fixed the seller's legal and trading name being swapped in the embedded XML.
- Factur-X: removed the currency attribute from amounts that must not carry it, which could cause a document to be rejected by a receiving portal.
- Factur-X: invoices to buyers who aren't on the Peppol network are no longer blocked or warned about — Factur-X doesn't use Peppol at all.
- Factur-X: the printed PDF now shows the VAT breakdown per rate, including the exemption reason for reverse charge and similar cases, plus any amount already paid.
- Fixed a stale Factur-X PDF being offered for download after an order was regenerated in a different format.
- Packaging fix for the 0.1.7 Factur-X release: corrected how the free build is generated so it contains no references to paid-only code. No functional change to the plugin itself.
- Added Factur-X (France) as a Format option in Settings: generates a PDF/A-3 invoice with a UN/CEFACT CII XML embedded inside it, ready to submit or email. Generating and downloading it is free, same as Peppol and XRechnung — there is no automatic transmission to Chorus Pro in this version, you download and submit it yourself.
- Added XRechnung (Germany) as a Format option in Settings — same UBL syntax as Peppol BIS with the correct XRechnung specification identifier, plus a check for the mandatory buyer reference (BT-10) that format requires. Generating and validating XRechnung is free, same as Peppol; transmitting it is Pro.
- Added Dutch, French and German translations (in addition to English). Set the site or user language under Settings → General (or your user profile) to switch.
- Text domain now matches the assigned WordPress.org slug, brightfern-e-invoicing-for-woocommerce.
- Reworded the description to drop comparative language about other plugins.
- Documented the third-party/public services this plugin calls (VIES, the Peppol SML/SMP network, and the configurable Access Point provider) in a new "External services" section below.
- Fixed the settings form: a naming mismatch introduced during the rename made every save silently discard the submitted values (and clear stored ones).
- Added a Payment means (BT-81) setting: credit transfer or SEPA credit transfer.
- Fixed the licensing menu wiring so account/opt-in screens render on the settings page instead of a permissions error.
- Inbound XML is now parsed with network access disabled (LIBXML_NONET).
- Corrected the Contributors header to the actual WordPress.org account.
- Removed the Plugin URI header: it duplicated the Author URI, which WordPress.org rejects. There is no separate product page yet.
- Providers reference the premium send types by fully-qualified name, so the free build carries no imports pointing at the stripped directory.
- Outbound Peppol transmission is now excluded from the WordPress.org build rather than disabled at runtime, per plugin directory guideline 5.
- Receiving inbound e-invoices moved from Pro to free.
- Uninstall cleanup now also clears the polling cron on a normal uninstall.
- Initial MVP: EN 16931 mapping, Peppol BIS UBL serialization, three-layer pre-flight validation (business rules + optional XSD + optional schematron), SMP recipient lookup, VIES VAT check, provider-agnostic send + receive (Storecove reference provider + offline mock), admin inbox, order metabox, settings.