In this guide
Use three independent questionsFollow an illustrative pending orderKeep units out of each other’s columnsReconcile at the actual actionCommunicate the dependency honestlyA customer can have paid while a provider action is still pending. A business can also hold purchased credits before any particular customer pays. These are ordinary differences in workflow, but a single generic balance or Done field can make them look contradictory.
The following example is hypothetical. It does not describe Dream’s payment processing, credit application speed or customer fulfilment policy.
Use three independent questions
First, what customer order was agreed and what payment state is confirmed? Second, which provider credits were purchased and applied? Third, which customer account action was actually completed? A reference can connect the answers, but one answer does not prove another. A payment image is evidence about money; an account result is evidence about the authorised operation.
Follow an illustrative pending order
A customer’s payment is recorded against Order C. The business has submitted a provider recharge request, but the resulting credit quantity remains unconfirmed. The correct update can state both facts. It should not say the customer account is ready merely because payment is confirmed, and it should not erase the customer payment because the provider step is pending.
Keep units out of each other’s columns
Customer money has a named currency. Provider package money uses the actual quoted currency, including USD for Dream’s published packages. Credits are quantities. Service terms are months or another explicitly described term. Combining these values into one number can produce a balanced-looking sheet that cannot explain what the balance represents. Give each field its unit and source.
Reconcile at the actual action
When the provider confirms the customer account action, record the action reference and any actual confirmed deduction. Link it to the customer order without guessing a conversion. If the consumption mapping is not known, keep the allocation question open. Do not derive a deduction from the customer’s payment amount or from a familiar convention used by a different provider.
Communicate the dependency honestly
A useful status says what is confirmed, what is pending and who owns the next step. It avoids both an invented deadline and a vague “almost done.” The customer does not need every internal ledger detail, but they do need an accurate description of their order. Separate states let the team communicate clearly while retaining the evidence needed to resolve the remaining step.
A handover should name which of the three states needs the next answer. Payment reconciliation may belong to one authorised colleague while the account-result question belongs to another. Link both through the order reference. This prevents a customer’s confirmed payment from being overlooked while also avoiding an unsupported claim that the provider action has finished.
Questions about this guide
Does the customer need to see the provider’s entire credit ledger?
Usually the customer needs a clear status for their own order and the relevant confirmation. Internal quantity records can remain restricted to the team that needs them. Do not expose unrelated customers or credentials in an attempt to prove one order’s state.