Release calendar​

No new features or changes have been introduced to the API for release 9.6.5.​

Release calendar​

Receipt API​

Rest API SCIM department master role with Buyer privilege.​

In the 9.6.2, we introduced a new API functionality “Extension of SCIM Rest API to import default department master role on user”. This new API functionality allows department roles to be added to users imported via the SCIM user interface via Rest API using a default department. In this way not all department roles will need to be imported, as the default department is picked from the user details, see 9.6.2 release notes.

Currently, if a department master role contains the Buyer privilege (open the department master role and go to the tab access privilege where the Buyer privilege is switched on) and this department – master role is imported via the SCIM, the user will only get this master role added on that department. The user will not be able to create requisitions on this department as then the Buyer master role needs be added to department.

In this release we have changed this. When a department master role has the access privilege added of Buyer, the Buyer role will automatically be added to the user when this master role is imported via SCIM.

So, in the above example, the master role “Assistant Manager” is having the access privilege Buyer switched on. After doing a SCIM import on department A-3000 with Master role Assistant Manager the Buyer role is also added automatically to department A-3000 and the user is allowed to use this department in a requisition.

Release calendar​

No new features or changes have been introduced to the API for release 9.6.3.​

Release calendar​

Receipt API​

Extension of SCIM Rest API to import default department master role on user.​

Currently it is only possible to import users with department roles via the SCIM user interface via Rest API. This is done via a group having the department – master role relation. As the set of data of the department – master role information can be very large, adding a user to each group needed can become very complex. For organisations only using one department per user we have made the SCIM user import more straightforward and easier to work with. In addition to the employee number, the SCIM user will need to be uploaded with a Department ID. This department ID will be store in the "Office" field in the Proactis user profile. The Proactis department roles will be added as groups in SCIM without the department UUID. When a user is added as a member to a group without a department UUID but only a role, the user will be linked using that role to the department saved in the Proactis user profile.

Release calendar​

No new features or changes have been introduced to the API for release 9.6.1.​

Release calendar​

No new features or changes have been introduced to the API for release 9.5.12.​

Release calendar​

Receipt API​

Export via GET including or excluding Doctype​

The function of including or excluding the doctype in the Receipt export has been added in this release. This function can be enabled or disabled via the "Receipt Communication Settings" endpoint.

“includeDoctype”: false

Must be added if the Doctype should not be included in the receipt export.

By default, the Doctype is added, so if the Doctype is required then this setting is not needed.

Release calendar​

Contract API​

Start and enddate in contract export​

In the contract export API the start and end date did not have the proper dates but were one day earlier. This has been changed.

Release calendar​

Contract API​

New endpoint Contract Export​

In this release a new endpoint is created for the Contract Export.

/{domainId}/contracts

Provides high level information for a set number of contracts.

Path Parameters

DomainID - string - required

Sortfield - string

SortOrder - string

PageNumber - integer

PageSize - integer

ContractNumber - string

ContractName - string

ContractStatus - array

ContractType - string

SupplierNumber - string

SupplierName - string

EndDateFrom - string($date-time)

EndDateTo - string($date-time)

LastModifiedFrom - string($date-time)

/{domainId}/contracts/{contractNumber}/{contractVersion}

Provides detailed information per contract

Path Parameters

DomainID - string - required

ContractNumber - string - required

ContractVersion - string - required

/{domainId}/contracts/{contractId}

Provides detailed information per contract, same as above only now by ContractId.

Path Parameters

DomainID - string - required

ContractId - string - required

The new Endpoints will be added in the integration documentation during next weeks.

Release calendar​

No new features or changes have been introduced to the API for release 9.5.8.​

Release calendar​

No major new features or changes have been introduced to the API for release 9.5.7.​

This release focuses on addressing some minor bugs.​

Release calendar​

Order/Invoice API​

Invoice, supplier order and ERP order export via Rest API​

To prevent invoices, supplier orders and ERP orders from being sent more than once within a short period of time, a check is built in to check whether invoices (with the same status), supplier orders or ERP orders have already been submitted in the past minute. If an invoice or order is presented again within that minute, it will not be sent again via the Rest API.

Release calendar​

Order API​

ESIZEJEE-8838 Order Cancellation sending order to supplier​

For customers using Biztalk integration on organisation level, it is possible to use Rest API on supplier level with the setting Supplier Order Export Via API in the supplier profile.

This setting allows the system to export the orders, changed orders and cancelled orders to this specific supplier via Rest API while the organisation is set up to export orders via Biztalk.

Currently, when cancelling an order in Proactis S2P, the order cancelation is not exported to the suppliers with the setting Supplier Order Export Via API enabled. This is resolved with 9.5.5.

ESIZEJEE-8913 Addition of OCI Attributes in the supplier order export​

For OCI catalogue, a mapping is created to map OCI fields to P9 fields, not all the OCI fields are used for the order but are needed by the supplier. With this release we are adding all the OCI attribute fields to the Rest API order export to the supplier per line item in < ItemDetail > when available for OCI products only.

            <Extrinsic name="ProactisContractNumber">C58317</Extrinsic>
            <Extrinsic name="NEW_ITEM-CURRENCY">EUR</Extrinsic>
            <Extrinsic name="NEW_ITEM-CUST_FIELD1">21.00</Extrinsic>
            <Extrinsic name="NEW_ITEM-CUST_FIELD2">441200</Extrinsic>
            <Extrinsic name="NEW_ITEM-CUST_FIELD4">21.00</Extrinsic>
            <Extrinsic name="NEW_ITEM-CUST_FIELD5">0.21</Extrinsic>
            <Extrinsic name="NEW_ITEM-DESCRIPTION">Poly-line afvalzak 38 my 60x80cm</Extrinsic>
            <Extrinsic name="NEW_ITEM-MANUFACTCODE">1000011414</Extrinsic>
            <Extrinsic name="NEW_ITEM-PRICE">29.34</Extrinsic>
            <Extrinsic name="NEW_ITEM-PRICEUNIT">1</Extrinsic>
            <Extrinsic name="NEW_ITEM-QUANTITY">3.0000</Extrinsic>
            <Extrinsic name="NEW_ITEM-UNIT">box</Extrinsic>
            <Extrinsic name="NEW_ITEM-VATPERCENTAGE_SINGLEBASE">21.00</Extrinsic>
            <Extrinsic name="NEW_ITEM-VENDORMAT">1000011414</Extrinsic>

Order API​

ESIZEJEE-8934 Receipt export with a more than 4 decimals quantity​

Previously, for Rest API exported receipts, when the quantity had more than 4 decimals they were giving a 500 error. This is corrected with 9.5.5, receipts can now be exported with Rest API with quantities having up to 6 decimals.

Release calendar​

Receipt API​

ESIZEJEE-8915 Receipt export with setting "includeAttachments"​

