Day 44 – Making Tax Digital

 

17th July 

Our demo to HMRC has been completed successfully. We are now in a position to apply for our production credentials required to submit live VAT returns as part of the controlled go live pilot.

A separate application to be admitted to the pilot will be made once we have the production credentials.

The VAT registration numbers (VRN’s) of all test clients taking part in the pilot will be checked by HMRC for eligibility in the pilot scheme.

At least two successful submissions to HMRC need to be accepted. These are planned for the next week on a pre-agreed submission date with HMRC.

Day 40 – Making Tax Digital

13th July 

Development completed!!!

We are now coordinating with HMRC to arrange a date to demo the functionality we have built, once we have approval from HMRC we will be able to submit our first tax return as a part of our pilot, before rolling out to our entire client base.

We set out to complete this project over a 40 day period, and although we still have a couple of ticks in the boxes outstanding the hard work has been done. Stay tuned for our updates once HMRC have verified the development.

 

10th July 

Development of our making tax digital compatible VAT module is all but complete and we are nearly ready to submit our first VAT return as part of the pilot.

 

Next steps are:

  1. Verify our test client’s VAT submissions are eligible for the pilot
  2. Provide A demonstration of our product to HMRC in the sandbox environment
  3. Make an application to HMRC for live credentials
  4. Submit VAT return as part of the pilot

 

Our development is on schedule to be finished within our initial target time period. As long as the above steps with HMRC are completed in good time, we will be have completed our goal close to our target.

Day 32 – Making Tax Digital

5th July

We have successfully integrated HMRC OAuth2 verification with MDA!!

So the HMRC API’s currently integrated into MDA are as follows:

Re-generate Access Token using Refresh Token

Retrieve VAT obligations

Retrieve VAT liabilities

Retrieve VAT payments

 

So we’re now in the final stretch and are working on integrating the “Submitting a VAT return for a period” API into the system

 

Day 29 – Making Tax Digital

2nd July 2018
Since our last post we have successfully received the test “hello world” response from HMRC through our application and moved onto integrating the APIs within MDA.

MTD (Making Tax Digital) is now configurable at the company level in our testing environment and MTD VAT enabled companies can create test users via the MTD API. Once test users are created for MTD, enabled companies will automatically switch to the new VAT submission flow.

We have also successfully integrated HMRC OAuth2 verification and used the Access code received to get an Access Token.

Summary of HMRC APIs integrated into MDA:
1. Create test User
2. Authorisation Code
3. Get Access Token
We are now in the process of retrieving a New Access Token using the “Refresh Token” process .

Day 22 – Making Tax Digital

25th June 2018
We have completed the first draft of our screen designs for MTD – Click through the links below
Decision still needs to be made to which period we will get obligations for, financial year is preferred over tax year but API range is restricted to only 12 months.
New liabilities and payment screens will allow agents access to payment information that was previously unavailable
Direct Debit marker will give the user an indication if HMRC plan to take by DD

Get obligations screen
View liabilities screen
View payments screen
Submitted VAT return screen
Submit VAT return screen

Day 17 – Making Tax Digital

20th June 2018
We have now successfully tested all HMRC API’s
We are using HMRC’s generated test data which is working well
We are now progressing with our own database design to accommodate the new workflow
For those going through the same process, our more detailed summary can be seen below

Types of API endpoints in MTD:

  1. unrestricted endpoint
  2. application-restricted
  3. user-restricted

Application-restricted endpoint follows OAuth protocol to do two step verification, from that you can retrieve an access_token (expired in 4 hours) to access the API.

Step 1: Request authorisation (GET)

Step 2: (POST) Receive authorisation results from redirection UR & get authorisation code then request for access_token

Day 12 – Making Tax Digital

15th June 2018
We have successfully hit 3 of the 5 API’s “Obligations”, “Liabilities” and “Payments”.
We have used the two factor authentication flow requiring access token.
Redirection of the client to a URL embedded into our application is necessary to authorise. This will be built into our workflow when creating screen designs.
Using the Auth code we can get the access token to the API’s
We are now working on the “View return” and “Submit return” API’s

Day 9 – Making Tax Digital

12th June 2018
After analysing the API’s it is clear that our current VAT workflow would not be appropriate.
We are in the process or redesigning the workflow and user interface. Wireframe designs are being put together by our user experience team.
Which workflow the user follows will be configurable in the limited company’s settings.
Each workflow will have a different menu item. Only one menu item
Each of the API’s are being tested for a positive response in isolation, in parallel with this work.

Day 4 – Making Tax Digital

7th June 2018
We are now happy with the MTD API’s and each of their functions.
We are now working on how we can incorporate each of the API’s into a workflow.
We will create the screen designs based on our intended workflow
Consideration must be given to how we manage dual processes at the same time in the same environment (XML flow and MTD API flow)
Configuration at company level is unavoidable