CPA score release dates are targets, and the published pattern changes in July 2027. AICPA currently lists October 19, 2027 for Core sittings from July 12 through September 30. That is a testing-date range, unlike the file-receipt cutoffs used in the earlier Core tables. Therefore, do not carry a short rolling-release assumption into the transition period.
Official sources checked October 26, 2026. Update owner: CPA Exam Prep editorial team. Recheck when AICPA changes the schedule or your intended sitting changes. This update covers remaining 2026 targets and the announced second-half 2027 shift. The official page also contains early-2027 and 2028 rows. Those dates, your actual result and your personal deadlines remain separate planning records.

CPA Score Release Dates Still Ahead in 2026
The current AICPA schedule provides the following late-2026 rows. AUD, FAR and REG are Core sections; BAR, ISC and TCP are Disciplines. First identify the section group. Then read the exact condition in the middle column before using the target.
| Section group | Published input condition | Target release |
|---|---|---|
| Core | AICPA receives the data file by October 23, 2026 | November 10, 2026 |
| Core | AICPA receives the data file by November 15, 2026 | November 24, 2026 |
| Core | AICPA receives the data file by December 8, 2026 | December 16, 2026 |
| Core | AICPA receives the data file by December 31, 2026 | January 12, 2027 |
| Discipline | Testing dates October 1–31, 2026 | December 15, 2026 |
Although October 23 has passed as of this check, its November target is still ahead. Also, the final Core row crosses into January 2027. Neither fact changes the row’s input condition. Your appointment date alone does not prove when AICPA received the file from Prometric.
What the July 2027 Transition Changes
AICPA’s platform-transition announcement gives target dates of July 1–11, 2027 for a testing pause and July 12 for testing to resume. It also explains that item recalibration after the new platform launches requires an adjusted score-release schedule for 12 months. Accordingly, candidates planning that period need the transition tables.
| Group | Testing dates | Target release |
|---|---|---|
| Core | July 12–September 30, 2027 | October 19, 2027 |
| Core | October 1–December 15, 2027 | December 28, 2027 |
| Discipline | July 12–August 12, 2027 | September 28, 2027 |
| Discipline | October 1–31, 2027 | December 17, 2027 |
These are announced dates, subject to change, rather than a candidate-specific release promise. In particular, a date inside a published testing range is not proof of appointment availability. Check the full official schedule if your plan reaches another period instead of extending these rows beyond their stated boundaries.
The published adjusted tables currently continue through the second quarter of 2028. However, that boundary does not authorize inventing the schedule for a later quarter. If your plan extends beyond the rows available, mark its release date unresolved and recheck when the responsible source publishes it.
Read the New Core Rows as Testing Ranges
The earlier Core table asks when AICPA receives the examination data file. For example, its June 8, 2027 cutoff points to June 16 as the target. The later table instead labels its first column “Testing Dates.” Therefore, copying the earlier heading above the July–September range would change what the source actually says.
For content questions, use the AICPA Blueprint resources for your sitting. A release date does not identify the syllabus or prove that a study edition applies.
Keep the original column meaning in your notes. For a late-2026 Core sitting, identify the file-receipt condition. For a Core sitting in the published July–September 2027 range, use that range’s target while preserving its provisional status. Neither method requires guessing a private transmission timestamp or inventing an individual processing guarantee.
Also verify conflicting CPA score release dates against the live official row. A year label or a recent page update does not establish that every cell is current. Save the source link, section group, row condition and check date together. That makes a later correction traceable without treating an old screenshot as permanent authority.
For example, if your copied cell says October 9 but the current official row says October 19, correct your copy and record the source checked. That comparison alone does not prove when AICPA changed its own page. Distinguish correcting a secondary copy from documenting an actual official revision.
Compare Mara’s AUD Dates Against One Target
Consider Mara, a fictional AUD candidate comparing August 10 and September 20, 2027. Assume both dates fit Mara’s personal authorization and that no appointment has been booked. These are proposed alternatives, not verified seats. Both dates sit inside the current Core July 12–September 30 range, which points to the same October 19 target.
| Proposed AUD sitting | Current published target | Calendar gap |
|---|---|---|
| August 10, 2027 | October 19, 2027 | 70 days |
| September 20, 2027 | October 19, 2027 | 29 days |
| October 1, 2027 | December 28, 2027 | 88 days |
The subtraction uses target date minus proposed sitting date; it excludes the starting day. Thus, 70 and 29 describe planning gaps, not measured score-processing times. Testing 41 days earlier within this particular range does not bring forward the published target. However, actual score availability can differ because the dates remain targets.
You can reproduce the first calculation as 21 remaining August days, 30 September days and 19 October days. The September alternative uses 10 remaining September days plus 19 October days. These are calendar days, not business days or a service standard promised by an administrator.
The October 1 alternative crosses into the next Core row. As a result, it points to December 28, not October 19. An 11-day move from September 20 therefore changes the published target by much more than 11 days. This is why a changed appointment should trigger a fresh row check.

