Report Animal Concerns

Budget Consultation & Billing Inquiries

Managing the many complexities of your research project can be challenging enough without worrying about the financial aspects associated with animal care and use. That’s why the ULAM Business Office is available to assist Study Teams with questions and concerns about budgeting, billing, and per-diem rates.

Blue calendar icon with snowflakes

ULAM Business Office Winter 2024 Holiday Hours

The ULAM Business Office will be closed beginning at 3:00 PM on Tuesday, December 24, 2024 – Wednesday, January 1, 2025, for U-M’s holiday season days.

The office will re-open at 8:00 AM on Thursday, January 2, 2025.

Budget Consultation

If you’d like assistance with budget planning for your next project proposal, the Unit for Laboratory Animal Medicine (ULAM) can:

Billing Inquiries

The University tracks many of the costs associated with day-to-day animal care and use through a barcoding system, which is primarily managed through the eResearch Animal Management System (eRAM). Billing for the costs associated with the purchase of animals and supplies, daily care of animals, technical assistance, and specialized research support services are billed monthly to departmental or investigator accounts.

Specific information about ULAM rates, including current per-diem rates for animal husbandry, animal acquisition, and research support services, can be found on the Rates page. For details on how to access eRAM, please visit our eRAM page.

Additional information about how barcoding is used to keep track of animals in our facilities is available on the Animal Ordering & Acquisition page.

Billing FAQs

The ULAM Billing Team can assist with questions regarding the ULAM Statement of Charges and short code activities (e.g., transfers, sharing). The team also provides guidance and resources to help researchers self-manage their short codes in eRAM.

If you are unsure about whether your issue is related to billing, send an email to [email protected] and your question will be routed to the appropriate party.

In order to prevent charges from hitting your original short code, you will need to perform a short code transfer.

Step-by-step instructions on how to perform a short code transfer are available via the eRAM: Manage Shortcodes Self-Guided Help document.

For assistance with moving specific charges, please email [email protected] with the following information:

  • the original short code that was charged
  • the new short code where the charges should be moved
  • the month that the charges hit your short code
  • list of all charge(s) that should be moved 

You may also include a copy of your billing statement (if available) with all relevant charge(s) to be moved clearly highlighted or otherwise denoted.

To expedite processing, please also include the name and preferred method of contact (e.g., email, phone number, etc.) for one individual in case the ULAM Billing Team may need to reach out with any additional questions about your request.

NOTE: The Billing Team is unable to look up charges, statements, or accounts by Project Grant Number (PGNS) or USE Numbers, so it is critical that short code information be included in all requests.

General questions may be sent to [email protected].

Please include the following details (where applicable):

  • Affected PI name
  • Protocol number
  • Short code
  • Charge ID (from the ULAM Statement of Charges)
  • A brief explanation of your billing issue or question

Managing Short Codes in eRAM

Looking for answers? Find step-by-step instructions for self-managing common short code activities in eRAM, including: short code transfers, designating a Short Code Manager or Billing Viewer, and sharing short codes with another PI.

Review self-guided help documents

Understanding Per-Diem Rates

This Quick Reference Sheet, available via PDF download, outlines the types of husbandry and vet tech services that are covered by standard ULAM per-diem rates and which services are additional fee-for service.

download the pdf

Questions?

Last updated: