> For the complete documentation index, see [llms.txt](https://engyon.gitbook.io/engyon/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://engyon.gitbook.io/engyon/en/whats-new/what-is-new.md).
# What's new
Product updates. Filter by New, Improvement, or Fixed.
Product updates for Engyon in English start here. Each card is one change: what you can do now, or what no longer goes wrong.
* **New** — something that changes how you work.
* **Improvement** — a change in speed, ease of use, or stability.
* **Fixed** — a problem you may have run into.
Filter on **New**, **Improvement**, or **Fixed**. Older updates move to a quarter page once they are older than eight weeks. Those pages are not how Engyon works today. For that, use [Reference](/engyon/en/reference/reference.md).
{% updates format="full" %}
{% update date="2026-10-20" tags="improvement" %}
## Search and filter content updates
On the screen for choosing content you can search by title or description, and show only created, updated, or deleted updates. The collection icon then selects only what you see, so you can apply those updates together. Procedures stay in the same order as in the audit.
See [Performing a content update](/engyon/en/how-to-guides/audit/performing-a-content-update.md).
{% endupdate %}
{% update date="2026-10-20" tags="improvement" %}
## Formatting stays visible on an inherent risk factor
Underline, bold text, and a list in a text field of an inherent risk factor stay after you save. The preview (the eye) already showed that formatting. After saving you see the same formatting in the description, the explanation, and on the card.
{% endupdate %}
{% update date="2026-10-20" tags="fixed" %}
## A content update opens again on an older audit
The screen for choosing content kept loading until the connection dropped when the audit already had many procedures. That screen opens now for such an audit too.
See [Performing a content update](/engyon/en/how-to-guides/audit/performing-a-content-update.md).
{% endupdate %}
{% update date="2026-10-20" tags="fixed" %}
## Engagement quality reviewer can open a document
A document that nobody had opened yet was refused for the engagement quality reviewer. That role can open the document now, including the first time.
{% endupdate %}
{% update date="2026-10-19" tags="new" %}
## Work programme for other assurance engagements
You can now open an audit with the work package FI NL COS 3000 Assurance-opdrachten anders. That is the engagement under Standard 3000. From FI NL GAAP - 2026 you can also choose this work package as a linked engagement.
{% endupdate %}
{% update date="2026-10-19" tags="new" %}
## Engagement quality review on a COS 810 subsidy audit
On an audit that uses the COS 810 subsidies work package, you can record the engagement quality review in the audit. Turn the setting on. In an existing audit, bring those procedures in with a content update first.
See [Recording engagement quality review](/engyon/en/how-to-guides/audit/record-engagement-quality-review.md).
{% endupdate %}
{% update date="2026-10-19" tags="improvement" %}
## Assign a review request to yourself
On a review that has not been approved yet, you can use Make me the requester. You become the requester. The review stays traceable when the original requester is no longer on the team. An approved review cannot be taken over this way.
See [Closing a procedure](/engyon/en/how-to-guides/procedures/closing-a-procedure.md).
{% endupdate %}
{% update date="2026-10-19" tags="improvement" %}
## The audit Dashboard
Next to the progress of procedures and sources, the Dashboard now also shows Reviews, Entity insights, Scope, Risks, and Findings. A phase, a team member, a review note, a risk, or a bar opens the matching screen. Click a status in the legend to see only that status in that chart.
See [Dashboard](/engyon/en/reference/dashboard.md).
{% endupdate %}
{% update date="2026-10-19" tags="improvement" %}
## An internal control name stops at 255 characters
On the screen where you create an internal control, Name stops at 255 characters. A longer text is cut off there. Create no longer closes the screen because the name is too long.
{% endupdate %}
{% update date="2026-10-19" tags="fixed" %}
## Audit units show again on a file request
On a group audit the audit units show again on a file request that hangs on a process, source system, control, or test plan, and you change them with the icon (pen) :pen:. When that object has no audit units yet, you choose from every audit unit of the group. A general request stays without that choice.
{% endupdate %}
{% update date="2026-10-18" tags="fixed" %}
## Duplicate test plan on Risk response
One risk sometimes showed two test plans for the same line item and the same assertion, while that combination existed only once in the scope. Risk response now keeps the test plan that belongs to the current line item.
{% endupdate %}
{% update date="2026-10-16" tags="new" %}
## Audit units on a file request
A file request that hangs on a process, source system, internal control, or IT general control receives the audit units of that object when it is created. A file request on a procedure of a test plan receives the audit units of the risk. That audit, and its group audit, can upload the file there. On the group audit you change those audit units with the icon (pen) :pen:. You choose from that object's audit units, or a smaller set. Engyon keeps that change when the object's audit units change later.
See [Managing and creating file requests](/engyon/en/reference/sources/managing-and-creating-file-requests.md).
{% endupdate %}
{% update date="2026-10-18" tags="new" %}
## Request phases that have no procedures through the API
The API normally returns only phases that contain procedures. You can now also request the other phases. Each phase says whether it contains procedures. A phase without procedures can be opened, and users can be assigned to it.
{% endupdate %}
{% update date="2026-10-16" tags="new" %}
## Filter permanent file requests
The filter on Sources has a Permanent switch. It shows only the file requests that are copied on roll forward.
{% endupdate %}
{% update date="2026-10-16" tags="new" %}
## Copy a lead schedule into Excel
On a line item's Lead schedule tab you copy the rows you see to the clipboard, so you can paste them into Excel. A component you have opened is included. Collapsed rows are not.
See [The test plan per line item](/engyon/en/reference/checks/test-plan-per-line-item.md).
{% endupdate %}
{% update date="2026-10-16" tags="improvement" %}
## A risk beside the procedure shows its scope in a tooltip
On a procedure, a tagged risk showed only its title. Hovering that title shows the financial statement line item and the audit unit. The arrow opens Risk response, filtered on that tag.
{% endupdate %}
{% update date="2026-10-16" tags="improvement" %}
## A file request stays assigned until you submit it for review
An upload no longer sets a file request to For review by itself. Colleagues can each add a file while it stays Assigned. When the delivery is complete, click Status and choose For review. After that, the client cannot set that status back. If the team needs more, they choose Request clarification.
See [Life cycle management](/engyon/en/reference/sources/life-cycle-management.md).
{% endupdate %}
{% update date="2026-10-16" tags="improvement" %}
## The audit name shows in the browser tab
With several audits open, the tab only showed the screen name. Inside an audit the tab now shows the audit name, then >, then the screen name. A screen without an audit keeps the title it already had.
See [Operations](/engyon/en/reference/operations.md).
{% endupdate %}
{% update date="2026-10-16" tags="fixed" %}
## Decouple an activity only after the procedure is already decoupled
On the group audit you could still decouple a single activity inside a coupled procedure. That activity stayed locked, because the procedure itself stayed coupled. You can decouple an activity only after the procedure itself is decoupled, including on the group audit.
{% endupdate %}
{% update date="2026-10-15" tags="fixed" %}
## An ITGC's links hold on every screen
An application control that uses two applications could not be linked to an ITGC that covers only one of them. One shared application is now enough. The matrix saved the whole column on a click, which dropped links the matrix does not show. A click now saves only that cell. Supporting internal controls now open with the linked controls ticked, you can untick one, and from a component you see the controls of the group. Deleting an ITGC deletes a supporting internal control that is linked to nothing else, and the confirmation names those controls. Deleting an application names an ITGC that is then left with no application. That ITGC stays.
See [Recording processes, applications and internal controls](/engyon/en/how-to-guides/risks/recording-processes-applications-and-internal-controls.md).
{% endupdate %}
{% update date="2026-10-15" tags="fixed" %}
## A client file stays when its audit documentation is removed
A client file you placed on an activity with Use as audit documentation pointed at the same stored file. Removing that audit documentation removed the client's file too, while the file request stayed green. A file that is still used somewhere else is no longer removed.
{% endupdate %}
{% update date="2026-10-15" tags="fixed" %}
## Decoupling a file request on an archived audit
You could still decouple a file request that lives on an archived audit. That only removed the link; its files and comments stayed linked. Decouple is now disabled while that audit is archived. Decouple all is disabled as soon as one of the coupled audits is archived. On an open audit, the files and comments are decoupled too.
{% endupdate %}
{% update date="2026-10-15" tags="fixed" %}
## A link in a text field shows again in the preview
A link in a text field could still be opened from the preview (the eye), but it looked like ordinary text. In that preview the link is underlined again, as it is in the saved text.
{% endupdate %}
{% update date="2026-10-15" tags="fixed" %}
## File request on each file in the export
The Files sheet listed each file without the file request it belongs to. Each row now names that file request, so the two sheets can be matched.
{% endupdate %}
{% update date="2026-10-15" tags="fixed" %}
## File request numbers in the Excel export
The Sources Excel list showed file requests without the number you see in Engyon. That number is in the export when file requests are numbered.
{% endupdate %}
{% update date="2026-10-15" tags="fixed" %}
## File request numbers stay visible while you scroll
Numbered file requests kept their number on the first rows and lost it once you scrolled further down Sources. The numbers stay now. Deleting one empty file request removes only that request. The rest of the list stays in place.
{% endupdate %}
{% update date="2026-10-14" tags="improvement" %}
## Several file requests at once
On Sources, assign, publish, approve, lock, and delete sit under Bulk actions. File requests that are for review are approved together, including their files. Deleting a file request also deletes the files in it. Deleting files leaves the file request in place.
See [Managing and creating file requests](/engyon/en/how-to-guides/sources/manage-and-create-file-requests.md).
{% endupdate %}
{% update date="2026-10-14" tags="improvement" %}
## Unapproved file as a reference
A client file that is not yet approved stays in its place when you choose a reference. It is grey and you cannot select it until it is approved.
{% endupdate %}
{% update date="2026-10-14" tags="fixed" %}
## An application's links hold when you save or delete it
Deleting an application left its internal controls behind, including an application control that no longer had any application. Now an application control or IT-dependent control that is left with no application or no process is deleted with it, and the confirmation names those controls. An application also saved processes that did not fit it. That is now refused, and nothing is saved. When you change the audit units of an application, Engyon also checks that the linked ITGCs still fit. The same rules apply when you roll forward an audit.
See [Recording processes, applications and internal controls](/engyon/en/how-to-guides/risks/recording-processes-applications-and-internal-controls.md).
{% endupdate %}
{% update date="2026-10-14" tags="fixed" %}
## Audit documentation from a file on the group audit
From a component audit, Use as audit documentation failed when the client file lived on the group audit. That works now. The audit documentation is stored on the group audit, on the activity of the procedure that requested the file.
{% endupdate %}
{% update date="2026-10-14" tags="fixed" %}
## A zero on the consolidation sheet is not a difference
A line item with a zero balance showed an exclamation mark on Checks when the trial balance contained no zero account for that line item. That exclamation mark is gone.
{% endupdate %}
{% update date="2026-10-14" tags="fixed" %}
## Evidence total on every linked test plan
Changing the evidence of a procedure or internal control linked to several test plans updated the total on only one test plan. Substantive evidence and System based evidence now update on every linked test plan.
{% endupdate %}
{% update date="2026-10-13" tags="new" %}
## Documentation in English
Engyon's documentation is now available in English, alongside the Dutch documentation. The screens, steps, and training use the English labels you see in Engyon.
{% endupdate %}
{% update date="2026-10-13" tags="improvement" %}
## See who executed or reviewed a work step
On the procedure list you can filter on who executed or reviewed a work step, without opening the step. You choose people, and above that Assigned to, Executed by, or Reviewed by. Set the list in front of that to not to leave those people out. The filter stays when you open a work step and come back.
{% endupdate %}
{% update date="2026-10-13" tags="fixed" %}
## Files come along when you couple one file request
When you couple one file request with the icon (link) :link:(tooltip `Couple`), the files on that request are copied to the underlying audit. That used to happen only with Couple all.
{% endupdate %}
{% endupdates %}