You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: