Concordato Preventivo Biennale: What Should an App Track?
A tax-deadline app should make the filing decision easier to manage—not decide eligibility. Here is a practical scope for dates, documents, reminders and reliable sources.
Italian coverage is drawing attention to the Concordato Preventivo Biennale (CPB) for 2026–2027 and a reported upcoming adherence deadline. ANSA’s 6 October headline says adherence is due by 2 November; MySolution also lists a guide to the 2026–2027 arrangement. Those signals establish a timely product question, not a substitute for checking current official guidance or a taxpayer’s circumstances. A hypothetical tax-support app could help users organise dates, documents and questions for a qualified adviser. Its job would be to make a time-bound decision visible and manageable—not to determine eligibility, calculate a tax position or imply that a reminder is legal advice.
Make dates visible, qualified and traceable
A deadline screen should distinguish a reported date from a verified, applicable filing date. ANSA’s headline reports 2 November for adherence, but an app should not present a news headline as the final authority for every user. Show the date, the event it refers to, the jurisdiction or tax year if confirmed, when the information was checked, and a direct link to the relevant official guidance. Where the date or applicability has not been verified, label it clearly as unconfirmed and prompt the user to consult an accountant or official source. This provenance is a core product requirement: users need to know not only what the app displays, but why.
The reminder model should handle more than one alarm. Let users choose advance notices, a due-date reminder and a follow-up task, while stating that alerts depend on notification permissions and device connectivity. Store the date as a calendar date in the relevant jurisdiction, rather than letting time-zone conversion shift the apparent day. If authoritative information changes, preserve the previous date and record when the app updated it; notify affected users without silently replacing a date they may have already acted on. A user should be able to dismiss or snooze a reminder, see the next action, and open the supporting source from the notification or task.
- For each date, record its meaning, source URL, verification timestamp, applicability note and update history.
- Offer configurable reminders and a clear fallback: check the source or contact a qualified adviser.
Track decision readiness without making the decision
Eligibility notes should be a structured checklist of questions and evidence, not a green light. A user might record that they have reviewed an official eligibility source, asked an adviser about a specific condition, or still need to confirm a detail. The app can show statuses such as “not started,” “awaiting adviser” and “document attached,” but should avoid asserting that a person qualifies based on a short questionnaire. Rules can depend on facts the app does not hold, and the supplied trend signal does not specify the eligibility criteria. Each note should therefore carry its source and date, and the interface should make the boundary between general information and professional advice easy to understand.
For documents, start with a user-controlled inventory rather than an expansive request to upload sensitive tax records. Let people mark an item as needed, collected, shared with an adviser or not applicable, and add a private note about where it is stored. If uploads are part of the product, define access controls, encryption, retention and deletion before adding the feature; a checklist can be useful without centralising documents. A decision log can capture the user’s selected next step, outstanding questions and the date they intend to discuss them. Keep it factual and editable, and make clear that recording a decision in the app does not submit a filing or establish compliance.
- Use user-confirmed readiness statuses; do not convert incomplete answers into an eligibility result.
- Make document upload optional, with explicit retention and deletion controls if implemented.
Scope a safe, useful first release
A focused MVP can deliver value with four capabilities: a source-linked deadline card, a short document and question checklist, configurable reminders, and an update history. Before building, identify who maintains the date and source links, how updates are reviewed, and what happens when an official page is unavailable or unclear. Define those operating responsibilities alongside the screen designs: stale information is a product risk, not merely a content inconvenience. Test the app with scenarios such as a date revision, a user who has not confirmed applicability, a disabled notification permission, and a reminder opened after its source has changed. Verify that every path leads to a clear next step rather than a confident but unsupported answer.
Keep the first release out of automated tax interpretation unless the team has a separate, well-governed basis for offering it. Do not infer eligibility from uploaded files, generate a filing position, or imply that completing the checklist means a user has adhered. Measure product quality through operational checks such as source-link availability, successful reminder scheduling and timely review of date changes; these are service indicators, not promises of filing outcomes. If advisers are involved, define what information is shared, with whose consent, and who is responsible for responding. This boundary makes the app easier to scope, safer to explain and more credible to users facing a deadline.
- MVP acceptance check: a user can identify the date’s source, see its verification status, organise open tasks and reach qualified help.
- Assign an owner and review process for source changes before launch.
A useful CPB deadline app would make dates, supporting sources, open questions and document readiness visible in one place. It would not tell a user whether they qualify or replace official guidance and professional advice. Treat the 2 November date reported by ANSA as a prompt to verify the applicable deadline, not as a universal in-app conclusion. For product leaders, the practical scope is a traceable calendar and checklist workflow, with clear update ownership and careful handling of sensitive records. Build trust into the information model before adding automation.