Giter Site home page Giter Site logo

vat-api's Introduction

vat-api

vat-api has five endpoints:

  • GET obligations
  • POST returns
  • GET returns
  • GET payments
  • GET liabilities

Prerequisites

Development Setup

Run from the console using: sbt "~run 9675"

Highlighted SBT Tasks

Task Description Command
test Runs the standard unit tests $ sbt test
func:test Runs the functional tests $ sbt func/test
dependencyCheck Runs dependency-check against the current project. It aggregates dependencies and generates a report $ sbt dependencyCheck
dependencyUpdates Shows a list of project dependencies that can be updated $ sbt dependencyUpdates
dependencyUpdatesReport Writes a list of project dependencies to a file $ sbt dependencyUpdatesReport

Reporting Issues

You can create a GitHub issue here.

License

This code is open source software licensed under the Apache 2.0 License

vat-api's People

Contributors

abutters avatar ahlee0 avatar betadraconis avatar dabd avatar daniel-andrews1123 avatar david-walters-hmrc avatar derickdamoah avatar hicnar avatar jacobbrownlow avatar james-work-account avatar jeremystone avatar jonathanleather avatar ma3574 avatar macgrewal avatar markakelly avatar meliadavies avatar narendravijayarao avatar nboaram avatar nganganjiraini avatar peckover avatar rachgibbons avatar rajanimohan22 avatar rakeshavasarala avatar rgladwell avatar scott-goodwin avatar sudoku007 avatar thepworth95 avatar westwater avatar wp94 avatar yangwong9664 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

vat-api's Issues

Error where MTD user attempts to submit via gateway

I am creating user stories covering users who are taking part in the MTD for VAT beta and have a couple of scenarios where I need to know the errors that will be returned from HMRC.

1 - User of accounting software has been accepted onto the beta
2 - The user submits a VAT return via the new API and is accepted by HMRC
3 – User remains on the BETA but attempts to submit the next VAT return via the previous system (Government Gateway)
4 – What error will be returned by the government gateway ?

Zero value submission error

We are in the final testing stages of our product,.
We are testing a zero value submission, ie all 9 boxes are zero.
When submitting this, we get an INTERNAL_SERVER_ERROR.

Data we submit:-
{"periodKey":"#1","vatDueSales":"0.00","vatDueAcquisitions":"0.00","totalVatDue":"0.00","vatReclaimedCurrPeriod":"0.00","netVatDue":"0.00","totalValueSalesExVAT":"0","totalValuePurchasesExVAT":"0","totalValueGoodsSuppliedExVAT":"0","totalAcquisitionsExVAT":"0","finalised":true}

So, is this a valid submit?
If not, should there not be a more fitting response returned rather than an INTERNAL_SERVER_ERROR?

Internal Server Error 500 On Submit - A note for everyone

I've been experiencing internal server errors recently whilst trying to submit vat returns.
These vat returns have worked before but now they don't.
But, I have found out why -
If you need to obtain a new test user account, you will be given a new vat registration number at the same time. You must use this new vat registration number at all times, any other vat reg number will result in a Internal Server Error.
So maybe the devs need to catch this and return a more meaningful error.

Hope this helps
Simon

X-CorrelationId

What is the expected usage of the X-CorrelationId on the methods in this api?

return - finalised: false

Could I get an understanding of the use case for submitting not finalised?

How would the benefit to the user be, is it to run some sort of validation check?

AAS balancing payments

Will the new API support AAS (annual accounting scheme) balancing payments, currently supported in the existing XML API in the <vat:AASBalancingPayment> element?

INVALID_DATE_RANGE for list obligations

Hi,

I wanted to clarify how the INVALID_DATE_RANGE validation works for list obligations. It seems that you can only request for one year of returns based on this code.

Based on a) the above and b) my understanding you can only submit VAT returns in sequential order:

  • How does software work out what date range it should retrieve? If the next 'open' return falls outside a year, is it expected that we'd have to allow making lists requests till the year with the earliest 'open' VAT return? Not sure how often this scenario would occur but could potentially impact the 150 requests/minute limit.
    • Example: In April 2019, a quarterly VAT business hasn't submitted any VAT returns for more than a year. We'd have to make two requests one for period 31/03/2018-31/03-2019 and 28/02/2017-28/02/2018 assuming the last completed VAT return was 30/09/2017.
  • Ideally there would be an endpoint that lets us know what the next 'open' VAT return for submission is so we can adjust the date range relative to that.
  • In the reverse scenario, do we know how far into the future from 'today's' date the VAT obligations list will return us an open VAT return? Think it's been asked a few times earlier so a few of us must be keen for this answer 🙂

