The standard Salesforce Case field IsClosedOnCreate (also known as "Closed When Created") is documented to reflect a value of TRUE only when the Date/Time Closed equals the Date/Time Opened on a Case record. However, in practice this is not always the observed behavior.
When an organization reports on Case.IsClosedOnCreate, it is important to understand that "closed during creation" does not necessarily mean that the Date/Time Closed value precisely equals the Date/Time Opened value. While a user can create a Case and immediately choose to close it using the Save & Close button, both the IsClosedOnCreate flag and the DateClosed value are not written to the record until the Case is saved in a Closed status. This timing difference means the two timestamp values may not be exactly equal.
Salesforce allows multiple methods to create Case records. Any method that strays from the standard, linear creation flow may lead to discrepant behavior of the IsClosedOnCreate flag with respect to the Date/Time Closed and Date/Time Opened values.
This article explains why Case.IsClosedOnCreate may not behave as expected, and provides a recommended workaround for organizations that require a stricter definition of "Closed When Created."
If your organization requires "Closed When Created" to mean precisely that Date/Time Opened equals Date/Time Closed, the standard field does not reliably enforce this constraint due to the way the system processes and writes these values.
Recommended Workaround: Create a Custom Formula Field
Create a custom formula field on the Case object that explicitly evaluates whether DateOpened = DateClosed. Reference this custom formula field in your reports instead of the standard IsClosedOnCreate field.
This approach gives your organization a precise, deterministic calculation that is independent of system-write timing and supports accurate reporting in multilingual and high-volume Case creation environments.
000387621

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.