The diagram is schematic, not to scale. Use the table for exact calendar-day calculations.
Plan Work That Does Not Require the Missing Result
Mara should not choose September merely because the arithmetic shows a shorter gap. Earlier testing could fit preparation, work or personal constraints better. Later testing could allow more useful study. Those considerations require Mara’s own facts; the release table cannot choose the better appointment or establish readiness.
Instead, divide the next tasks by whether the result is needed. Reviewing another section’s study coverage can often be planned without knowing this AUD outcome. Deciding that AUD must be retaken requires the actual result. Keep the latter decision open rather than converting a target date into an assumed failure or pass.
The NASBA examination FAQ explains that retaking a failed section depends on receiving the score, registering again, obtaining a new NTS and finding a testing date. Therefore, October 19 in the current table does not reserve an October retake. A later target also does not, by itself, extend an existing notice or credit deadline.
Core and Discipline CPA Score Release Dates Differ
Now change only the section group in a separate hypothetical check. A July 20, 2027 AUD sitting falls in the published Core range with an October 19 target. A July 20 ISC sitting falls in the Discipline July 12–August 12 range with a September 28 target. The same proposed day leads to different rows.
Do not treat that comparison as advice to switch a Discipline or as permission to book either sitting. It demonstrates why the section field matters when reading the update. Similarly, a September date that fits the Core range does not automatically fit the Discipline range. Check the relevant table before calculating a gap.
The following expandable branches help identify the rule to read. Open the branch that matches the section and period you are investigating. Then return to the current official row; this aid does not determine a candidate’s eligibility or retrieve a result.
Choose the applicable release rule
Is this a Core sitting through June 2027?
Read the applicable Core file-receipt cutoff and its target. Your appointment date alone does not prove when AICPA received the file.
Does the Core sitting fall July 12–September 30, 2027?
Use the current Testing Dates range, which points to October 19, 2027 as the target. Keep that target provisional and verify the live row again when the plan changes.
Are you investigating a Discipline sitting?
Choose the Discipline row for the correct year and testing period. A date that fits the Core range may fall outside the Discipline range.
Keep a Target Separate From an Available Score
NASBA’s score information confirms that targets are not guaranteed and that most jurisdictions receive scores through its candidate portal. An advisory result and the later Score Notice are separate events. Save the notice when it becomes available, because access is limited.
Our score-check guide covers the retrieval task. Here, the planning consequence is narrower: reserve decisions that require the actual result until that result exists. A missing score on a social-media timeline does not establish that your own result is late, passed or failed.
If the expected event is missing, identify it precisely before asking for help. “No advisory result yet” and “advisory result visible, notice missing” describe different situations. Also check whether the published target changed. Avoid using a provider’s usual posting hour as a guaranteed time for every jurisdiction.
Recheck CPA Score Release Dates When the Plan Changes
Finally, reopen the official schedule when you change the sitting date, section group or planning period. For Mara, moving within the July–September Core range keeps the same current target. Crossing into October changes the row. Neither comparison removes the need to confirm an appointment and follow personal deadlines.
Record the planning statement with its condition: “Proposed AUD sitting August 10; current range target October 19; 70-day calendar gap; seat unconfirmed.” Update that statement when evidence changes. The useful outcome is a plan that can absorb the announced release pattern, rather than a countdown presented as a promise.
