Qvalia

Qvalia Developer Tools

JSON/XML or JSON to XML

Attachments to messages

Invoice APIs

Get incoming invoices

Post incoming invoice

Get incoming read invoices

Get outgoing invoices

Post outgoing invoice

Credit Note APIs

Get incoming credit notes

Post incoming credit note

Get incoming read credit notes

Get outgoing credit notes

Post outgoing credit note

Order APIs

Get incoming orders

Post incoming order

Get incoming read orders

Get outgoing orders

Post outgoing order

Order Response APIs

Get incoming order responses

Post incoming order response

Get incoming read order responses

Get outgoing order responses

Post outgoing order response

Order Change APIs

Get incoming order changes

Post incoming order change

Get incoming read order changes

Get outgoing order changes

Post outgoing order change

Order Cancellation APIs

Get incoming order cancellation

Post incoming order cancellation

Get incoming read order cancellations

Get outgoing order cancellations

Post outgoing order cancellation

Catalogue APIs

Get incoming catalogues

Post incoming catalogue

Get incoming read catalogues

Get outgoing catalogues

Post outgoing catalogue

Despatch Advice

Get incoming despatch-advices

Post incoming despatch-advices

Get incoming read despatch-advices

Get outgoing despatch-advices

Post outgoing despatch-advices

Get outgoing read despatch-advices

Account Functions

Invoice Functions

This documentation covers only Enrichment endpoint. Please use this alongside Qvalia API documentation at https://api.qvalia.com. API for uploading and enriching invoices (PDF, XML - later). PDFs are converted to digital format and presented as a Peppol XML document. Supports single and batch file processing with asynchronous polling.

Enrichment API

API accepts a single invoice file (PDF or XML) and processes it asynchronously. Returns a polling ID to check the status of enrichment.

Upload a single invoice file for enrichment. Using AI, the uploaded PDF will be converted to Peppol XML.

Check the status of an invoice file's enrichment using the polling ID. Returns the result when processing is complete.

Poll the enrichment status of a single file.

Get the enrichment result using the polling ID. Returns the result in the format requested.

Enrichment result.

Sample Data

SFTP-Integration

Custom format

Sending and receiving

Error handling

Processed files

Consolidation

Dynamic Routing

Operator

Partner

Partner API

Get Account

Get Peppol ID

Get Specific Account

Post Account

Put Account

Delete Account

Put Account Peppol Identifier

Delete Account Peppol Identifier

Qvalia API

Production

Sandbox

Access APIs and technical requirements and get connected in no time!

Our APIs and onboarding team ensures a swift integration into your systems and processes. Qvalia integrates with major ERPs and accounting software.

 based and we use both JSON and XML request and response payloads. All message formats are based upon 

 and our JSON format is a representation of the XML called UBL JSON by OASIS Open group. We strive to use the REST standards for response codes and “verbs” (e.g. GET and POST).

The Qvalia API has two separate endpoints for our Production and a Test (Quality Assurance) environment.

You must obtain a Qvalia account prior to using (or testing) the API!

We use API keys for the Authentication of requests. You can get your API key from our Support team and you’ll get a separate key and URL for Production and Test environments. All requests are using HTTPS with a minimum of TLS 1.2

Parameters
Some of our API's has the possibility to provide parameters for e.g. filtering. These parameters are sent as a query string and the options are listed per endpoint under the technical API documentation.

We offer various error codes based upon the type of error, along with a descriptive error message (in JSON or XML). Like any other API codes in the range of 2xx is a successful request while a status of 4xx indicates an error that occurred because of the data sent or a parameter missing/in error. In the 5xx range indicate an error with our server/service and you should contact the Qvalia Support if you ever would end up getting any 5xx code as response.

You can always contact Qvalia Support through your Qvalia Sales representative or by using our Support e-mail (see your Qvalia Account for details).

We use Node.js inhouse, and JSON is our format of choice, however, as many ERP and Financial systems are using XML we have opted to add support for both formats in our API. You can freely swap between XML and JSON, just by using different headers:

Title

Description

Node.js sample code for calling the API for sending a JSON request could look like:

<p>APIs related to invoice handling</p><p></p>

<p>APIs related to credit note handing</p><p></p>

<p>APIs related to order handing</p><p></p>

<p>APIs related to order response handing</p><p></p>

