Release Notes

October 2025

We have added a new column, kind, to the PURPOSE table.

We have added the following new columns to the SUPPLIER_INFORMATION_ADDRESS table:

account_type_item
address_name
bank_account_number
bank_address
bank_city
bank_code
bank_fax_phone_area_code
bank_fax_phone_country_code
bank_fax_phone_extension
bank_fax_phone_id
bank_fax_phone_number
bank_postal_code
bank_routing_number
bank_state_region
bank_work_phone_area_code
bank_work_phone_country_code
bank_work_phone_extension
bank_work_phone_id
bank_work_phone_number
bank_country_id
bic
bic_routing_code
bsb_number
csp_rta_id
custom_field_1
custom_field_2
custom_field_3
custom_field_4
custom_field_5
custom_field_6
custom_field_7
custom_field_8
custom_field_9
custom_field_10
custom_field_11
custom_field_12
custom_field_13
custom_field_14
custom_field_15
custom_field_16
custom_field_17
custom_field_18
custom_field_19
custom_field_20
email
iban_number
ifsc
intermediary_bank_name
international_bank_account_number
kind
name_on_bank_account
payment_method_item
po_box
po_box_postal_code
sort_code
state_region
street_address
street_address2
street_address3
street_address4
supplier_information_id
swift_code
transit_number_and_institution_number
virtual_card_email
wire_routing_number

We have discontinued the following columns from the SUPPLIER_INFORMATION_ADDRESS table:

attention
business_group_name
custom_fields
external_src_name
external_src_ref
local_tax_number
name
state
street_1
street_2
street_3
street_4
vat_country_id
vat_number

September 2025

We now sync the TAG and TAGGING tables from the /api/requisitions endpoint. To backfill historical data, you can trigger a re-sync for these tables.

We have added a new column, rejected, to the EASY_FORM_DATA table.

We have added the tax_code_id column to the INVOICE_HEADER table and the code column to the TAX_CODE table.

July 2025

We've fixed a data consistency issue in the EASY_FORM_DATA table where the subject column had inconsistent null value representations. The subject column now consistently uses proper SQL NULL values. Previously, some records returned a true SQL NULL while others returned the text string null, which could cause data processing errors and affect analytics quality.

Re-sync the EASY_FORM_DATA table to fix historical data with inconsistent null value representations. The first re-sync will count towards free MAR.

We have added the following columns to the PROJECT table:

additional_negotiated_savings'
additional_planned_savings
additional_realized_savings
allow_users_to_view_member
completion_percentage
copy_project_id
enabled_tabs
external_reference_number
project_id
show_contracts_rollup_fields
show_sourcing_rollup_fields
show_suppliers_rollup_fields
status
template_group

We now sync TAGGING data from the PROJECT table.

We have added the following columns to the CHARGE table:

accounting_currency
accounting_total
document_id
document_type
expense_holding_account
legal_entity_name
posting_date
holding_account
issuer_reconciliation_id
payment_partner

We now sync TAX_LINE data from the CHARGE table. We have added a column charge_id to the TAX_LINE table.

We have added a new foreign key relationship between the CHARGE and VIRTUAL_CARD tables. The CHARGE table now includes a virtual_card_id column that references the id column in the VIRTUAL_CARD table.

June 2025

We have added a new column, released_at, to the CP_PAYMENT table to store the date and time when a purchase order was sent to the supplier. We will automatically re-sync the historical data for this column.

We have added the following columns to the INVENTORY_TRANSACTION table:

adjustment_code
adjustment_code_created_at
adjustment_code_id
adjustment_code_name
adjustment_code_type
adjustment_code_updated_at

We now sync TAG data from the REQUISITION_LINE table. We have added a column requisition_line_id to the TAG table.

May 2025

We now support table-level re-syncs for our Coupa connector. We are gradually rolling out these changes to all existing connections. For more information, see our documentation.

We have added a new table, CP_PAYMENT, to track payments.

We have added two new columns, adjuster_id and adjuster_type, to the BUDGET_LINE_ADJUSTMENT_TABLE. To backfill historical data for these columns, re-sync the table or contact Fivetran Support to re-sync it for you.

We have added the uom_id column to the INVOICE_LINE table and the currency_id column to the ORDER_LINE table.

To backfill historical data for these columns, re-sync the tables or contact Fivetran Support to re-sync them for you.

April 2025

We now support SUPPLIER_INFORMATION table and its child table.

For information, see supplier information API doc.

March 2025

We have added two new tables, USER_ADDRESS and USER_ADDRESS_MAPPING. We sync the data using the User API endpoint.

We now sync data from the following API endpoints to the COMMENT table:

ExpenseReport
InvoiceHeader
OrderHeader
RequisitionHeader
User

Re-sync the connection to backfill the historical data for these tables, or contact Fivetran Support to re-sync the data only for these specific endpoints.

February 2025

We have added a new table, MATCHING_ALLOCATION.

November 2024

We have updated our sync strategy for the COMMODITY table. We now sync the table data using the commodities API endpoint.

We have added a new table, SUPPLIER_PREFERRED_COMMODITIES_MAPPING. The table stores the preferred commodities of a supplier.

October 2024

We now capture deletes for the parent tables. We use the _fivetran_deleted column to capture the deletes for these tables. To avoid longer sync times, we perform incremental syncs every Saturday.

September 2024

We have added the expense_line_id column to the composite primary key of the EXPENSE_ATTENDEE table.

August 2024

