Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Following a VAT Return submission POST (box 5 non-zero), subsequent Liabilities calls return 404 #904

Open
karolskrobot opened this issue Aug 4, 2022 · 3 comments

Comments

@karolskrobot
Copy link

karolskrobot commented Aug 4, 2022

Describe the bug
Following a successful submission of a VAT Return, which has a box 5 negative or positive value, the subsequent liabilities call after that returns 404 (intermittent).

Not only the immediate call to liabilities endpoint does return 404, but subsequent calls over the spans of days also do.

Example requests:

1. Submission call (POST)
URL: https://api.service.hmrc.gov.uk/organisations/vat/REDACTED/returns
Request body: {"periodKey":"22C2","vatDueSales":5259.47,"vatDueAcquisitions":0.0,"totalVatDue":5259.47,"vatReclaimedCurrPeriod":5646.96,"netVatDue":387.49,"totalValueSalesExVAT":27098,"totalValuePurchasesExVAT":42777,"totalValueGoodsSuppliedExVAT":0,"totalAcquisitionsExVAT":0,"finalised":true}
Request timestamp: 2022-08-02 13:09:23.341653+00
Response body: {"processingDate":"2022-08-02T13:09:23.000Z","formBundleNumber":"REDACTED","paymentIndicator":"BANK"}
Response timestamp: 2022-08-02 13:09:24.590532+00
Response status code: 201.

2. Liabilities call (GET)
URL: https://api.service.hmrc.gov.uk/organisations/vat/REDACTED/liabilities?from=2022-04-01&to=2022-06-30
Request timestamp: 2022-08-02 13:11:00.432338+00
Response body: {"code":"NOT_FOUND","message":"The remote endpoint has indicated that no data can be found"}
Response timestamp: 2022-08-02 13:11:00.844791+00
Response status code: 404.

To Reproduce
Call the API as above.

Expected behavior
Liabilities endpoint returns 200 OK with liability data showing the relevant liability and the amount due for payment / refund.

Screenshots / Requests / Responses
As above.

Additional context
The scale of this problem is quite major, affecting thousands of our customers.

@DDCTLS-DEV-TEAM
Copy link

Good Morning @karolskrobot

Thank you for reaching out.
We are looking into this issue and have reached out to the relevant teams. Could you please forward an email to the SDS team with the information that is redacted in it? (if you haven't done already) This will help out with the investigation.

As for your question about us returning the HTML in the error. That is something we can look into and we will be.

Thank you for flagging this and we are hoping we can get some resolution from the various teams.

@karolskrobot
Copy link
Author

Thanks. I have provided the omitted information to the SDS team. Looking forward to a resolution.

@karolskrobot
Copy link
Author

Can I please have an update?

I understand that in the example I have given above, 404 response may be expected behaviour. As the SDS team explained to me, the liability can get updated with a delay (by the following working day morning).

We have however examples where the liabilities endpoint keeps returning 404, example provided to the SDS team:

URL: https://api.service.hmrc.gov.uk/organisations/vat/REDACTED/liabilities?from=2022-03-01&to=2022-05-31
Request timestamp: 2022-06-28 15:54:06.591304+00

URL: https://api.service.hmrc.gov.uk/organisations/vat/REDACTED/liabilities?from=2022-03-01&to=2022-05-31
Request timestamp: 2022-06-28 15:54:19.316016+00

URL: https://api.service.hmrc.gov.uk/organisations/vat/REDACTED/liabilities?from=2022-03-01&to=2022-05-31
Request timestamp: 2022-07-05 10:55:25.551345+00

URL: https://api.service.hmrc.gov.uk/organisations/vat/REDACTED/liabilities?from=2022-03-01&to=2022-05-31
Request timestamp: 2022-07-06 14:19:54.097009+00

and 4 more calls with the same response up until 2022-08-04 19:56:51.94707+00

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants