Related articles

DevelopersAPI guides

Scheme PDF and specialist module enhancements - Just a taste of what May's updates have to offer

May’s update covers enhancements across the board, from our scheme PDF and replication functionality to specialist modules such as the Executive Summary and Forecasting.


What’s new?

Scheme pdf updates

Enable's scheme PDF is available to all users who have either manual or automated workflow configured.

Date format change

The date format on the scheme PDF will be updated to use the standard Enable format. For example, 01/06/2019 will become Jun 1, 2019.


Page break setting

It is now possible for Enable administrators to introduce page breaks into scheme PDF layouts. Please raise a ticket via the Support Hub if you would like page breaks to be configured, and a member of our Client Services team will be on hand to assist.

Deal and scheme replication changes

The Earnings marked as final field of a deal will no longer be copied when replicating a scheme or deal.

This update is available for all Enable users who have access to the Cash App.


Executive summary updates

Net spend changes

When confirming the net spends in the "to do" tasks area, the Confirm button will not be visible if net spends have never been calculated for the proposal. Otherwise, the Confirm button will be visible. When starting a workflow, Enable will now allow net spends to be confirmed even if calculations are pending.

This update is available for all Enable users who have access to the Executive Summary module.

Refresh warning

A user will now be made aware that the executive summary needs refreshing if calculations have been completed which are relevant to any deals used in the Executive Summary.

This update is available for all Enable users who have access to the Executive Summary module.

Display of approval hierarchy changes

In the approval hierarchy, by default, all roles will be expanded to display all users and any comments in the role section in all scenarios.


This update is available for all Enable users who have access to the Executive Summary module.

Forecasting module configurability

The Forecasting module introduces the concepts of forecasting and phasing periods. These allow users to enter granular turnover forecasts at the phasing period level but report their forecast earnings at the forecast period level.

The initial version of the Forecasting module had a fixed forecasting period of a calendar year and a fixed phasing period of a month. Going forward, these periods can be configured by Enable administrators on a per client basis. This will allow the module to accommodate your business if you wish to record differing levels of granularity in their forecasts or who’s forecast reporting period does not line up with a calendar year.

Due to the addition of the concept of phasing periods, functionality has also be added to allow you, if you have the Forecasting module enabled, to restrict deals (on a trading partner by trading partner basis) to have start and end dates that coincide with phasing periods.

This update is available for all Enable users who have access to the Forecasting module.

Deal start and end date restrictions

A new checkbox setting has been added at the trading partner level to enforce that deals must coincide with phasing periods. This setting will only be visible if the Forecasting module is enabled.

If this setting is true, then the system will require any deals for that trading partner to have a start date that coincides with the start date of a phasing period and an end date which coincides with an end date of a phasing period. It will not be possible to turn this setting on without the previous requirements being met for every deal for the trading partner.

By default, new trading partners will have this setting enabled, and existing trading partners will have this enabled if they meet the requirements the setting imposes.

This update is available for all Enable users who have access to the Forecasting module.

Hide payment frequency setting

A new setting has been developed that can be configured by an Enable administrator to hide the payment frequency around the system. When it is selected, the payment frequencies will be hidden from the create / edit / view deal page.

This update is available for all Enable users, although can only be activated if the Cash App is not in use.

Enable authentication and decoupling improvements

Enable consists of many separate solutions that integrate together to form one system, time is being invested into identifying improvements to how authentication is managed between these separate solutions with the aim of moving to a centralised single sign-on in the future.

SSO redirection

Users who utilise SSO and attempt to access a scheme approval page in Enable via a link are first redirected away from Enable in order to use SSO. Upon successful authentication, the user is then redirected back to Enable.

Previously, this second redirection returned the user to the Enable homepage and not to the scheme approval page they originally requested access to.

In order to improve the user experience, Enable has been adapted in a way which allows for the user to be returned to the page they were originally trying to access before being redirected for SSO.

Trading partner collaboration portal

