Financial responsibilities and payment recording
Financial records require a clear separation of duties. Sales may receive information from a buyer, Administration may manage contracts and documents, and Finance may verify and record transactions. The Wamule Operations Platform should reflect each part of that process without allowing one operational status to stand in for another.
Core responsibilities
Sales staff
Sales staff should:
- record what the buyer said or sent;
- identify the related lead, reservation, application, or customer;
- forward proof or payment information through the approved internal process;
- avoid confirming funds before Finance verification;
- keep the buyer's next action current; and
- notify Finance when a reservation deadline or customer commitment depends on verification.
Sales should not create a financial entry merely because a screenshot or promise was received unless their role and the business process explicitly authorize it.
Finance or authorized Admin staff
Finance/Admin staff are responsible for:
- verifying the customer and contract;
- checking amount, method, date, and transaction evidence;
- searching for duplicate entries;
- entering required receipt or bank references;
- reviewing proof and authorization;
- confirming the payment saved;
- investigating discrepancies;
- maintaining statement and balance accuracy; and
- escalating exceptions that require management, legal, or system review.
Management
Management should define:
- approved payment methods;
- who may receive and verify funds;
- receipt-number standards;
- bank-reference and proof requirements;
- correction, void, and reversal authority;
- collections escalation rules;
- customer communication standards; and
- access levels for financial information.
Required separation
A reservation is not a payment. Deposit readiness is not ledger confirmation. Uploaded proof is not reconciliation. A customer promise is not a transaction. AI or Smart Insights cannot confirm financial truth. An actual payment must be verified and recorded separately in Payments.
Cash-payment procedure
- Confirm the customer's identity and intended contract/account.
- Count and verify the cash using the approved cash-handling process.
- Confirm the payment purpose and amount.
- Issue or identify the correct receipt according to business procedure.
- Open Payments and search for any existing entry.
- Record customer, contract, date, amount, transaction type, and cash method.
- Enter the manual receipt number and other required metadata.
- Add a concise note only when context is needed.
- Save once.
- Re-open or search for the payment and confirm it exists once.
- Confirm the customer/contract history and statement reflect the expected result.
- Secure the cash and supporting records according to business policy.
Online-transfer procedure
- Receive the transfer reference or proof through an approved channel.
- Confirm the buyer/customer and intended account.
- Review the company bank or authorized verification source.
- Confirm amount, date, sender/reference, and status.
- Search Payments for an existing matching entry.
- Record the transaction against the correct customer/contract.
- Select the correct transfer method.
- Enter the bank reference exactly and attach approved proof where supported.
- Complete any authorization or reviewer step.
- Save once and verify the entry.
- Notify Sales/Collections of the verified outcome.
- Update the reservation or other operational workflow separately.
Receiving proof that cannot yet be verified
When proof is received but cannot be confirmed:
- record that proof was received in the relevant operational activity;
- do not create a confirmed payment or alter the balance unless authorized by procedure;
- assign the verification task to Finance;
- record what information is missing;
- set a review deadline; and
- communicate a careful status to the buyer, such as “proof has been received and is being verified,” rather than “payment is confirmed.”
Duplicate prevention
Before saving a payment, search using several of the following:
- customer;
- contract;
- date;
- amount;
- payment method;
- receipt number;
- bank reference; and
- recent payment history.
After a slow response or page error, check whether the record saved before submitting again.
Receipt standards
A receipt record should be traceable and consistent. The approved standard should define:
- required format;
- who issues the number;
- whether numbers are sequential;
- whether different locations or methods use separate ranges;
- how voided receipts are handled;
- how corrections are documented; and
- where the receipt document is stored.
Do not invent, reuse, or alter a receipt number merely to clear a missing-information alert.
Bank-reference and proof standards
For transfers, use the reference from the approved source rather than a shortened personal note. Proof should:
- belong to the correct transaction;
- display only the information required for verification;
- be stored through the approved method;
- avoid exposing unrelated account information; and
- remain linked to the correct payment record.
Post-entry verification
A payment-recording task is not complete until staff confirm:
- one payment entry exists;
- customer and contract are correct;
- amount and date are correct;
- method and transaction type are correct;
- receipt/reference/proof requirements are satisfied;
- any authorization is complete;
- statement or balance changed as expected; and
- Sales/Collections received the correct outcome.
Example: buyer sends proof to Sales
A fictional buyer, Derrick Training, sends Sales a transfer screenshot for BZ$750.
- Sales records the receipt of proof in the reservation activity and forwards it to the approved Finance channel.
- Sales tells Derrick that the proof is being verified—not that payment is confirmed.
- Finance verifies the company bank record and reference.
- Finance searches for an existing payment.
- Finance records one payment against the correct customer and contract.
- Finance checks the statement and balance.
- Sales is informed that the transaction is recorded.
- The reservation and downstream contract work are updated separately.
Daily financial review
At the end of each day, the finance owner should review:
- payments entered that day;
- missing receipt numbers;
- missing bank references or proof;
- unmatched or unclear customer/contract links;
- duplicate-looking payments;
- voids or corrections;
- unresolved verification tasks; and
- customer disputes or urgent collections issues.
Common mistakes
- Confirming payment from a screenshot alone.
- Recording the transaction under the lead rather than the customer/contract.
- Using the proof upload as a substitute for the ledger entry.
- Entering the wrong transaction date.
- Saving twice after a slow response.
- Guessing a receipt or bank reference.
- Correcting a financial error by deleting history.
- Failing to tell Sales whether verification succeeded or failed.