How to map Accounting data to tax fields
For your Pixie CRM team: Follow the Tax Mappings workflow in Pixie CRM to map accounting data to tax fields.
Before you start
Required access: Manage tax settings. 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 map Accounting data to tax fields
- Review Accounting adapter controls and Available Accounting source catalogues.
- Under Create immutable mapping select Taxpayer profile and Tax regime.
- For VAT choose an Accounting tax code or No-tax transaction category and Tax treatment; check the resulting statutory numeric field.
- For Income Tax choose HMRC business source, Submission scope, Tax year, Accounting account, aggregation treatment and HMRC/statutory numeric field.
- Complete the applicable foreign-property identity and Mapping rule version; choose Create immutable mapping.
- Check Mapping register. Use the available active-state control to retire an obsolete mapping, then prepare and validate a fresh snapshot.
Controls and limits
- Mappings are versioned evidence; changed mappings do not rewrite an existing frozen filing.
- Foreign-property identity fields depend on the selected year and business type. Resolve missing, ambiguous or overlapping mappings before filing.
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.