A new version of the Trading Partner Collaboration Portal is now available on request. Once configured this will allow your trading partners (suppliers or customers) to sign in to the portal to review and approve specific schemes and deals.

The new version of the Trading Partner Collaboration Portal will also support new email content templates. The new email templates will be for the following cases: welcome emails; sign-off requests; schemes signed by; scheme fully signed.

If you are interested in discussing the Trading Partner Collaboration Portal in more detail, please contact your Customer Success Manager.

Deal scaling calculation changes

Enable will now store and maintain a client latest scaling date. Forecast earnings will now use the later of the client latest scaling date and deal latest transaction date rather than client latest transaction date to scale the earnings of the deal.

Baseline earnings will use the later of client latest scaling date and deal latest baseline transaction date rather than client latest transaction date to scale the baseline earnings of the deal.

Replicated schemes should now have be using the same scaling dates as the scheme they were replicated from. This means that baseline earning and forecast earning calculations for each should now be the same.

This update is available for all Enable users that are using baseline earnings or the Forecasting module.

Enable's API

Enable have continued to enhance Enable's API capabilities. This update includes a number of new user endpoints, enhanced performance and even more detailed support documentation, including C# code examples.

What’s coming up?

In line with Enable’s commitment to release an Enable update every six weeks, we have a tonne of updates coming up and will be ready to test in your UAT environment on 28th June, with deployment to your Live environment to take place on 7th August.

If you have any questions regarding our current or upcoming Enable updates, please contact your Client Services team via the Support Hub at

Recalculate baseline earnings improvements

When the baseline earnings of a scheme are being calculated, the existing Recalculate baseline earnings button will be disabled. The text will also be updated to inform the user calculations are ongoing.

Upon completion of the baseline earnings calculations, the user will be informed that the calculations have finished, and if the user has remained on the baseline page, the values on the page will be updated without needing to refresh.

Automatic proposal replication

It will be possible for Enable administrators to configure Enable to allow for automatic scheme replication to generate a proposal scheme

SSO – Unique Entity ID

It will be possible for Enable administrators to enable a new "Unique Entity ID" option within a client’s SAML configuration. This will assign that client a new entity ID for the environment, allowing a single G-suite instance to access multiple Enable instances.

Expanding calculation history

The functionality of the Calculation history tab will be expanded. For example, it will show one row per calculation completed in the past 24 hours:

  • Completed scheme level calculations;
  • Completed baseline earnings calculations;
  • Completed Watchlist app calculations.

In addition, reason queued and priority level columns will be added to the Calculation history tab.

Filtering views in processing area

A section for filtering the Calculation queue and Calculation history tabs will be added to the right panel. This will allow a user to filter the list by one or several criteria, such as reason queued or priority level. The calculation count in each tab will display the number of calculations matching the given filters.

Integrating scheme level calculations into the deal level queue

Scheme level calculations that enter the calculation queue will be displayed alongside the deal level calculations. The UI will be updated to reflect this change, including updating the calculation count in the panel on the right-hand side of the page.

Integration of Forecasting module with accrual earnings

A new deal level setting named "Use forecasting module for accrual" will be added. Using this setting, the value of the deal’s total forecast will be taken from the Forecasting module, and the correct accrual band for this specific deal will be selected automatically. When the setting is deactivated, the accrual band will be deselected and the manual forecast value will be cleared. This setting will only be visible for to you if you have the Forecasting module enabled.

Interim scheme removal

References to interim schemes will be removed if your instance does not allow the creation of interim schemes.

Replication of fully signed schemes

The client level setting "Interim replication for fully signed schemes only" will be renamed and re-purposed to control whether schemes that are not fully signed are eligible for automatic replication. Previously this setting only applied to interim replication.

Replication of schemes with manual workflow

The notion of a default workflow status will be added. A scheme with manual workflow that is manually or automatically replicated will have its workflow status set to the default if the original scheme has no workflow status upon replication.

Not useful
Very useful
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Still have questions?
Raise a ticket or contact our support team.