Skip to main content

Payment Editing

Learn how to modify and correct payment records in DooUMS while maintaining data integrity and audit compliance.

When to Edit Payments​

Payment editing should be used for:

✅ Appropriate Editing Scenarios​

  • Data Entry Errors: Incorrect amounts, dates, or reference numbers
  • Typographical Mistakes: Misspelled reference numbers or notes
  • Date Corrections: Wrong payment dates due to processing delays
  • Reference Updates: Bank-provided reference number changes
  • Amount Adjustments: Correction of calculation or entry errors

❌ Avoid Editing For​

  • Fraudulent Transactions: Use deletion or reversal instead
  • Refund Processing: Create separate refund/adjustment records
  • Package Changes: Modify package details, not payment records
  • Historical Corrections: Old verified payments without proper authorization

Pre-Edit Considerations​

Authorization Requirements​

Before editing any payment:

  • ✅ Confirm you have appropriate user permissions
  • ✅ Check if payment is verified (may require special authorization)
  • ✅ Gather supporting documentation for the change
  • ✅ Consider impact on financial reports and reconciliation

Documentation Preparation​

Collect necessary evidence:

  • Original Documentation: Bank slips, receipts, transfer confirmations
  • Correction Evidence: Updated bank statements, pilgrim communications
  • Authorization Records: Approvals for changes (if required)
  • Audit Trail: Reasons for modification with supporting details

Step-by-Step Editing Process​

1. Locate Payment to Edit​

  1. Navigate to Payments page
  2. Find the specific payment using:
    • Search Bar: Pilgrim name, receipt number, or reference
    • Filters: Date range, payment type, verification status
    • Pagination: Browse through payment pages

2. Access Edit Function​

  1. Locate the payment row in the table
  2. Click Actions → Edit
  3. The payment editing form will open
  4. Review current information before making changes

3. Make Required Changes​

Field Modification Guidelines​

Pilgrim Selection​
  • When to Edit: Wrong pilgrim linked to payment
  • Caution: Ensure new pilgrim has valid registration
  • Impact: Changes pilgrim's payment history and balance
Payment Type​
  • When to Edit: Incorrect payment category selected
  • Options: Deposit, Second Payment, Third Payment, Final Payment
  • Impact: Affects payment schedule and balance calculations
Receipt Number​
  • When to Edit: Duplicate or incorrect receipt numbers
  • Format: Follow organization's receipt numbering system
  • Impact: Affects receipt generation and tracking
Reference Number​
  • When to Edit: Bank provides corrected reference
  • Accuracy: Must match bank documentation exactly
  • Impact: Critical for bank reconciliation
Amount​
  • When to Edit: Wrong amount entered or bank correction
  • Validation: Double-check against bank evidence
  • Impact: Changes package balance and payment status
Payment Date​
  • When to Edit: Actual transaction date differs from entry
  • Consideration: Use actual bank processing date
  • Impact: Affects financial reporting periods
Notes/Description​
  • When to Edit: Add clarification or correct information
  • Best Practice: Append edit reason rather than overwriting
  • Format: Include date and reason for changes

4. Verify Changes​

Before saving modifications:

  • ✅ Double-Check Accuracy: All fields contain correct information
  • ✅ Cross-Reference: Changes match supporting documentation
  • ✅ Impact Assessment: Consider effects on related records
  • ✅ Validation: Ensure data formats and requirements met

5. Save and Document​

  1. Click Save button to apply changes
  2. Add Edit Reason: Include explanation in notes or comment field
  3. Expected Result: Payment table updates with modified information
  4. Document Change: Record edit details for audit trail

Editing Scenarios and Examples​

Scenario 1: Amount Correction​

Situation: Payment entered as RM 3,150 but bank shows RM 3,510

Original Entry:

  • Amount: 3150
  • Reference: 15022025 13:33 CASH DEPOSIT CIMB

Editing Process:

  1. Locate payment record
  2. Click Actions → Edit
  3. Update Amount field: 3510
  4. Add to Notes: Amount corrected from RM 3,150 to RM 3,510 per bank statement dated 2025-02-16
  5. Save changes

Documentation: Attach bank statement showing correct amount

Scenario 2: Reference Number Update​

Situation: Bank provides updated reference number for transaction

Original Entry:

  • Reference: TEMP-REF-001
  • Amount: 2500

Editing Process:

  1. Access payment edit form
  2. Update Reference field: TXN20250215078965
  3. Add to Notes: Reference updated with bank-provided transaction ID on 2025-02-16
  4. Save changes

Documentation: Bank communication confirming reference number

Scenario 3: Date Correction​

Situation: Payment processed on different date than initially recorded

