Skip to main content

Delete Lock Amount - Product Documentation

Business Overview​

The Delete Lock Amount feature allows authorized bank staff to release temporary holds on customer funds that are no longer needed. When a lock is deleted, the held funds are immediately returned to the customer's available balance, restoring full access to those funds.

This capability is essential for managing various business scenarios where funds need to be temporarily reserved but the underlying transaction is cancelled, expires, or is no longer required. Common use cases include releasing expired card pre-authorizations, cancelling hotel holds, removing temporary legal holds, and reversing merchant reservations.

Key Benefits​

  • Immediate Fund Availability: Released funds are instantly available for customer use
  • Customer Satisfaction: Quickly resolve holds that are no longer needed
  • Operational Efficiency: Simple process to release funds without complex approvals
  • Audit Trail: Complete record of who released the hold and why
  • Reconciliation Support: Clear tracking of lock lifecycle from creation to deletion

Feature Capabilities​

What You Can Do​

  • Release temporary holds on customer funds
  • Restore full account balance immediately
  • Add explanatory notes for audit purposes
  • Track all lock deletions with timestamps
  • View complete history of deleted locks
  • Handle expired card pre-authorizations
  • Cancel hotel and rental car holds
  • Remove temporary legal or compliance holds

User Roles​

Operations Manager

  • Review and approve lock deletion requests
  • Monitor lock deletion patterns
  • Generate reconciliation reports
  • Handle escalated lock deletion issues

Customer Service Representative

  • Process customer requests to release holds
  • Explain lock deletion to customers
  • Verify customer identity before releasing
  • Document reason for lock deletion

Branch Teller

  • Release holds for walk-in customers
  • Process expired pre-authorization requests
  • Print lock deletion receipts
  • Update customer on fund availability

Compliance Officer

  • Review lock deletion audit trails
  • Ensure proper authorization for deletions
  • Monitor for unusual deletion patterns
  • Generate compliance reports

How It Works​

Lock Deletion Process​

When a lock is deleted, the system performs several coordinated actions:

  1. Validation: Verifies the lock exists and can be deleted
  2. State Update: Changes lock status from LOCKED to UNLOCKED
  3. Balance Restoration: Returns held amount to available balance
  4. Transaction Cancellation: Marks the hold transaction as CANCELLED
  5. Notification: Alerts customer of fund release
  6. Audit Logging: Records complete details of the deletion

Business Rules​

  • Lock must be in LOCKED state (cannot delete already SEIZED or UNLOCKED locks)
  • Original hold transaction must be in HOLD state
  • Funds are restored atomically (all-or-nothing operation)
  • Customer notification is sent automatically
  • Audit trail includes staff ID, timestamp, and reason
  • Lock deletion cannot be reversed (permanent operation)

Fund Flow​

Before Lock Deletion:

  • Account Balance: $10,000
  • Blocked Amount: $2,000 (locked)
  • Available Balance: $8,000

After Lock Deletion:

  • Account Balance: $10,000 (unchanged)
  • Blocked Amount: $0 (released)
  • Available Balance: $10,000 (fully restored)

Common Use Cases​

1. Expired Card Pre-Authorization​

Scenario: A customer made a $500 purchase with their debit card. The merchant pre-authorized the amount but never completed the transaction. After 7 days, the pre-authorization expires.

Process:

  1. Customer contacts bank about the lingering hold
  2. CSR verifies the merchant never settled the transaction
  3. CSR releases the lock using the card transaction reference
  4. Funds immediately become available
  5. Customer receives SMS notification

Timeline: 5-10 minutes from customer call to resolution

2. Hotel Hold Cancellation​

Scenario: Customer booked a hotel that placed a $1,000 hold on their account. The reservation was cancelled 2 days before check-in, but the hotel hasn't released the hold.

Process:

  1. Customer provides hotel confirmation and cancellation proof
  2. CSR verifies the cancellation with hotel (if needed)
  3. CSR deletes the lock with cancellation reason documented
  4. Customer can access funds immediately
  5. Confirmation email sent to customer

Timeline: 10-15 minutes including hotel verification

