Filament Money Field Laravel Package

Product Decisions This Supports

• Money/currency input on Filament admin panels. Any roadmap item involving prices, invoices, budgets, payouts, or multi-currency catalogs gets a ready-made form component instead of a custom-built masked input — this is a "buy/reuse" lever for admin-surface features rather than customer-facing UI.
• Filament major-version upgrade planning. This release is the compatibility signal: Filament v4 support is now real (with a fix for the currency-switch error that made v4 unusable for multi-currency forms), and v5 installation is unblocked at the dependency level. That directly gates whether an admin-panel v4/v5 migration can proceed without losing money-field functionality.
• Build vs buy for the 2.0 line. The 2.0 rewrite plus two rounds of compatibility work in one release cycle is evidence of a maintained package tracking upstream Filament releases. That supports "adopt" over "fork and own a bespoke field" — but only for teams already committed to Filament.
• Scope decisions on financial admin tooling. Use cases it unlocks cheaply: currency-aware price entry with per-locale formatting, index/table display of monetary values, editable amounts across currencies. If those are on the roadmap, this package collapses a scoping conversation into an integration task.
• Risk register entry, not a green light. This is still a beta (2.0.0-beta.4). v5 support appears to be a Composer constraint widening ("allow installation"), not verified runtime support. Do not let it justify putting Filament v5 in a delivery commitment.

When to Consider This Package

Adopt when:

• You are on Filament v4 (or planning it) and need money/currency fields — this release is aimed squarely at that, including the multi-currency editing fix.
• Your admin layer is already Filament; the integration cost is a field class, not a subsystem.
• You need multiple currencies in one form and want the currency-switching behavior handled rather than hand-rolled.
• You can tolerate a beta dependency in internal/admin surfaces, where a defect degrades back-office data entry rather than checkout.

Look elsewhere or wait when:

• You need Filament v5 in production — treat "allow installation" as untested. Pin it, spike it, and expect follow-up fixes; the pattern in this changelog (v4 support shipped, then a currency-switch fix in the next release) is a good predictor of what v5 will look like.
• Your money handling must be auditable and stable — a 2.0 major with an active beta stream means breaking changes and field-behavior fixes are still landing. For regulated or ledger-facing flows, budget for wrapping it rather than exposing it directly.
• You are not on Filament. This is a Filament field, not a general Laravel money library; the value is entirely in the form-builder integration.
• You need server-side money semantics (rounding policy, currency conversion, tax). This is presentation/input; don't expect it to be your money model.

How to Pitch It (Stakeholders)

To executives: This is a small, well-scoped open-source component that gives our Filament admin panel correct multi-currency amount inputs without custom development. The new beta adds the compatibility work needed for Filament v4 and opens the door to v5, which de-risks our admin-panel upgrade path. Cost is negligible; the main caveat is that it's a beta, so we use it for internal tools and hold it out of anything customer-facing or financially regulated until it stabilizes.

To engineering: Adopt on Filament v4 — 2.0.0-beta.4 adds v4 support and fixes the currency-change bug from beta.3, so multi-currency editing is now viable. Filament v5 is only permitted at the Composer level, not validated; treat it as a spike, not a supported target. This is a 2.0 major, so budget a migration pass from 1.x and pin the beta version explicitly. Keep money math and rounding in our domain layer — use this for input and display only.