Note we are embarking soon on new improvements to the ESFA Submissions page - in release 5.08.0 due in Production
Setting up Standards
Against the standard there is a field called "External Standard Code". This is the unique numerical reference that the ESFA uses to reference the standard (sometimes referred to as a LARS code) i.e. Commis chef under Catering and Hospitality is 93.
Against Carpentry & Joinery is 239.
| Info |
|---|
NOTE since the introduction of the https://covalenttech.atlassian.net/l/c/cHhvMsuk a new tab contains the details for the Standard |
...
Under the Specialism tab and against the listed specialism there is a field called "Course Option".
...
These are the specialisms defined by the ESFA, based on the external standard code (LARS code). They are supplied by the ESFA and cannot be customised. Any specialism must have one of these set, otherwise submission to the ESFA for a certificate will be rejected.
...
Testing API on your UAT
| Info |
|---|
Firstly Note:- you do not require an API key for UAT |
...
"1" - leading digit
"xxxx" - 4 digits of EPAOrgId
"xxx" - 3 digits of LARS Standard Code (leading 0swill need a leading 0, if under 3 digits e.g. 80 will become 080)
"00 - 09" - 10 unique ulns per standard code
...
Example. For EPA0001, LARS Standard Code = ST023780, and 1st uln in the sequence
uln = "1" + "0001" + "080" + "01" = 10001237011000108001
givenNames = Test
familyName = 1000123701 1000108001 (same value as uln)
LARS standard code = 80
The next test ULN would be 10001237021000108002, then 100123703 100108003 etc.
Your EPAO registration number can be found on the Register of End Point Assessment Organisations if you do not know it
...
Reporting → Assessment → Certification Overview
...
Known error messages returned from ESFA
The most common error messages:-
...
You will need to check if the specialism has a course option set via Entity Management → Standards → Edit Standard → Specialisms → Course Option check the dropdown as you may have the course option set to 1.1 rather that 1.0.
...
The error is saying the apprentices are expected on standard version 1.0 (based on the image above you can see the version at the end of the /api/v1/standard/options/239/1)
...
This also includes instructions on two different ways to set up standards, in order to accommodate specialism versioning.
If you see this sort of issue within the EPAPro reports - the 'certificate submitted' date does not match the date of 'certificate created' then this is likely to be because the certificates were requested via the ESFA Portal. The ESFAs API cannot currently handle multiple submissions of certificates, for example if they have been re-printed with changes and so there will be an issue with the dates that are in EPAPro vs their online portal.