Skip to Content

Making tax easier - a Government consultation on changes to the way you deal with Inland Revenue

Inland Revenue still designs in a paper environment rather than for the electronic environment (issue 2/3)

Inland Revenue still requires information to be delivered in a format designed around paper forms, rather than the electronic environment.

See current state

Inland Revenue’s systems were designed around the processing of paper forms, and the ability to process electronic data has been “bolted on”.
This means that the requirements for electronic data are largely the same as those that apply to paper forms.
This means software developers have to design systems which largely replicate the ATA outputs paper forms would create.
 

View current example

Whilom Software Limited builds accounting software for small businesses.
The PAYE process is based on two paper returns (IR348 and IR345) rather than a single filing and paying process.
The businesses that use the software pay their employees weekly or fortnightly, but Inland Revenue requires the returns monthly, because that’s the way the paper form was designed.
 

What is being proposed

Specifications will be provided to software developers allowing information to be provided in a generic form.

See proposal

Inland Revenue’s specifications for information will be changed so that the information can be provided to suit customers’ business cycles and pay frequencies.
This will allow software developers to design software in a way that puts users’ needs first.
 

View future example

Whilom Software Limited builds payroll software that sends PAYE information directly to Inland Revenue each pay-day.
Clients who use this software no longer need to complete a separate employer monthly schedule (IR348) and employer deductions form (IR345).
 

Do you agree?

Join the discussion on this issue

Back to top