Previously, for rest API exported receipt, when the webhook for receipts exports in the swagger pages the attribute "includeAttachments" was added, it was ignored when set up to false.

This is corrected with 9.5.4, if the attribute "includeAttachments" is set to false, receipts attachment will not be included when the receipts are exported.

Release calendar​

Order API​

ESIZEJEE-8896 City added in Address information in Rest API order pdf not using custom order pdf​

Previously, for rest API exported orders, the city in the address information was missing when the custom order pdf template was not used and the default template was used.

This is corrected with 9.5.3, all the address information now contains the city in the PDF.

Release calendar​

Order API​

INTEG-2866 New endpoint: Cancel Order​

In this release we are adding the function to cancel an order via the new Cancel Order function.

A new Endpoint is created: Cancel order

Path Parameters:

DomainID – string – required

proactisOrderNumber – string – required

Body:

Comment – string - required

Similar to when cancelling an order in Proactis it is only possible to cancel an order with status 'Ordered', 'Rejected', or 'Confirmed', else a 400 error will show.

When the order is cancelled successful the 200 code will be received with "Order is successfully canceled!"

The order will get status ‘Cancelled’, the order lines will be changes with price 0, VAT not defined (0%) and quantity 0 and the cancelation comment is added in the comment details where the Author is added as “import import”.

The requisition get status ‘Cancelled’, but the lines will not change.

The new Endpoint will be added in the integration documentation during next weeks.

Release calendar​

Invoice API​

INTEG-2905 cXML : response without the DOCTYPE”​

In 9.4.11, we introduced the attribute” includeDocType=false”

Some SRP systems do not support the DOCTYPE in the cXML messages. To allow integration with these systems, the addition of the attribute” includeDocType=false” to the communication settings disables the DICTYPE in the cXML.

As standard process the DOCTYPE is added to the cXML response for invoice export.

Again, some parties are not able to return the DOCTYPE in the cXML response. To send a cXML response without the DOCTYPE, if in the communication settings we have attribute” includeDocType=false, the format of the cXML response should be:

<?xml version="1.0" encoding="UTF-8"?>
<cXML payloadID="1628239652567.37776.32900@proactis.com" timestamp="2021-08-06T10:47:32-10:47" xml:lang="en">
    <Response>
        <Status code="200" text="OK"/>
    </Response>
</cXML>

Receipt API​

ESIZEJEE-8778 : Workforce receipts not being exported via Rest API”​

Prior to 9.5.1, Workforce receipts were not automatically exported via Rest API, this has been corrected with 9.5.1.

Release calendar​

No major new features or changes have been introduced to the API for release 9.4.12.​

This release focuses on addressing some minor bugs.​

Release calendar​

Supplier API​

INTEG-2601: Addition of 3 new supplier statuses in Vendor import and export​

3 new supplier statuses have been added to the vendor status in Vendor import and export.

• One time supplier > XML Value > One-Time-Supplier
• Black list > XML Value > Black-List
• Project bound > XML Value > Project-Bound

The possible values now are: Empty, Preferred, Alternative, Strategic, Excellent, Prospect, One-Time-Supplier, Black-List, Project-Bound, No Preference, Not-Accepted and Not-Creditable.

cXML sample:

Invoice API​

INTEG-2791: Eliminate difference between Procurement and Workforce PO invoice export​

As preannounced in the previous release notes, when exporting an invoice there is a difference between the export of a PO invoice of workforce and of procurement.

Workforce version of the invoice: cXML/Request/InvoiceDetailRequest/InvoiceDetailOrder/InvoiceDetailServiceItem

Procurement version of the invoice: cXML/Request/InvoiceDetailRequest/InvoiceDetailOrder/InvoiceDetailItem

In this release we are making the two versions the same and use: cXML/Request/InvoiceDetailRequest/InvoiceDetailOrder/InvoiceDetailItem

INTEG-2877 : Communication Settings attribute: “includeDocType=false”​

As standard process the DOCTYPE is added to the cXML for invoice export. Some SRP systems do not support the DOCTYPE in the cXML messages. To allow integration with these systems, the addition of the attribute” includeDocType=false” to the communication settings will disable the DICTYPE in the cXML.

includeDocType=false NOT in the invoice export setting

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cXML SYSTEM "http://xml.cxml.org/schemas/cXML/1.2.051/InvoiceDetail.dtd">
<cXML payloadID="20241025055600010.31364.92354@proactiscloud.com" timestamp="2024-10-25T05:56:10+0200" xml:lang="en-US">

includeDocType=false added the invoice export setting

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<cXML payloadID="20241025055300046.31364.46259@proactiscloud.com" timestamp="2024-10-25T05:53:46+0200" xml:lang="en-US">

Release calendar​

Preannouncement release 9.4.11​

When exporting an invoice there is a difference between the export of a PO invoice of workforce and of procurement.

Workforce version of the invoice: cXML/Request/InvoiceDetailRequest/InvoiceDetailOrder/InvoiceDetailServiceItem

Procurement version of the invoice: cXML/Request/InvoiceDetailRequest/InvoiceDetailOrder/InvoiceDetailItem

In release 9.4.11 we want to make the two versions the same and use: cXML/Request/InvoiceDetailRequest/InvoiceDetailOrder/InvoiceDetailItem

Supplier API​

INTEG-2845: Behaviour specific cXML fields when not included in import​

Customer sometimes like to configure certain elements in the UI. Usually because the supplier data source doesn't contain the required data. Currently when importing all fields must be added and populated to make sure the values will remain. We have changed this behaviour for Spending pool, Commodity code, Invoice Matching Method, Vendor Group and Value Added Tax.

• When this cXML element is not included: the existing value will not change
• If the cXML element is included: the data of the field will be updated
• If the cXML element is included but empty: the data of the field will be removed

Spending Pool & Commodity Code

<Commodity>
   <Classification domain="SpendingPool" code="4000">Name of SpendingPool</Classification>
</Commodity>
<Commodity>
   <Classification domain="CommodityCode" code="4010">Name of CommodityCode</Classification>
</Commodity>

Invoice Matching Method

<Extrinsic name="ProactisInvoiceMatchingMethod">3Way</Extrinsic>

Vendor Group

<Extrinsic name="ProactisSupplierGroup">Name of SupplierGroup</Extrinsic>

Value Added Tax

<Extrinsic name="ProactisApplyValueAddedTax">false</Extrinsic>

Order API​

INTEG-2838: ERP limit orders have quantity and price set to zero​

ERP limit orders were having zero set as a value for quantity and price. This has been changes so the ERP order export for limit orders will contain the correct values for quantity, price and total values.

INTEG-2643: Improved smart form processing for order import​

This release further improves smart form processing when smart forms are connected to a catalog and/or supplier. Duplicate extra fields and missing parents will result in an error message.