<p>APIs related to order change handing</p><p>Order Change is part of Advanced Ordering 3.0: <a href="https://docs.peppol.eu/poacc/upgrade-3/profiles/65-advanced-ordering/" target="_blank">https://docs.peppol.eu/poacc/upgrade-3/profiles/65-advanced-ordering/</a></p><p>Message Syntax: </p>

Order Change is part of Advanced Ordering 3.0: 

<p>APIs related to order cancellation handing</p><p>Order Change is part of Advanced Ordering 3.0: <a href="https://docs.peppol.eu/poacc/upgrade-3/profiles/65-advanced-ordering/" target="_blank">https://docs.peppol.eu/poacc/upgrade-3/profiles/65-advanced-ordering/</a></p><p>Message Syntax: </p>

APIs related to order cancellation handing

<p>APIs related to catalogue handing</p><p></p>

<p>A collection of endpoints where Qvalia account information is gathered, such as Invoice status, and automation tasks, e.g. creating an outgoing Invoice from an incoming Order.</p><p></p>

A collection of endpoints where Qvalia account information is gathered, such as Invoice status, and automation tasks, e.g. creating an outgoing Invoice from an incoming Order.

<p class="slate-p " >This documentation covers only Enrichment endpoint. Please use this alongside Qvalia API documentation at <a href="https://api.qvalia.com" target="_self">https://api.qvalia.com</a>. API for uploading and enriching invoices (PDF, XML - later). PDFs are converted to digital format and presented as a Peppol XML document. Supports single and batch file processing with asynchronous polling.</p><p class="slate-p " ></p>

This documentation covers only Enrichment endpoint. Please use this alongside Qvalia API documentation at 

. API for uploading and enriching invoices (PDF, XML - later). PDFs are converted to digital format and presented as a Peppol XML document. Supports single and batch file processing with asynchronous polling.

<p class="slate-p " >API accepts a single invoice file (PDF or XML) and processes it asynchronously. Returns a polling ID to check the status of enrichment.</p><p class="slate-p " ></p>

The name of the file being uploaded, including extension (e.g., invoice.pdf).

fileName

fileContent

Account registration number issued by Qvalia.

accountRegNo

The unique ID for polling the file's enrichment status.

pollingId

status

data

Status of the processing (e.g., processing, error).

Invalid or expired polling ID.

<p class="slate-p " >Get the enrichment result using the polling ID. Returns the result in the format requested.</p><p class="slate-p " ></p>

The enrichment type returned in the polling endpoint.

enrichmentType


As the request and response sample data are quite big, and scrolling through each sample on every endpoint would get quite tedious, we've opted to add sample data for the various messages here instead of in the actual Endpoint data.

Regardless if you are POST'in or GET'ing data the message structure of the messages will be the same.

 section of the documentation, and under 

 all our transaction messages are bidirectional and can be transformed to/from JSON/XML.f

<p>The Qvalia SFTP integration handles all Peppol XML <a href="https://docs.peppol.eu/edelivery/codelists/" target="_blank">Document types</a> by default but we also support "custom" formats.</p><p></p><p>The SFTP setup is done by our helpdesk, and you will require a Qvalia account prior to being able to test the SFTP integration.</p>

The Qvalia SFTP integration handles all Peppol XML 

 by default but we also support "custom" formats.

The SFTP setup is done by our helpdesk, and you will require a Qvalia account prior to being able to test the SFTP integration.

Qvalia hosts an SFTP Server, and both sending and receiving is done through an SFTP client from your environment.

<p class="slate-p" placeholder="Type / for widgets">For Swedish operators Qvalia can offer support for the legacy formats Svefaktura 1.0 (Basic Invoice) as well as Svefaktura 2 (Peppol BIS2/4A).</p><p class="slate-p" placeholder="Type / for widgets"><strong class="slate-bold">Qvalia is primarily using the protocol </strong><code class="slate-code"><strong class="slate-bold">SFTI Transportprofil Bas 2.0</strong></code><strong class="slate-bold"> over </strong><code class="slate-code"><strong class="slate-bold">HTTP POST</strong></code><strong class="slate-bold"> for the Swedish legacy formats. SFTP transportation can also be accepted, and configured, for any Operator who wants to send legacy formats.</strong></p><p class="slate-p" placeholder="Type / for widgets">We <strong class="slate-bold">strongly</strong> encourage the usage of <strong class="slate-bold">Peppol</strong> instead of legacy formats, but we do understand that some older systems still needs to fall back on older versions of specifications, and we try our best to meet the needs of our customers.</p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"><strong class="slate-bold">Please reach out to peppol@qvalia.com if you are an Operator who wants to use any of the legacy formats!</strong></p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets">SFTI Transportprofil Bas 2.0 is an old and not supported standard, but as some companies and Operators in Sweden still cling to it Qvalia has the option of POST&apos;ing Transportprofil Bas 2.0 over HTTP.</p><p class="slate-p" placeholder="Type / for widgets">As we would like to follow the recommendation of the Swedish Government and the IT authorities of Sweden we have deprecated the usage of Svefaktura, and try to move all our customers over to Peppol.</p><p class="slate-p" placeholder="Type / for widgets">After the 1st of March 2021, no new established Svefaktura connections should be added according to DIGG&apos;s recommendations and mandate <code class="slate-code">MDFFS 2021:1</code>. See article from SFTI/DIGG here (in Swedish) for more information: <a href="https://sfti.se/sfti/standarder/rekommenderadestandarder/avfordameddelanden.52834.html" target="_blank">https://sfti.se/sfti/standarder/rekommenderadestandarder/avfordameddelanden.52834.html</a></p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p><table class="slate-table"><colgroup></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr"><td class="slate-td"><div class="slate-TableCellElement-content"><p class="slate-p" placeholder="Type / for widgets"><code class="slate-code"><strong class="slate-bold">Sample of a Transportprofil Bas 2.0 Envelope with Svefaktura</strong></code></p></div><div class="slate-TableCellElement-resizableWrapper" contenteditable="false"><div style="position:relative;user-select:auto;width:100%;height:100%;box-sizing:border-box;flex-shrink:0" ><div><div  style="position:absolute;user-select:none;width:10px;height:calc(100% + 12px);top:-12px;cursor:col-resize;right:-5px;z-index:20"></div></div></div><div class="slate-TableCellElement-handle"></div></div><div class="slate-TableCellElement-selectedCell" contenteditable="false"></div></td></tr><tr class="slate-tr"><td class="slate-td"><div class="slate-TableCellElement-content"><pre class="slate-CodeBlockElement slate-code_block"><div contenteditable="false"><div ><span aria-live="polite" aria-atomic="false" aria-relevant="additions text" ></span><div ><div ><div >Select...</div><div ><div  style="display:inline-block"><input type="text" autoCapitalize="none" autoComplete="off" autoCorrect="off" id="react-select-6-input" spellcheck="false" tabindex="0" value="" aria-autocomplete="list" style="box-sizing:content-box;width:1px;label:input;background:0;border:0;font-size:inherit;opacity:1;outline:0;padding:0;color:inherit"/><div style="position:absolute;top:0;left:0;visibility:hidden;height:0;overflow:scroll;white-space:pre"></div></div></div></div><div ><span ></span><div  aria-hidden="true"><svg height="20" width="20" viewBox="0 0 20 20" aria-hidden="true" focusable="false" ><path d="M4.516 7.548c0.436-0.446 1.043-0.481 1.576 0l3.908 3.747 3.908-3.747c0.533-0.481 1.141-0.446 1.574 0 0.436 0.445 0.408 1.197 0 1.615-0.406 0.418-4.695 4.502-4.695 4.502-0.217 0.223-0.502 0.335-0.787 0.335s-0.57-0.112-0.789-0.335c0 0-4.287-4.084-4.695-4.502s-0.436-1.17 0-1.615z"></path></svg></div></div></div></div></div><code class="keep-markup drop-tokens"><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets">Content-Type: multipart/related; boundary=&quot;BoundarY&quot;; type=&quot;text/xml&quot;;
soapaction: ebXML</p></code></pre></div><div class="slate-TableCellElement-resizableWrapper" contenteditable="false"><div style="position:relative;user-select:auto;width:100%;height:100%;box-sizing:border-box;flex-shrink:0" ><div><div  style="position:absolute;user-select:none;width:10px;height:calc(100% + 12px);top:-12px;cursor:col-resize;right:-5px;z-index:20"></div></div></div><div class="slate-TableCellElement-handle"></div></div><div class="slate-TableCellElement-selectedCell" contenteditable="false"></div></td></tr><tr class="slate-tr"><td class="slate-td"><div class="slate-TableCellElement-content"><pre class="slate-CodeBlockElement slate-code_block"><div contenteditable="false"><div ><span aria-live="polite" aria-atomic="false" aria-relevant="additions text" ></span><div ><div ><div >Select...</div><div ><div  style="display:inline-block"><input type="text" autoCapitalize="none" autoComplete="off" autoCorrect="off" id="react-select-7-input" spellcheck="false" tabindex="0" value="" aria-autocomplete="list" style="box-sizing:content-box;width:1px;label:input;background:0;border:0;font-size:inherit;opacity:1;outline:0;padding:0;color:inherit"/><div style="position:absolute;top:0;left:0;visibility:hidden;height:0;overflow:scroll;white-space:pre"></div></div></div></div><div ><span ></span><div  aria-hidden="true"><svg height="20" width="20" viewBox="0 0 20 20" aria-hidden="true" focusable="false" ><path d="M4.516 7.548c0.436-0.446 1.043-0.481 1.576 0l3.908 3.747 3.908-3.747c0.533-0.481 1.141-0.446 1.574 0 0.436 0.445 0.408 1.197 0 1.615-0.406 0.418-4.695 4.502-4.695 4.502-0.217 0.223-0.502 0.335-0.787 0.335s-0.57-0.112-0.789-0.335c0 0-4.287-4.084-4.695-4.502s-0.436-1.17 0-1.615z"></path></svg></div></div></div></div></div><code class="keep-markup drop-tokens"><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets">--BoundarY
Content-ID: &lt;ebxhmheader1@avsandare.com&gt;
Content-Type: text/xml

