Apply Customer Payments to Properties

Goal

Manually apply customer payments to specific properties and tax types when automated matching is not possible or when special circumstances require manual intervention.

[Screenshot: Customer Payment Application Dashboard showing pending payments requiring manual assignment]

When to Use This Workflow

  • Unmatched payments: Automated matching failed and manual assignment is needed

  • Special circumstances: Payment requires specific allocation or handling

  • Partial payments: Customer paid less than full amount and allocation must be specified

  • Dispute resolutions: Payments related to customer disputes or account adjustments

  • Multiple property payments: Single payment covers multiple properties

  • Historical corrections: Applying payments to prior tax years or correcting previous errors

Prerequisites

Before starting this workflow, ensure you have:

  • Customer ledger access: Permission to view and modify customer payment records

  • Property payment history: Access to complete payment and assessment history

  • Authorization levels: Appropriate permissions for manual payment applications

  • Payment documentation: Original payment receipts or bank records

  • Tax year knowledge: Understanding of which tax year the payment should apply to

[Screenshot: User Permission Settings screen showing payment application authorization levels and access controls]

Step-by-Step Instructions

Step 1: Locate the Payment

  1. Navigate to PaymentsUnmatched Payments or Payment Research

  2. Search for the payment using available criteria:

    • Payment amount

    • Payment date

    • Check/reference number

    • Bank transaction ID

  3. Select the payment that needs manual application

  4. Review payment details including amount, date, and source

[Screenshot: Unmatched Payments search interface with filter options and payment list grid showing Amount, Date, Reference, and Source columns]

Step 2: Research Customer and Property Information

  1. Use available information to identify the correct property:

    • Customer name (exact or partial match)

    • Property address

    • Account number or property ID

    • Previous payment history

  2. Click Customer Search or Property Search

  3. Review multiple potential matches if necessary

  4. Verify property ownership and current status

[Screenshot: Customer and Property Search dialog with search fields and results grid showing potential matches with confidence scores]

[Screenshot: Property Details screen displaying ownership information, current status, and property characteristics]

Step 3: Access Property Payment History

  1. Once property is identified, click View Payment History

  2. Review current balances for all tax types:

    • Current year property tax

    • Prior year balances

    • Special assessments

    • Interest and penalties

  3. Note payment priority order based on municipal policy

[Screenshot: Property Payment History screen showing chronological payment list with balances for each tax component and year]

Step 4: Determine Payment Allocation

  1. Compare payment amount to outstanding balances

  2. Apply municipal payment allocation rules (typically oldest first)

  3. For partial payments, determine which components to pay:

    • Principal tax amounts

    • Interest charges

    • Penalty fees

    • Special assessments

  4. Document allocation decision in payment notes

[Screenshot: Payment Allocation Calculator showing outstanding balances by component with suggested allocation amounts based on municipal policy]

Step 5: Apply Payment to Property

  1. Click Apply Payment on the selected property

  2. Specify payment allocation:

    • Select tax year(s)

    • Choose specific tax components

    • Enter amounts for each component

  3. Verify total allocation equals payment amount

  4. Add detailed notes explaining manual application reason

  5. Click Process Application

[Screenshot: Payment Application screen with tax year tabs, component breakdown fields, and allocation summary section]

[Screenshot: Payment Application Confirmation dialog showing before and after balances with detailed transaction breakdown]

Step 6: Verify and Confirm

  1. Review payment application summary

  2. Check that property balance is correctly updated

  3. Confirm payment status changed to "Applied"

  4. Generate payment confirmation if required

  5. Document any special circumstances in customer notes

[Screenshot: Payment Application Results screen showing updated account balance, transaction confirmation number, and customer notification options]

Example Scenario

Multiple Property Payment Application:

  • Customer submits $3,500 payment for three rental properties

  • Payment note indicates: "Property A: $1,200, Property B: $1,100, Property C: $1,200"

  • Research confirms customer owns all three properties

  • Apply payment as directed: $1,200 to Property A current year tax, $1,100 to Property B (partial payment), $1,200 to Property C current year tax

  • Document specific allocation in payment notes for audit trail

[Screenshot: Multiple Property Payment Application screen showing three property tabs with individual allocation amounts and running total]

Common Errors & How to Fix Them

Incorrect Property Assignment

Problem: Payment applied to wrong property due to similar names or addresses
Solution:

  • Always verify property ownership before applying payment

  • Check property ID numbers against customer records

  • Cross-reference with previous payment history

  • Reverse incorrect application and reapply to correct property

[Screenshot: Property Verification screen showing ownership confirmation with highlighted warnings for similar addresses or names]

Overpayments

Problem: Payment amount exceeds current balance on property
Solution:

  • Check if payment should apply to multiple tax years

  • Verify if customer has other properties with balances

  • Create credit balance if overpayment is confirmed

  • Contact customer to clarify payment intent

[Screenshot: Overpayment Resolution dialog with options for credit balance creation, multiple property application, or customer contact]

Timing Issues

Problem: Payment applied to wrong tax year or billing cycle
Solution:

  • Review payment date against tax year deadlines

  • Check customer's payment intent from documentation

  • Apply to correct tax year even if it creates credit in current year

  • Adjust interest calculations if payment timing affects charges

[Screenshot: Tax Year Selection screen with payment timing analysis and interest calculation impact display]

Allocation Errors

Problem: Payment not allocated according to municipal policy
Solution:

  • Review standard payment allocation procedures

  • Correct allocation to follow oldest-first or other policy

  • Recalculate interest if allocation affects penalty dates

  • Document any approved deviations from standard policy

[Screenshot: Payment Allocation Policy Reference screen showing standard allocation order with override authorization options]

What Happens After This Workflow

Immediate Results:

  • Payment Applied: Customer payment correctly allocated to specified property and tax components

  • Balance Updated: Property tax balance reflects payment application

  • Customer Record: Payment history updated with manual application details

  • Audit Trail: Complete documentation of manual application process and reasoning

Follow-up Actions:

  • Customer Notification: Send payment confirmation showing allocation details

  • Balance Verification: Confirm property balance calculations are accurate

  • Exception Reporting: Include manual applications in daily payment processing reports

  • Quality Review: Supervisor review of manual applications if required by policy

Tips for Success

  • Always document the reason for manual application in detailed notes

  • Double-check property ownership and current status before applying payments

  • Follow municipal payment allocation policies consistently

  • Keep detailed records of customer communications regarding payment intent

  • Review manual applications regularly to identify process improvement opportunities

  • Train staff on proper research techniques to minimize manual applications

Screenshot Placeholders

[Screenshot: Manual Payment Application Workflow Overview diagram showing decision points and process flow]

[Screenshot: Payment Research Tools menu displaying available search methods and data sources]

[Screenshot: Customer Account Overview screen showing all properties owned with current balance summary]

[Screenshot: Payment Allocation Policy Configuration displaying municipal rules and priority settings]

[Screenshot: Payment Application Audit Log showing complete transaction history with user actions and timestamps]

[Screenshot: Batch Payment Application interface for processing multiple related payments simultaneously]

[Screenshot: Payment Application Exception Report listing manual applications requiring supervisor review]

[Screenshot: Customer Communication Templates for payment confirmation and balance update notifications]

[Screenshot: Quality Control Dashboard showing manual application statistics and accuracy metrics]

[Screenshot: Payment Reversal Interface for correcting incorrectly applied payments with authorization workflow]

[Screenshot: Advanced Search Options for locating properties using partial information and fuzzy matching]

[Screenshot: Payment Application Training Mode showing guided walkthrough of manual application process]