Release news ยท
PHP Ledger 1.3.0: from the installer to a reviewed year end
PHP Ledger 1.3.0 connects reviewed payroll, schedules and year-end workflows to its existing invoices, bills, stock and reports, and lets you try the actual installer before setting up your own hosting.
Walk through setup, then follow a transaction
The public demo uses the real installer and business onboarding in one shared disposable installation. The database step displays labelled dummy values; the real host settings stay protected. If another visitor has already finished setup, use the fixed public login displayed on the sign-in page.
Everyone shares fictional records until the hourly reset removes the database contents and PHP sessions. Use made-up information only. Start with a receipt or expense, review its posting and follow the amount into an account statement and trial balance.
Expense and receipt entry have separate screens: record who you paid and the expense category, or who paid you and the income category. The form stays with that task, and saved drafts keep their original type.
Review obligations and the close in the same books
Aggregate payroll accounting records reviewed accruals, staff advances and partial settlements. The confidential employee register links explicitly to sales-staff and driver identities while preserving historical labels. Employment does not automatically make someone a related party.
Recurring entries, accrual releases and loan schedules create ordinary drafts for review. Loan conventions are displayed so the operator can check dates, principal and interest against the actual agreement. Scheduled jobs do not make payments or post transactions automatically.
Cash counts and period-close checklists support the review before closing. Fiscal year end requires an explicit legal treatment, destination accounts and any reviewed partnership ratios. Close, roll-forward and reopen remain traceable, and closing transfers do not erase performance-report comparatives.
Choose the sample data you need
The core keeps its neutral starter. Eleven optional multi-year histories are separate CC0 data-only packages. Open Packages, explicitly refresh the directory and review a sample before installing it. Onboarding can use its structure with zero balances for a real business, or its complete fictional history in a separate practice company.
Package manifests, payload hashes and requirements are checked. A sample never silently installs an executable dependency. The shared demo uses verified, read-only host preloads. Removing a source package leaves previously created companies and journals intact. Browse the sample directory.
Run the same release on your own hosting
Use the packaged browser installer on PHP 8.2+ with the documented extensions and MySQL 8.0.19+ (8.4 recommended) or MariaDB 10.4+. Installation-specific table prefixes and explicit database TLS help operators configure compatible hosting. Arabic and Urdu are draft translations; native language and accounting review remain pending.
The official image channels are ghcr.io/phpledger/phpledger and phpledger/phpledger on Docker Hub. Both package the same verified application ZIP. Use the published release record for available tags, digests and completed verification, then follow the container guide.
New installations offer an optional anonymous technical installation notice and a separate, unchecked named-registration choice. Existing installations stay silent until an administrator chooses. Disabling notices does not restrict the software; demo and test modes do not send them. Read the privacy notice for fields, controls and retention.
Keep the limits in view
Payroll here is aggregate accounting, not per-person pay runs, payslips or statutory filing. A loan schedule does not certify agreement with a lender contract. Industry-themed samples are teaching data, not complete industry systems or regional compliance packages.
Independent accounting and security review, native translation review, managed-provider acceptance and supervised real-business use remain separate gates. The published release notes and verification receipt identify the evidence for the actual artifact.
Download, rehearse and contribute
Get the application ZIP, checksum and signed update metadata from the 1.3.0 release. Back up matching files, private configuration and database before upgrading, and rehearse the documented path on a restored copy.
The matching 1.3.0 media kit includes announcement drafts, a guided tour, FAQs and release screenshots with captions and alt text. Use its manifest and the publication receipt for exact artifact provenance.
Try a workflow, improve a guide, offer native language review or share a reproducible fictional example. Support the project through testing, documentation and reviewed contributions.