# Approved, submitted, settled, reconciled: what payment status should explain

> Understand the evidence behind common payment states and the questions to ask when a payment remains uncertain.

- **Source:** https://www.runproper.com/resources/payments/payment-status-submitted-settled-reconciled
- **Publisher:** Proper Technologies Inc.
- **Format:** Article · Payments
- **Reading time:** 3 min

A useful payment status tells the team what has happened, what evidence supports that statement and what still needs to occur. Approval, submission, completion and reconciliation are distinct steps. Map the terms to the actual payment provider and accounting workflow rather than treating “paid” as a single universal event.

## Approval records a decision

An approval identifies what a person or configured policy authorized. Depending on the process, it may cover an invoice, a payment proposal or a release instruction. Ask which amount, payee, date, funding account and version the decision concerns. An old decision does not explain whether changed details have been reviewed.

A good interface makes that scope understandable. A reviewer should see what is ready, which condition remains unresolved and why. If a bank detail changes, preserve the earlier approval and show what additional verification or authorization is required under the business’s rules.

## Submission records a handoff

Submission means an instruction reached a particular stage. The receiving service may acknowledge it and still perform later checks or processing. Retain its reference and response so the team can look up the same instruction rather than create a new one to find out what happened.

For a delayed or ambiguous response, ask who owns the investigation and when the next status check will occur. A timeout is not proof of failure. A workflow that retries without understanding the first instruction can make the record harder to interpret and may create duplicate movement.

## Completion needs the provider’s evidence

Payment methods and providers use different state names. Establish which response represents the result your team needs and what exceptions can follow. The user-facing label should not claim more than the underlying response supports.

The team also needs the amount, destination and relevant reference associated with that outcome. A generic “success” message without the instruction it belongs to is difficult to use when a supplier later asks about an invoice. Keep the source response available to authorized users.

## Reconciliation connects the money to the books

Reconciliation establishes how the bank result and related amounts connect to the accounting record. A payment can be completed while an allocation, fee, currency difference or posting exception remains unresolved. Those outstanding items need ownership even though the bank movement itself is no longer in doubt.

Proper’s payment stories distinguish controlled release and follow-through from the explanatory work Penny performs when a supplier cannot recognize a payment. In an evaluation, follow one item all the way from obligation to bank result to its ledger effect. Confirm the actual supported methods and connections; the films illustrate the intended workflow.

-   What evidence changes each status?
-   Which role can resolve an exception or authorize a correction?
-   How does the system identify an existing payment before a retry?
-   Can a colleague trace the final accounting result back to the original instruction?

## Questions & answers

### Can a single “paid” badge be enough?

Only if its meaning is clear for the task. The detail should still show the underlying outcome and any unfinished reconciliation work. Avoid making different states indistinguishable.

### Does a failed screen request prove the payment failed?

No. The request may have failed after the receiving service accepted the instruction. Check the original reference and provider status through the authorized recovery process before deciding what to do next.