Original Entry:

  • Payment Date: 2025-02-15
  • Reference: 16022025 09:45 ONLINE TXN

Editing Process:

  1. Open payment for editing
  2. Update Payment Date: 2025-02-16
  3. Add to Notes: Date corrected to actual bank processing date per statement
  4. Save changes

Documentation: Bank statement showing actual processing date

Scenario 4: Pilgrim Correction​

Situation: Payment mistakenly linked to wrong pilgrim

Original Entry:

  • Pilgrim: Ahmad Bin Ali
  • Amount: 1500

Editing Process:

  1. Edit payment record
  2. Update Pilgrim field: Select Fatimah Binti Ahmad
  3. Add to Notes: Pilgrim corrected - payment was made by Fatimah Binti Ahmad, not Ahmad Bin Ali. Verified with counter receipt dated 2025-02-15
  4. Save changes

Documentation: Counter receipt with correct pilgrim signature

Handling Verified Payments​

Special Considerations for Verified Payments​

Additional Authorization​

  • May require supervisor approval
  • Need documented reason for change
  • Consider financial reporting impact
  • Follow organization's change control procedures

Re-verification Requirements​

After editing verified payments:

  1. Status Change: Payment may revert to "Not Verified"
  2. Re-verification Process: Must verify payment again
  3. Documentation Update: Include edit explanation in verification
  4. Audit Trail: Maintain clear record of all changes

Best Practices for Verified Payment Edits​

Before Editing:​

  • Get proper authorization if required
  • Document comprehensive reason for change
  • Notify relevant stakeholders (finance team, auditors)
  • Backup original data if possible

During Editing:​

  • Make minimal necessary changes only
  • Preserve original information in notes
  • Add timestamp and editor identification
  • Include reference to authorization

After Editing:​

  • Re-verify payment immediately
  • Update related documentation
  • Notify affected parties of changes
  • File edit authorization documents

Edit Validation and Quality Control​

Automatic Validations​

The system typically checks for:

  • Required Fields: All mandatory fields completed
  • Data Formats: Proper number, date, and text formats
  • Business Rules: Valid pilgrim associations and amount ranges
  • Duplicate Prevention: Unique receipt and reference numbers

Manual Quality Checks​

Before finalizing edits:

  • ✅ Accuracy Verification: All changes match source documents
  • ✅ Consistency Check: Related fields align logically
  • ✅ Impact Assessment: Consider effects on reports and balances
  • ✅ Documentation Review: Adequate explanation for changes provided

Common Editing Challenges​

Challenge 1: System Validation Errors​

Problem: System rejects edit due to validation rules Solutions:

  • Check required field completion
  • Verify data format compliance
  • Review business rule conflicts
  • Contact system administrator if needed

Challenge 2: Verification Status Confusion​

Problem: Uncertainty about re-verification requirements Solutions:

  • Check organization's verification policy
  • Document edit reason clearly
  • Plan immediate re-verification
  • Consult with finance supervisor

Challenge 3: Audit Trail Concerns​

Problem: Maintaining proper change documentation Solutions:

  • Use structured comment format
  • Include date, reason, and authorization
  • Attach supporting documentation
  • Follow consistent editing procedures

Edit Tracking and Audit Trail​

System-Generated Tracking​

Most systems automatically record:

  • Edit Timestamp: When change was made
  • User Identification: Who made the change
  • Field Changes: What specifically was modified
  • Original Values: Previous data for comparison

Manual Documentation Requirements​

In addition to system tracking:

  • Reason Documentation: Clear explanation for each change
  • Authorization Records: Approval documentation if required
  • Supporting Evidence: Attachments or references to source documents
  • Impact Assessment: Effects on related records and reports

Audit Preparation​

For compliance and audit purposes:

  • Maintain chronological edit logs
  • Organize supporting documentation
  • Prepare change summary reports
  • Ensure all edits have proper authorization

Integration Impact​

Pilgrim Records​

  • Payment history updates
  • Balance recalculations
  • Status changes

Package Management​

  • Payment schedule adjustments
  • Completion status updates
  • Balance tracking modifications

Financial Reporting​

  • Report data changes
  • Reconciliation adjustments
  • Period-end calculations

Communication Requirements​

After significant edits:

  • Finance Team: Notify of amount or date changes
  • Package Managers: Inform of status impacts
  • Audit Team: Document for compliance tracking
  • Pilgrim Services: Update customer records if needed

Next Steps​

After mastering payment editing:

  1. Learn Search and Filtering to efficiently locate payments for editing
  2. Explore Troubleshooting for handling complex editing scenarios
  3. Review Payment Verification for re-verification procedures