In this article
Locate the last proven payment event and send the right owner a concise case with the amount, reference and unresolved question.
If an expected reimbursement has not arrived, preserve the existing claim. Creating another expense can produce a duplicate without fixing the payment problem. Begin with the reference you already have and establish whether the delay sits before approval, before payment release or after release.
Check the expected amount first
Compare the employee-reimbursable amount with the payment you are looking for. Do not use the overall report total when it includes company-paid charges or excluded items. Keep the currency attached and note any approved adjustments. If you do not understand the amount, resolve that difference with finance before asking a bank to find it.
Our end-to-end route map explains the distinction. It is especially useful when the report combines corporate-card transactions and personal out-of-pocket purchases.
If approval is still open
Look for an unanswered question or an assigned reviewer. The next action may be yours, even if you remember submitting everything. Use the approval handoff check to identify the owner. There is little value in counting bank-processing days before the claim has reached a payment stage.
For Professional, the public status guide distinguishes draft, approval and payment-related stages. It also describes a user marking the report paid. Treat the history as workflow evidence, not independent confirmation of a bank credit.
If approval is complete but no payout is confirmed
Ask the payment owner whether the claim has been scheduled or released, and which system handles it. “Approved on Tuesday” does not necessarily mean “payment began Tuesday.” Request the relevant event and date rather than a broad reassurance that it is being processed.
For Spend specifically, the reimbursement page describes configurable payout schedules and a generally two-to-six-business-day ACH settlement period after payout begins. These are qualified product descriptions, not a promised date for an individual claim. Do not apply that interval to Professional, Enterprise or an employer’s separate payment route.
If the payment route is Emburse Spend
The official missing-reimbursement FAQ points to reimbursement history and bank-account setup as checks. It also identifies failed-payment possibilities such as incorrect details or a closed account. Review your own account only through your established, trusted sign-in route. Do not send full banking details in a general support message.
If you receive a failure notification, verify it inside the trusted application or with the authorized payment owner before following an emailed link. Ask which record failed and what the approved correction process is. Changing details repeatedly without understanding the failure can make the chronology harder to follow.
If finance confirms a Professional payment-service route
Emburse publishes an administrator guide for the Convera arrangement within Emburse Pay Professional. It distinguishes processing, release, rejection and return events. This guide is relevant only if your organization uses that arrangement. Ask the administrator to interpret the actual payment event and provide an appropriate reference; do not infer access to those administrative records.
Prepare a minimal case
- Product and employer-approved expense reference
- Confirmed reimbursable amount and currency
- Last approval or payment event, with its date
- Whether finance has confirmed release
- The exact unresolved question or error message
- Any existing support case reference
A fictional inquiry might read: “Report TR-318 has a confirmed reimbursement of 86.40 USD. Finance advised that payment was released on [date], but I cannot match the credit. Can you confirm the current payment state and the reference I should use for a bank inquiry?” This asks for evidence without asserting that a particular party lost the money.
Keep one claim and one clear owner
If the payment failed, finance should explain the authorized reissue path. If the claim itself was wrong, correct it through the appropriate workflow. Those are different actions. Our duplicate prevention guide explains why a second claim is not a repair method.
Use the safe support checklist if the status cannot be interpreted or the screen is malfunctioning. Close the issue only after the expected credit is matched, finance explains why no payment is due, or the unresolved case has a documented next action and owner.