How to complete year-end checks and a final declaration
For your Pixie CRM team: Follow the Income Tax → year-end readiness → Annual final declaration workflow in Pixie CRM to complete year-end checks and a final declaration.
Before you start
Required access: Prepare, review, approval and submit capabilities as applicable. The module must be enabled and its installed version ready for your workspace. Select the intended taxpayer, authority and period before changing a record.
How to complete year-end checks and a final declaration
- Load the taxpayer’s Tax year in year-end readiness.
- Review each business and supplementary item. For accepted workspace evidence enter a Completion review note and choose Confirm complete from accepted Britixo evidence.
- Where applicable select Not required or Blocked / unresolved and record the reason. For an approved external route enter its evidence/reference and update the readiness item.
- Return to Income Tax and request the correct intent-to-finalise calculation; review and acknowledge the full Assist report when required.
- Under Annual final declaration select Final declaration or Confirm amendment, choose authority and confirm completion of the required business and Self Assessment information.
- Prepare the exact snapshot, review and approve it, then submit only after the declaration and filing gates pass.
Controls and limits
- A checklist tick is not a substitute for accepted source evidence or a statutory declaration.
- An amendment must use its own current calculation, snapshot and authority; older approvals cannot authorise changed data.
Check the result
Reopen the affected record and confirm the taxpayer, period, saved values and status. For external actions, inspect the actual authority acknowledgement or settlement evidence; a local saved or queued state is not acceptance.
If you cannot continue
Read the displayed validation or readiness message. Check the module version, role, source scope, authority, period and current approval evidence. If another person changed the record, refresh and review the current version. Give support the screen, error wording and correlation reference; keep passwords, one-time codes and tax identifiers out of public messages.