If assumption b) is not right - please let me know. Hope that's clear!

On a side note, I found the validation didn't work as I expected (1/1/2017-1/1/2018 works - I'd expected it to error out! (greater than a year)).

Cheers,

Nick

EDITED - updated example for clarity

Liabilites Tax Period

Should the tax period in a liability match the obligation?

Small thing, maybe irrelevant but just for consistency. Should the model be normalised? so that it is
{ "taxPeriod": { "from": "2017-04-06", "to": "2017-07-06" }, "type": "VAT ...", "originalAmount": 6000.00, "outstandingAmount": 100.00, "due": "2017-07-06" }
to
{ "from": "2017-04-06", "to": "2017-07-06", "type": "VAT ...", "originalAmount": 6000.00, "outstandingAmount": 100.00, "due": "2017-07-06" }

All other objects have the dates inline

"Finalised" flag versus actual final return

How will the new API support the situation when a return is actually a final return (ie the last ever return for a registration) which is currently supported in the existing XML API with the <vat:VATDeclarationRequest finalReturn="yes"> attribute.

In the Sandbox documentation, the "finalised" field is described as:
“Declaration that the user has finalised their VAT return.”
However the relevant error code is described as:
User has not declared VAT return as final 403 (Forbidden) NOT_FINALISED
These descriptions are ambiguous and initially I thought this was how a final return might be filed. However, as there appears to be an expectation that the "finalised" field will be true 100% of the time, it appears pointless.

Unable to retrieve token from code

I have been able to send authorization and received a code back but I am not able to then retrieve the token. I am using curl with example below where I enter my client_id and client_secret and redirect_uri.

curl -X POST --data
'client_secret=[]&client_id=[]&grant_type=authorization_code&redirect_uri=[]&code=[]' \ https://test-api.service.hmrc.gov.uk/oauth/token

Any ideas or guidance would be appreciated

Submit VAT Return Access Token Problem

I have successfully implemented the Hello User and VAT Obligations api's,
but I am having a problem with the Submit VAT Return function.

I request an authority code with a scope of "write:vat"
I show the HMRC Login page where i enter my test user account number and password.
This redirects me to the page to Grant Authority for my application to 'Change your VAT information'
When I click 'Grant', I receive the access token and refresh token.
But using the access token to submit the VAT return gives me a 401 unauthorized where the whole process of logining is repeated for ever.

Is this a known issue?

PeriodKey info - API inconsistency between /obligations and /submit

Hi,

According to /submit API documentation the payload below should be accepted hovever it generates internal server error on Sanbox side; when # is replaced by zero in periodKey value ("#1" -> "0001") the call are accepted.

/obligations API still returns periodKey as "#1" - my question here is whether these two APIs will get in sync (periodKey from obligations can be used directly in submissions) or it's expected the consumer application does some transformation of periodKey value?

Thanks,
Robert

submission payload
{
"periodKey": "#1",
"vatDueSales": 100.00,
"vatDueAcquisitions": 100.00,
"totalVatDue": 200,
"vatReclaimedCurrPeriod": 100.00,
"netVatDue": 100,
"totalValueSalesExVAT": 500,
"totalValuePurchasesExVAT": 500,
"totalValueGoodsSuppliedExVAT": 500,
"totalAcquisitionsExVAT": 500,
"finalised": true
}

obligation info:
{
"start": "2017-04-06",
"end": "2017-07-05",
"due": "2017-08-05",
"status": "F",
"received": "2017-08-05",
"periodKey": "#1"
}

VAT Submissions - Gov-Test-Scenario header values

Hi,

The documentation https://test-developer.service.hmrc.gov.uk/api-documentation/docs/api/service/vat-api/1.0#_submit-vat-return-for-period_post_accordion mentions an optional Gov-Test-Scenario (Sandbox only) request header facilitating testing of different HMRC responses.