Scenario: A $5,000 legal hold was placed pending investigation. The investigation cleared the customer, and the hold needs to be released.

Process:

  1. Compliance receives clearance from legal department
  2. Compliance officer verifies proper authorization
  3. Lock is deleted with legal case reference number
  4. Customer is notified of hold release
  5. Case is closed in compliance system

Timeline: 1-2 hours from legal clearance to fund release

4. Merchant Reservation Release​

Scenario: Customer rented a car with a $300 security deposit hold. They returned the car with no damages, but the rental company hasn't released the hold after 3 days.

Process:

  1. Customer provides rental return receipt
  2. Teller contacts rental company for confirmation
  3. Teller releases the lock with rental agreement reference
  4. Customer withdraws cash from newly available funds
  5. Receipt printed showing released amount

Timeline: 15-20 minutes including merchant contact

UI Walkthrough​

Accessing Lock Deletion​

Navigation to Deposits

  1. Log into BankLingo Core Banking
  2. Navigate to Deposits → Account Management
  3. Search for the customer account by account number or customer name
  4. Open the account details page
  5. Click on the Locks & Holds tab
  6. Locate the specific lock to delete

Deleting a Lock​

Lock Deletion Form

Step-by-Step Process:

  1. Select Lock: Click the "Delete" button next to the lock entry
  2. Verify Details: Review lock information displayed:
    • Block Reference: BLK-2024-001234
    • Locked Amount: $2,000.00
    • Lock Reason: Card Pre-Authorization
    • Date Created: Dec 15, 2024 10:30 AM
  3. Add Notes: Enter reason for deletion (required):
    • "Merchant pre-auth expired after 7 days without settlement"
  4. Confirm Account: Verify account details match customer
  5. Submit Request: Click "Delete Lock" button

Confirmation Screen​

Lock Deletion Confirmation

The confirmation screen displays:

  • ✅ Lock successfully deleted
  • Released Amount: $2,000.00
  • New Available Balance: $10,000.00
  • Block Reference: BLK-2024-001234
  • Deleted By: Jane Smith (CSR-1023)
  • Timestamp: Dec 17, 2024 02:45 PM
  • Customer Notification: SMS sent to +1-555-0123

Post-Deletion Verification​

Account Balance Update

Verify the deletion:

  1. Check updated available balance
  2. Confirm lock status changed to UNLOCKED
  3. Review transaction history for CANCELLED entry
  4. Verify customer notification was sent
  5. Print receipt for customer if requested

Managing Lock Deletions​

Daily Operations​

Morning Review

  • Review overnight lock expiration reports
  • Identify locks pending deletion
  • Process expired pre-authorizations
  • Clear pending customer requests

Throughout the Day

  • Respond to customer inquiries about holds
  • Process walk-in lock deletion requests
  • Verify merchant settlements before releasing
  • Document all deletions with proper notes

End of Day

  • Reconcile all lock deletions
  • Review exception reports
  • Prepare summary for operations manager
  • Archive completed deletion requests

Authorization Levels​

Teller (Up to $1,000)

  • Standard card pre-authorizations
  • Hotel and rental holds
  • Merchant reservations
  • ATM holds

Customer Service Rep (Up to $5,000)

  • All teller-level deletions
  • Larger merchant holds
  • Multiple simultaneous locks
  • Disputed transaction holds

Operations Manager (Up to $25,000)

  • All CSR-level deletions
  • Legal hold releases
  • Court order holds
  • Special compliance cases

Branch Manager (No Limit)

  • All operations manager deletions
  • Executive account holds
  • Multi-account releases
  • Emergency situations

Best Practices​

  1. Always Verify Customer Identity

    • Check government ID for in-person requests
    • Use security questions for phone requests
    • Verify callback number matches account records

  2. Document Everything

    • Include specific reason for deletion
    • Reference related transaction IDs
    • Note any customer communications
    • Attach supporting documentation

  3. Confirm Before Releasing

    • Verify merchant hasn't settled transaction
    • Check with originating party if needed
    • Ensure no pending legal obligations
    • Review account for other restrictions

  4. Communicate Clearly

    • Explain process to customer
    • Set accurate time expectations
    • Confirm fund availability timing
    • Provide reference numbers

