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 an Invoice PDF

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

Poll for and get enrichment

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

Get individual enrichment result

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

SFTP-Integration

Custom format

Sending and receiving

Error handling

Processed files

Consolidation

Dynamic Routing

Operator

Sample Data

Qvalia API

Production

Production server.

Sandbox server for testing.

Sandbox

Create from Order

Get status

Internetbank (Sweden only)

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 class="slate-p " >APIs related to invoice handling</p><p class="slate-p " ></p><p class="slate-p " ></p>

<p class="slate-p " >APIs related to credit note handing</p><p class="slate-p " ></p><p class="slate-p " ></p>

<p class="slate-p " >APIs related to order handing</p><p class="slate-p " ></p><p class="slate-p " ></p>

<p class="slate-p" placeholder="Type / for widgets">APIs related to order response handing</p><p class="slate-p" placeholder="Type / for widgets"></p>

<p class="slate-p" placeholder="Type / for widgets">APIs related to order change handing</p><p class="slate-p" placeholder="Type / for widgets">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 class="slate-p" placeholder="Type / for widgets">Message Syntax: <a href="https://docs.peppol.eu/poacc/upgrade-3/syntax/OrderChange/tree/" target="_blank">https://docs.peppol.eu/poacc/upgrade-3/syntax/OrderChange/tree/</a></p><p class="slate-p" placeholder="Type / for widgets"></p>

Order Change is part of Advanced Ordering 3.0: 

<p class="slate-p" placeholder="Type / for widgets">APIs related to order cancellation handing</p><p class="slate-p" placeholder="Type / for widgets">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 class="slate-p" placeholder="Type / for widgets">Message Syntax: <a href="https://docs.peppol.eu/poacc/upgrade-3/syntax/adv-order-cancellation-3.0/tree/" target="_blank">https://docs.peppol.eu/poacc/upgrade-3/syntax/adv-order-cancellation-3.0/tree/</a></p><p class="slate-p" placeholder="Type / for widgets"></p>

APIs related to order cancellation handing

<p class="slate-p" placeholder="Type / for widgets">APIs related to catalogue handing</p><p class="slate-p" placeholder="Type / for widgets"></p>

<p class="slate-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 class="slate-p " ></p><p class="slate-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 " >The Enrichment API provides a powerful service for processing and digitizing invoice documents. It offers automated conversion of PDF invoices into structured digital formats, specifically Peppol XML/UBL JSON documents, using AI technology.</p><p class="slate-p " >Key Features:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Single and batch invoice processing</div></li><li class="slate-li " ><div style="position:relative">Asynchronous processing with polling mechanism</div></li><li class="slate-li " ><div style="position:relative">Conversion to Peppol/UBL standard format</div></li><li class="slate-li " ><div style="position:relative">Comprehensive error and warning reporting</div></li></ul><p class="slate-p " >The API follows a two-step process:</p><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative">Upload: Submit invoice files with specified enrichment types</div></li><li class="slate-li " ><div style="position:relative">Retrieval: Poll for results using the provided polling ID</div></li></ol><p class="slate-p " >Authentication is managed through account registration numbers issued by Qvalia, required for all API calls. The service is available in both production and sandbox environments for testing purposes. <strong class="slate-bold">Enrichment API has a separate subscription plan and is only accessible by invitation.</strong></p><p class="slate-p " >This API is ideal for businesses looking to automate their invoice processing workflow and achieve compliance with Peppol standards.</p><p class="slate-p " ></p>

The Enrichment API provides a powerful service for processing and digitizing invoice documents. It offers automated conversion of PDF invoices into structured digital formats, specifically Peppol XML/UBL JSON documents, using AI technology.

Authentication is managed through account registration numbers issued by Qvalia, required for all API calls. The service is available in both production and sandbox environments for testing purposes. 

Enrichment API has a separate subscription plan and is only accessible by invitation.

This API is ideal for businesses looking to automate their invoice processing workflow and achieve compliance with Peppol standards.

