Post a customer receipt
Where: Draft payment detail → Post receipt.
Who: payment.post, viewing permission and access to the receipt's business unit.
Posting is not allocation
Posting makes a customer receipt available for allocation and records posting context. It does not automatically pick an invoice, charge a card, transmit money or certify bank clearance.
Steps
- Open the receipt and check Customer payment and Draft.
- Review the receipt checklist.
- Select Post receipt.
- Read Post this draft receipt? in the confirmation section.
- Select Confirm post, or Keep reviewing to abandon the confirmation without posting.
- Check Receipt posted. and returned status Posted.
- Verify Amount, Base amount, Allocated and Available, and the Posted time/actor.
The stored payment and base amounts must be positive. A tiny positive input combined with rounding/storage can still fail posting if the saved base amount is not positive; inspect the saved values rather than assuming validation of the original field is enough.
Running example
| Field | Before | After posting |
|---|---|---|
| Status | Draft | Posted |
| Amount | 200.0000 GBP | 200.0000 GBP |
| Allocated | 0 | 0 |
| Available | 200 | 200 |
| Invoice 327.60 due | 327.60 | 327.60 |
Continue with Allocate to an invoice. Leaving a Posted receipt unallocated is appropriate for an advance or money waiting for invoice instructions, but it does not clear an existing bill.
After posting
The generic customer workspace no longer offers Draft cancellation. There is no unpost, reset-to-draft, refund or reverse action here, even though other internal/owning workflows may recognise more states.
Do not post an incorrect Draft with the intention of editing it afterwards. Check identity, unit and currencies before confirming.
Errors and result checks
| Message / condition | Recovery |
|---|---|
| Only DRAFT or IN_PROCESS payments can be posted | In this customer workspace, review why the receipt is no longer Draft; do not follow another type's lifecycle |
| Payment amount/base amount must be greater than zero | Inspect saved Amount/Base amount and refer invalid data to Accounts/support |
| Server returned a different status | Review actual returned state; do not announce success based on the click |
| Request timed out | Let refresh complete or reload/reopen, then inspect Posted context and allocations |
A duplicate posting attempt is not a harmless bank retry. Establish the first outcome before deciding the next action.