It depends on how the account information will be used. Different identifiers serve different purposes.
| Identifier | Unique | Can Change | User Friendly | Best Use |
|---|---|---|---|---|
| Salesforce Account ID | ✅ Yes | ❌ No | ❌ No | Integrations, APIs, data imports, and database relationships |
| Salesforce Account Number | ✅ If maintained as unique | ⚠️ Yes (unless controlled) | ✅ Yes | Business identifier, reports, and integrations |
| GoldFinch Customer No. | ✅ Yes | Usually No | ✅ Yes | Customer transactions and references within GoldFinch |
| GoldFinch Vendor No. | ✅ Yes | Usually No | ✅ Yes | Vendor transactions and references within GoldFinch |
| Account Name | ✅ If duplicate prevention is enabled | ⚠️ Yes | ✅ Best | User searches and day-to-day identification |
Recommendation
For integrations, imports, and data synchronization, the Salesforce Account ID is the best identifier. It is system-generated, guaranteed to be unique, and never changes, making it the most reliable technical key.
For business users, the preferred identifiers are the GoldFinch Customer No., Vendor No., or Salesforce Account Number, since they are shorter, more meaningful, and easier to reference during daily operations.
Account Name is the easiest identifier for users to recognize and search. If Salesforce is configured with Matching Rules and Duplicate Rules to prevent duplicate Account Names, it can also serve as a practical business identifier. However, because Account Names may change over time (for example, due to company name changes or corrections), they should not be used as the permanent technical identifier.
In summary:
- Use Salesforce Account ID for integrations and system-to-system processes.
- Use Customer No., Vendor No., or Account Number for business operations.
- Use Account Name for searching and display, with duplicate prevention enabled whenever possible.
Comments
0 comments
Please sign in to leave a comment.