INTEG-2829: Order import order creation date is not correct​

When importing an order the date used for the requisition would always be the specified date/time. However the order would have a creation date which is equal to the current date/time. This has been corrected. Both the requisition and order will have the same date/time, as specified in the order import message.

INTEG-2775 Order import on contract added to financial information​

In the previous release we add the possibility to add a contract on an order line. Now when this contract has financial information added and the creation date of the order falls within the start- and enddate of the financial information, the orderline spend will be added to the financial information and the spend and balance information will be adjusted.

Release calendar​

Accounting API​

INTEG-2825: Department address endpoints support address name with slash​

The addressName is part of the URL for the GET, PUT and DELETE methods of the department address endpoints. Previously these didn't support a slash in the addressName value, when you did it returned a 404-error. This error has been resolved.

INTEG-2826: Error message when request body contains invalid elements​

The accounting service would return an Invalid request body passed message when the ID element was part of the request body. The ID is supposed to be part of the request URL. The release updates the error message to a better understandable one.

Supplier API​

INTEG-2818: Supplier Extra Info field is missing in cXML​

In some case an Extra Info field was missing when exporting a supplier. This release fixes this issue and makes sure all Extra Info fields are added to the cXML.

Requisition API​

INTEG-2743: Introducing a scope for OAuth 2 authorization​

Sometimes an OAuth 2 token service requires a specific scope to be set in the token request. This release adds the option to add one or multiple scopes to the OAuth 2 token request.

To add a scope to the OAuth 2 token request, add this to the communication settings by adding the scope attribute as shown below. When using multiple scopes, separate those by spaces.