Reporting​

Available Reports​

Lock Deletion Summary

  • Daily count of deletions by staff member
  • Total dollar amount released
  • Deletion reasons breakdown
  • Average processing time

Expired Pre-Authorization Report

  • Pre-auths older than 7 days
  • Merchants with highest expiration rates
  • Recommended deletions
  • Customer impact analysis

Audit Trail Report

  • Complete deletion history by date range
  • Staff member activity logs
  • Authorization level compliance
  • Exception cases requiring review

Reconciliation Report

  • Locks created vs. deleted
  • Outstanding locks by age
  • Balance impact analysis
  • Month-end closure support

Generating Reports​

  1. Navigate to Reports → Deposits → Lock Management
  2. Select report type: "Lock Deletion Report"
  3. Choose date range
  4. Filter by staff member, branch, or amount range (optional)
  5. Select output format (PDF, Excel, CSV)
  6. Click "Generate Report"
  7. Review or download results

Troubleshooting​

Common Issues​

Issue: "Lock not found" error when trying to delete

Cause: Lock may have already been deleted or seized by another staff member

Solution:

  1. Refresh the locks list
  2. Check if lock status changed to UNLOCKED or SEIZED
  3. Review recent transaction history
  4. Contact supervisor if lock is genuinely missing

Issue: "Cannot delete seized lock" error

Cause: Lock has been permanently seized and funds debited from account

Solution:

  1. Explain to customer that lock was converted to permanent debit
  2. Review the seizure transaction details
  3. Identify why lock was seized (legal order, settlement, etc.)
  4. Direct customer to appropriate department for dispute if needed

Issue: Available balance not updating after deletion

Cause: System delay or database synchronization issue

Solution:

  1. Wait 30 seconds and refresh the account view
  2. Check if deletion actually completed successfully
  3. Review transaction log for balance update entry
  4. Contact IT support if balance remains incorrect after 5 minutes

Issue: Customer not receiving notification

Cause: Incorrect contact information or messaging service delay

Solution:

  1. Verify customer's phone number and email in system
  2. Check notification preferences
  3. Manually resend notification from transaction history
  4. Provide verbal confirmation and printed receipt as backup

Issue: "Transaction already settled" error

Cause: Merchant completed the settlement before lock could be deleted

Solution:

  1. Verify the settlement transaction in account history
  2. Explain to customer that merchant processed payment
  3. If customer disputes, initiate chargeback process
  4. Do not attempt to delete lock - it will auto-release

Training Requirements​

New Staff Training​

Week 1: Fundamentals

  • Understanding lock vs. seizure concepts
  • Lock lifecycle and states
  • Authorization levels and limits
  • System navigation basics

Week 2: Operations

  • Processing standard deletions
  • Handling customer inquiries
  • Documentation requirements
  • Using reporting tools

Week 3: Advanced Scenarios

  • Disputed transaction holds
  • Legal and compliance holds
  • Multi-lock deletions
  • Exception handling

Week 4: Practical Application

  • Shadow experienced staff
  • Process deletions under supervision
  • Handle real customer cases
  • Complete certification exam

Ongoing Education​

  • Monthly refresher on new policies
  • Quarterly compliance updates
  • Annual fraud prevention training
  • System update training as needed

Compliance & Audit​

Regulatory Requirements​

Record Retention

  • All lock deletions must be retained for 7 years
  • Audit trail includes staff ID, timestamp, IP address
  • Supporting documentation must be attached
  • Customer communications must be archived

Authorization Verification

  • Staff must be within authorization limits
  • Supervisory approval required for exceptions
  • Dual control for high-value deletions ($50,000+)
  • Automated alerts for unusual patterns

Customer Protection

  • Customer must be notified of all lock deletions
  • Deletions must be reversible via new lock creation
  • Customers can dispute unauthorized deletions
  • Clear explanation of deletion impact required

Audit Trail Contents​

Every lock deletion creates an audit record with:

  • Lock identification (block reference, amount, original reason)
  • Account identification (account number, customer name)
  • Staff identification (user ID, name, role)
  • Deletion details (timestamp, reason, notes)
  • System information (IP address, workstation ID)
  • Outcome (success/failure, balance changes)
  • Notification status (sent/failed, delivery confirmation)

