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

Obligation period beyond 366 days #874

Closed
Senthil-9111 opened this issue Oct 8, 2021 · 1 comment
Closed

Obligation period beyond 366 days #874

Senthil-9111 opened this issue Oct 8, 2021 · 1 comment

Comments

@Senthil-9111
Copy link

Senthil-9111 commented Oct 8, 2021

Support request

Dear Team

How would the following scenario be handled? a return to be submitted for a period beyond 366 days.
the recommendation is to query the obligation period before submission of the return and use the period key.
In this case the date range is beyond 366 days and the API call returns an error. This does not allow the submission of the return.

@hmrc-api-team
Copy link

Hi Senthil-9111,

We would expect that any obligation "end" date that falls within the queried date range to be returned.
So if you did have a VAT obligation spanning 366+ days, any date range that includes the obligation end date should return the obligation details, and periodKey.

So the following obligation could be queried with /obligations?from=2021-07-01&to=2021-07-31
{
"start": "2020-04-06",
"end": "2021-07-05",
"due": "2021-10-07",
"status": "O",
"periodKey": "18AE"
}

You can also query for “open” obligations without providing a date range.

Kind regards,

MTD API Team

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