<p class="slate-p " >The Partner API contains endpoints for usage of accounts and setup of accounts</p><p class="slate-p " >Under the Partner API section you&apos;ll find information about the endpoints used by Partners to Qvalia and how to handle the various functions offered.</p><p class="slate-p " ></p><div style="width:100%;
	min-width:100%;" class="callout-widget" data-type=info ><div class="callout-icon"><svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M10.0628 14.1676C10.2434 14.1676 10.3927 14.1086 10.5107 13.9905C10.6288 13.8725 10.6878 13.7232 10.6878 13.5426V9.77177C10.6878 9.6051 10.6253 9.46274 10.5003 9.34469C10.3753 9.22663 10.2295 9.1676 10.0628 9.1676C9.88227 9.1676 9.73296 9.22663 9.61491 9.34469C9.49685 9.46274 9.43783 9.61205 9.43783 9.7926V13.5634C9.43783 13.7301 9.50033 13.8725 9.62533 13.9905C9.75033 14.1086 9.89616 14.1676 10.0628 14.1676ZM10.0003 7.62594C10.1948 7.62594 10.358 7.56344 10.4899 7.43844C10.6219 7.31344 10.6878 7.15371 10.6878 6.95927C10.6878 6.76482 10.6219 6.59816 10.4899 6.45927C10.358 6.32038 10.1948 6.25094 10.0003 6.25094C9.80588 6.25094 9.64269 6.32038 9.51074 6.45927C9.3788 6.59816 9.31283 6.76482 9.31283 6.95927C9.31283 7.15371 9.3788 7.31344 9.51074 7.43844C9.64269 7.56344 9.80588 7.62594 10.0003 7.62594ZM10.0003 18.3343C8.81977 18.3343 7.72255 18.1225 6.70866 17.6989C5.69477 17.2752 4.81283 16.6884 4.06283 15.9384C3.31283 15.1884 2.72602 14.3065 2.30241 13.2926C1.8788 12.2787 1.66699 11.1815 1.66699 10.0009C1.66699 8.83427 1.8788 7.74399 2.30241 6.7301C2.72602 5.71621 3.31283 4.83427 4.06283 4.08427C4.81283 3.33427 5.69477 2.74399 6.70866 2.31344C7.72255 1.88288 8.81977 1.6676 10.0003 1.6676C11.167 1.6676 12.2573 1.88288 13.2712 2.31344C14.285 2.74399 15.167 3.33427 15.917 4.08427C16.667 4.83427 17.2573 5.71621 17.6878 6.7301C18.1184 7.74399 18.3337 8.83427 18.3337 10.0009C18.3337 11.1815 18.1184 12.2787 17.6878 13.2926C17.2573 14.3065 16.667 15.1884 15.917 15.9384C15.167 16.6884 14.285 17.2752 13.2712 17.6989C12.2573 18.1225 11.167 18.3343 10.0003 18.3343ZM10.0003 17.0843C11.9448 17.0843 13.6114 16.3898 15.0003 15.0009C16.3892 13.612 17.0837 11.9454 17.0837 10.0009C17.0837 8.05649 16.3892 6.38982 15.0003 5.00094C13.6114 3.61205 11.9448 2.9176 10.0003 2.9176C8.05588 2.9176 6.38921 3.61205 5.00033 5.00094C3.61144 6.38982 2.91699 8.05649 2.91699 10.0009C2.91699 11.9454 3.61144 13.612 5.00033 15.0009C6.38921 16.3898 8.05588 17.0843 10.0003 17.0843Z" fill="#3960B4"></path></svg></div><div ><p class="slate-p " ><strong class="slate-bold">Some Partner functions are partner specific and those are not documented here!</strong></p><p class="slate-p " >Reach out to your sales representative, or help@qvalia.com, to query about specific Partner functions, or if you can&apos;t find the information you need here.</p><p class="slate-p " ><strong class="slate-bold">All B2B/EDI functionality is developed, maintained and documented for each specific partner!</strong></p></div></div><p class="slate-p " ></p><p class="slate-p " >The Partner API is JSON only, so only <code class="slate-code">content-type: application/json</code> is used!</p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

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.

