|The Concur Invoice Purchase Order (PO) web service allows clients to send PO-related data in order to identify and resolve match exceptions on invoices. Clients can use this data in a variety of ways, including:
|Works With These Concur Products|
|Concur Connect API Structure|
Refer to Web Services > Core Concepts for:
You must have the Concur Invoice product to use this web service.
Concur products are highly configurable, and not all clients will have access to all features.
Partner developers must determine which configurations are required for their solution prior to the application review process. Use the Developer Forum if you have questions about the configuration settings.
Existing clients can work with Concur Advantage Technical Services to create custom applications that work with their configuration.
The version 3.0 documentation includes the data model and tools to send test requests to your developer sandbox.
Invoice Purchase Order Errors
The web service will not return a 4xx HTTP response code for a batch operation even when every item in the batch failed to be created, updated or deleted. The client must inspect the response to look for warnings or errors with individual batch items.
XML Response Error Codes:
|1000||The PO number is missing or invalid.|
|2000||There was no vendor found for the supplied Vendor Code and Vendor Address Code.|
|3000||The Currency Code is missing or invalid.|
|4000||There was no policy found matching the supplied External Id.|
|4001||The policy does not support purchase orders.|
|4002||The policy cannot be changed on the purchase order.|
|5000||The purchase order does not contain any line items.|
|5001||The line item must contain expense type or account code, but not both.|
|5002||The line item expense type is invalid.|
|5003||The line item account code is invalid.|
|5004||The line item tax and unit price must both match positive or negative.|
|5500||The line item contains an allocation, but no allocation form is defined.|
|5501||The line item allocation amounts exceed the line item total.|
|5502||The distribution amounts for a line item must match the line item amount positive or negative.|
|5503||The distribution amounts for a line item cannot be zero.|
|5600||The external id for the line item is not unique across the purchase order.|
|6000||The Ship To Address is missing or invalid.|
|6001||The Bill To Address is missing or invalid.|
|8000||A required field is missing.|
|8001||A field’s value exceeds the maximum length allowed.|
|8002||A field’s value is not the correct data type.|
|8003||A field’s value is an invalid list item.|
|8004||A field’s value is an invalid connected list item.|
|8005||The Country Code is missing or invalid.|
|8006||A value was supplied for a field that is not part of the form.|
|9999||An unexpected error occurred.|
The following field codes are used for error codes in the 8000 range, and identify which field is causing an error. Typically field codes are used when validating an XML element's value against a form field’s configuration for the supplied policy.
The table below lists all the field codes and at what level they are available. For example: Custom1 can point to an element at the purchase order or line item level where as PoNumber would only display for the purchase order level.
Last Modified: 10/18/2013 11:16 AM PDT