Editing CommunityData:Reimbursements (UW)

From CommunityData
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 40: Line 40:
=== Update the ledger ===
=== Update the ledger ===


Open the file <tt>expenses.ledger</tt> and scroll to the end of the file. For each receipt, add a new section like this:
Open the file <tt>expenses.ledger</tt> and scroll to the end of the file. Add a new section like this:


   2023/3/31 Xian Noodle  ; lunch with lab for haomin's visit
   2023/3/31 Xian Noodle  ; lunch with lab for haomin's visit
Line 65: Line 65:


# A clear sense of whether this will be charged to a grant or whether it will be charged to the general CDSC-UW budget, or to some other budget.
# A clear sense of whether this will be charged to a grant or whether it will be charged to the general CDSC-UW budget, or to some other budget.
# The budget codes for the expense. This process requires the use of multiple special numbers and tracking codes. If you have access to the ledger_mako git repository, the relevant details are in the file called budget. Ask Mako if you don't have access.
# The budget codes for the expense. Mako can provide these to you.


Once you know these these things—and have done everything on this page above—you are ready to request. To do so, go this page: https://admin-support.artsci.washington.edu/services/pay-pro#forms
Once you know these these things—and have done everything on this page above—you are ready to request. To do so, go this page: https://admin-support.artsci.washington.edu/services/pay-pro#forms
Line 86: Line 86:
== Following Up ==
== Following Up ==


As things are processed, you should update the ledger file with details on the status. At a minimum, you should (a) add the UWConnect ID and the Workday ID (formerly, Ariba ID) once you get them and (b) mark things as reimbursed once they are fully reimbursed. You can do both as a comments with the "; " syntax. There are lots of examples you can cut and paste from.
As things are processed, you should update the ledger file with details on the status. At a minimum, you should (a) add the UWConnect ID and the Ariba ID which each once you get them and (b) mark things as reimbursed once they are fully reimbursed. You can do both as a comments with the "; " syntax. There are lots of examples you can cut and paste from.


In terms of (a): You will get the former right when you submit and it will look like "REF0100000". The Workday ID will be created after your reimbursement has been approved and is submitted into Workday so that a check can be cut; Workday IDs look like this: ER-00000####. Mako likes to add dates to keep track of how things are going too.  
In terms of (a): You will get the former right when you submit and it will look like "REF0100000". The Ariba ID you will when it is submitted for reimbursement and it has a form that will start with letters and then followed by numbers. Mako likes to add dates to keep track of how things are going too.  


In terms of (b): Finally, when things are completely done, you should add a '*' right after the date. This marks the transaction as cleared.
In terms of (b): Finally, when things are completely done, you should '*' right after the date. This marks the transaction as cleared.


A cleared version of the transaction above might look like:
A cleared version of the transition above might look like:


   2023/3/31 * Xian Noodle  ; lunch with lab for haomin's visit
   2023/3/31 * Xian Noodle  ; lunch with lab for haomin's visit
Line 102: Line 102:
       ; Sent Food Form: 2023/05/14
       ; Sent Food Form: 2023/05/14
       ; UWConnect ID: REF0101824
       ; UWConnect ID: REF0101824
       ; Workday ID: ER-000001234
       ; Ariba ID: XR449943
       ; Reimbursed: 2023/05/22
       ; Reimbursed: 2023/05/22
Please note that all contributions to CommunityData are considered to be released under the Attribution-Share Alike 3.0 Unported (see CommunityData:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)