Inheritance Tax - IHT400 iForm

This page and video demonstrates an IHT400 & accompanying schedule digital service proof of concept.  It is created using the iforms project standards and GDS design manual guidelines demonstrating how seamlessly the main IHT400 service and separate schedules can be digitally completed.

The existing IHT-400 consists of a number of logically distinct forms. Everybody (the executor or their agent) needs to fill in the details in the IHT-400. Then, depending on the deceased’s circumstances, a set of the schedules must be completed. For example, if the deceased had any listed stocks and shares, the IHT-411 schedule must be completed.

The proof of concept is structured so that the executor must fill in the IHT-400 sections first. They are then presented with a set of questions to determine which of the separate schedules also need to be filled in. Having completed these questions, they are taken to a check list page listing all of the IHT400 sections and schedule sections they need to fill in. Each section listed has a short description of its state (not completed/completed) and a link to take the executor to the questions for the section. Once all sections are complete, the executor can submit the form.

The form adheres to the Goverment Design Manual and iform standards.

The form is implemented using a a feature of AEM Forms called “lazy loading” which works in conjunction with Adaptive Form fragments to provide a good user experience in spite of the quantity of information required.

Each section of the form was designed as a separate adaptive form, using the HMRC component list. Once completed, the sections were converted into adaptive form fragments, incorporated into the umbrella form and set to “load lazily”. In addition to the form development, the page manager in the HMRC template was modified to support the more complex than normal navigation of the IHT-400.

When rendered for completion, the lazy fragments are not loaded with the umbrella form until the user needs to see them. More importantly, once the fragments are hidden again, they are unloaded to keep the resource footprint of the browser as low as possible. This means that, although the form is large (around 100 pages), resource usage on the client is always kept to manageable levels, at the expense of more calls to the server.

All of the above means that the form can be treated as a normal HMRC form and will fit into the existing framework and work practices with only minor modifications.

Learn More

To find out more, call us on 0845 226 3351, click on the Contact Us button.

Contact Us

Top