Money Bundle Laravel Package

Product Decisions This Supports

• Currency-correct money handling in Symfony applications: pricing, cart/checkout totals, invoicing, refunds, payouts, tax lines, multi-currency catalogs, and reporting where mixed-currency or float arithmetic would produce wrong numbers.
• Build vs. buy: the package splits into two decisions. The durable asset is moneyphp/money (Fowler Money pattern, widely used). The bundle itself is only integration glue — DI configuration, Twig filters, form types, validators, Doctrine mapping. Buy the glue or write it; do not treat the bundle as a strategic dependency.
• Scope reduction on a roadmap: if the team is on Symfony and already needs formatted currency output, validated currency input on forms/APIs, and persistence of monetary values, this removes roughly a sprint of plumbing from the backlog.
• Risk reduction as a feature: the primary product value is eliminating a class of defects (rounding drift, accidental cross-currency arithmetic, integer/minor-unit confusion) that surface as billing incidents and customer-trust problems rather than as bug tickets.
• Not a Laravel answer. This is a Symfony bundle; bundles do not load in Laravel. If the roadmap item is "money handling in a Laravel product," the decision this package informs is which underlying library (moneyphp/money or brick/money), plus a thin service provider — not adoption of this bundle.

When to Consider This Package

Consider it when:

• The application is Symfony (verify the supported Symfony/PHP matrix yourself before committing) and uses or will use moneyphp/money.
• You want Twig filters, form types, validators, and Doctrine types wired up rather than hand-rolled, and the team is small enough that saved glue code is worth a dependency.
• You are comfortable with the risk profile: ~196 stars, 0 known dependents, single-maintainer concentration, MIT license. Note the listed release date (2026-10-12) is in the future — treat release provenance and maintenance cadence as an open verification item, not a given.
• Exit cost is acceptable: the bundle is a wrapper, so business logic written against the underlying library's API survives removal.

Look elsewhere when:

• You are on Laravel or any non-Symfony framework. Use moneyphp/money directly behind a service provider, or evaluate brick/money for higher-precision/decimal use cases.
• You only need arithmetic and value objects. moneyphp/money alone covers it; the bundle adds surface area for little return.
• You require high-adoption, actively maintained infrastructure. 0 dependents is a weak adoption signal — check commit recency, open issues, and test coverage before betting on it.
• You need advanced rounding, allocation, cash rounding, or crypto-scale precision. Compare brick/money first.
• Your app lacks the bundle's touchpoints (DI container configuration, Twig, Doctrine, Symfony Forms). Without those, the bundle's value collapses to near zero and you should depend on the library directly.

How to Pitch It (Stakeholders)

For executives: A small, MIT-licensed integration layer that makes currency handling correct by default, cutting a known category of billing and rounding defects. Cost is near zero and the exit cost is low, because the real dependency is a widely used open-source money library and this package is only the wiring. The caveat: low adoption (196 stars, no known dependents) and single-maintainer risk, so treat it as a convenience wrapper rather than platform strategy. Fund a short validation spike, not a migration.

For engineering: Symfony-only — do not assume Laravel compatibility, despite how it may be filed. Underneath is moneyphp/money; keep domain logic against that API so the bundle stays replaceable. The bundle contributes DI configuration, a Twig extension, a form type, a validator, and a Doctrine type. Before adoption: confirm Symfony/PHP version support, verify the release history (the published date is future-dated), check open issues and test coverage, and be prepared to vendor or fork. Estimate one to two days to validate; the documented fallback is roughly 100–200 lines of in-house glue over the same library.