In this article
“Where is the payment?” may contain three different questions. Identify whether the uncertainty concerns the amount, the processing stage or evidence of receipt.
Choose the question first
An amount question asks why a calculation or document shows a particular result. A status question asks what stage the official record currently shows. A receipt question asks whether the expected amount has arrived in the appropriate account. These questions can be related, but one answer does not automatically resolve the others.
Real's public get-paid guide distinguishes processing steps and arrival of funds. Its payment-help article provides an official route for investigating missing-payment questions. This publication does not verify individual payments or reproduce banking instructions. Start from current official information and the authorized channel, not a third-party promise about when you should be paid.
Record the observation without diagnosing it
Write down what you actually saw, when you saw it and which source you consulted. “The official record shows this status as of this date” is an observation. “The payment has been lost” is a diagnosis that needs evidence. Avoid turning the absence of an expected result into a specific cause before the relevant team has reviewed it.
If the concern is an amount, identify the document and exact line or total. If the concern is timing, identify the current status and relevant dates. Do not infer a payment receipt date from a download date or a transaction's expected closing date. Keep the basis of each observation explicit.
Build a bounded evidence packet
The packet should contain the relevant transaction reference through the approved channel, the specific question, the source version, the observation date and the evidence needed to understand the issue. Include prior case references when they help connect an existing review. Avoid creating duplicate requests that split the context across unrelated threads.
Do not attach every transaction, a full bank statement or unrelated client documents by default. Ask what evidence is required and how it should be supplied. This journal cannot receive or analyze private financial documents. Its contact address is for editorial corrections and privacy questions, not account support.
A fictional escalation example
A fictional agent, Jules, notices that a closing document differs from an earlier approved document. Jules also has a separate question about processing status. A vague message says, “The payment is wrong and late.” A useful message separates the two issues: explain the changed component, and clarify the current status shown in the official record.
Jules attaches only the relevant authorized references and states which versions were compared. The message does not assume that the changed amount caused a delay. If the team explains the adjustment but the status question remains open, the register shows one resolved issue and one pending issue. This is more accurate than marking the entire case finished after the first reply.
Use the official route deliberately
Real's support-contact article identifies its current support options. Use that official guidance to choose the appropriate route for your situation. A social-media comment or message from an unfamiliar account is not a substitute for an authenticated, authorized support process. This publication is independent and cannot forward a case into Real's internal systems.
When a question instead requires a broker, closing professional, bank or accountant, identify that boundary rather than asking one recipient to answer everything. Do not transmit payment instructions or sensitive account details merely because someone asks in an unverified channel. This guide does not direct transfers or changes to financial account settings.
Ask for the next evidence-bearing step
A good follow-up asks what remains needed, who is reviewing it and what event will establish progress. It does not demand an invented deadline from a general article. Current official guidance may describe ordinary processing expectations, but individual circumstances can differ. We do not turn those descriptions into a guarantee.
Keep the request respectful and specific. If the previous response did not answer the question, identify the remaining point and reference the earlier explanation. Repeating the entire history in every message can make the unresolved issue harder to find. A concise chronology often helps more than a growing collection of attachments.
Track the case without spreading the data
A private case note can record the opened date, official reference, question category, response summary and next step. It does not need copied credentials, full financial account numbers or all client details. Restrict access to those authorized for the business purpose.
For a team discussion, an aggregate status such as “one amount question awaiting explanation” may be sufficient. Sharing a whole individual statement should not be the default way to communicate progress. An operational summary can preserve accountability without exposing more information than the recipients need.
Close the specific question
A case is resolved when the defined question has a supported answer or the appropriate corrective record has been reviewed. A processing notification does not itself prove receipt, and an explanation of the amount does not necessarily resolve timing. Record which question was closed and what evidence supports that conclusion.
If the answer changes a reconciliation or planning assumption, update the affected working note and preserve the reason. The purpose of escalation is a reliable explanation and next step, not a promise this publication can enforce. Use the statement and adjustment guides when the remaining issue concerns document meaning rather than status.
Source notes
Public sources checked October 22, 2026. Product facts are attributed to the official references below. Review methods and fictional examples are original editorial analysis, not a private-account test or an official Real procedure. Current terms and product details can change. General information only, not tax, investment, legal or individual financial advice.