What happens automatically in Payments

Your action	Automatic result	Still requires a decision/action
Choose a customer search	Refreshes choices and clears earlier selection	Select the correct customer result
Load New customer receipt with permitted active settings	Fills read-only Ledger base currency	Resolve missing setup rather than guess a value
Save draft receipt	Generates number, stores Draft, computes base amount and initial allocation balances	Review and post
Post receipt	Records Posted context and makes money allocatable	Select invoices/amounts; no automatic allocation
Find invoices	Fetches a page for customer/unit and filters browser compatibility	Choose correct bill, check due and possibly use next page
Allocate	Stores allocation, updates receipt totals/status, applies invoice balance and triggers accounting integration	Review both documents and actual payment evidence
Use all Available	Receipt becomes Allocated	Target invoice may still be only Partially paid
Use some Available	Receipt becomes Partially allocated	Decide whether remainder stays on account or belongs to another bill
Cancel a Draft	Returns retained record in Cancelled state when successful	Verify actual returned state and create a replacement only if appropriate
Change register filters	Refreshes search after a short delay and updates URL context	Read current applied filters before acting

Allocation changes two documents

The two statuses answer different questions. A receipt can become Allocated while the invoice remains Partially paid, or a receipt can remain Partially allocated after the invoice becomes Paid.

Numbering and copied context

Payment number is generated on creation. The application does not retrieve an exchange rate, infer the bank evidence reference, select an invoice from free-text notes or obtain a customer's remittance instruction automatically.

An allocation's base amount uses the receipt's stored exchange rate. It does not silently revalue the invoice at a fresh market rate.

Things not performed automatically

• No bank transfer, card charge, cheque clearance or online processor settlement.
• No bank-statement import/matching or receipt PDF/email action in this workspace.
• No automatic oldest-invoice allocation or cross-currency allocation conversion.
• No automatic refund/write-off of excess money.
• No automatic second allocation to top up an already used receipt–invoice pair.
• No posted customer receipt reversal, refund or allocation-edit/delete button.
• No stock movement or dispatch from payment entry.
• No creation of supplier, expense or donation records through the customer receipt form.

Uncertain writes need investigation

A lost response is not evidence that the write failed. Creation can show The receipt may have been created; allocation can require closing/reloading before another action. Check the existing receipt and invoice state, not just the last browser message.

There is no user-visible idempotency reference field or automatic safe-replay workflow here. Do not repeatedly create/post/allocate in another tab to overcome a timeout.