Skip to main content

Payments

Payments is the financial ledger for transactions recorded in the Wamule Operations Platform. A payment entry should represent an actual transaction that has been received and verified according to Wamule Development's financial procedure.

A reservation, promised deposit, uploaded proof, WhatsApp message, or buyer statement is not a payment entry. Those items may support follow-up, but the financial record must be created and completed separately.

What a payment record may contain​

Depending on the transaction and payment method, review or enter:

  • customer;
  • related contract, when applicable;
  • payment date;
  • amount;
  • transaction type;
  • collection or payment method;
  • authorization or approval context;
  • manual receipt number;
  • bank or transfer reference;
  • notes;
  • supporting proof or document link; and
  • created/updated history.

Use the business's approved source documents and naming standards. Do not invent a receipt number or enter a placeholder that could later be mistaken for a real reference.

Before recording a payment​

Confirm:

  1. the correct customer;
  2. the correct contract or account, where applicable;
  3. the amount and currency;
  4. the date represented by the transaction;
  5. the payment method;
  6. the evidence required for that method;
  7. whether a receipt or bank reference is required; and
  8. that an entry has not already been created.

Search recent payments before retrying after a slow page or error. Duplicate financial entries can create incorrect balances and customer statements.

Recording a cash payment​

A cash-payment procedure should include:

  1. Count and verify the amount according to the business's cash-handling controls.
  2. Confirm the customer and contract.
  3. Select the correct payment or transaction type.
  4. Enter the amount and payment date.
  5. Select the cash collection method.
  6. Enter the required manual receipt number.
  7. Add a concise note when context is needed.
  8. Save once.
  9. Confirm the saved record appears in Payments and the customer/contract history.
  10. Confirm the receipt process was completed according to business policy.

Do not leave the receipt number blank when the process requires it. Do not reuse a receipt number.

Recording an online transfer​

For a bank or online transfer:

  1. Confirm the funds or approved evidence according to Wamule's reconciliation procedure.
  2. Verify the sender/customer and intended contract or account.
  3. Enter the amount and transaction date.
  4. Select the correct transfer payment method.
  5. Enter the bank or transaction reference exactly as required.
  6. Upload or link approved proof where supported.
  7. Record any exception or reviewer note.
  8. Save once and confirm the entry.
  9. Ensure any separate verification or authorization step is completed.

Uploaded proof does not by itself prove that funds are settled, correctly allocated, or free of duplication. Follow the business's financial verification process.

Deposit payments​

A reservation or deposit-readiness record may indicate that a deposit is expected, promised, or supported by proof. The deposit becomes part of the financial ledger only when the actual payment is recorded and verified.

Before telling Sales or the buyer that the deposit is confirmed:

  • open Payments;
  • confirm the correct customer or contract;
  • check amount, date, method, and references;
  • review proof and authorization requirements; and
  • confirm the reservation/contract workflow reflects the verified outcome.

Verifying that the payment saved​

After saving:

  • wait for the confirmation or updated page;
  • search by customer, date, amount, or reference;
  • confirm only one entry exists;
  • open the entry and review every field;
  • check the customer/contract balance or statement according to the implemented workflow; and
  • record or escalate any discrepancy.

If the page appears to fail, do not immediately submit again. First check whether the record was created.

Correcting a payment mistake​

Financial corrections should preserve accountability.

  1. Stop and identify exactly what is wrong.
  2. Do not delete or overwrite evidence casually.
  3. Confirm who is authorized to correct, void, or reverse the entry.
  4. Review the original source document and payment record.
  5. Use the approved correction, void, or reversal process.
  6. Record the reason and authorizer.
  7. Confirm the customer, contract, balance, statement, and Audit Trail reflect the expected result.
  8. Notify affected staff when the correction changes a customer-facing balance or receipt.

Restricted data-management tools are not the normal way to fix a live payment.

Missing-information queues​

Payments may appear in attention queues because of:

  • missing manual receipt number;
  • missing transfer proof;
  • missing bank reference;
  • unclear customer or contract link;
  • incomplete authorization information;
  • duplicate-looking date/amount/reference; or
  • a discrepancy with a statement or balance.

Resolve the missing information from an approved source. Do not fill the field with “N/A,” a guess, or an unrelated value merely to clear the alert.

Example: transfer proof received before payment verification​

A fictional buyer, Elena Training, sends a screenshot showing a transfer of BZ$500 for a reservation deposit.

  1. Sales records the buyer communication in the lead or reservation activity.
  2. Finance reviews the proof and verifies the transaction according to the approved banking process.
  3. Finance searches Payments to confirm no entry already exists.
  4. The payment is recorded against the correct customer/contract with the amount, date, method, reference, and proof.
  5. Finance confirms the saved entry and any balance change.
  6. Sales is informed that the payment has been financially recorded.
  7. The reservation/deposit-readiness workflow is updated separately as required.

The proof, payment entry, and reservation status are related but distinct records.

Reviewing payment history​

When reviewing a customer or contract:

  • confirm the date range;
  • compare amounts and transaction types;
  • review voided or corrected entries;
  • check receipt and bank references;
  • confirm proof is associated with the correct payment;
  • investigate duplicates or gaps; and
  • compare the history with the customer statement or contract balance.

Common mistakes​

  • Recording a payment from a message without financial verification.
  • Selecting the wrong customer or contract.
  • Entering the promise date instead of the transaction date.
  • Saving twice after a slow response.
  • Omitting a required receipt number or bank reference.
  • Uploading proof to the wrong payment.
  • Treating a reservation or deposit-readiness status as the ledger entry.
  • Correcting a live payment through destructive data tools.
  • Assuming a Dashboard alert or AI insight confirms financial truth.

Suggested training media​

Screenshot space: Add a payment-entry form screenshot using a fictional customer. Label customer, contract, amount, transaction type, payment method, payment date, receipt number, bank reference, proof, authorization, and notes.
Screenshot space: Add a saved payment-detail screenshot and the same payment as it appears in the customer or contract history. Use arrows to show how staff confirm the entry saved correctly.
Screenshot space: Add a missing-information example showing a transfer with no bank reference or proof. Annotate the approved source staff should use to complete each field.
Diagram space: Add a payment-control flow: Receive evidence → Verify transaction → Search for existing entry → Record payment → Confirm save → Review balance/statement → Update related operational workflow.
Video space: Record an 8–10 minute walkthrough showing one cash payment and one online transfer using fictional Training Data. Include the duplicate-check step, proof/reference requirements, and post-save verification.