Is there any description of available/ planned header values? The site mentions “Test Data table” which should include details but we can’t find this section for VAT Submission API.

Thanks,
Robert

View VAT Return - PeriodKey format

The VAT Obligations endpoint returns a period key (e.g. #001) for each corresponding VAT return.

We then attempt to feed the period key into the View Vat Return endpoint as follows:

GET: /vat/{vrn}/returns/{periodKey}

If we feed in the example key (#001) and VRN we get the response:

MATCHING_RESOURCE_NOT_FOUND

Removing the # prefix then returns:

PERIOD_KEY_INVALID

We've attempted various permutations but to no avail. Please can someone advise on the correct form for this request and whether there's some specific values we need to be using to get a canned response back?

Thanks.

OAuth authorisation scopes

Hi,

Will there be any errors when requesting authorisation for a scope the user has not been set up for (i.e. not opted into MTD, but we request access for VAT MTD permissions)?

Cheers,

Nick

VAT submission numbers - acceptable values

Hi,

When sending the payload below we receive a validation error; an equivalent of the payload used to work with SOAP based submissions, can you please explain whether it's a bug or expected behaviour - if the latter it would be good to have all the rules documented.

Same payload with totalValueSalesExVAT set to 100 works OK.

Thanks,
Robert

Payload:
{
"periodKey": "#42",
"vatDueSales": "0",
"vatDueAcquisitions": "0",
"totalVatDue": "0",
"vatReclaimedCurrPeriod": "0",
"netVatDue": "0",
"totalValueSalesExVAT": "-100",
"totalValuePurchasesExVAT": "0",
"totalValueGoodsSuppliedExVAT": "0",
"totalAcquisitionsExVAT": "0",
"finalised": true
}

Error response:
"code": "INVALID_REQUEST",
"message": "Invalid request",
"errors": [
{
"code": "INVALID_MONETARY_AMOUNT",
"message": "amount should be a whole monetary value between 0 and 9,999,999,999,999",
"path": "/totalValueSalesExVAT"
}

Relationship between obligation periods and MTD subscription dates ?

Lets say a user is on quarterly filing scheme with periods as follows:

  • 1st Jan - 31st Mar
  • 1st Apr - 30th Jun
  • 1st Jul - 30th Sep
  • 1st Oct - 31st Dec.

What will be the obligation dates and first OPEN obligation period be for filing via MTD apis for the following MTD subscription dates.

  1. 1st of April.
  2. 30th of April.
  3. 30th of June.

API performance

Hi,

Are there any performance metrics for how the VAT API will perform? If not, will they be published at a later date?

Cheers,

Nick

Rate limiting

Hi,

I just wanted to confirm my understanding of rate limiting with the API's. Is it up to 150 requests a minute from when the first request in a rate limit period? i.e. if I make 150 requests at 12:00pm, I won't be able to make another request until 12:01pm?

Or is it up to 150 concurrent requests? i.e. if I have 150 requests being processed at the same time, as soon as one request is finished we're free to make another request.

Cheers,

Nick

Period Key - Relation between Obligations, View and Submit VAT return

  1. What is the relation of Period Key in Obligations, View and Submit VAT return.
  2. Should the period key be generated by our systems or we must use the Period Key generated during retrieving obligations. Below is a sample representation of the response we get during retrieving obligations.

Start Date | End Date | Due | Status | Received | Period Key
2017-01-05 | 2017-04-04 | 2017-05-04 | Fulfilled | 2017-03-30 | #1
2017-04-05 | 2017-07-04 | 2017-08-04 | Open |   | #2
2017-07-05 | 2017-10-04 | 2017-11-04 | Open |   | #3
2017-10-05 | 2017-12-31 | 2018-01-31 | Open |   | #4

  1. In the above scenario, will the period key be #5 for the next period (for 2018).

Valid period key formats for vat/{vrn}/returns

For the submissions, we noticed that any alphanumeric period key of length 4 ( E.g. : “#xyz” ) is considered as a valid submission in HMRC , i.e. we dint get any invalid period key response for the same. Is that an expected behavior ? Also , can you please provide some examples or rules around validity of period keys for test purposes?

MTD VAT beta/ pilot questions.

If a business qualifies for the MTD VAT beta / pilot and they want to opt out of MTD VAT during the pilot phase, what do they do?

If a business opts out of the MTD VAT Pilot, is the MTD VAT access/refresh token 'dropped' preventing them from attempting use MTD VAT? What would they experience?

During MTD Pilot if someone attempts to submit VAT return(s) via MTD and the portal (or software via the existing gateway) , what will they experience? Will the systems prevent them doing the same thing by MTD and existing channels?

If someone signs up for pilot, but they do not qualify at that time they sign up, what will they experience?

When will there be automated systems/UI to support people signing up to MTD
I see on the roadmap the self assessment UI to enable a new business to register and signup for MTD has been pushed out from March, but do not see anything for VAT? Am I missing something?

Thank you!

Error response inconsistency

Hi,

We've encountered two sets of error responses:
image
(code is in the message property, statusCode provided)

image
(code is in the code property, no statusCode provided)

Are there plans to make them consistent in the future?

Cheers,

N

INTERNAL_SERVER_ERROR for /vat/{vrn}/obligations

Getting the Internal server error {"code":"INTERNAL_SERVER_ERROR","message":"An internal server error occurred"} .
We are getting the Internal server error whenever the from and to dates are less than 6 months apart( E.g.:- from=2017-01-01 , to=2017-06-30 ). Is this a requirement on the dates ? If this is a valid error which we might have to consider for the PROD environment , is there a way to provide a more detailed / readable error message pointing to the actual issue ?

ID on payment

Could there be an if added to the payment?

I want to be able to reconcile a payment against vat returns and if there were two payments on the same day then it would be hard to say which one is which. In the example where the organisation is late paying and makes two payments at once.

Do you have any link from the payment to the vat return or do organisation sometimes make one payment for multiple returns?

Revoking authority and refreshing tokens

Hi,

Im working out what happens when we revoke authority. When I revoke authority and try to refresh my tokens (on /oauth/token) I get this response:

{
   "error": "invalid_grant",
   "error_description": "refresh_token is invalid"
}

In the documentation it's listed that I should get back an "invalid_request":
image

Is that an issue or should we handle both scenarios?

Thanks!

Cheers,

N

Submit VAT return for period response documentation

Hi,

https://test-developer.service.hmrc.gov.uk/api-documentation/docs/api/service/vat-api/1.0#_submit-vat-return-for-period_post_accordion does not document response payloads for VAT submissions; should it be assumed tha the payload will always have a constant number of fields as in the response below?
{
"processingDate": "2018-01-16T08:20:27.895+0000",
"paymentIndicator": "BANK",
"formBundleNumber": "256660290587",
"chargeRefNumber": "aCxFaNx0FZsCvyWF"
}
I believe a question related to the meaning of the fields was already raised.

Thanks,
Robert

periodKey - possible values

On the endpoint /vat/{vrn}/returns

Could you confirm the valid values for periodKey
I can see an example of #1
Is this mapping to months/quarters or is it simply any string that the sender chooses?

VAT return payload - finalised flag meaning

Hi,

When I try sending the request having finalised flag set to false the service responds with an error below; is this a feature of Sandbox API only or not finalised returns are not permitted at all? If the latter then what's the intention of having the flag?

{ "code": "BUSINESS_ERROR", "message": "Business validation error", "errors": [ { "code": "NOT_FINALISED", "message": "The return cannot be accepted without a declaration it is finalised.", "path": "/finalised" } ] }

Thanks,
Robert

End point for healthcheck

Hi,

Is there an endpoint you'd advise we can use to to see if the MTD VAT service is down? i.e. a ping endpoint? We'd like to incorporate it into our health checks - and hopefully one that doesn't use up one of our client requests (impacting 150 requests/minute)?

AFAIK - only hello world can do this but will there be one for VAT?

Cheers,

Nick

Obligation request returning error code 500

We have been advised to contact you by SDS who seem unable to help.
Our code worked fine a few weeks ago and we could test obligation requests and submit test VAT returns. This is the first time we've tried a test with the latest release of the VAT API.

Due to the clear out of the API by HMRC every month or so, we had to create a new user.
Our code gets the HMRC authentication token and then tries to make an obligations request. The details at this stage are:

GET request = https://test-api.service.hmrc.gov.uk/vat/XXXXXXXXX/obligations?from=2017-10-01&to=2017-12-31&status=A

application/vnd.hmrc.1.0+json
application/json
Headers.Add("Authorization", "Bearer f85737e41b3c72f219b77282bae91");

(Where XXXXXXXXX is the VRN and the token received back from HMRC is added to the request headers.)

At this point the server returns the 500 error. Can you help?

Error 500 on authorisation today

Anyone else getting Error 500 when trying to obtain an access token from /oauth/token ?
Hoping to prepare for the hackathon in Birmingham tomorrow.

Error reporting API for user that leaves the beta but attempts submission

I am creating user stories covering users who are taking part in the MTD for VAT beta and have a couple of scenarios where I need to know the errors that will be returned from HMRC.

1 - User of accounting software has been accepted onto the beta
2 - The user submits a VAT return via the new API and is accepted by HMRC
3 – User leaves the beta program and submits next VAT return via the Government Gateway
4 – User attempts to submit a VAT return via the MTD API
5 – What error will be returned by the MTD API?

Retrieve VAT Obligation questions and scenarios - few questions

The Retrieve VAT obligation endpoints, definition and example provided appears to reflect a common situation of 4 equal quarterly periods in a year. There's a corresponding periodKey to identify the return.
We have some questions on different scenarios and situations - how things will be handled in practice. Some test scenarios and examples for common use cases people will need to achieve would be good.

How will MTD API's reflect returns from different years? or is it only going to offer a current year available in list?

When will the next years VAT returns for a business be available to view?

If available to view in advance, will the system have something to limit the earliest returns can be submitted. (eg, will MTD prevent a return period from being lodged if is received before the period too date?)

How will MTD VAT API's identify different return obligations where periods might change in different use cases including:

  • A business (someone reg'd for VAT) de-registers, so they have to do a VAT return to a specific date, which may not be the normal period end date.

  • A business changes their VAT reporting dates from they are currently. So they may have a return period of 2 months or 4 months, rather than 1 month or 3 months as it might usually be.

  • A business registers for VAT from a day in the month - so they will do their first VAT return from that first day, to the regular reporting end date.

Does HMRC MTD VAT list information update immediately / instantaneously following an update from any HMRC system? or is there a time delay or some kind. If so, what is it?

User first use flow

Hello,

A few questions around the first use/onboarding experience from software perspective, and following on from a few earlier issues:

  • Based on the excellent responses in #42 - the only way I can see a software determining whether a business/VRN is MTD enabled will be by hitting the obligation list endpoint? And then gracefully handling the yet to be determined unauthorized error? Is that correct and the expected flow?
  • Does a user nominate a software for a business/VRN from the HMRC website? Based on the user auth flow and within the sandbox environment I understand this isn’t the case but would like to double confirm.
    • We’re considering the scenario where a user login is associated with multiple businesses.
    • For example - let’s say a user owns two businesses, Bob’s Fried Chicken (BFC) and Sally’s Cafe (SC), if a user logs into their software of choice and goes through the user authorisation flow with VAT scopes for that software, then those OAuth tokens could be used to hit the VAT api endpoints for either BFC and SC? Is that right?
  • Closed #23 and bringing my last question over - is there a scenario where the user will get an error during the user authorisation process given an authorize link contains all the correct query parameters?
    • For example if a user is not associated with any business but requests read/write scopes for VAT - will that result in an error or continue on?
    • For clarity - I’m not talking about accessing API’s but the user authorisation flow.
  • In sandbox if we pass in invalid parameters for example:
    https://test-api.service.hmrc.gov.uk/oauth/authorize?response_type=code&client_id=[YOUR-CLIENT-ID]&scope=[REQUESTED-SCOPE]&state=[STATE]&redirect_uri=[YOUR-REDIRECT-URI]
    It gives a service error response, in production will that give an actual error page?
  • Will the XML gateway throw an error if a business/VRN has already been setup for MTD?

Thanks and cheers,

Nick

Documentation on the definitive list of errors returned by MTD API - when?

Hi,

We're working on showing more customer friendly messages when an error occurs.

When (whether?) we can expect more complete information on errors returned by the API? Examples:

  • /vat/{vrn}/returns lists 8 error scenarios only, it looks incomplete - e.g. one of the error we found some time ago was INVALID_MONETARY_AMOUNT not shown on the page, I guess there might be more?
  • judging by other threads here there will be background services connected with the MTD API, if so - what additional errors we may expect?
  • are there plans related to change error wording

We're aware the MTD service is still in Alpha stage so changes may happen - having to do deal with changes is usually easier than implementing from scratch, any documentation improvement would be appreciated!

Thanks,
Robert

API call using curl utility

I am not clear if we need to use 2 way authorization when submitting GET/POST for Obligations and Returns. Most of our clients are on premise and this would make things more complicated.

Unexpected http status code (201) when sending VAT submission

Hi,

We started experiencing issues when sending VAT submission - it looks like the Sandbox API responds with http status code 201 and empty content instead of 200 and submission response. It happened for VAT no 666807229 and application id 82d3cdb5-85cd-45b8-870b-7246a18ab0c5.

Trying to re-submit data for a VAT no/ period already sent in the past generates expected 403 error and business errors.

Thanks,
Robert

Submit VAT return for period - periodKey meaning + lack of submission year

Hi,

The documentation of the periodKey in VAT submission API says: "Identifier for the period of the VAT return, For example: #1".

How the software is supposed to generate the period information? How/ whether is this related to dates i.e. I cannot see any field in the request which says for which range of dates a given submission applies - in the legacy gateway submission there were fields named PeriodStart/ PeriodEnd?

Thanks,
Robert

'Submit VAT return for period' response documentation

Hi,

I've been testing out the VAT end points in sandbox and found the response for 'Submit VAT return for period' is not documented and so have a few questions:

  • What do the properties mean? i.e. formBundleNumber, chargeRefNumber
{
    "processingDate": "2018-01-17T23:06:59.035+0000",
    "paymentIndicator": "DD",
    "formBundleNumber": "395256427162",
    "chargeRefNumber": "R4t58D5SlG5vxk3X"
}
  • Does a successful response change the status in the obligations list for that period from O to F? If not, is there a plan to add an additional status like 'Processing'?

Thanks!

Nick

EDITED to make second point clearer

Submit VAT Return - Mandatory Field Missing Error

Hello,

We are trying to post the following payload to "/vat/666592090/returns"

{"periodKey":"#001","vatDueSales":20000.0,"vatDueAcquisitions":40000.0,"totalVatDue":60000.0,"vatReclaimedCurrPeriod":65000.0,"netVatDue":5000.0,"totalValueSalesExVAT":123131.0,"totalValuePurchasesExVAT":121313.0,"totalValueGoodsSuppliedExVAT":147654654.0,"totalAcquisitionsExVAT":147654654213.0,"finalised":true}

but we are getting the following error:

{"code":"INVALID_REQUEST","message":"Invalid request","errors":[{"code":"MANDATORY_FIELD_MISSING","message":"a mandatory field is missing","path":"/vatReclaimedCurrPeriod"},{"code":"MANDATORY_FIELD_MISSING","message":"a mandatory field is missing","path":"/periodKey"},{"code":"MANDATORY_FIELD_MISSING","message":"a mandatory field is missing","path":"/totalAcquisitionsExVAT"},{"code":"MANDATORY_FIELD_MISSING","message":"a mandatory field is missing","path":"/netVatDue"},{"code":"MANDATORY_FIELD_MISSING","message":"a mandatory field is missing","path":"/totalVatDue"},{"code":"MANDATORY_FIELD_MISSING","message":"a mandatory field is missing","path":"/totalValueGoodsSuppliedExVAT"},{"code":"MANDATORY_FIELD_MISSING","message":"a mandatory field is missing","path":"/totalValuePurchasesExVAT"},{"code":"MANDATORY_FIELD_MISSING","message":"a mandatory field is missing","path":"/finalised"},{"code":"MANDATORY_FIELD_MISSING","message":"a mandatory field is missing","path":"/totalValueSalesExVAT"},{"code":"MANDATORY_FIELD_MISSING","message":"a mandatory field is missing","path":"/vatDueAcquisitions"},{"code":"MANDATORY_FIELD_MISSING","message":"a mandatory field is missing","path":"/vatDueSales"}]}

All the fields are available in the payload and we don't have a clue about this error. Can you please tell us where are we doing wrong?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.