Skip to content

Commit

Permalink
Update CONCUR_Reimbursement.md
Browse files Browse the repository at this point in the history
  • Loading branch information
sattertt authored Nov 12, 2024
1 parent 125f5ae commit 7c1d444
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion docs/LabHome/CONCUR_Reimbursement.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,8 @@ Please note: it is essential that reimbursements are submitted in a timely manne

For more details on funding for travel, please see the [travel guidelines wiki](https://pennlinc.github.io/docs/LabHome/TravelGuidelines/).

Also, note that there is a the weekly office hour on Thursdays 11:00a-12:00am with Patrick Doyle for questions on concur reimbursment. (zoom link pinned on #concur channel in slack).


## Adding delegates
Please give Concur delegate access to the finance team members below. This only needs to be done once.
Expand Down Expand Up @@ -60,7 +62,9 @@ Extensive additional resources on expense reports can be found [here](https://be

## Ask the finance team to review your report

Email Patrick that you’ve created the report and ask him to review it. Once any suggested edits are incorporated, you can submit it. If a concur report is returned, you can find the business administrator's feedback by clicking into the report where you see the listed expenses --> click “details” --> “comments” – this is where approvers will comment if they need additional information or documentation.
Email Patrick that you’ve created the report and ask him to review it. Once any suggested edits are incorporated, you can submit it.

If a concur report is returned, you can find the business administrator's feedback by clicking into the report where you see the listed expenses --> click “details” --> “comments” – this is where approvers will comment if they need additional information or documentation.


## Update the Travel Reimbursement Tracker
Expand Down

0 comments on commit 7c1d444

Please sign in to comment.