Prepare a reimbursement request without counting the expense twice
Connect a personal advance, its supporting evidence, the review decision, and any later repayment.
Distinguish purchase, request, and payment
A personal purchase, a request for repayment, and the eventual reimbursement are three events. They should be connected, but they should not all appear as separate expenses. Begin with one expense record identifying the person who paid. Then add a reimbursement record with its own submission and review history.
Submitting a request does not mean that it has been approved. Approval does not mean money has been sent. A useful status sequence is draft, submitted, awaiting information, approved or declined, and paid. You may need a partially paid status as well. These labels are workflow choices; they do not establish a legal entitlement to repayment.
Build the request packet
Include the expense reference, date, vendor, full purchase amount, proposed reimbursable amount, purpose, and payer. Attach an itemized receipt when available and a relevant payment record if requested. State whether any other person, insurer, vendor, or account has already repaid part of the amount.
Explain unusual facts directly. “Paid personally because the locksmith required payment on arrival” is more helpful than “urgent.” If evidence is missing, say what is missing and what you have done to recover it. Never substitute a recreated receipt that looks like an original. A written explanation should remain visibly separate from vendor evidence.
- One underlying expense reference
- Identity of the original payer
- Amount requested and any excluded personal portion
- Receipt or an explicit missing-evidence note
- Prior refunds, credits, or repayments
- Review decision and payment reference when complete
Worked example: a partial reimbursement
Taylor pays $180 for a storage unit. A reviewer approves $150 and asks for more information about a $30 add-on. Keep the expense at $180, the request at $180, and the approved amount at $150. Record the $30 as unresolved rather than silently deleting it from the request.
When the estate sends $150, record a reimbursement payment linked to that request. The outstanding requested amount is $30, but only $150 has been approved. If the remaining $30 is later declined, preserve the decision and reason. The record should distinguish an unpaid approved amount from a disputed amount; both can otherwise look like “money still owed.”
Close the loop respectfully
Provide a short confirmation that states the amount paid, payment date, reference, and remaining status. Avoid putting bank routing details in the message. Ask the recipient to report a missing or incorrect payment through a known contact channel. Keep that confirmation with the request rather than relying on a chat history.
If the requester and reviewer are the same person, record that fact and seek the appropriate independent review for the estate. Questions about authority, conflicts, priority of payment, or the reasonableness of an expense belong with the relevant legal adviser. The CFPB’s fiduciary guidance provides context for careful records and handling another person’s money. The packet described here makes the facts visible for that review; it cannot decide the outcome.
Before marking the request closed, compare total approved repayments with the original approved amount. Check for duplicate transfers and returned payments. Record the result so the next reviewer does not repeat the same reconciliation.
Sources and further reading
The workflow and examples above are organizational suggestions. Official references provide context; requirements vary by jurisdiction and circumstances.
These guides are AI-assisted educational writing and have not been reviewed by an attorney or accountant. Our editorial policy.