伊人直播

Introduction

This page provides quick links for Financial Managements Systems (FMS) software providers with information needed to integrate their software with the DfE鈥檚 financial data collection forms.

Detailed information about the academies chart of accounts (CoA) can also be found here.

Academy trust finance automation: guide to software integration

This provides FMS software providers with the information needed to register the software product and prepare for integration with the DfE鈥檚 automation API. It is intended for use by business analysts, technical architects and software developers.

Find and Use an API

The (previously known as the Developer Hub) is a self-service portal for FMS software providers to register their product and subscribe to the submission API. A provider can register the application, generate the client credentials and the subscription keys for the API.

Test environments

You can read full details about test environments on the site.

• The is used by software providers to test their use of the API. Live data must not be used within this environment. This environment is available all year round.

• The user acceptance testing (UAT) environment is no longer used.

Academies chart of accounts

Academies chart of accounts versions

The academies CoA version defines the account codes being used for the financial year. The version format has three digits (for example: 2.0.0).

Submissions via the API must include a 鈥�CoA version鈥�. Format requirements and validation requirements are detailed in the .

The academies chart of accounts (CoA) is published each spring at Academies chart of accounts and automating the accounts return. Two versions are available concurrently for trusts:

1. The 鈥榣补迟别蝉迟鈥� CoA version is released in the spring in advance of the next financial year. This provides trusts with an up-to-date CoA version for their budget planning and FMS suppliers should ensure updates are enabled clients general ledger.

2. The 鈥榩谤别惫颈辞耻蝉鈥� CoA version: this will be used for the remainder of the current financial year, even though there will be some overlap with the latest CoA version. It will also be used for the accounts return (AR) collection for the same financial year.

Academies CoA 鈥榟ybrid鈥� versions (updated for FMS provider systems only)

The academies CoA version for the relevant financial year is updated for mapping changes required in the AR collection for the same period. No changes will be made to the account codes themselves.

Two updates will be released during the year leading up to the next AR collection period to FMS suppliers only. We will publish links on this page.

• 1st update: to be released in March prior to the AR collection window: this will contain all known updates and will be the 鈥楲atest鈥� published CoA version at this point in time, please follow link to download

• 2nd update: to be released in prior to the AR collection window: this will contain all final updates and will be the 鈥楶revious鈥� published CoA version at this point in time, please follow link to download

Academies CoA version change logic

The academies CoA version can change depending on the changes made to the CoA for the financial year. We will avoid major changes whenever possible and communicate these separately if required.

Revision	Academies CoA change
Major (1st digit)	- ACoA code change
Minor (2nd digit)	- Mapping change - Signage adjustment change - Rounding account change - Description changes or reformatting
Maintenance 鈥� internal updates only (3rd digit)	- Description changes or reformatting

However, it is only essential for the FMS software to be using the correct major version number for the trust to be able to send automated data to the DfE, but it is recommended that you use the most up to date version if your software has system reports based on the mapping.

DfE temporary account codes

We have introduced temporary grant income codes into the academies CoA so that trusts can react to reporting requirements that change mid accounting year.

FMS providers should add these account codes to their databases as inactive codes, which can be switched to active during the financial year, following advice from the DfE. We will communicate any updates to you via e-mail from our helpdesk, so please ensure your contact details are up to date.

This change would affect a 鈥榤inor (2nd digit)鈥� update to the version number as the account code already exists.

For more information view 鈥楢CoA account code structure鈥� section of the 鈥楪uide for software integration with automation API鈥�.

Academies CoA timeline and impacts

The table below shows the timings for academies CoA releases working up to the accounts return collection.

Time	Activity
May or June	Publish academies CoA for the upcoming academic year
September to August	Trusts use this academies CoA version in their FMS
March or April	An updated version of the academies CoA is 聽shared with FMS providers for upcoming accounts return (AR) to review changes
May or June	Above version will be loaded into the supplier test environment for trusts to begin testing for upcoming AR
August	A final version of the academies CoA is released for any mapping changes identified since March for the upcoming AR, and loaded into the DfE鈥檚 back-end functionality to map the API to the AR
September to Jan	AR collection window - no academies CoA changes

Communicating academies CoA changes

We will publish changes to academies CoA for the next academy trust year (the 鈥榣补迟别蝉迟鈥� version) on the Academies chart of accounts and automating the accounts return in:

• the 鈥楪uide to adopting the academies chart of accounts鈥� updates section
• the 鈥楢cademies chart of accounts鈥� change control tab

FMS suppliers must review the academies CoA updates and take the following action so trusts can update their systems for the financial year ahead:

• where a trust has adopted the academies CoA within the general ledger (natively), ensure they have the ability to apply any required changes into their general ledger
• where a trust is mapping its own academies CoA to the DfE鈥檚 academies CoA via the FMS supplier鈥檚 software, suppliers must also communicate changes to their trusts to ensure they have the equivalent change made in their own academies CoA and the mapping is created to the DfE鈥檚 academies CoA

We will release the 鈥榟ybrid鈥� versions of the academies CoA in line with the timelines stated above. We will notify supplier directly when we release updates by:

• adding to the Information for software suppliers page
• sending a bulletin to all contacts from our
• including a notification in our FMSWire newsletter, sent to all contacts and added as a link to our help centre
• you can also receive instant notifications of our webpage updates by clicking on 鈥楪et e-mails about this webpage鈥� from the Academies chart of accounts and automation homepage

Enquiries

If you have any questions, please submit a ticket via our

FMS provider help centre:听

Our provides a single platform for FMS software providers to view up to date information about academies CoA, view alerts鈥痑nd raise enquiries or let us know about updates. Incidents which require FMS software provider support received from academy trusts will also be raised via our help centre.聽聽

Our help centre offers:听

• A banner message: This will be used for alerts and known issues. Therefore, when visiting our Zendesk site, FMS providers can review the banner heading before continuing to raise an enquiry.聽聽

• Useful links: Visit our for general information. FMS suppliers might find solutions to common queries without needing to raise a ticket within our articles.聽

• Send a message and help bot functions: As users type an enquiry description into the 鈥楬elp鈥� widget bot or the 鈥楽end a message鈥� link, the system will suggest relevant knowledge base articles, potentially resolving suppliers鈥� queries without needing to raise a ticket.聽聽

If a query is not resolved, FMS software providers can 鈥榞et in touch鈥� and 鈥榣eave a message鈥� by submitting key information regarding the query. Users will also receive an automated email notification confirming that the request has been received. We will endeavour to respond within three working days, this will be shorter when the AR form is live.