PHP Ledger 1.3.0

PHP Ledger 1.3.0

This release brings the previously deferred plugin runtime into the actual archive, together with period review and cash counts, an employee register, protected package credentials, fixed assets, recurring drafts, release and loan schedules, aggregate payroll accounting and explicit year-end closing. Posting remains a deliberate authorized action: scheduled jobs create review drafts and never make payments or post transactions automatically.

• Separate expense and receipt entry: dedicated screens use clear payer/payee, cash-account and category labels, with no transaction-type switch inside the form. Existing drafts reopen with their original type; older entry links still reach the matching screen.
• Period and year-end review: close checklists and cash differences, synchronous reversals on period reopening, explicit fiscal-year treatment, reviewed company/partnership allocation, immutable closing and reopening receipts, final-day adjustments and performance comparatives that exclude closing transfers.
• Schedules and payroll: recurring documents, exact prepayment/deferral releases, reviewed loan conventions and revisions, payroll accruals and partial settlements. Payroll is aggregate accounting, not per-person calculation, payslips or statutory filing. Employee assignments are explicit; existing operational labels are preserved rather than inventing employment history.
• Packages and samples: the executable plugin framework, scoped package administration and encrypted package secrets are included. Eleven optional fictional sample histories are separate data-only packages; the core archive retains the neutral starter. Install a sample to choose its structure without transactions or its full practice history during onboarding.
• Installation and hosting: database table namespaces, verified TLS options, MySQL 8.0.19+ support, a checked CLI upgrade entry point, and the same verified release archive underlying both GHCR and Docker Hub images. Existing installations retain their current table namespace.
• A shared installer demo: visitors experience the normal installer and onboarding. Database fields display read-only dummy values; real settings stay on the server. The fixed public application login is shown at sign-in. Everyone shares fictional data until the hourly reset returns the demo to the first installer step.
• Language and privacy: draft Arabic with right-to-left presentation and English fallback joins the existing draft Urdu. Both need native review. New installs offer an anonymous installation notice and a separate, unchecked named-registration choice. Installation administrators can change consent in Updates; demo/test modes never send notices. The receiver stores the latest notice for at most 90 days and no accounting records.
• Permissions: membership uses the existing role-ID capability model throughout; migration 056 retires the legacy role ENUM, retaining its original values as a deprecated text snapshot for compatibility with the 1.2.1 updater. Permissions use role IDs and grants. Owner changes cannot strand a company without an active owner. The fixed public demo identity and executable package controls are protected server-side.

Back up matching files, private configuration and database before upgrading; rehearse on a copy. The new migration sequence through 056 is forward-only. See UPGRADE.md for the ordinary browser updater, manual CLI and container paths. Historical migration files have not been rewritten.

The matching 1.3.0 media kit accompanies this x.y.0 release, including announcement drafts, a guided demo, FAQs and release screenshots: download the media kit. Download the application, checksum and signed update metadata from the 1.3.0 release.

Internal worked examples and technical checks do not establish independent accounting/security certification, native translation review, every managed provider's acceptance or a real-business month-end pilot. Those remain separate assurance work; real-book pilots are recorded for 2.0. Hosting templates are documented starting points, not evidence that each provider has accepted or published them.

Publication is complete: the website, shared installer demo, GitHub Wiki, signed sample directory, and GHCR/Docker Hub images are live. See the publication and verification receipt for artifact hashes, upgrade checks, responsive browser evidence and the two hosting-only corrections.