Skip to main content

Celonis Product Documentation

Connecting to Coupa

You can connect your Coupa tenant to the Celonis Platform, allowing you to integrate your procurement, invoicing, expenses, and payment data. This connection is managed through the extractor builder, either using the Coupa cloud extractor template or a process connector template for specific accounts payable and purchase-to-pay processes. By connecting your Coupa tenant, you grant the Celonis Platform read-only access to your data, with any data shared through HTTPS, ensuring an encrypted information exchange.

For more information about using the process connector template to integrate your Coupa accounts payable and purchase-to-pay processes, see: Using process connector templates.

For a video overview of the process described in this topic:

 
Prerequisites for connecting to Coupa

Before connecting to your Coupa tenant, you must meet the following prerequisites:

  • OAuth: Coupa uses the OAuth 2.0 authentication method, meaning that you must create an OAuth client and have access to the client ID, client secret, and OIDC scope.

    You can create OAuth credentials by navigating to your Coupa instance OAuth page:

    https://<yourinstance>.coupahost.com/oauth2/clients

    For more information, see: Coupa Compass Documentation - OAuth 2.0 Transition Guide.

  • Allowlist Celonis Platform IPs and domains: If your Coupa instance is only reachable within a certain IP range, you need to allowlist the outbound IPs of the Celonis Platform, otherwise data cannot be extracted. The IPs of the Celonis Platform are different depending on the cluster (eu-1 or us-1).

    For more information, see: Allowlisting domain names and IP addresses

Creating a data connection between Coupa and the Celonis Platform

With access to your Coupa OAuth authentication credentials, you can create a data connection between your Coupa instance and the Celonis Platform from your data pool diagram:

  1. Click Data Connections.

    data_connections_within_data_pool_diagram.png

  2. Click Add Data Connection and select Connect to Data Source.

    add_data_connection.png

  3. Select Cloud - Coupa.

    Cloud_coupa.png

  4. Configure the following connection details:

    • Name: An internal reference for this data connection.

    • Tenant: Enter your Coupa tenant using the following format:

      https://yourtenant.coupacloud.com

    • API version: We recommend selecting the latest API version.

    • Authentication method - OAuth: Supply your Coupa OAuth client ID, client secret, and OICD scopes.

    • Advanced settings: Configure your pseudonymization algoritm and enable custom metadata if you want to extract custom tables and columns from Coupa. For more information, see: Adding custom tables and columns to Coupa extraction.

  5. Click Test Connection and correct any issues highlighted.

  6. Click Save.

    The connection between your Coupa tenant and the Celonis Platform is establised. You can manage this connection at any time by clicking options:

    manage_existing_coupa_connection.png
Supported API endpoints

When connecting your Coupa tenant to the Celonis Platform, the following API endpoints are supported. These endpoints are dependent on three sources:

  • Tables that are defined in a static definition of metadata.

  • Tables for which the metadata is dynamically retrieved from the API response.

  • Tables that are configured using the customize metadata JSON.

API

Table Name

Used in Accounts Payable Process

Used in Purchase-to-Pay Process

Addresses API

addresses

Nested tables:

  • addresses_tax_registrations

  • addresses_purposes

  • address_content_groups

Yes

Yes

Approvals API

approvals

Nested tables:

  • approvals_reasons

  • approvals_delegates

Yes

Yes

Business Groups API

business_groups

Yes

Yes

Contracts API

contracts

Nested tables:

  • contracts_reason_insight_events

  • contracts_tags

  • contracts_diversity_categories

  • contracts_taggings

  • contracts_current_parallel_approvals

  • contracts_contract_clauses

  • contracts_contract_terms

  • contracts_contract_parties

Yes

Yes

Departments API

departments

Yes

Yes

Inventory Transactions API

inventory_transactions

Nested tables:

  • inventory_transactions_attachments

  • inventory_transactions_inventory_transaction_lots

  • inventory_transactions_current_integration_history_records

  • inventory_transactions_asset_tags

  • inventory_transactions_account_allocations

  • inventory_transactions_inventory_transaction_valuations

No

No

Invoice Revision API

invoice_revision_records

Nested tables:

  • invoice_revision_records_invoice_lines

Yes

Yes

Invoices API

invoices

Nested tables:

  • invoices_invoice_charges

  • invoices_tags

  • invoices_failed_tolerances

  • invoices_attachments

  • invoices_payments

  • invoices_tcs_tax_lines

  • invoices_withholding_tax_lines

  • invoices_invoice_payment_receipts

  • invoice_lines

  • invoices_tax_lines

  • invoices_approvals

  • invoices_dispute_reasons

  • invoices_taggings

  • current_integration_history_records

  • invoices_payment_agreement_notes

  • revision_records_invoiceheader

Yes

Yes

Order Revisions API

order_revision_records

Nested tables:

  • order_revision_records_order_lines

Yes

Yes

Purchase Order Lines API

purchase_order_lines

Nested tables:

  • purchase_order_lines_account_allocations

  • purchase_order_lines_form_response

  • purchase_order_lines_attachments

  • purchase_order_lines_recurring_rules

  • purchase_order_lines_asset_tags

  • purchase_order_lines_milestones

Yes

Yes

Purchase Order Revisions API

purchase_order_revisions

Nested tables:

  • purchase_order_revision_order_lines

No

Yes

Purchase Orders API

purchase_orders

Nested tables:

  • purchase_orders_attachments

  • purchase_orders_recurring_rules

  • purchase_orders_reason_insight_events

  • purchase_orders_order_lines

  • purchase_orders_current_integration_history_records

  • purchase_orders_milestones

  • revision_records_orderheader

No

Yes

Requisition Revisions API

requisition_revision_records

Nested tables:

  • requisition_revision_records_requisition_lines

Yes

Yes

Requisitions API

requisitions

Nested tables:

  • requisitions_attachments

  • requisitions_current_parallel_approvals

  • requisitions_approvals

  • requisition_lines

  • requisitions_recurring_rules

  • requisitions_tags

  • requisitions_taggings

  • requisitions_milestones

  • requisition_lines_account_allocations

  • revision_records_requisitionheader

Yes

Yes

Supplier Items API

supplier_items

Yes

Yes

Suppliers API

suppliers

Nested tables:

  • suppliers_preferred_commodities

  • suppliers_remit_to_addresses

  • suppliers_supplier_addresses

  • suppliers_customer_support_contacts

  • suppliers_diversities

  • suppliers_taggings

  • suppliers_diversity_categories

  • suppliers_invoice_emails

  • suppliers_supplier_sites

  • suppliers_integration_contacts

  • suppliers_payment_terms

  • suppliers_restricted_account_types

  • suppliers_contacts

Yes

Yes

Users API

users

Nested tables:

  • users_working_warehouses

  • users_account_groups

  • users_roles

  • users_expenses_delegated_to

  • users_approval_groups

  • users_user_groups

  • users_inventory_organizations

  • users_can_expense_for

Yes

Yes