Weave Code
Vat Bundle Laravel Package
ibericode/vat-bundle
Symfony bundle wrapping the ibericode/vat library to validate EU VAT numbers against the official VIES service. Check VAT IDs, retrieve registered company details, and add reliable, framework-friendly VAT validation to any Symfony application. Supports all EU member states.
Symfony bundle for ibericode/vat
Frequently asked questions about Vat Bundle
- Can I use ibericode/vat-bundle in a Laravel application?
- No. ibericode/vat-bundle is a Symfony bundle that registers through Kernel::registerBundles() and Symfony's DependencyInjection extension and Configuration tree, which Laravel does not provide. In a Laravel app its practical value is close to zero as packaged. Install the underlying ibericode/vat library directly and wrap it in your own service provider instead.
- What is the difference between ibericode/vat-bundle and ibericode/vat?
- The bundle is a thin Symfony integration layer that wires the framework-agnostic ibericode/vat library into Symfony's service container. The library contains the actual VIES VAT number validation and VAT rate lookup logic and works in any PHP application, including Laravel. For Laravel, adopt the library and ignore the bundle.
- How do I install EU VAT validation in Laravel without the Symfony bundle?
- Require ibericode/vat with Composer and bind it behind an application-owned interface such as VatValidator or VatRateProvider in a dedicated service provider. Keep thresholds, cache TTLs, timeouts, and an offline-mode feature flag in config/vat.php. This keeps the vendor library out of controllers and models and is roughly a day of engineering.
- Does ibericode/vat-bundle support Laravel 10 or Laravel 11?
- The bundle targets Symfony and does not provide a Laravel service provider, so Laravel version support is not applicable. The underlying ibericode/vat library is framework-agnostic PHP; check its PHP constraint against your floor rather than looking for a Laravel version matrix. Laravel 10 and 11 projects can consume the library if the PHP requirement is met.
- How does VIES validation work and what happens if VIES is down?
- The library validates EU VAT numbers through the official VIES service, combining per-member-state format rules with a remote lookup. VIES uptime, per-country outages, and throughput limits belong to the EU, so a design that assumes a definitive synchronous answer is fragile. Put timeouts and a feature flag for offline or deferred validation in config, and decide your checkout tolerance for VIES downtime up front.
- Can I retrieve registered company details for a VAT number?
- Yes, VIES lookups can return registered company details alongside the validity result when the member state provides them. The bundle exposes this through Symfony's container; in Laravel you would call the same underlying library methods through your own wrapper. Treat the returned data as evidence to store if you issue reverse-charge invoices.
- Do I need to store VIES consultation evidence for reverse-charge invoices?
- That is a tax and compliance question, not a library feature. Many businesses keep the VIES consultation number, timestamp, and request and response as evidence for cross-border supplies. Confirm your obligation with whoever signs off on tax logic, and design your wrapper so the raw consultation details can be persisted.
- Is ibericode/vat-bundle actively maintained and safe for production?
- Community signal is thin: around 20 stars and zero dependents means little third-party validation and a single-maintainer bus factor. The maintainer is credible and active, and a 2026 release date indicates maintenance, but the current tag has limited production exposure. You are effectively the QA function, so pin versions, add tests, and own the edge cases.
- What are the alternatives to ibericode/vat-bundle for Laravel VAT validation?
- The primary alternative is using ibericode/vat directly with a small Laravel wrapper, which is the recommended path. You could also call VIES or a commercial VAT validation API yourself, or use another EU VAT package, but you would still own caching, timeouts, and evidence storage. Skipping the Symfony bundle avoids shimming Symfony's DI extension system into Laravel.
- Does the library handle VAT rate changes and reverse charge rules?
- VAT rate lookup is largely local data shipped with the library and refreshed on releases, so statutory changes between releases are a compliance gap you own. Domain complexity exceeds code complexity: reverse charge, place of supply, B2B versus B2C, and evidence retention are tax questions the library does not answer. Decide whether validation, rate lookup, or both are in scope before adopting it.
Weaver
How can I help you explore Laravel packages today?