In this article
A photographed check is the start of a deposit process, not proof that every dollar can be spent. A simple record helps you distinguish what you submitted, what the institution accepted, and what is available for upcoming payments. This matters most when a bill depends on that particular deposit.
Check the instructions before taking pictures
LMCU lists check deposit among its mobile banking features. Use the current instructions in the official app to verify check eligibility, endorsement wording, deposit limits, and the destination account. Do not assume another institution’s instructions apply to LMCU, or that instructions remembered from an older deposit are unchanged.
Work somewhere private with good light. Compare the amount you enter with the check itself, and review both images before submitting. If the app reports a problem, read the message rather than repeatedly submitting the same check. When the result is unclear, check deposit history or ask LMCU before trying again.
Record three separate milestones
Keep the submission confirmation, the later deposit status, and the amount available as separate observations. A confirmation can show that an instruction was received without settling every question about review or availability. Use the exact status words the app displays instead of translating all of them into “done.”
A private deposit log can contain the submission date, amount, destination account nickname, confirmation reference, and next action. Avoid copying a full account number into a casual notes app. Record any displayed release date and whether it covers all or only part of the deposit.
Ask about holds without guessing the rule
LMCU’s membership disclosure describes check-deposit delays involving circumstances such as concerns about payment, returned checks, repeated overdrafts, and operational emergencies. It also describes special treatment for new accounts. These general provisions are not a substitute for the mobile deposit terms and notice applying to your specific transaction.
Useful questions are concrete: Was the deposit accepted? Is a hold active? What amount is available now? What release date applies to the remainder? Does an additional review remain? Avoid treating a general website example as a promise for your check. If a payment is approaching, make a plan based on confirmed available funds rather than an assumed release time.
Protect the paper check and prevent duplicates
Place the original in a secure location and follow LMCU’s current retention and destruction instructions. Keep it separate from checks waiting to be deposited. Do not deposit the same item at an ATM, branch, or another institution while trying to resolve a confusing mobile status.
In a fictional example, Eli submits a reimbursement check on a weekend and sees a confirmation. He records it as submitted, checks the later status, and waits for verified availability before using it for a scheduled bill. He does not infer a deadline from how quickly a previous check became available.
Finish with a transaction check
When the deposit posts, compare the amount and destination with your log. Investigate differences through LMCU’s official channels, keeping the confirmation handy. Availability does not by itself establish that a check cannot later be returned, so be cautious about unfamiliar check senders.
Connect this record to your payment calendar and regular statement review. A short, consistent record is easier to maintain than reconstructing an uncertain deposit weeks later.
Use a private log that answers the next question
A deposit log should reduce uncertainty without becoming a second archive of sensitive check images. A short row for each check is often enough. Record its amount and submission date, the destination nickname, the confirmation reference, the latest status, and what you need to check next. Store any images or notices only where you can protect them.
- Before submission: is this check eligible under the current instructions?
- After submission: was a confirmation shown, or did the process stop with an error?
- During review: is there a message requiring action, and has it been addressed?
- After posting: does the amount match, and what portion is available?
- Before disposal: have the applicable retention instructions been satisfied?
Do not mark all five stages complete because one screen displays a successful submission. Each question describes a different part of the workflow.
Handle uncertainty without creating a second deposit
Suppose, in a fictional example, Nora submits a check and loses connectivity before seeing a clear result. The safe organizational response is to find out whether the original submission exists. Nora checks the official app’s history and messages, then asks LMCU if the status remains unclear. She does not interpret the interrupted screen as proof that nothing happened.
Another fictional situation involves a partial amount becoming available. Sam expected to use an entire reimbursement for two bills, but the account shows only part of the deposit available. Sam records the available portion separately from the remainder and checks the notice. That distinction makes it possible to ask a precise question instead of reporting only that “the balance looks wrong.”
If a deposit is rejected, save the explanation and confirm the appropriate next step before altering, resubmitting, or depositing the check elsewhere. If you notice an amount-entry mistake, report it through the official service rather than trying to offset it with another transaction. A clean record of the original attempt is usually more useful than a series of improvised fixes that are harder to explain.
Sources and limits
Public sources checked November 4, 2026. The checklists and fictional examples are educational analysis, not a private-account test or individualized financial advice.
- LMCU Mobile Banking: Mobile banking includes check deposits and balance/activity access.
- LMCU Membership Agreement and Disclosures: General check-deposit hold circumstances and special new-account provisions; not presented as a mobile-specific release schedule.