AccountID Shows as Null in Before Insert or Before Update Case Trigger During Email-to-Case or Manual Case Creation

This behavior is considered working as designed. Because the Account field is Read-Only for the Standard User (as determined by field-level security or the page layout), the AccountId is resolved from the database via the Contact record's relationship — a process that occurs after the Before Trigger events. During the Before Insert trigger, the AccountId has not yet been populated for users without edit access to the Account field.

Recommended Workarounds

Choose one of the following workarounds based on your implementation requirements:

Option 1: Make the Account Field Editable Make the Account field on the Case object editable for non-administrator users by updating both the field-level security settings and the Case page layout. This allows Salesforce to populate AccountId in the Before Insert trigger.

Option 2: Move Trigger Logic to After Trigger Context Move the trigger logic that depends on AccountId into the After Insert or After Update trigger context. In the After trigger context, AccountId is fully populated and accessible for all user profiles.

Option 3: Query the AccountId in the Before Insert Trigger In the Before Insert trigger, programmatically retrieve the AccountId by querying the Contact record using the ContactId from Trigger.new. Assign the Contact's AccountId to the Case's AccountId field within the trigger.

Note: the query approach requires a SOQL query per trigger invocation — ensure you are following bulkification best practices.