We have identified and fixed a bug to prevent sync failures of the INVENTORY_TRANSACTION and CONTRACT_TEMPLATE tables. To sync the tables, update the core.contracts_template.read and core.inventory.transaction.read scopes in your Coupa OAuth Client. We are gradually rolling out this change to all existing connections.

June 2024

We have added a new column, channel, to the INVOICE_HEADER table. Be sure to re-sync the INVOICE_HEADER table to backfill the historical data for this column or contact our support team to re-sync it for you.

January 2024

We have added a new table, BUDGET_LINE_ADJUSTMENT. Be sure to re-sync the connector to backfill the historical data or reach out to Fivetran Support to re-sync it for you.

December 2023

We have added two new tables, APPROVER and APPROVER_GROUP_USER_MAPPING, to store information about the users involved in the approval. Be sure to re-sync the connector to backfill the historical data or contact Fivetran Support to re-sync it for you.

October 2023

We have fixed a bug where we were facing delays in updating the records of the ORDER_HEADER table. We have updated our sync strategy and implemented a new weekly lookback window of 7 days to avoid data discrepancy issues of the ORDER_HEADER table.

June 2023

We have made the following changes to the INVOICE_LINE_ALLOCATION table:

Added a new column, invoice_header_id.
Changed the primary key of the table. The new composite key is a combination of the following columns:
- id
- invoice_header_id
- invoice_line_id

Be sure to re-sync the table for the latest changes or contact our support team to re-sync it for you.

We have renamed the savings-pact column of the CONTRACT table to savings-pct. Be sure to re-sync the table for the latest changes or contact our support team to re-sync it for you.

March 2023

We have added a new table, SUPPLIER_ITEM. We are gradually rolling out this change to all existing connections.

November 2022

We have fixed a bug in our Coupa connectors that use OAuth2.0 authentication, where we didn't sync the INVENTORY_TRANSACTION table. To sync the INVENTORY_TRANSACTION table, select the following read scopes for the Client ID when configuring the connector:

core.inventory.transfer.read
core.inventory.consumption.read
core.inventory.adjustment.read
core.inventory.return_to_supplier.read

For existing connectors using OAuth2.0, go to your Coupa portal and add the above scopes to your Client ID.

October 2022

We have fixed a bug in our Coupa connectors that use OAuth2.0 authentication where we didn't sync a few tables.

To sync these tables, select the following read scopes for the Client ID when configuring the connector:

core.easy_form_response.read
core.item.read
core.sourcing.read
core.sourcing.response.read
core.supplier.read

For existing connectors using OAuth2.0, go to your Coupa Portal and add the above scopes to your Client ID.

August 2022

We now support the OAuth 2.0 authentication. If you are using the API Key authentication, you need to migrate to OAuth 2.0 before December 1, 2022. You can migrate to OAuth 2.0 by editing the connection parameters and providing the Client ID and Client Secret instead of the API Key. See our Coupa Setup Guide for details about how to obtain them.

April 2022

We have added a new table, SUPPLIER_ADDRESS, that stores the supplier's address.

February 2022

We are deprecating the following tables:

EASY_FORM
EASY_FORM_WIDGET
EASY_FORM_WIDGET_RULE

January 2022

We have added the following new tables:

EASY_FORM_DATA
EASY_FORM_WIDGET_DATA
EASY_FORM_APPROVAL_MAPPING

We have linked the APPROVAL and EASY_FORM_DATA tables by adding the easy_form_id column as a foreign key in the APPROVAL table.

EASY_FORM_DATA is a child table of the USER table. To sync the EASY_FORM_DATA table, select it on the Schema tab in your Fivetran dashboard and re-sync the USER table.

May 2021

Our Coupa connector is now generally available.

Read our Coupa connector documentation.

We have added a new column, custom_fields, to all the tables except the mapping tables (tables whose names end with the _MAPPING suffix). We will sync the custom fields as JSON objects.

April 2021

We have added two new tables, EXPENSE_LINE_DAILY_PER_DIEM and PER_DIEM_DEDUCTION.

We have renamed the EASYFORM_WIDGET_RULE table to EASY_FORM_WIDGET_RULE.

We have added a new column, custom_fields, to the following tables to sync custom fields as JSON objects:

USER
ORDER_HEADER
INVOICE_HEADER
INVOICE_LINE

We will discontinue the following columns from the USER table after July 30, 2021:

custom_fields_costCenter
custom_fields_dadsArea
custom_fields_dadsDistrict
custom_fields_dadsDivision
custom_fields_dadsStore
custom_fields_division
custom_fields_endDate
custom_fields_orgUnitNName
custom_fields_region

Be sure to update your queries before we discontinue the columns.

March 2021

We have fixed a bug where the attributes of the EXPENSE_MILEAGE_VEHICLE_TYPE table were added to the separate EXPENSE_TRIP_MILEAGE table. We no longer add the attributes of the EXPENSE_MILEAGE_VEHICLE_TYPE table to the EXPENSE_TRIP_MILEAGE table.

We have renamed the following tables in the Schema tab of your connector details page to align them with the source table names:

CHARGES to CHARGE
PROJECT_BUSINESS_GROUP_RELATION to PROJECT_BUSINESS_GROUP_MAPPING
PROJECT_USER_RELATION to PROJECT_USER_MAPPING
SHIPPING_TERM_BUSINESS_GROUP_RELATION to SHIPPING_TERM_BUSINESS_GROUP_MAPPING
UOM to UNIT_OF_MEASURE

These name changes will not impact your destination tables.

February 2021

Coupa is a cloud platform for business spend management.

Read our Coupa connector documentation.