- What is kch/pcc-3-deklaracja used for?
- It is a PHP library of DTO and domain classes for representing a Polish PCC-3 civil-law transaction tax declaration and serializing it to XML. It is aimed at developers who need to assemble taxpayer, transaction, and declaration fields in a structured way. Despite the Laravel-friendly label, it is framework-agnostic and contains no Laravel service provider, config, facade, or migration.
- Is kch/pcc-3-deklaracja a real Laravel package?
- No, not in the usual Laravel sense. The repository is a framework-agnostic Composer library built around DTO/domain classes and JMS Serializer annotations; there is no service provider, configuration file, facade, or migration. You can use it inside a Laravel app, but you must wire it yourself behind an application service or adapter.
- Does kch/pcc-3-deklaracja support Laravel 10 or Laravel 11?
- There is no official Laravel 10/11 support. The last release was in October 2017, and the code likely targets PHP 5.6/7.x with JMS Serializer 1.x-era annotations. A modern Laravel app on PHP 8.2+ should expect Composer constraint conflicts and annotation-reader deprecations, so plan to fork and upgrade or rebuild the small DTO surface.
- How do I install kch/pcc-3-deklaracja with Composer?
- The nominal command is composer require kch/pcc-3-deklaracja, but installation on a current Laravel stack will usually fail or require unacceptable pinned legacy dependencies. It may install on PHP 7.4 with Laravel 6–8 using pinned constraints, but that anchors you to an unsupported runtime. For production, fork it into an internal repository, update PHP and JMS Serializer constraints, and tag an internal version.
- Does kch/pcc-3-deklaracja calculate PCC tax automatically?
- The package blurb mentions tax calculation, but the technical assessment describes it primarily as DTO/domain classes that describe the declaration and serialize it to XML. You should inspect the source and confirm whether any tax computation is implemented and correct for your case. Treat any tax calculation as something finance or an accounting partner must sign off on before filing.
- Does it validate XML against the official PCC-3 XSD schema?
- No official XSD validation or known test coverage is confirmed. The package provides validation support for taxpayer and transaction details at the data level, but that is not the same as validating the emitted XML against the Ministry of Finance schema. Add golden-file regression tests and XSD validation in your own test suite before relying on its output.
- Is the generated XML ready to submit to e-deklaracje?
- Do not assume so without verification. Because the last release was in 2017, schema drift and changed tax rules are high-risk, and well-formed XML can still be rejected by the portal. Validate output against the current PCC-3 XSD and compare it with the current e-deklaracje specification before any customer-facing use.
- Which PCC declaration types does this package cover?
- It covers the PCC-3 declaration for civil-law transactions only. It does not cover PCC-1, PCC-2, or PCC-3/D, so confirm which variant your product actually needs. If you need multiple variants, you will likely need separate DTOs or a broader internal compliance module.
- Is kch/pcc-3-deklaracja maintained and safe to use?
- It appears abandoned: last release October 2017, one star, no dependents, and no issue traffic. There is no active security or patch posture, so you would permanently own upgrades and schema updates. The MIT license with no CLA or copyleft makes forking into an internal repository legally clean, which is the main mitigating factor.
- Should I fork kch/pcc-3-deklaracja or rebuild PCC-3 DTOs from scratch?
- Fork and harden only if you can upgrade PHP and JMS Serializer, convert annotations to attributes or explicit metadata, and add regression plus XSD tests within roughly two to three engineering days. If that exceeds your budget, rebuild the DTOs directly from the current PCC-3 schema; the domain surface is small enough that a rewrite is competitive. Either way, wrap it behind an internal Pcc3Generator interface so the rest of the Laravel app is insulated.