SOP — Payment recording

Purpose: record a verified financial transaction with sufficient receipt and proof evidence.

Field	Standard
Trigger	Cash received or online transfer verified under company process.
Responsible role	Finance/Admin.
Required information	Customer, contract if applicable, amount, type, method, receipt, bank reference, proof, authorization.
Steps in platform	Open customer/payment form; enter verified data; upload proof; save once; review receipt/proof queues and customer balance.
Expected status changes	Transaction is recorded; linked request may be updated only after verification.
Required documents	Receipt, transfer proof, signed note, or approved supporting file as needed.
Financial checks	Exact amount, method, receipt number/date, bank reference, customer/contract match.
Follow-up deadline	Same business day or approved finance close.
Escalation conditions	Duplicate transaction risk, mismatch, missing evidence, disputed allocation, failed save.
Completion criteria	Ledger record, supporting evidence, and missing-information status are accurate.
Audit/accountability evidence	Transaction, document link, receipt metadata, Audit Trail.
Common mistakes	Retrying without checking save; treating deposit readiness as payment.

Media: Video, screenshot, checklist, fictional scenario.