# Financial settings runtime audit
This audit checks `config/financial-settings.php` against runtime consumers in the company admin, public booking, payment, invoice, refund, pricing, fiscal, and notification code.
## Currently applied
- Company-scoped deposit settings and deposit requirement during public booking creation and deposit payment.
- Company-scoped VAT rate, tax-inclusive pricing, category tax rates, and tax display through `BookingPaymentService`.
- Company-scoped refund policy, refund window, and cancellation fee through `BookingPaymentService`.
- Company-scoped configuration storage and typed controls in the non-Filament company admin.
- Company-scoped settings page and the existing financial controls in the Filament admin.
- Subscription payment configuration remains governed by the B2B billing/myPOS service rather than the legacy booking gateway settings.
## Settings requiring runtime integration
The following values are currently editable and stored but are not consistently consumed by algorithms:
- Payment gateway mode and webhook secret.
- Detailed refund policy windows, partial-refund switch, processing days, and policy descriptions.
- Dynamic pricing peak hours, weekend/holiday/seasonal factors, and early-bird/last-minute rules.
- Multi-currency conversion, allowed currencies, exchange-rate provider, formatting, and update frequency.
- Security-deposit type, percentage, automatic refund, and separate hold behavior.
- Invoice numbering, due dates, automatic delivery, invoice language, QR code, and late-payment fee rules.
- Minimum/maximum booking amounts, rounding, group/long-stay/loyalty pricing rules.
- Payment-method availability, default method, receipt requirements, card rules, and bank-transfer details.
- Fiscal reporting settings and payment-reminder notification settings.
These settings must not be presented as fully enforced until each has a runtime consumer and a feature test. The next implementation pass should add a single company-scoped financial policy service and route all public booking, company-admin booking, Filament booking, payment, refund, invoice, fiscal, and notification decisions through it.
## Verification command
The current audit can be repeated by extracting leaf keys from `config/financial-settings.php` and searching `app/`, `routes/`, and `resources/` for each key. Direct calls to `config('financial-settings')` should be reviewed manually because they can hide individual key usage.