In this article
Changing a payroll destination is a record change with a later observable result. A confirmation that a request was saved, a paycheck's distribution section, and a bank's posted transaction are three different pieces of evidence. Keeping them separate helps an employee ask a precise question without exposing account information in the wrong place.
The University of Utah's Direct Deposit Information page provides official direct-deposit information and links to its help material. This publication does not reproduce a banking form or collect account numbers. Use the University's own verified service for any actual change, and ask its payroll specialists about the applicable processing details.
Start from a verified destination
A payroll-change request can arrive at a busy moment, which is exactly when a familiar-looking email link can be persuasive. Rather than entering banking information through an unexpected message, begin from the University's official payroll resources or a trusted bookmark whose destination you have checked.
Do not send passwords, one-time codes, routing numbers, account numbers, or screenshots containing them to this publication. We have no relationship with the University and no ability to update payroll records. A page that explains a process is not a safe destination for the data used in that process.
If you are uncertain whether a message is legitimate, use an independently verified University support route to ask. Do not use a phone number or reply address from the suspicious message as the only verification. The purpose of this article is to improve the evidence trail around an authorized change, not to encourage any change you did not intend.
Define the intended change before making it
A clear intention is narrower than “fix my deposit.” Are you adding a destination, replacing one, removing an old destination, or asking why a distribution differs from an earlier statement? Those are different tasks. Knowing which one you mean reduces the risk of changing an unrelated instruction.
Read the official interface's current instructions rather than relying on screenshots from an old manual. A form can change its layout, labels, validation, or confirmation behavior. If a control is unclear, stop and ask payroll what it does before submitting. Do not infer that a default value has the same meaning as at another employer.
There may also be more than one destination involved in a distribution. Keep your own intended arrangement clear, but do not publish or email the account details as part of an ordinary help request. A verified specialist can explain the appropriate secure route if detailed information is necessary.
A saved instruction is not proof of a posted payment
Imagine a fictional employee who changes a destination on Tuesday and sees a confirmation. That establishes something about the request or saved record, depending on the confirmation's wording. It does not, by itself, establish that a particular future payroll has been recalculated or that a bank will post a payment at a particular hour.
The next useful question is which payroll the change is expected to affect. That answer must come from the University's current process and the employee's actual situation. This publication deliberately does not supply a universal lead time, effective-payday promise, or bank-availability estimate.
Preserve the confirmation in a location you are authorized to use, without creating unnecessary copies of sensitive fields. Note the date and the wording of the status. If the result later differs from the expectation, those nonsecret details can help payroll identify the request without requiring an initial message full of account numbers.
Read the payment distribution separately from earnings
A paycheck can have correct earnings and still raise a distribution question. It can also have an earnings issue that no change to the deposit destination will solve. Keeping those categories separate avoids using one system as a workaround for a problem in another.
For a fictional comparison, suppose a statement shows net pay of nine hundred dollars and two distribution amounts of six hundred and three hundred dollars. Their sum matches the supplied net pay. That arithmetic says nothing about the accuracy of the destinations or the bank's posting status. It only shows a relationship between the amounts supplied in the example.
If the concern is where payment went, ask about the distribution record. If the concern is why net pay changed, begin with earnings and deductions. If both are uncertain, state that there are two questions. A clear distinction helps the office avoid treating an amount question as a request to modify banking instructions.
MyTime is not the deposit record
The Introducing MyTime announcement says direct-deposit information is housed separately from MyTime. That is a particularly useful boundary when employees are learning a new timekeeping interface. A change in the appearance of a timecard does not establish that payment instructions changed with it.
If you recently moved between positions or departments, do not assume that the timekeeping change answers every payroll-destination question. Verify the relevant record through the official route. Conversely, do not change a deposit instruction simply because a time entry appears under an unfamiliar job label.
Treat each change according to its purpose. The time record concerns work and leave entries. The earnings statement concerns payroll results. The distribution instruction concerns payment destinations. They can affect the same payday without being managed through the same screen or by the same evidence.
When the expected payment is not visible
An absent bank notification is an observation, not a diagnosis. The bank may display pending and posted activity differently, and the University's record may need review. Contact the appropriate official parties using verified information rather than assuming which stage failed.
Describe the issue without guessing the cause: identify the payroll date in question, say that you expected a payment, and ask which record should be checked first. Follow the University's instructions for any trace or correction. This publication cannot inspect a payment, identify the account used, or promise that an issue will resolve automatically.
Avoid repeatedly changing destinations while an unresolved payment is being investigated unless payroll specifically directs that action. A second change can complicate the explanation of what was in effect at the relevant time. Keep a short chronology of confirmed actions and responses so that each party is discussing the same event.
Close the loop with the right evidence
A useful completion check asks whether the intended instruction is confirmed and whether the relevant payment result has been observed or explained. Those may happen at different times. If payroll supplies an expected next record, use that record to close the loop rather than relying only on a successful form submission.
The University's Paycheck Information page notes that when direct deposit is not set up, payroll checks are mailed to the home address on file until activation. That makes address accuracy a separate issue worth raising through the official service when relevant. It is not a reason to post an address here or assume a universal delivery date.
The best deposit-change record is small and secure: what you intended, what the official service confirmed, which payroll was discussed, and what result followed. It gives you a factual basis for a question while keeping the details that can move money out of an editorial website and ordinary correspondence.
Sources and reading limits
Public sources reviewed October 15, 2026. These links support the specific University context above; the comparison methods and hypothetical examples are original editorial work. No authenticated system was tested. Policies and interfaces can change. Individual pay, benefits, tax and employment decisions require the appropriate official or qualified advice.