Monthly Audit Process​

  1. Week 1: Export all lock deletion records
  2. Week 2: Review for policy compliance
  3. Week 3: Investigate exceptions and outliers
  4. Week 4: Report findings to management
  5. Ongoing: Implement corrective actions as needed

Integration Points​

External Systems​

Core Banking System

  • Real-time balance updates
  • Transaction history synchronization
  • Account state management
  • Customer profile access

Card Management System

  • Pre-authorization tracking
  • Merchant settlement status
  • Card transaction matching
  • Authorization code linking

Customer Notification System

  • SMS and email delivery
  • Delivery confirmation
  • Customer preference management
  • Template customization

Compliance & Legal System

  • Hold authorization tracking
  • Legal order management
  • Case reference linking
  • Document storage

API Integration​

Lock deletions can be triggered via API for automated scenarios:

  • Expired pre-authorization cleanup jobs
  • Merchant settlement reconciliation
  • Legal hold expiration processing
  • System-initiated releases

Frequently Asked Questions​

Q: Can a deleted lock be restored?

A: No, lock deletion is permanent. If funds need to be held again, a new lock must be created. The original lock reference remains in history but cannot be reactivated.

Q: What happens if a merchant tries to settle after lock is deleted?

A: The merchant settlement will be processed as a normal debit transaction. If sufficient funds are available, the transaction succeeds. If not, the account may become overdrawn or the transaction may be declined based on account settings.

Q: How quickly are funds available after deletion?

A: Immediately. The balance update is atomic and real-time. Customers can withdraw, transfer, or use the funds instantly after lock deletion.

Q: Can customers request lock deletion themselves?

A: Not directly. Customers must contact bank staff (phone, branch visit, or secure message). This ensures proper verification and prevents unauthorized deletions.

Q: What if I delete the wrong lock?

A: Contact your supervisor immediately. If the deletion was in error, a new lock can be created. Document the mistake in the incident log and follow your institution's error correction procedures.

Q: Are there fees for lock deletion?

A: Typically no. Lock deletion is considered an operational correction. However, if the lock was created due to customer overdraft or NSF, those fees may still apply.

Q: How do I handle bulk deletions?

A: For multiple locks on the same account, delete each lock individually with specific notes. For system-wide expired pre-auth cleanup, use the batch deletion tool under Reports → Automated Cleanup.

Q: What's the difference between deleting and seizing a lock?

A: Deletion releases the funds back to the customer (cancellation). Seizing converts the lock to a permanent debit (completion). Choose based on whether the underlying obligation was fulfilled.

Demo Script​

Scenario: Release Expired Card Pre-Authorization​

Setup: Customer Sarah Johnson calls about a $75 hold from Gas Station ABC that's been pending for 10 days.

Script:

  1. Greet Customer

    • "Thank you for calling. My name is [Your Name]. How can I help you today?"
    • Customer explains the lingering hold

  2. Verify Identity

    • "I'd be happy to help with that. For security, may I verify your account?"
    • Confirm account number, last 4 of SSN, and address

  3. Locate Lock

    • "Let me pull up your account... I can see the $75 hold from Gas Station ABC"
    • "It was created on December 1st, so it's been 10 days"

  4. Explain Situation

    • "This looks like a pre-authorization that was never settled"
    • "Gas stations typically have 7 days to complete the transaction"
    • "Since it's past that timeframe, I can release this hold for you right now"

  5. Process Deletion

    • "I'm going to delete this lock now... one moment please"
    • [Navigate to lock, click Delete, enter notes, submit]
    • "Done! The $75 is now available in your account"

  6. Confirm Results

    • "Your new available balance is $2,150"
    • "You should receive a text message confirmation shortly"
    • "You can use those funds immediately"

  7. Close Call

    • "Is there anything else I can help you with today?"
    • "Thank you for banking with us!"

Duration: 3-5 minutes

For additional support, contact the Operations Help Desk or refer to the Developer Documentation for technical implementation details.