&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;SOAP:Envelope xmlns:xlink=&quot;http://www.w3.org/1999/xlink&quot;
	xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
	xmlns:SOAP=&quot;http://schemas.xmlsoap.org/soap/envelope/&quot;
	xmlns:eb=&quot;http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd&quot;
	xsi:schemaLocation=&quot;http://schemas.xmlsoap.org/soap/envelope/ http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd&quot;&gt;
	&lt;SOAP:Header&gt;
	  &lt;eb:MessageHeader SOAP:mustUnderstand=&quot;1&quot; eb:version=&quot;2.0&quot;&gt;
		  &lt;eb:From&gt;
			  &lt;eb:PartyId eb:type=&quot;countrycode:organizationid&quot;&gt;SE1234567890&lt;/eb:PartyId&gt;
		  &lt;/eb:From&gt;
			&lt;eb:To&gt;
			  &lt;eb:PartyId eb:type=&quot;countrycode:organizationid&quot;&gt;SE9876543210&lt;/eb:PartyId&gt;
			&lt;/eb:To&gt;
			&lt;eb:CPAId&gt;20160214:SE1234567890:SE9876543210&lt;/eb:CPAId&gt;
			&lt;eb:ConversationId&gt;20160214:4567:SE1234567890&lt;/eb:ConversationId&gt;
			&lt;eb:Service&gt;urn:sfti:services:documentprocessing:BasicInvoice&lt;/eb:Service&gt;
			&lt;eb:Action&gt;incomingBasicInvoice&lt;/eb:Action&gt;
		  &lt;eb:MessageData&gt;
			  &lt;eb:MessageId&gt;20160214-102030-28572@foretag.se&lt;/eb:MessageId&gt;
				&lt;eb:Timestamp&gt;2016-02-14T11:12:12&lt;/eb:Timestamp&gt;
			&lt;/eb:MessageData&gt;
		&lt;/eb:MessageHeader&gt;
		&lt;eb:AckRequested SOAP:mustUnderstand=&quot;1&quot; eb:version=&quot;2.0&quot; eb:signed=&quot;false&quot; SOAP:actor=&quot;urn:oasis:names:tc:ebxml-msg:actor:toPartyMSH&quot;/&gt;
		&lt;eb:SyncReply eb:id=&quot;&quot; eb:version=&quot;2.0&quot; SOAP:mustUnderstand=&quot;1&quot; SOAP:actor=&quot;http://schemas.xmlsoap.org/soap/actor/next&quot;&gt;
		&lt;/eb:SyncReply&gt;
	&lt;/SOAP:Header&gt;
	&lt;SOAP:Body&gt;
	  &lt;eb:Manifest eb:version=&quot;2.0&quot;&gt;
		  &lt;eb:Reference xlink:href=&quot;cid:ebxmlpayload1@avsandare.com&quot; xlink:type=&quot;simple&quot;&gt;
			  &lt;eb:Description xml:lang=&quot;se&quot;&gt;Fritext beskrivning av meddelande&lt;/eb:Description&gt;
				&lt;eb:Schema eb:location=&quot;urn:se:sfti:collaborationprocesses:BasicInvoice.xsd&quot; eb:version=&quot;1.0&quot;&gt;&lt;/eb:Schema&gt;
			&lt;/eb:Reference&gt;
		&lt;/eb:Manifest&gt;
	&lt;/SOAP:Body&gt;
