Connector Improvement: Add Audit_Status to Coupa Expense Line Object
CompletedWe are using the Fivetran Coupa connector and have identified that the audit_status field, which is present in the Coupa UI and exposed in the Coupa Expense Lines transactional API, is not being synced into our destination through Fivetran.
According to Coupa’s official documentation, the Expense Lines API includes an audit-status element with defined allowed values (e.g., Verified Receipt Online, Waiting for Receipt, etc.).
-
Official comment
Hi everyone,
The addition of the audit_status fields to the Coupa Expense Line object are now live and generally available in the Fivetran connector. This enhancement ensures the audit_status data is synced into your destination as outlined in Coupa’s API documentation.
Documentation and release notes are available in our release notes page for details.
Thank you to everyone on this thread for your feedback and patience throughout the release process.
Thanks,
Frank -
Hi Sean,
The request to include the audit_status field in the Coupa Expense Line object is noted and added to our feature improvements backlog. I am interested in learning more about your specific use case—could you share how the audit_status information would help with your business reporting or workflows? Understanding the problem you are trying to solve will help us prioritize and shape this enhancement.
We will keep the community updated on this thread as we make progress.
Thanks,
Frank -
Hi Frank,
Thanks for adding this to the backlog. We need audit_status mainly for compliance and workflow reporting to see which expense lines have passed audit and which still require review. This status isn’t derivable from other fields, so having it in the connector is important for accurate finance reporting and internal controls. -
Perfect! Thanks so much Frank and to the rest of the team, really appreciate the work on this
Please sign in to leave a comment.
Comments
4 comments