Skip to content

[IP-126]: implement peppol - #471

Draft
nielsdrost7 wants to merge 2 commits into
developfrom
feature/126-implement-peppol
Draft

[IP-126]: implement peppol#471
nielsdrost7 wants to merge 2 commits into
developfrom
feature/126-implement-peppol

Conversation

@nielsdrost7

@nielsdrost7 nielsdrost7 commented Jun 12, 2026

Copy link
Copy Markdown
Collaborator

Given the work already in PR #471, the remaining Sprint 5 deliverables are:

  • Make UblHandler::generateXml() produce real UBL 2.1 XML — this unblocks NLCIUS ([Invoices]: NLCIUS (Dutch CIUS) e-invoicing profile for UBL 2.1 export #487), BE, NL, and most of Europe
  • Fix recommendedForCountry('NL') → UBL_21 (one line)
  • Promote SendInvoiceToPeppolAction to a Filament Action and wire it to EditInvoice
  • Add Peppol fields to customer form (conditional on EU country)
  • Add LetsPeppolProvider directory + tests
  • Add feature test for the end-to-end send flow

Summary by CodeRabbit

Release Notes

New Features

  • Peppol E-Invoicing Integration: Send invoices to Peppol networks with support for multiple providers and document formats
  • Multi-Format Support: Automatically select appropriate invoice formats based on customer country (UBL, FatturaPA, Factur-X, EHF, OIOUBL, and others)
  • Transmission Tracking: Monitor invoice transmission status with automatic polling and retry capabilities for failed transmissions
  • Peppol ID Validation: Validate customer Peppol identifiers against the network before sending
  • Provider Management: Configure and test Peppol provider integrations with support for e-invoice.be and Storecove

Addresses #126

nielsdrost7 and others added 2 commits June 12, 2026 20:34
Restore full Peppol integration on this feature branch:
- Peppol models, migrations, enums, events, jobs, listeners, traits
- EInvoiceBe and Storecove provider implementations
- Format handlers (UBL, BIS, CII, Factur-X, ZUGFeRD, FatturaPA, etc.)
- Artisan commands: PollPeppolStatus, RetryFailedTransmissions, TestPeppolIntegration
- Client peppol-fields migrations for relations table
- Full unit test suite for Peppol integration

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@nielsdrost7
nielsdrost7 force-pushed the feature/126-implement-peppol branch from 6c38c5d to b3c2b7a Compare June 12, 2026 18:34
@InvoicePlane InvoicePlane deleted a comment from coderabbitai Bot Jun 13, 2026
@InvoicePlane InvoicePlane deleted a comment from coderabbitai Bot Jun 13, 2026
@InvoicePlane InvoicePlane deleted a comment from coderabbitai Bot Jun 13, 2026
@InvoicePlane InvoicePlane deleted a comment from coderabbitai Bot Jun 13, 2026
@nielsdrost7

Copy link
Copy Markdown
Collaborator Author

@coderabbitai full review

@coderabbitai

coderabbitai Bot commented Jun 13, 2026

Copy link
Copy Markdown
Contributor
✅ Action performed

Full review finished.

@b12f

b12f commented Jun 13, 2026

Copy link
Copy Markdown

Hey @nielsdrost7 both this and #473 seems like huge PRs do to in 2 commits with apparently little oversight. v1 has some overly generous AI coding as well, but it does not seem to be as bad. This feels like it will turn into a maintenance nightmare.

@nielsdrost7

nielsdrost7 commented Jun 13, 2026

Copy link
Copy Markdown
Collaborator Author

@b12f thanks for tagging me.
You're correct about V1 and AI.
I'll definitely keep an eye on that one, but it has a specific reason.

Don't worry about #473 for a while, I had it working some time ago.
Basically those import menu items are in 2 locations and that blows up the PR. Above all it needed methods in the Services and it needed phpunit tests, so it blew up a bit more.

You're correct about this PR, but i'll keep an eye on it.
It's actually the reason why I kept if from the develop branch and I was thinking "too big".
If you want to help with this Peppol thing, just let me know, I could use some help.

I squashed some commits, therefore it looks big, but trust me, I developed it diligently

I can be found on Discord: https://discord.gg/PPzD2hTrXt

@InvoicePlane InvoicePlane deleted a comment from coderabbitai Bot Jun 13, 2026
@InvoicePlane InvoicePlane deleted a comment from coderabbitai Bot Jun 14, 2026
@InvoicePlane InvoicePlane deleted a comment from coderabbitai Bot Jun 14, 2026
@nielsdrost7 nielsdrost7 linked an issue Jun 14, 2026 that may be closed by this pull request
36 tasks
@InvoicePlane InvoicePlane deleted a comment from coderabbitai Bot Jun 14, 2026
@InvoicePlane InvoicePlane deleted a comment from coderabbitai Bot Jun 14, 2026
coderabbitai[bot]

This comment was marked as outdated.

@nielsdrost7 nielsdrost7 changed the title Feature/126 implement peppol [IP-126]: implement peppol Jul 24, 2026
@InvoicePlane InvoicePlane deleted a comment from coderabbitai Bot Jul 24, 2026
@InvoicePlane InvoicePlane deleted a comment from coderabbitai Bot Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Invoices]: Peppol e-invoicing — pluggable multi-provider architecture

2 participants