Invoice_search not returning NetAmount or VatAmount

Extensibility
1

Hi,

My return when I search for invoices is

<Invoice_Search>
   <Header>
     <MessageType>Response</MessageType>
     <SubmissionNumber>82425e13-2335-xxxxxxxxxxxx</SubmissionNumber>
   </Header>
   <Body>
     <RecordsetCount>xx</RecordsetCount>
     <ReturnCount>xxx</ReturnCount>
     <Record>
       <IssueDate>xxxx-01-19</IssueDate>
       <DueDate>xxx-02-16</DueDate>
       <OverdueDays>81</OverdueDays>
       <InvoiceID>xxx7424</InvoiceID>
       <ClientID>1xxxx633</ClientID>
       <ClientCompanyName>Company name</ClientCompanyName>
       <ClientContactName>contact name</ClientContactName>
       <InvoiceNumber>00123111</InvoiceNumber>
       <Description>description</Description>
       <Currency>GBP</Currency>
       <Amount>10.00</Amount>
       <PaidToDate>2.43</PaidToDate>
       <Status>PAIDPART</Status>
       <ViewHref><![CDATA[REMOVED]]></ViewHref>
     </Record>

Can you please help?

2

Hi @APereira

Can I just check, do you include these in the original API call?

      <AdditionalParameters>
        <ShowNetAmount>true</ShowNetAmount>
        <ShowVatAmount>true</ShowVatAmount>
      </AdditionalParameters>

They can be seen here:
https://api.quickfile.co.uk/d/v1_2/Invoice_Search

Body >> SearchParameters >> AdditionalParameters

1 Like
3

@QFMathew thanks for your quick reply.

I’ve tried it before and the reply I have.

<Errors>
<Error>22The 'https://api.quickfile.co.uk:ShowNetAmount' element has an invalid value according to its data type.</Error>
<Error>23The 'https://api.quickfile.co.uk:ShowVatAmount' element has an invalid value according to its data type.</Error>
</Errors>
4

End of my XML

   </Status>
   <AdditionalParameters>
      <ShowNetAmount>true</ShowNetAmount>
      <ShowVatAmount>true</ShowVatAmount>
   </AdditionalParameters></SearchParameters>
</Body>
</Invoice_Search>
5

I’ve tried an example with the below body, which has worked successfully:

  <Body>
    <SearchParameters>
      <ReturnCount>10</ReturnCount>
      <Offset>0</Offset>
      <OrderResultsBy >InvoiceNumber</OrderResultsBy>
      <OrderDirection>ASC</OrderDirection>
      <InvoiceType>INVOICE</InvoiceType>
      <ShowDeleted>false</ShowDeleted>
      <IssueDateFrom>2017-01-01</IssueDateFrom>
      <Status>SENT</Status>
      <AdditionalParameters>
        <ShowNetAmount>true</ShowNetAmount>
        <ShowVatAmount>true</ShowVatAmount>
      </AdditionalParameters>
    </SearchParameters>
  </Body>

The section you’ve pasted above looks correct, so I’m not sure why this would be returning an error. Are you able provide me with an example of a request you’re making please (removing any sensitive details)?

6

thanks for your reply.
`

<Invoice_Search  xmlns="http://www.QuickFile.co.uk"  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  xsi:schemaLocation="http://www.QuickFile.co.uk http://www.quickfile.co.uk/WebServices/API/Schemas/invoices/Invoice_Search.xsd">
  <Header>
    <MessageType>Request</MessageType>
    <SubmissionNumber>[IDSubmittion]</SubmissionNumber>
    <Authentication>
      <AccNumber>xxxxxx40</AccNumber>
      <MD5Value>[MD5]</MD5Value>
      <ApplicationID>xxxxxxx7f246bf7df2b</ApplicationID>
    </Authentication>
  </Header>
  <Body>
    <SearchParameters>
      <ReturnCount>100</ReturnCount>
      <Offset>0</Offset>
      <OrderResultsBy>InvoiceNumber</OrderResultsBy>
      <OrderDirection>ASC</OrderDirection>
      <InvoiceType>INVOICE</InvoiceType>
      <ShowDeleted>false</ShowDeleted>
      <InvoiceNumber>00</InvoiceNumber>
      <Status>AGED</Status>
      <AdditionalParameters>
        <ShowNetAmount>true</ShowNetAmount>
        <ShowVatAmount>true</ShowVatAmount>
      </AdditionalParameters>
    </SearchParameters>
  </Body>
</Invoice_Search>
7

@QFMathew

Issue seems to be related with the value is on your side of the API.

If I use 1 it works absolutelly fine.

Will you change this?

8

@APereira - Apologies for the delayed response. I’ve been doing some tests on this with one of our developers, but we’ve tried both true and 1, and both have worked successfully.

I can see from your sample above you’re using the old schema which doesn’t support true - this was added in v1.2. In versions prior to this however, 1 is accepted as a value.

9

Not an issue, I was confused why was not working for me, hence why I’ve tried this :slight_smile: Thanks.