&lt;/SOAP:Envelope&gt;

--BoundarY
Content-ID: &lt;ebxmlpayload1@avsandare.se&gt;
Content-Type: text/xml

&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
&lt;StandardBusinessDocument xmlns:xsd=&quot;http://www.w3.org/2001/XMLSchema&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xmlns=&quot;http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHeader&quot;&gt;
  &lt;StandardBusinessDocumentHeader&gt;
    &lt;HeaderVersion&gt;1.0&lt;/HeaderVersion&gt;
    &lt;Sender&gt;
      &lt;Identifier
        Authority=&quot;iso6523-actorid-upis&quot;&gt;0088:7301234567890&lt;/Identifier&gt;
    &lt;/Sender&gt;
    &lt;Receiver&gt;
      &lt;Identifier
        Authority=&quot;iso6523-actorid-upis&quot;&gt;0007:1234567890&lt;/Identifier&gt;
    &lt;/Receiver&gt;
    &lt;DocumentIdentification&gt;
      &lt;Standard&gt;urn:oasis:names:specification:ubl:schema:xsd:Invoice-2&lt;/Standard&gt;
      &lt;TypeVersion&gt;2.1&lt;/TypeVersion&gt;
      &lt;InstanceIdentifier&gt;2016021401022&lt;/InstanceIdentifier&gt;
      &lt;Type&gt;Invoice&lt;/Type&gt;
      &lt;CreationDateAndTime&gt;2016-02-14T14:40:38.4644993+02:00&lt;/CreationDateAndTime&gt;
    &lt;/DocumentIdentification&gt;
    &lt;BusinessScope&gt;
      &lt;Scope&gt;
        &lt;Type&gt;DOCUMENTID&lt;/Type&gt;
        &lt;InstanceIdentifier&gt;urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1&lt;/InstanceIdentifier&gt;
      &lt;/Scope&gt;
      &lt;Scope&gt;
        &lt;Type&gt;PROCESSID&lt;/Type&gt;
        &lt;InstanceIdentifier&gt;urn:fdc:peppol.eu:2017:poacc:billing:01:1.0&lt;/InstanceIdentifier&gt;
      &lt;/Scope&gt;
    &lt;/BusinessScope&gt;
  &lt;/StandardBusinessDocumentHeader&gt;
  &lt;Invoice xmlns:cac=&quot;urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2&quot; xmlns:cbc=&quot;urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2&quot; xmlns=&quot;urn:oasis:names:specification:ubl:schema:xsd:Invoice-2&quot;&gt;
    &lt;cbc:CustomizationID&gt;urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0&lt;/cbc:CustomizationID&gt;
    &lt;cbc:ProfileID&gt;urn:fdc:peppol.eu:2017:poacc:billing:01:1.0&lt;/cbc:ProfileID&gt;
    &lt;cbc:ID&gt;...&lt;/cbc:ID&gt;
    &lt;cbc:IssueDate&gt;2016-02-14&lt;/cbc:IssueDate&gt;
    &lt;cbc:DueDate&gt;2016-03-31&lt;/cbc:DueDate&gt;
    &lt;cbc:InvoiceTypeCode&gt;380&lt;/cbc:InvoiceTypeCode&gt;
    &lt;cbc:DocumentCurrencyCode&gt;SEK&lt;/cbc:DocumentCurrencyCode&gt;
    &lt;cbc:BuyerReference&gt;...&lt;/cbc:BuyerReference&gt;
    &lt;cac:AccountingSupplierParty&gt;
      ...
    &lt;/cac:AccountingSupplierParty&gt;
    &lt;cac:AccountingCustomerParty&gt;
      ...
    &lt;/cac:AccountingCustomerParty&gt;
    &lt;cac:PaymentMeans&gt;
      ...
    &lt;/cac:PaymentMeans&gt;
    &lt;cac:PaymentTerms&gt;
      ...
    &lt;/cac:PaymentTerms&gt;
    &lt;cac:TaxTotal&gt;
      ...
    &lt;/cac:TaxTotal&gt;
    &lt;cac:LegalMonetaryTotal&gt;
      ...
    &lt;/cac:LegalMonetaryTotal&gt;
    &lt;cac:InvoiceLine&gt;
      ...
    &lt;/cac:InvoiceLine&gt;
  &lt;/Invoice&gt;
