Topic
This article is primarily used by Finance and ITS staff to resolve tickets related to Concur-Banner integrations. The following diagrams review which integrations (labeled: jobs/processes) send information to Concur, and which files go from Concur to Banner. Finance staff need to know where data is flowing from Banner. ITS staff need to know what downstream impacts integrations might have when resolving tickets for Concur-Banner integrations or Banner-Concur integrations. All Concur modules (Request, Expense, Invoice) have integrations with Banner and are listed below as different diagrams.
About Concur: Concur facilitates expense submission, and travel processes, and automates invoice capture/submission for Gonzaga. Concur is owned by Finance, with integrations to Banner Finance supported by ITS.
The landscape for Concur-Banner integrations and downstream systems that input data into Concur
Prerequisites
- Access to Concur is through Finance
- Access to Banner jobs/processes is through ITS
Concur Request
Request facilitates purchase order submissions in Concur
This data flow diagram reviews how Finance inputs data for purchase requests through purchase order.
Concur Expense
Concur Expense facilitates the expense submission and travel processes for Gonzaga. Since travel processes do not integrate with Banner, this was not reviewed.
Concur Invoice
Invoice captures both manual and automatic invoice submissions in Concur. From creating a new invoice to invoice submission back to Banner.
Need more help?
Videos from process exploration calls