REL-2026-06-01

Logic to determine if an auditor can purchase a specific exam (Part 1, 2, or 3). Includes prerequisites (status, sequencing), generating the invoice line item, capturing exam language preferences, and enforcing invoice validity periods.

Workflow for Firm users to select multiple employed auditors, validate their eligibility in batch, and generate a single bulk invoice for multiple exams.

The API integration with ProctorU (for Part 1/2) and the hybrid Calendly-to-ProctorU flow (for Part 3). Includes enforcing lead times, mapping time zones, and creating/linking ProctorU accounts via API.

Logic for auditor self-service exam changes. Includes enforcing fee windows, reschedule limits, and determining payer based on original invoice ownership.

A ticketing workflow for Firms to request changes for exams they funded. Includes logic to transfer credits, cancel exams without auditor consent, and manage disputes.

The day-of workflow for exam delivery. Generating the unique launch link, managing status transitions, and providing backup access if the platform is inaccessible.

Processing webhooks from ProctorU, mapping external statuses to APSCA statuses, and handling manual score entry.

Automation of status changes and requirements based on failure counts. Enforces waiting periods and training/audit log redo requirements.

Backend management of exam type definitions containing metadata required by the ProctorU API (duration, allowed resources, proctor notes) for each exam type and language variant.

Administrative interface to view, schedule, reschedule, or force-cancel exams on behalf of auditors, including the ability to override standard business rules.