The current bill import functionality relies primarily on contact names for matching, which creates two significant problems:
### 1. Unreliable Contact Matching
- Contact names can change over time
- Even minor differences (single character) result in creating new duplicate contacts
- No fallback to more reliable identifiers
### 2. Character Encoding Problems
- Special characters (e.g., apostrophes in names like "O'Connor") cause import failures
- This particularly affects common surnames and business names
### Proposed Solution
Implement a hierarchical matching system for contacts during bill imports:
1. First attempt: Match by account code
2. Second attempt: Match by database ID
3. Final fallback: Match by contact name
### Benefits
- More reliable contact matching during bills import
- Reduced duplicate contact creation
- Better handling of contact name changes
- Elimination of character encoding issues
- Alignment with standard software engineering practices
- Reduces data integrity issues
This change would improve data accuracy and reduce manual cleanup work for users dealing with:
- Businesses with frequently changing names
- Contacts with special characters in names
- High-volume bill imports
- Integration with other systems
Dan Brady
supported this idea
·
The current bill import functionality relies primarily on contact names for matching, which creates two significant problems:
### 1. Unreliable Contact Matching
- Contact names can change over time
- Even minor differences (single character) result in creating new duplicate contacts
- No fallback to more reliable identifiers
### 2. Character Encoding Problems
- Special characters (e.g., apostrophes in names like "O'Connor") cause import failures
- This particularly affects common surnames and business names
### Proposed Solution
Implement a hierarchical matching system for contacts during bill imports:
1. First attempt: Match by account code
2. Second attempt: Match by database ID
3. Final fallback: Match by contact name
### Benefits
- More reliable contact matching during bills import
- Reduced duplicate contact creation
- Better handling of contact name changes
- Elimination of character encoding issues
- Alignment with standard software engineering practices
- Reduces data integrity issues
This change would improve data accuracy and reduce manual cleanup work for users dealing with:
- Businesses with frequently changing names
- Contacts with special characters in names
- High-volume bill imports
- Integration with other systems