Property Tax Payment Integration

Complete guide for integrating property tax assessments and payments using DyerPay's API and CSV features. Works with any property tax system including Tyler, Incode, and legacy databases.

Typical Scenario

County Tax Assessor's Office needs to accept property tax payments online. Property data lives in a legacy system with annual assessments, multiple parcels per owner, and periodic installment payments.

Data Source

Legacy property tax system or Tyler Technologies ERP

Update Frequency

Annual assessments, monthly balance updates

Volume

10,000 - 500,000 parcels

Step 1: Configure Field Mappings

Set up custom field aliases in your DyerPay dashboard to match your property tax system's terminology:

DyerPay Standard Fields

• account_number
• first_name
• last_name
• remaining_cents
• due_date
• address
• city
• state
• zip

Your Custom Aliases

→ "Parcel Number"
→ "Owner First Name"
→ "Owner Last Name"
→ "Tax Due"
→ "Due Date"
→ "Property Address"
→ "Property City"
→ "Property State"
→ "Property Zip"

Option A: API Integration

Best for: Automated nightly syncs, real-time updates, integration with existing software

Import Property Tax Balances

POST request to import or update property tax balances (up to 1,000 parcels per request):

curl -X POST https://api.dyerpay.com/v1/reports/{report_id}/balances/import \
  -u dp_live_propertytax_abc123: \
  -H "Content-Type: application/json" \
  -d '{
  "balances": [
    {
      "Parcel Number": "R12345-001",
      "Owner First Name": "John",
      "Owner Last Name": "Smith",
      "Tax Due": "2345.67",
      "Due Date": "2024-12-31",
      "Property Address": "123 Main Street",
      "Property City": "Springfield",
      "Property State": "IL",
      "Property Zip": "62701"
    },
    {
      "Parcel Number": "R12346-002",
      "Owner First Name": "Jane",
      "Owner Last Name": "Doe",
      "Tax Due": "3456.78",
      "Due Date": "2024-12-31",
      "Property Address": "456 Oak Avenue",
      "Property City": "Springfield",
      "Property State": "IL",
      "Property Zip": "62702"
    }
  ]
}'

API Response

{
  "success": true,
  "imported": 2,
  "updated": 0,
  "created": 2,
  "errors": []
}

Export Property Tax Payments

Retrieve payments for reconciliation back to your property tax system:

curl https://api.dyerpay.com/v1/reports/{report_id}/payments/export?start_date=2024-03-01 \
  -u dp_live_propertytax_abc123:

Option B: CSV Integration

Best for: Manual imports, annual assessment uploads, offices without IT resources

CSV Format Example

Export data from your property tax system and format as CSV with these columns:

Parcel Number,Owner First Name,Owner Last Name,Tax Due,Due Date,Property Address,Property City,Property State,Property Zip
R12345-001,John,Smith,$2,345.67,2024-12-31,123 Main Street,Springfield,IL,62701
R12346-002,Jane,Doe,3456.78,12/31/2024,456 Oak Avenue,Springfield,IL,62702
R12347-003,Bob,Johnson,"4,567.89",2024/12/31,789 Pine Road,Springfield,IL,62703

CSV Import Steps

1 Export property tax data from your system to Excel or CSV
2 Ensure column headers match your configured field aliases (case-insensitive)
3 Save as CSV (UTF-8 encoding recommended)
4 Log into DyerPay dashboard → Select your Property Tax report → Import Balances
5 Upload CSV file and review validation results before confirming

Common Property Tax Scenarios

Installment Payments

Many counties allow quarterly or semi-annual installments. Update balances after each installment deadline passes.

Tip: Use due_date field for the next installment due date. Update remaining balance as installments are paid.

Multiple Parcels Per Owner

Owners with multiple parcels can see all balances and pay individually or in bulk.

Tip: Use unique parcel numbers as account_number. DyerPay automatically groups by owner name/email.

Partial Payments

Taxpayers can make partial payments. Export payment data daily and update your system with remaining balances.

Tip: Set up automated nightly export to sync payment data back to your property tax system.

Enterprise Security & Compliance

DyerPay meets the highest security and compliance standards for government payment processing:

Compliance Certifications

PCI DSS Compliant: Payment Card Industry Data Security Standard certified for secure card processing
SOC 2 Compliant: Service Organization Control audited for security, availability, and confidentiality

Comprehensive Insurance Coverage

Business Liability Insurance: Full coverage for business operations
Cyber Security Insurance: Protection against data breaches and cyber incidents
E&O Insurance: Errors and Omissions coverage for professional services

Your taxpayers' payment data is protected by industry-leading security standards and comprehensive insurance coverage, giving your agency peace of mind.

Best Practices

✓ Recommended

• Use parcel number as the unique identifier
• Import all parcels at start of tax year
• Update balances after each installment period
• Export payments daily for reconciliation
• Include property address for easier lookup
• Test with a small batch first (10-50 parcels)

✗ Avoid

• Don't use owner name as the unique ID
• Don't import zero-balance paid accounts
• Don't mix current and prior year taxes
• Don't include special assessments in tax amount
• Don't forget to update for payment plans
• Don't import without testing field mappings