<p class="slate-p" placeholder="Type / for widgets">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 &quot;custom&quot; formats.</p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets">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><p class="slate-p" placeholder="Type / for widgets">Qvalia hosts an SFTP Server, and both sending and receiving is done through an SFTP client from your environment.</p><p class="slate-p" placeholder="Type / for widgets"></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 " >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 " ><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 " >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 " ></p><p class="slate-p " ><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 " ></p><p class="slate-p " >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 " >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 " >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="_self">https://sfti.se/sfti/standarder/rekommenderadestandarder/avfordameddelanden.52834.html</a></p><p class="slate-p " ></p><p class="slate-p " ></p><div class="table-container" style="width:100%;min-width:100%"><table class="slate-table" style="min-width:100%"><div class="published-table-header" style="width:100%;min-width:100%;min-height:initial;visibility: hidden;border:initial"><div style="width:100px;">Title</div></div><colgroup ><col style="width:initial"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><code class="slate-code"><strong class="slate-bold">Sample of a Transportprofil Bas 2.0 Envelope with Svefaktura</strong></code></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden">Content-Type: multipart/related; boundary="BoundarY"; type="text/xml";
soapaction: ebXML </textarea><code class="language-plainText keep-markup drop-tokens"></code></pre></div></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden">--BoundarY
Content-ID: <ebxhmheader1@avsandare.com>
Content-Type: text/xml

<?xml version="1.0" encoding="UTF-8"?>
<SOAP:Envelope xmlns:xlink="http://www.w3.org/1999/xlink"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
	xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"
	xsi:schemaLocation="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">
	<SOAP:Header>
	  <eb:MessageHeader SOAP:mustUnderstand="1" eb:version="2.0">
		  <eb:From>
			  <eb:PartyId eb:type="countrycode:organizationid">SE1234567890</eb:PartyId>
		  </eb:From>
			<eb:To>
			  <eb:PartyId eb:type="countrycode:organizationid">SE9876543210</eb:PartyId>
			</eb:To>
			<eb:CPAId>20160214:SE1234567890:SE9876543210</eb:CPAId>
			<eb:ConversationId>20160214:4567:SE1234567890</eb:ConversationId>
			<eb:Service>urn:sfti:services:documentprocessing:BasicInvoice</eb:Service>
			<eb:Action>incomingBasicInvoice</eb:Action>
		  <eb:MessageData>
			  <eb:MessageId>20160214-102030-28572@foretag.se</eb:MessageId>
				<eb:Timestamp>2016-02-14T11:12:12</eb:Timestamp>
			</eb:MessageData>
		</eb:MessageHeader>
		<eb:AckRequested SOAP:mustUnderstand="1" eb:version="2.0" eb:signed="false" SOAP:actor="urn:oasis:names:tc:ebxml-msg:actor:toPartyMSH"/>
		<eb:SyncReply eb:id="" eb:version="2.0" SOAP:mustUnderstand="1" SOAP:actor="http://schemas.xmlsoap.org/soap/actor/next">
		</eb:SyncReply>
	</SOAP:Header>
	<SOAP:Body>
	  <eb:Manifest eb:version="2.0">
		  <eb:Reference xlink:href="cid:ebxmlpayload1@avsandare.com" xlink:type="simple">
			  <eb:Description xml:lang="se">Fritext beskrivning av meddelande</eb:Description>
				<eb:Schema eb:location="urn:se:sfti:collaborationprocesses:BasicInvoice.xsd" eb:version="1.0"></eb:Schema>
			</eb:Reference>
		</eb:Manifest>
	</SOAP:Body>
</SOAP:Envelope>

--BoundarY
Content-ID: <ebxmlpayload1@avsandare.se>
Content-Type: text/xml