&lt;/StandardBusinessDocument&gt;

--BoundarY––
</p></code></pre></div><div class="slate-TableCellElement-resizableWrapper" contenteditable="false"><div style="position:relative;user-select:auto;width:100%;height:100%;box-sizing:border-box;flex-shrink:0" ><div><div  style="position:absolute;user-select:none;width:10px;height:calc(100% + 12px);top:-12px;cursor:col-resize;right:-5px;z-index:20"></div></div></div><div class="slate-TableCellElement-handle"></div></div><div class="slate-TableCellElement-selectedCell" contenteditable="false"></div></td></tr><tr class="slate-tr"><td class="slate-td"><div class="slate-TableCellElement-content"><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets"><code class="slate-code"><strong class="slate-bold">Sample of a Transportprofil Bas 2.0 Acknowledgement Response</strong></code></p></div><div class="slate-TableCellElement-resizableWrapper" contenteditable="false"><div style="position:relative;user-select:auto;width:100%;height:100%;box-sizing:border-box;flex-shrink:0" ><div><div  style="position:absolute;user-select:none;width:10px;height:calc(100% + 12px);top:-12px;cursor:col-resize;right:-5px;z-index:20"></div></div></div><div class="slate-TableCellElement-handle"></div></div><div class="slate-TableCellElement-selectedCell" contenteditable="false"></div></td></tr><tr class="slate-tr"><td class="slate-td"><div class="slate-TableCellElement-content"><pre class="slate-CodeBlockElement slate-code_block"><div contenteditable="false"><div ><span aria-live="polite" aria-atomic="false" aria-relevant="additions text" ></span><div ><div ><div >Select...</div><div ><div  style="display:inline-block"><input type="text" autoCapitalize="none" autoComplete="off" autoCorrect="off" id="react-select-8-input" spellcheck="false" tabindex="0" value="" aria-autocomplete="list" style="box-sizing:content-box;width:1px;label:input;background:0;border:0;font-size:inherit;opacity:1;outline:0;padding:0;color:inherit"/><div style="position:absolute;top:0;left:0;visibility:hidden;height:0;overflow:scroll;white-space:pre"></div></div></div></div><div ><span ></span><div  aria-hidden="true"><svg height="20" width="20" viewBox="0 0 20 20" aria-hidden="true" focusable="false" ><path d="M4.516 7.548c0.436-0.446 1.043-0.481 1.576 0l3.908 3.747 3.908-3.747c0.533-0.481 1.141-0.446 1.574 0 0.436 0.445 0.408 1.197 0 1.615-0.406 0.418-4.695 4.502-4.695 4.502-0.217 0.223-0.502 0.335-0.787 0.335s-0.57-0.112-0.789-0.335c0 0-4.287-4.084-4.695-4.502s-0.436-1.17 0-1.615z"></path></svg></div></div></div></div></div><code class="language-xml keep-markup drop-tokens"><div class="slate-code_line">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;SOAP:Envelope
	xmlns:SOAP=&quot;http://schemas.xmlsoap.org/soap/envelope/&quot;
	xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
  xsi:schemaLocation=&quot;http://schemas.xmlsoap.org/soap/envelope/ http://www.oasis-
  open.org/committees/ebxml-msg/schema/envelope.xsd&quot;
	xmlns:eb=&quot;http://www.oasis-
  open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd&quot;&gt;
	&lt;SOAP:Header xsi:schemaLocation=&quot;http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd
    http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd&quot;&gt;
		&lt;eb:MessageHeader SOAP:mustUnderstand=&quot;1&quot; eb:version=&quot;2.0&quot;&gt;
			&lt;eb:From&gt;
				&lt;eb:PartyId eb:type=&quot;countrycode:organizationid&quot;&gt;SE1234567890&lt;/eb:PartyId&gt;
			&lt;/eb:From&gt;
			&lt;eb:To&gt;
				&lt;eb:PartyId eb:type=&quot;countrycode:organizationid&quot;&gt;SE9876543210&lt;/eb:PartyId&gt;
			&lt;/eb:To&gt;
			&lt;eb:CPAId&gt;20160214:SE1234567890:SE9876543210&lt;/eb:CPAId&gt;
			&lt;eb:ConversationId&gt;20160214:4567:SE1234567890&lt;/eb:ConversationId&gt;
			&lt;eb:Service&gt;urn:oasis:names:tc:ebxml-msg:service&lt;/eb:Service&gt;
			&lt;eb:Action&gt;Acknowledgment&lt;/eb:Action&gt;
			&lt;eb:MessageData&gt;
				&lt;eb:MessageId&gt;bba2674a-4bf3-453e-a129-4f2a2da7f004@b2b.qvalia.com&lt;/eb:MessageId&gt;
				&lt;eb:Timestamp&gt;2016-02-14T08:56:56.390Z&lt;/eb:Timestamp&gt;
				&lt;eb:RefToMessageId&gt;20160214-102030-28572@foretag.se&lt;/eb:RefToMessageId&gt;
			&lt;/eb:MessageData&gt;
		&lt;/eb:MessageHeader&gt;
		&lt;eb:Acknowledgment SOAP:mustUnderstand=&quot;1&quot; eb:version=&quot;2.0&quot;
      SOAP:actor=&quot;urn:oasis:names:tc:ebxml-msg:actor:toPartyMSH&quot;&gt;
			&lt;eb:Timestamp&gt;2016-02-14T08:56:56.390Z&lt;/eb:Timestamp&gt;
			&lt;eb:RefToMessageId&gt;20160214-102030-28572@foretag.se&lt;/eb:RefToMessageId&gt;
			&lt;eb:From&gt;
				&lt;eb:PartyId eb:type=&quot;countrycode:organizationid&quot;&gt;SE9876543210&lt;/eb:PartyId&gt;
			&lt;/eb:From&gt;
		&lt;/eb:Acknowledgment&gt;
	&lt;/SOAP:Header&gt;
	&lt;SOAP:Body xsi:schemaLocation=&quot;http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd
    http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd&quot;/&gt;
