Articles in this section

Available Concur Invoice and Concur Expense DI objetcs

Naga Sri Hari Gonaboyina
Updated

Concur Invoice DI objects

The following objects are available when using Concur Invoice as a source in Celigo Data Integration (DI).

Primary key: Most Concur Invoice DI objects use a top-level id as the primary key (Common: Lists, User: Spend extension, User: Travel extension). The exception is Invoice payment confirmation, which keys on requestId.

Note

SAP Concur Invoice does not expose a deleted-records feed for these objects. Users are deactivated rather than physically deleted and remain retrievable via the API; payment-confirmation records are historical and are not removed; and list entries that are removed simply stop appearing in results rather than being returned with a deleted flag.

Object API endpoint Available extract modes Delta field
Common: Lists (v4) Get all lists Full —
Invoice payment confirmation (v4) Retrieve historical invoice payments Full, Incremental payStatusFromDate
User: Spend extension (v4.1) Retrieve all spend users in a company Full —
User: Travel extension (v4) Retrieve the information of a SAP Concur travel user Full —

Response schemas

Click an object below to view its response fields and delta configuration.

Common: Lists (v4) — Get all lists

Response schema:

Field Type
id string (Primary key)
value string
levelCount number
searchCriteria string
displayFormat string
category object
category.id string
category.type string
isReadOnly boolean
isDeleted boolean
Invoice payment confirmation (v4) — Retrieve historical invoice payments

Delta configuration: use it to request incremental data.

Setting Value
Delta filter payStatusFromDate = {{{lastExportDateTime}}}
Date format YYYY-MM-DD

Response schema:

Field Type
requestId string (Primary key)
invoiceNumber string
requestName string
purchaseOrderNumber string
paymentMethodType string
paymentAmount number
paymentAdjustmentNotes string
paymentStatusDate string
checkNumber string
paymentStatus string
supplierName string
vendorCode string
vendorAddressCode string
paymentDemandId string
fundingInitiationDate string
fundingSettlementDate string
returnInitiationDate string
returnSettlementDate string
paymentInitiationDate string
paymentSettlementDate string
cashAccountCode string
liabilityAccountCode string
batchId string
fundingSourceReference string
fundingRequestReference string
providerPaymentMethod string
thirdPartyReference string
invoiceCurrency string
fundingCurrency string
paymentCurrency string
foreignExchangeRate number
User: Spend extension (v4.1) — Retrieve all spend users in a company

Response schema:

Field Type
id string (Primary key)
externalId string
userName string
displayName string
title string
active boolean
name object
name.formatted string
name.familyName string
name.givenName string
name.middleName string
emails objectarray
emails.value string
emails.type string
emails.primary boolean
User: Travel extension (v4) — Retrieve the information of a SAP Concur travel user

Response schema:

Field Type
id string (Primary key)
externalId string
userName string
displayName string
title string
active boolean
name object
name.formatted string
name.familyName string
name.givenName string
name.middleName string
emails objectarray
emails.value string
emails.type string
emails.primary boolean

Concur Expense DI objects

The following objects are available when using Concur Expense as a source in Celigo Data Integration (DI).

Primary key: All Concur Expense DI objects use a top-level ID as the primary key (Allocations, Attendee types, Attendees, Digital tax invoices, Entry-attendee associations, Itemizations, Reports). Concur's v3.0 Expense APIs return a unique ID on every object, so ID is the consistent key across resources.

Note

SAP Concur Expense does not expose a deleted-records feed for these objects. Expense reports and related records move through workflow/approval status transitions rather than being physically removed, and records that are deleted simply stop appearing in search results rather than being returned with a deleted flag.

Object API endpoint Available extract modes Delta field
Expense: Allocations Retrieve all allocations per entry or report Full —
Expense: Attendee types Retrieve all attendees types Full —
Expense: Attendees Retrieve all attendees owned by the specified user Full —
Expense: Digital tax invoices Retrieve all digital tax invoices that can be validated by the user based on the search criteria Full, Incremental modifiedAfter
Expense: Entry attendee association Retrieve all digital tax invoices that can be validated by the user based on the search criteria Full —
Expense: Itemizations Get all expense itemizations Full —
Expense: Reports Retrieve reports owned by the user based on search criteria Full, Incremental modifiedDateAfter

Response schemas

Click an object below to view its response fields and delta configuration.

Expense: Allocations — Retrieve all allocations per entry or report

Response schema:

Field Type
ID string (Primary key)
Percentage number
URI string
Expense: Attendee types — Retrieve all attendees types

Response schema:

Field Type
ID string (Primary key)
AllowAttendeeCountEditing boolean
AllowManuallyEnteredAttendees boolean
AttendeeFormID string
ConnectorID string
DuplicateSearchFields array
Code string
Name string
URI string
Expense: Attendees — Retrieve all attendees owned by the specified user

Response schema:

Field Type
ID string (Primary key)
AttendeeTypeID string
Company string
CurrencyCode string
ExternalID string
FirstName string
LastName string
MiddleInitial string
Suffix string
Title string
TotalAmountYTD number
URI string
Expense: Digital tax invoices — Retrieve all digital tax invoices that can be validated by the user based on the search criteria

Delta configuration: use it to request incremental data.

Setting Value
Delta filter modifiedAfter = {{{lastExportDateTime}}}
Date format YYYY-MM-DDTHH:mm:ss

Response schema:

Field Type
ID string (Primary key)
Comment string
Status string
URI string
Expense: Entry attendee association — Retrieve all digital tax invoices that can be validated by the user based on the search criteria

Response schema:

Field Type
ID string (Primary key)
Amount number
AssociatedAttendeeCount number
AttendeeID string
Custom1 string
Custom2 string
Custom3 string
Custom4 string
Custom5 string
EntryID string
URI string
Expense: Itemizations — Get all expense itemizations

Response schema:

Field Type
ID string (Primary key)
Comment string
Description string
EntryID string
ExpenseTypeCode string
IsBillable boolean
IsPersonal boolean
OrgUnit1 string
OrgUnit2 string
OrgUnit3 string
OrgUnit4 string
OrgUnit5 string
OrgUnit6 string
TransactionAmount number
TransactionDate string
URI string
Expense: Reports — Retrieve reports owned by the user based on search criteria

Delta configuration: use it to request incremental data.

Setting Value
Delta filter modifiedDateAfter = {{{lastExportDateTime}}}
Date format YYYY-MM-DDTHH:mm:ss

Response schema:

Field Type
ID string (Primary key)
Name string
Purpose string
PolicyID string
Comment string
UserDefinedDate string
AmountDueCompanyCard number
AmountDueEmployee number
ApprovalStatusCode string
ApprovalStatusName string
ApproverLoginID string
ApproverName string
Country string
CountrySubdivision string
CreateDate string
CurrencyCode string
EverSentBack boolean
HasException boolean
LedgerName string
OwnerLoginID string
OwnerName string
PaymentStatusCode string
PaymentStatusName string
PersonalAmount number
ProcessingPaymentDate string
ReceiptsReceived boolean
SubmitDate string
Total number
TotalApprovedAmount number
TotalClaimedAmount number
URI string
WorkflowActionUrl string