liberusoftware / module-accounting-year-end-filament

1.0.0 2026-11-02 16:43 UTC

Requires

• php: ^8.5
• filament/filament: ^5.11.0
• liberusoftware/module-accounting-year-end: ^1.0

MIT

Published on Packagist.org on 2026-11-02 16:45 UTC

README

Filament presentation package for Year End. The root Composer manifest declares liberusoftware/module-accounting-year-end-filament. Review its source and tests for implemented behavior, supported contracts and current release compatibility; the capability plan describes the intended scope.

Develop locally

Use the PHP requirement in composer.json and a compatible Laravel/Filament host. From a clone of this package:

composer install
composer validate
composer run-script --list

The consuming application selects a reviewed package version and registers its public Filament plugin/resources through its existing panel composition. Inspect the package's actual src entry points; do not infer class names or install identities from the repository slug. Follow the Composer module lifecycle for the approved installer and module placement.

Installation, enablement, entitlements and authorization are separate. Keep tenant context, policies, validation, transactions and records in the canonical domain owner; presentation code calls reviewed public actions/queries. Verify allowed, denied and wrong-tenant behavior when changing protected workflows.

Presentation architecture and project hosts

• Capability/source key: liberusoftware/module-accounting-year-end.
• Actual Composer identity: liberusoftware/module-accounting-year-end-filament.
• Filament capability plan · Filament standard · Module architecture.

The application owns panel composition, routing, session integration and deployment. This module owns its focused presentation and delegates domain behavior to reviewed public owner contracts. Keep host App aliases, duplicate records and client-only authorization outside reusable package boundaries.

Documented consumer project families:

• Accounting ERP: Ledgers, tax, reporting and finance workflows.

Other web, mobile and desktop presentations are listed in the project catalog. Those skeletons provide starting structures; links do not establish feature parity, compatible releases or completed device/API integrations. Independent presentation packages keep their own Composer, npm or pub metadata.