&lt;/SOAP:Envelope&gt;</div></code></pre></div><div class="slate-TableCellElement-resizableWrapper" contenteditable="false"><div style="position:relative;user-select:auto;width:100%;height:100%;box-sizing:border-box;flex-shrink:0" ><div><div  style="position:absolute;user-select:none;width:10px;height:calc(100% + 12px);top:-12px;cursor:col-resize;right:-5px;z-index:20"></div></div></div><div class="slate-TableCellElement-handle"></div></div><div class="slate-TableCellElement-selectedCell" contenteditable="false"></div></td></tr></tbody></table><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p>

For Swedish operators Qvalia can offer support for the legacy formats Svefaktura 1.0 (Basic Invoice) as well as Svefaktura 2 (Peppol BIS2/4A).

 for the Swedish legacy formats. SFTP transportation can also be accepted, and configured, for any Operator who wants to send legacy formats.

 instead of legacy formats, but we do understand that some older systems still needs to fall back on older versions of specifications, and we try our best to meet the needs of our customers.

Please reach out to peppol@qvalia.com if you are an Operator who wants to use any of the legacy formats!

SFTI Transportprofil Bas 2.0 is an old and not supported standard, but as some companies and Operators in Sweden still cling to it Qvalia has the option of POST'ing Transportprofil Bas 2.0 over HTTP.

As we would like to follow the recommendation of the Swedish Government and the IT authorities of Sweden we have deprecated the usage of Svefaktura, and try to move all our customers over to Peppol.

After the 1st of March 2021, no new established Svefaktura connections should be added according to DIGG's recommendations and mandate 

. See article from SFTI/DIGG here (in Swedish) for more information: 

<p>The Partner API contains endpoints for usage of accounts and setup of accounts</p><p>Under the Partner API section you'll find information about the endpoints used by Partners to Qvalia and how to handle the various functions offered.</p><p></p><div><div></div></div>

The Partner API contains endpoints for usage of accounts and setup of accounts

Under the Partner API section you'll find information about the endpoints used by Partners to Qvalia and how to handle the various functions offered.