<?xml version="1.0" encoding="utf-8"?>
<StandardBusinessDocument xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHeader">
  <StandardBusinessDocumentHeader>
    <HeaderVersion>1.0</HeaderVersion>
    <Sender>
      <Identifier
        Authority="iso6523-actorid-upis">0088:7301234567890</Identifier>
    </Sender>
    <Receiver>
      <Identifier
        Authority="iso6523-actorid-upis">0007:1234567890</Identifier>
    </Receiver>
    <DocumentIdentification>
      <Standard>urn:oasis:names:specification:ubl:schema:xsd:Invoice-2</Standard>
      <TypeVersion>2.1</TypeVersion>
      <InstanceIdentifier>2016021401022</InstanceIdentifier>
      <Type>Invoice</Type>
      <CreationDateAndTime>2016-02-14T14:40:38.4644993+02:00</CreationDateAndTime>
    </DocumentIdentification>
    <BusinessScope>
      <Scope>
        <Type>DOCUMENTID</Type>
        <InstanceIdentifier>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</InstanceIdentifier>
      </Scope>
      <Scope>
        <Type>PROCESSID</Type>
        <InstanceIdentifier>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</InstanceIdentifier>
      </Scope>
    </BusinessScope>
  </StandardBusinessDocumentHeader>
  <Invoice xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2">
    <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>
    <cbc:ProfileID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</cbc:ProfileID>
    <cbc:ID>...</cbc:ID>
    <cbc:IssueDate>2016-02-14</cbc:IssueDate>
    <cbc:DueDate>2016-03-31</cbc:DueDate>
    <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
    <cbc:DocumentCurrencyCode>SEK</cbc:DocumentCurrencyCode>
    <cbc:BuyerReference>...</cbc:BuyerReference>
    <cac:AccountingSupplierParty>
      ...
    </cac:AccountingSupplierParty>
    <cac:AccountingCustomerParty>
      ...
    </cac:AccountingCustomerParty>
    <cac:PaymentMeans>
      ...
    </cac:PaymentMeans>
    <cac:PaymentTerms>
      ...
    </cac:PaymentTerms>
    <cac:TaxTotal>
      ...
    </cac:TaxTotal>
    <cac:LegalMonetaryTotal>
      ...
    </cac:LegalMonetaryTotal>
    <cac:InvoiceLine>
      ...
    </cac:InvoiceLine>
  </Invoice>
</StandardBusinessDocument>

--BoundarY––
 </textarea><code class="language-plainText keep-markup drop-tokens"></code></pre></div></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p slate-indent-0" style="0px"><code class="slate-code"><strong class="slate-bold">Sample of a Transportprofil Bas 2.0 Acknowledgement Response</strong></code></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"><?xml version="1.0" encoding="UTF-8"?>
<SOAP:Envelope
	xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://www.oasis-
  open.org/committees/ebxml-msg/schema/envelope.xsd"
	xmlns:eb="http://www.oasis-
  open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">
	<SOAP:Header xsi:schemaLocation="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">
		<eb:MessageHeader SOAP:mustUnderstand="1" eb:version="2.0">
			<eb:From>
				<eb:PartyId eb:type="countrycode:organizationid">SE1234567890</eb:PartyId>
			</eb:From>
			<eb:To>
				<eb:PartyId eb:type="countrycode:organizationid">SE9876543210</eb:PartyId>
			</eb:To>
			<eb:CPAId>20160214:SE1234567890:SE9876543210</eb:CPAId>
			<eb:ConversationId>20160214:4567:SE1234567890</eb:ConversationId>
			<eb:Service>urn:oasis:names:tc:ebxml-msg:service</eb:Service>
			<eb:Action>Acknowledgment</eb:Action>
			<eb:MessageData>
				<eb:MessageId>bba2674a-4bf3-453e-a129-4f2a2da7f004@b2b.qvalia.com</eb:MessageId>
				<eb:Timestamp>2016-02-14T08:56:56.390Z</eb:Timestamp>
				<eb:RefToMessageId>20160214-102030-28572@foretag.se</eb:RefToMessageId>
			</eb:MessageData>
		</eb:MessageHeader>
		<eb:Acknowledgment SOAP:mustUnderstand="1" eb:version="2.0"
      SOAP:actor="urn:oasis:names:tc:ebxml-msg:actor:toPartyMSH">
			<eb:Timestamp>2016-02-14T08:56:56.390Z</eb:Timestamp>
			<eb:RefToMessageId>20160214-102030-28572@foretag.se</eb:RefToMessageId>
			<eb:From>
				<eb:PartyId eb:type="countrycode:organizationid">SE9876543210</eb:PartyId>
			</eb:From>
		</eb:Acknowledgment>
	</SOAP:Header>
	<SOAP:Body xsi:schemaLocation="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"/>
</SOAP:Envelope> </textarea><code class="language-xml keep-markup drop-tokens"></code></pre></div></td></div></tr></tbody></table></div><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></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: 


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

Sections