"authentications": [
{
   "type": "OAUTH2",
   "clientId": "clientId",
   "clientSecret": "clientSecret",
   "scope": "https://company.com/scope1 https://company.com/scope2",
   "tokenUrl": "https://company.com/oauth2/token"
}

Order API​

INTEG-2772: Internal ID of a catalog product added​

A catalog product can have multiple identifiers. Currently only the main one, the Product ID is added to the order cXML. This release adds a new element BuyerPartID to the cXML which will contain the Internal ID of a catalog product.

<ItemOut quantity="1.0000" lineNumber="1" requestedDeliveryDate="2024-08-27T00:00:00">
   <ItemID>
      <SupplierPartID>889387</SupplierPartID>
      <BuyerPartID>000001734921</BuyerPartID>
   </ItemID>
   <ItemDetail>
      <UnitPrice>
         <Money currency="EUR">1.0000</Money>
      </UnitPrice>
      <Description xml:lang="en">
         <ShortName>Red Pen</ShortName>
      </Description>
      <UnitOfMeasure></UnitOfMeasure>
      <PriceBasisQuantity quantity="0.0100" conversionFactor="1">
         <UnitOfMeasure></UnitOfMeasure>
      </PriceBasisQuantity>

INTEG-2773: Manufacturer Product ID of a catalog product added​

A catalog product can have multiple identifiers. Up till this release only the Product ID was added to the order cXML. The Internal ID has been added and described in the change above. This release also adds the Manufacturer Product ID to the order cXML. For this a new element SupplierPartAuxiliaryID will be added to the order cXML.

<ItemOut quantity="1.0000" lineNumber="1" requestedDeliveryDate="2024-08-27T00:00:00">
   <ItemID>
      <SupplierPartID>889387</SupplierPartID>
      <SupplierPartAuxiliaryID>PENRED001</SupplierPartAuxiliaryID>
      <BuyerPartID>000001734921</BuyerPartID>
   </ItemID>
   <ItemDetail>
      <UnitPrice>
         <Money currency="EUR">1.0000</Money>
      </UnitPrice>
      <Description xml:lang="en">
         <ShortName>Red Pen</ShortName>
      </Description>
      <UnitOfMeasure></UnitOfMeasure>
      <PriceBasisQuantity quantity="0.0100" conversionFactor="1">
         <UnitOfMeasure></UnitOfMeasure>
      </PriceBasisQuantity>

INTEG-2765: Add a contract number to the order import​

This release adds the option to specify a contract number when importing orders. To add a contract number, add an Extrinsic element with the name ProactisContractNumber to the product line.

Before you use this functionality, make sure the assigned catalog allows contract references. Also the contract has to be active and linked to the correct supplier.

<ItemOut quantity="10.0000" lineNumber="1" requestedDeliveryDate="2024-06-08T12:00:00" isAdHoc="yes">
   <ItemID>
      <SupplierPartID>FF1</SupplierPartID>
   </ItemID>
   <ItemDetail>
      <UnitPrice>
         <Money currency="EUR">10.0000</Money>
      </UnitPrice>
      <Description xml:lang="en">Blue Pen 22 cm
         <ShortName>Blue Pen</ShortName>
      </Description>
      <UnitOfMeasure>PCE</UnitOfMeasure>
      <PriceBasisQuantity quantity="1.0000" conversionFactor="1">
         <UnitOfMeasure>PCE</UnitOfMeasure>
      </PriceBasisQuantity>
      <Classification domain="" code=""></Classification>
      <Extrinsic name="ProactisContractNumber">C1000000068</Extrinsic>
   </ItemDetail>

INTEG-2393: Improved smart form processing for order import​

This release adds improved processing for smart forms connected to a catalog and/or supplier. Missing, but mandatory smart forms will result in an error message.

Receipt API​

INTEG-2746: Introducing a scope for OAuth 2 authorization​

Sometimes an OAuth 2 token service requires a specific scope to be set in the token request. This release adds the option to add one or multiple scopes to the OAuth 2 token request.

To add a scope to the OAuth 2 token request, add this to the communication settings by adding the scope attribute as shown below. When using multiple scopes, separate those by spaces.

"authentications": [
{
   "type": "OAUTH2",
   "clientId": "clientId",
   "clientSecret": "clientSecret",
   "scope": "https://company.com/scope1 https://company.com/scope2",
   "tokenUrl": "https://company.com/oauth2/token"
}

INTEG-2749: Quantitative receipt status will be checked during import​

When importing a receipt you can specify the Quantitative receipt status. This value is currently not checked against a predefined configurable list (menu Procurement > Receiving statuses). This release introduces a check and will return an error when the value is not specified in the predefined list.

<Classification domain="ItemReceivingCondition" code="Delivery is ok">Delivery is ok</Classification>

INTEG-2830: Correct deploymentMode on production​

The deploymentMode used on our production environment was to set to test as a default value. This has been updated and on production the deploymentMode is now set to production.

Invoice API​

INTEG-2747: Introducing a scope for OAuth 2 authorization​

Sometimes an OAuth 2 token service requires a specific scope to be set in the token request. This release adds the option to add one or multiple scopes to the OAuth 2 token request.

To add a scope to the OAuth 2 token request, add this to the communication settings by adding the scope attribute as shown below. When using multiple scopes, separate those by spaces.

"authentications": [
{
   "type": "OAUTH2",
   "clientId": "clientId",
   "clientSecret": "clientSecret",
   "scope": "https://company.com/scope1 https://company.com/scope2",
   "tokenUrl": "https://company.com/oauth2/token"
}

Timecard API​

INTEG-2748: Introducing a scope for OAuth 2 authorization​

Sometimes an OAuth 2 token service requires a specific scope to be set in the token request. This release adds the option to add one or multiple scopes to the OAuth 2 token request.

To add a scope to the OAuth 2 token request, add this to the communication settings by adding the scope attribute as shown below. When using multiple scopes, separate those by spaces.

"authentications": [
{
   "type": "OAUTH2",
   "clientId": "clientId",
   "clientSecret": "clientSecret",
   "scope": "https://company.com/scope1 https://company.com/scope2",
   "tokenUrl": "https://company.com/oauth2/token"
}

Release calendar​

Preannouncement release 9.4.9​

When importing a receipt you can specify the Quantitative receipt status. This value is currently not checked against a predefined configurable list (menu Procurement > Receiving statuses). Release 9.4.9 (September) will introduce a check and will return an error when the value is not specified in the predefined list.

<Classification domain="ItemReceivingCondition" code="Delivery is ok">Delivery is ok</Classification>

Accounting API​

INTEG-2183: Endpoints no longer return an 404-error when value contains slash​

The ID of Cost Accounts, Cost Centers, Cost Dimensions or Departments can contain slashes and using those in the URL of the API endpoint would result in an 404-error. This error has been resolved.

Please note that slashes in values are only allowed in the last variable part of the URL.

For instance: GET ​/{domainId}​/costdimensions​/{costDimensionId}​/values​/{costDimensionValueId} The {costDimensionId} variable can not contain a slash. However the {costDimensionValueId} variable can contain a slash.

INTEG-2774: 500-error when updating cost center​

In few cases updating a cost center would result in a 500 (Internal Server Error) response. This error has been resolved, the cost center is now successfully updated and a proper response is returned.

Supplier API​

INTEG-2735: GET returns invalid cXML​

Bank accounts added to a supplier record are part of the supplier cXML. When using a GET method to retrieve supplier data, the returned cXML was because some mandatory elements were missing. These elements have been added according to the cXML DTD.

 <PaymentInformation>
   <PaymentMethodRemittanceInformation>
      <Contact role="payee">
         <Name xml:lang="en">Supplier Ltd.</Name>
         <PostalAddress>
            <Street />
            <City>London</City>
            <Country isoCountryCode="" />
         </PostalAddress>
         <IdReference identifier="GB65BARC20038015941114" domain="ibanID"/>
         <Extrinsic name="ProactisDefaultAccount">true</Extrinsic>
      </Contact>
   </PaymentMethodRemittanceInformation>
</PaymentInformation>

Requisition API​

INTEG-2704: Endpoint to retrieve requisitions has been added​

A new endpoint has been added to retrieve requisitions. This includes the use of filters.

The endpoint will return a list of requisitions matching the filters. To get the requisition details each item from the result list has to be requested individually.

Order API​

INTEG-2744: Introducing a scope for OAuth 2 authorization​

Sometimes an OAuth 2 token service requires a specific scope to be set in the token request. This release adds the option to add one or multiple scopes to the OAuth 2 token request.

To add a scope to the OAuth 2 token request, add this to the communication settings by adding the scope attribute as shown below. When using multiple scopes, separate those by spaces.

"authentications": [
{
   "type": "OAUTH2",
   "clientId": "clientId",
   "clientSecret": "clientSecret",
   "scope": "https://company.com/scope1 https://company.com/scope2",
   "tokenUrl": "https://company.com/oauth2/token"
}

Invoice API​

INTEG-2767: Error while exporting Invoice Capture invoices in Concept​

Invoices which were to be exported in status Concept and are created by Invoice Capture caused an error due to an invalid cXML. This error has been resolved.

INTEG-2726: Timesheet numbers for workforce based invoices added​

Invoices based on a workforce order will now list the timesheet(s) which are linked to the invoice lines. Each invoice line can contain one or multiple timesheets. The week number of the timesheet is the value between parenthesis.

      <Extrinsic name="ProactisReceiptNumber">Rec_1000002357</Extrinsic>
      <Extrinsic name="ProactisTimesheet">TS1000123_00(34)</Extrinsic>
      <Extrinsic name="ProactisInvoicedCompletely">true</Extrinsic>
   </InvoiceDetailServiceItem>
</InvoiceDetailOrder>

INTEG-281: Adding the last date/time of approval​

The invoice cXML message currently displays all kinds of important process timestamps. This functionality was introduced in the previous release but under certain circumstances showed an incorrect date/time. This has been resolved..

      <PaymentInformation paymentNetDueDate="2024-05-22T10:00:00+02:00"/>
      <Extrinsic name="ProactisStatus">Processed</Extrinsic>
      <Extrinsic name="ProactisInvoiceNumber">INV100018667</Extrinsic>
      <Extrinsic name="ProactisCreationDate">2024-05-22T09:51:00+02:00</Extrinsic>
      <Extrinsic name="ProactisApprovalDate">2024-05-22T12:03:04+02:00</Extrinsic>
      <Extrinsic name="ProactisProcessedDate"></Extrinsic>
    </Extrinsic>
  </InvoiceDetailRequestHeader>
<InvoiceDetailOrder>

INTEG-2811: Support for slashes in supplier invoice numbers​

This release adds support for slashes in supplier invoices numbers when updating the invoice payment data. Previously this would return an 404-error.

Please note that slashes in values are only allowed in the last variable part of the URL.

For instance: PUT ​/{domainId}​/{supplierNumber}​/{supplierInvoiceNumber} The {supplierNumber} variable can not contain a slash. However the {supplierInvoiceNumber} variable can contain a slash.

Release calendar​

Generic​

INTEG-2625: Error notifications by mail​

Widgets are available to keep track of imported and exported messages. For every message the widget shows the last known status. When volume rises it might become hard to keep track of all the messages and make sure that errors are processed correctly.

This release adds the possibility to send error notifications by email. A notification will be sent for each message returning an error. Add up till 5 email addresses per widget.

Order API​

INTEG-2707: Import orders endpoint adds support for supplier comments​

The order import API includes functionality to add comments to an order. These comments are currently not shared with the supplier. This release adds functionality to share the comments on the imported order with the supplier.

To add comments which should be shared with the supplier, simply add the type="supplier" attribute to the Comments element. When this attribute is missing comments will not be shared with the supplier.

   </Contact>
   <Comments type="supplier">Comments to be shared with supplier</Comments>
   <IdReference identifier="20240612-001" domain="OrderReference"/>
   <Extrinsic name="ProactisSendSupplierOrder">true</Extrinsic>
   <Extrinsic name="ProactisSendERPOrder">true</Extrinsic>
</OrderRequestHeader>

INTEG-2761: Incorrect values calculation for imported orders when VAT is disabled​

This release fixes a bug in the order import endpoint where line and header values were calculated incorrectly when VAT was disabled on organisation level.

INTEG-2754: User ID of the Buyer has been added​

This release adds the User ID of the buyer to the order cXML. For this a new Extrinsic element with the name ProactisUserId has been added to the Contact segment.

<Contact role="buyer">
  <Name xml:lang="en">John Doe</Name>
  <Email>john@doe.com</Email>
  <Phone>
    <TelephoneNumber>
      <CountryCode isoCountryCode="NL"/>
      <AreaOrCityCode></AreaOrCityCode>
      <Number>012-3456789</Number>
      <Extension></Extension>
    </TelephoneNumber>
  </Phone>
  <Extrinsic name="ProactisUserId">johndoe</Extrinsic>
</Contact>

INTEG-2751: Adding a unique supplier account number per department​

Sometimes suppliers require a specific value (for example an account number) to be added to orders. For this we have added functionality to add an attribute on department level of which the value will be added to orders created for this specific supplier.

To use this functionality, add an attribute AccountNumber_{suppliernumber} to the department where the stringvalue is equal to the value which has to be added to the cXML order. A new Extrinsic element with the name ProactisAccountNumber will be added to the cXML.

<Contact role="supplierCorporate">
  <Name xml:lang="en">Supplier B.V.</Name>
  <PostalAddress name="supplierCorporate">
    <Street>Damrak 1</Street>
    <City>Amsterdam</City>
    <PostalCode>1000 AB</PostalCode>
    <Country isoCountryCode="NL">Nederland</Country>
  </PostalAddress>
  <Email name="Order">inkoop@supplier.com</Email>
  <IdReference identifier="NL123456789B01" domain="vatID"/>
  <IdReference identifier="98765432" domain="companyRegistrationNumber"/>
  <Extrinsic name="ProactisAccountNumber">SomeValue</Extrinsic>
</Contact>

Receipt API​

INTEG-2740: Incorrect status for imported receipts​

This release fixes a status difference between imported receipts and those which are manually created. Previously the Receipt Status was incorrect and the delivery status for the line was empty.

Invoice API​

INTEG-2737: ProactisProcessedDate contains invalid timestamp​

Until this release the ProactisProcessedDate Extrinsic element would contain the date/time of export when the invoice did not yet reach the Cleared status. This release changes this behavior, only when the invoice is in Cleared status the ProactisProcessedDate Extrinsic will contain a date/time.

  <Extrinsic name="ProactisProcessedDate">2024-06-24T08:32:17+02:00</Extrinsic>
</InvoiceDetailRequestHeader>
<InvoiceDetailOrder>
  <InvoiceDetailOrderInfo>

  <Extrinsic name="ProactisProcessedDate"></Extrinsic>
</InvoiceDetailRequestHeader>
<InvoiceDetailOrder>
  <InvoiceDetailOrderInfo>

INTEG-2736: Adding the last date/time of approval​

The invoice cXML message currently displays all kinds of important process timestamps. In this release we will be adding the timestamp on which the last approval has been done. For this the Extinsic element with name ProactisApprovalDate has been added. The element value will remain empty if no approval has been done.

      <PaymentInformation paymentNetDueDate="2024-05-22T10:00:00+02:00"/>
      <Extrinsic name="ProactisStatus">Processed</Extrinsic>
      <Extrinsic name="ProactisInvoiceNumber">INV100018667</Extrinsic>
      <Extrinsic name="ProactisCreationDate">2024-05-22T09:51:00+02:00</Extrinsic>
      <Extrinsic name="ProactisApprovalDate">2024-05-22T12:03:04+02:00</Extrinsic>
      <Extrinsic name="ProactisProcessedDate"></Extrinsic>
    </Extrinsic>
  </InvoiceDetailRequestHeader>
<InvoiceDetailOrder>

Release calendar​

Supplier API​

INTEG-2707: Audit log shows incorrect values for imported suppliers​

When updating a supplier through the API and changing the Online Status, this would not reflect correctly in the Audit Log. This has been corrected in this release.

User API​

INTEG-2738: Patch operations have been made case insensitive​

PATCH operations of the Users endpoints used to be case sensitive. To better support IAM application like Entra ID (formerly Azure AD) the operations have been made case insensitive.

INTEG-2739: Add search for groups based on displayName​

A new filter called displayName had been added to the Groups endpoints to allow searches based on displayName.

Order API​

INTEG-2699: TaxableAmount is wrongly displayed when PriceBasisQuantity is not 1​

The TaxableAmount value was not displayed properly when the price of a catalog item would be based on multiple products (PriceBasisQuantity not equal to 1). This has been fixed and the TaxableAmount element now displays the correct value.

<ItemOut quantity="5.0000" lineNumber="1">
   <ItemID>
      <SupplierPartID>FF1</SupplierPartID>
   </ItemID>
   <ItemDetail>
      <UnitPrice>
         <Money currency="EUR">8.9877</Money>
      </UnitPrice>
      <Description xml:lang="en">Dove original multi package                        
         <ShortName>Dove Multi</ShortName>
      </Description>
      <UnitOfMeasure></UnitOfMeasure>
      <PriceBasisQuantity quantity="4.0000" conversionFactor="1">
         <UnitOfMeasure></UnitOfMeasure>
      </PriceBasisQuantity>
      <Classification domain="" code=""></Classification>
   </ItemDetail>
   <Tax>
      <Money currency="EUR">1.1235</Money>
      <Description xml:lang="en">PLI Tax</Description>
      <TaxDetail category="tax" percentageRate="10.0000" taxRateType="VAT10.0">
         <TaxableAmount>
            <Money currency="EUR">11.2346</Money>
         </TaxableAmount>
         <TaxAmount>
            <Money currency="EUR">1.1235</Money>
         </TaxAmount>
         <TaxLocation xml:lang="en"></TaxLocation>
      </TaxDetail>
   </Tax>
   <Distribution>
      <Accounting name="CostCoding">
         ....
      </Accounting>
      <Charge>
         <Money currency="EUR">12.3581</Money>
      </Charge>
   </Distribution>
</ItemOut>

INTEG-2710: ERP order does not contain comments which are not send to supplier​

When a buyer creates a requisition the buyer can include comments and select whether these comments are to be shared with the supplier. These comments were only included in the ERP order when the checkmark "Show To Supplier" was selected, but not when the "Show To Supplier" checkbox was not selected. This has been fixed.

<Comments>This is an internal comment
   <Attachment>
      <URL>cid:00096253.pdf</URL>
   </Attachment>
</Comments>

INTEG-2641: Add checks for unique extra fields names​

Importing an order with Smart Forms fields on line level have now extra checks to validate the name of the Smart Form field and make sure it's unique. Imported orders with duplicate Smart Form names will return an error upon sending the request.

<Extrinsic name="Concerns a requisition for">Hardware</Extrinsic>
<Extrinsic name="Type of request - Hardware">New</Extrinsic>
<Extrinsic name="Type of hardware">Standard Notebook (incl. keyboard + mouse + bag)</Extrinsic>

INTEG-2433: Catalog product information is used during order import​

The order import API just supported free format products. This release adds support for catalog products. Whenever the product exists for the specified supplier in a catalog, those product details will be used. This means the pricing details, VAT and cost coding values used in the XML will be overwritten by the values used in the catalog while creating the order.

INTEG-2727: Retrying an order import would not export the same to ERP and/or supplier​

Whenever an order fails to import due to a functional error, this order would be shown in the widget and could be reprocessed. Reprocessing the order would however not send the order to the ERP application and/or supplier. This issue has been resolved.

Receipt API​

INTEG-2700: Rounding issues in receipt export​

For product lines which have a UnitPrice which is based on multiple products the receipt would display incorrect values for the UnitPrice and ReceivedAmount elements. This issue has been resolved.

         <ReceiptItem receiptLineNumber="1" quantity="5.0000" completedIndicator="yes">
            <ReceiptItemReference lineNumber="1">
               <ItemID>
                  <SupplierPartID>FF1</SupplierPartID>
               </ItemID>
               <Description xml:lang="en-US">Dove original multi pack
                  <ShortName>Dove Multi</ShortName>
               </Description>
               <ReferenceDocumentInfo>
                  ...
               </ReferenceDocumentInfo>
            </ReceiptItemReference>
            <UnitRate>
               <Money currency="EUR">8.9877</Money>
               <UnitOfMeasure></UnitOfMeasure>
               <PriceBasisQuantity quantity="4.0000" conversionFactor="1.0000">
                  <UnitOfMeasure></UnitOfMeasure>
               </PriceBasisQuantity>
            </UnitRate>
            <ReceivedAmount>
               <Money currency="EUR">11.2346</Money>
            </ReceivedAmount>
            <DeliveryAddress>
               ...
            </DeliveryAddress>
            <Classification domain="ItemReceivingCondition" code="Delivery is not ok">Delivery is not ok</Classification>
            <Extrinsic name="ProactisOrderedQuantity">5.0000</Extrinsic>
         </ReceiptItem>
      </ReceiptOrder>
   <Total>
      <Money currency="EUR">11.2346</Money>
   </Total>
</ReceiptRequest>

Release calendar​

Supplier API​

INTEG-2590: Creation and modified timestamp are added to supplier message​

Two new Extrinsic elements have been added to the supplier message to show the timestamps for the creation date and last modified date of the supplier.

            <Extrinsic name="ProactisDateCreated">2020-07-05T09:12</Extrinsic>
            <Extrinsic name="ProactisDateModified">2024-04-12T15:33</Extrinsic>
         </Organization>
      </OrganizationDataResponse>
   </Response>
</cXML>

INTEG-2688: Order locale becomes mandatory when order email address is specified​

Whenever the Extrinsic with the name ProactisOrderEmail is included in the supplier import message, the ProactisOrderLocale will become mandatory. Currently ProactisOrderLocale is optional. The locale is required to send orders by email to the supplier.

<Extrinsic name="ProactisOrderEmail">orders@northwestgoods.com</Extrinsic>
<Extrinsic name="ProactisOrderLocale">en_US</Extrinsic>

Requisition API​

This release introduces the new budget endpoint. This endpoint works in conjunction with the requisition API and is used when an external application is used for budget approval.

For more information read the requisition API documentation.

Order API​

INTEG-2651: Mark imported orders​

An order imported by the API is now marked as being an imported order. When the same order is exported the Extrinsic element with the name ProactisImportStatus will be set to true.

   <Extrinsic name="ProactisImportStatus">true</Extrinsic>
</OrderRequestHeader>

Invoice API​

INTEG-2695: Duplicate cost dimensions on invoice line level​

A bug has been resolved where cost dimensions would be duplicated on line level of NON-PO invoice. In those cases the same cost dimension would also have been specified on header level.

INTEG-2692: Code and Swift Code are added to the supplier message for type "Bank"​

This release adds the Code and Swift (BIC) Code to the supplier export message whenever the bank type BANK is selected.

<PaymentInformation>
   <PaymentMethodRemittanceInformation preferredPaymentMethod="other">
      <Contact role="payee">
         <Name xml:lang="en">Northwest Goods</Name>
         <PostalAddress>
            <City>London</City>
         </PostalAddress>
         <IdReference identifier="55555555" domain="accountID"/>
         <IdReference identifier="BARCGB22XXX" domain="swiftID"/>
         <IdReference identifier="202015" domain="bankNationalID"/>
         <Extrinsic name="ProactisDefaultAccount">false</Extrinsic>
      </Contact>

Release calendar​

Preannouncement release 9.4.5​

Release 9.4.5 will introduce a breaking change to the supplier import endpoint (POST ​/{domainId}). Whenever the Extrinsic with the name ProactisOrderEmail is included in the supplier import message, the ProactisOrderLocale will become mandatory. Currently ProactisOrderLocale is optional. The locale is required to send orders by email to the supplier.

<Extrinsic name="ProactisOrderEmail">orders@northwestgoods.com</Extrinsic>
<Extrinsic name="ProactisOrderLocale">en_US</Extrinsic>

Accounting API​

INTEG-2269 : Add additional sorting options for the departments endpoint​

The GET departments endpoint (GET ​/{domainId}​/departments) now supports additional sorting options. Sorting can be done based on name, description, online flag, parentId, id and lastModified.

INTEG-2271 : Add additional sorting options for the cost account endpoint​

The GET cost account endpoint (GET ​/{domainId}​/costdimensions​/CostAccount​/values) now supports additional sorting options. Sorting can be done based on id, description, online flag, lastModified, erpId and type.

Supplier API​

INTEG-2598 : Indicator to show the supplier is managed by Source-to-Contract​

When using the Source-to-Contract module to manage (part) of your suppliers, these suppliers will contain a new Extrinsic element called ProactisS2CSupplier. Its value will be true whenever Source-to-Contract is the source of this supplier.

          <Extrinsic name="ProactisOnlineFlag">true</Extrinsic>
          <Extrinsic name="ProactisStatusOfVendor">Preferred</Extrinsic>
          <Extrinsic name="ProactisS2CSupplier">true</Extrinsic>
        </Organization>
      </OrganizationDataResponse>
    </Response>
  </cXML>

INTEG-2639 : Support for multiple order mail addresses​

Adding multiple order mail address to a supplier would result in a 406 Not Acceptable error. This release adds support for multiple order mail addresses. Each mail address is to be separated by a semicolon.

                <Extrinsic name="ProactisOrderEmail">address1@domain.com;address2@domain.com</Extrinsic>
                <Extrinsic name="ProactisOrderEmailDoNotAttachPDF">true</Extrinsic>
                <Extrinsic name="ProactisOrderEmailDoNotAttachXML">true</Extrinsic>
                <Extrinsic name="ProactisOrderLocale">en_US</Extrinsic>
            </Organization>
        </OrganizationChangeMessage>
    </Message>
</cXML>

INTEG-2636 : Add Registered Chamber of Commerce to the message​

This release adds support for the Registered Chamber of Commerce field to the import and export message. A new Extrinsic element with the name ProactisRegisteredChamberOfCommerce will be added with the value.

          <Extrinsic name="ProactisRegisteredChamberOfCommerce">Amsterdam</Extrinsic>
        </Organization>
      </OrganizationDataResponse>
    </Response>
  </cXML>

User API​

INTEG-2568 : Check locale when adding or updating an user​

Validation on the locale set in the SCIM user message has been updated. Only supported languages will be allowed in the user message, other locales will result in a 400 error. A valid example of a locale would be nl, nl-NL or nl_NL.

Requisition API​

This release introduces the new requisition API. This API has currently one endpoint to configure the communication settings to receive requisitions from Proactis. An upcoming release will be adding the budget check response.

For more information read the requisition API documentation.

Order API​

INTEG-2623 : Add supplier GLN number to the order message​

Supplier can have multiple identifiers, the GLN number is one of them. The GLN number is stored on the Address info tab of the supplier.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cXML SYSTEM "http://xml.cxml.org/schemas/cXML/1.2.051/cXML.dtd">
<cXML version="1" payloadID="20240216135400024.31124.77768@proactiscloud.us" timestamp="2024-02-16T13:54:20" xml:lang="nl">
   <Header>
      <From>
         <Credential domain="NetworkId">
            <Identity>Demo</Identity>
         </Credential>
      </From>
      <To>
         <Credential domain="NetworkId">
            <Identity>SUP001</Identity>
         </Credential>
         <Credential domain="GLN">
            <Identity>1234567890123</Identity>
         </Credential>            
      </To>
      <Sender>
         <Credential domain="NetworkId">
            <Identity>Proactis</Identity>
            <SharedSecret></SharedSecret>
         </Credential>
         <UserAgent>proactis-eu-agent</UserAgent>
      </Sender>
   </Header>

INTEG-2624 : Add organisation GLN number to the order message​

The organisation (buyer) can have multiple identifiers, the GLN number is one of them. Whenever the ship to address used for the order has a GLN number, this element will be added to the order cXML message.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cXML SYSTEM "http://xml.cxml.org/schemas/cXML/1.2.051/cXML.dtd">
<cXML version="1" payloadID="20240216135400024.31124.77768@proactiscloud.us" timestamp="2024-02-16T13:54:20" xml:lang="nl">
   <Header>
      <From>
         <Credential domain="NetworkId">
            <Identity>Demo</Identity>
         </Credential>
         <Credential domain="GLN">
            <Identity>9876543210987</Identity>
         </Credential>
      </From>
      <To>
         <Credential domain="NetworkId">
            <Identity>SUP001</Identity>
         </Credential>
      </To>
      <Sender>
         <Credential domain="NetworkId">
            <Identity>Proactis</Identity>
            <SharedSecret></SharedSecret>
         </Credential>
         <UserAgent>proactis-eu-agent</UserAgent>
      </Sender>
   </Header>

INTEG-2496 : Additional Smart Form validations added​

This release adds additional Smart Form validations to the order import. Whenever only one Smart Form is linked to the supplier or catalog, mandatory fields will be checked for.

INTEG-2443 : Introduce calculation of line and order totals for order import​

As pre-announced, this release will introduce a major change to the way the order import endpoint (POST ​/{domainId}) works. Up till this release the total amounts on line and header level use the XML input as its source. This release changes this as the total amounts on line and header level will be calculated based on the line level values.

Receipt API​

INTEG-2588 : Closing order lines or the entire order for receiving​

The cXML receipt message can contain two optional attributes which can close individual order lines or the entire order for further receiving.

The ReceiptOrder element can contain an attribute called closeForReceiving=yes. Upon adding this attribute to the receipt message the entire order will be closed for receiving.

For closing individual order lines, one can add the completedIndicator=yes attribute to the ReceiptItem element. This will close the order line.

<Request deploymentMode="production">
   <ReceiptRequest>
      <ReceiptRequestHeader receiptID="REC-00086952-001" receiptDate="2024-01-29T10:00:00" />
         <ReceiptOrder closeForReceiving="yes">
            <ReceiptOrderInfo>
               <OrderReference orderID="00086952" orderDate="2024-01-29T09:11:18">
                  <DocumentReference payloadID="20240129091100021.21296.78144@proactiscloud.us"/>
               </OrderReference>
            </ReceiptOrderInfo>
            <ReceiptItem receiptLineNumber="1" quantity="5.0000" completedIndicator="yes">
               <ReceiptItemReference lineNumber="1">

INTEG-2633 : Importing receipt lines with a different unit of measurement​

When the Unit of Measure used in the receipt import message is different from the one used in the order, then the receipt import is successful but you can not manually create an additional receipt for the same order. An error screen would be displayed. This release fixes this issue.

Invoice API​

INTEG-2622 : Invoice attachment order adjusted​

Invoices containing attachments are send as a multipart request. Like the cXML, other attachments are added to the requests as "parts". The order in which the attachments were added to the multipart request was random which made it hard to figure out which was the invoice copy.

This change implements sorting. The PDF-attachment which is displayed in the UI will always be the first PDF-attachment, but will be preceded by XML-attachments.

Release calendar​

Contract API​

INTEG-2494 : New endpoint to retrieve contract Classifications​

This release will add a new endpoint to retrieve Classifications which are configured in Proactis: GET ​/{domainId}​/classifications. A Classification is a mandatory element when importing a contract.

The Classification endpoint uses pagination whenever the results list exceeds the page size. Check the pagination page for more information.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:page xmlns:ns2="http://api.proactis.com/common" xmlns:ns3="http://api.proactis.com/contracts">
  <ns2:pageNumber>0</ns2:pageNumber>
  <ns2:pageSize>25</ns2:pageSize>
  <ns2:totalElements>58</ns2:totalElements>
  <ns2:content>
    <classification>
      <name>Marketing and Communication</name>
      <description>Marketing and Communication Contracts</description>
      <type>Regular Contract</type>
      <online>true</online>
      <ns2:templates>
        <template>
          <name>Audit Template</name>
          <description>Audit Template</description>
          <online>true</online>
        </template>
      </ns2:templates>
    </classification>
    ....
  </ns2:content>
</ns2:page>

{
  "pageNumber": 0,
  "pageSize": 25,
  "totalElements": 58,
  "content": [
    {
      "name": "Marketing and Communication",
      "description": "Marketing and Communication Contracts",
      "type": "Regular Contract",
      "online": true,
      "templates": [
        {
          "name": "Audit Template",
          "description": "Audit Template",
          "online": true
        }
      ]
    },
    ...
  ]
}

INTEG-2495 : New endpoint to retrieve contract additional fields​

This release will add a new endpoint to retrieve additional fields for templates which are configured in Proactis: GET /{domainId}/template/{templateName}. Usually a templates and its additional fields are mandatory when importing a contract.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns3:template xmlns:ns2="http://api.proactis.com/common" xmlns:ns3="http://api.proactis.com/contracts">
  <name>Audit Template</name>
  <description>Audit Template</description>
  <online>true</online>
  <ns2:additionalFields>
    <additionalField>
      <name>Yearly audit</name>
      <description>Is a yearly audit to be done</description>
      <online>true</online>
      <type>TEXT_SINGLE</type>
      <ns2:possibleValues>
        <possibleValue>true</possibleValue>
        <possibleValue>false</possibleValue>
      </ns2:possibleValues>
      <ns2:defaultValues>
        <defaultValue>false</defaultValue>
      </ns2:defaultValues>
      <required>true</required>
    </additionalField>
    <additionalField>
      <name>Audit month</name>
      <description>In which month is the audit expected</description>
      <online>true</online>
      <parent>Yearly audit</parent>
      <type>TEXT_SINGLE</type>
      <ns2:possibleValues/>
      <ns2:defaultValues/>
      <required>false</required>
    </additionalField>
  </ns2:additionalFields>
</ns3:template>

{
  "template": {
    "name": "Audit Template",
    "description": "Audit Template",
    "online": true,
    "additionalFields": {
      "additionalField": [
        {
          "name": "Yearly audit",
          "description": "Is a yearly audit to be done",
          "online": true,
          "type": "TEXT_SINGLE",
          "possibleValues": {
            "possibleValue": [
              "true",
              "false"
            ]
          },
          "defaultValues": "false",
          "required": true
        },
        {
          "name": "Audit month",
          "description": "In which month is the audit expected",
          "online": true,
          "parent": "Yearly audit",
          "type": "TEXT_SINGLE",
          "possibleValues": "",
          "defaultValues": "",
          "required": false
        }
      ]
    }
  }
}

Invoice API​

INTEG-2567 : Add the contract number to the individual invoice lines​

Whenever a contract is added to a requisition this was already shown in the ERP and supplier order XML. The invoice cXML didn't have this information added to the individual lines. This release adds two new Extrinisic elements, one with the Proactis assigned contract number and the other with your contract reference.

<ItemDetail>
  <UnitPrice>
    <Money currency="EUR">11.0000</Money>
  </UnitPrice>
  <Description xml:lang="en">
    <ShortName>Pen Blue</ShortName>
  </Description>
  <UnitOfMeasure>PCE</UnitOfMeasure>
  <PriceBasisQuantity quantity="1.0000" conversionFactor="1">
    <UnitOfMeasure>PCE</UnitOfMeasure>
  </PriceBasisQuantity>
  <Classification domain="" code=""></Classification>
  <Extrinsic name="ProactisContractNumber">C1000000154</Extrinsic>
  <Extrinsic name="ProactisContractReference">stationary</Extrinsic>
</ItemDetail>

INTEG-2596 : Add receipt references to individual invoice lines​

PO based invoices usually have one or more receipts. This release adds the receipt number to each invoice line. The number of receipts per invoice line can vary, multiple is possible.

    <Distribution>
      <Accounting name="CostCoding">
        <Segment type="DepartmentId" id="A-7000" description="A070 - Customer support"/>
        <Segment type="CostCenterType" id="001" description="Regular Cost Centers"/>
        <Segment type="CostCenterId" id="CC001" description="Central Procurement"/>
        <Segment type="CostAccountId" id="CA3003" description="ICT software"/>
      </Accounting>
      <Charge>
        <Money currency="EUR">121.0000</Money>
      </Charge>
    </Distribution>
    <Extrinsic name="ProactisReceiptNumber">Rec_1000002217</Extrinsic>
  </InvoiceDetailItem>
</InvoiceDetailOrder>

Order API​

INTEG-2612 : GET order returns a 500 error​

In some cases, when address information doesn't exist on the order, the GET endpoint to retrieve an individual order would return a 500 error. This has been fixed and the order should be retrieved as expected.

Receipt API​

INTEG-2603 : Receipt import requests were sometimes returning a 400 error​

When the receipt ID contained special characters a 400-error could be returned. This error has been resolved and receipts containing special characters should now be processed fine.

Supplier API​

INTEG-2543 : Add default order cost account to supplier​

The release adds support for a default order cost account on supplier level. The API requires the cost account to be present to be added to the supplier profile, but if won't fail in case the cost account does not exist.

<Extrinsic name="ProactisDefaultCostAccount">CA123456</Extrinsic>

INTEG-2602 : Default bank account not set​

When trying to update a supplier with a default bank account number this would sometimes fail and no default bank account would be set. This issue has been resolved and a default bank account should now be set in case the XML contains an Extrinsic with the name ProactisDefaultAccount set to true. Only one bank account can be set as default.

<PaymentInformation>
  <PaymentMethodRemittanceInformation preferredPaymentMethod="other">
    <Contact role="payee">
      <Name xml:lang="en">Company Ltd 1</Name>
      <PostalAddress>
        <Street></Street>
        <City>London</City>
        <Country isoCountryCode=""></Country>
      </PostalAddress>
      <IdReference identifier="GB94BARC10201530093459" domain="ibanID"/>
      <Extrinsic name="ProactisDefaultAccount">true</Extrinsic>
    </Contact>
  </PaymentMethodRemittanceInformation>
  <PaymentMethodRemittanceInformation preferredPaymentMethod="other">
    <Contact role="payee">
      <Name xml:lang="en">Company Ltd</Name>
      <PostalAddress>
        <Street></Street>
        <City>London</City>
        <Country isoCountryCode=""></Country>
      </PostalAddress>
      <IdReference identifier="NL91ABNA0417164300" domain="ibanID"/>
      <Extrinsic name="ProactisDefaultAccount">false</Extrinsic>
    </Contact>
  </PaymentMethodRemittanceInformation>
</PaymentInformation>