| | Categories: Blog, News

API support for TLS versions 1.0 and 1.1

Action Required for Web service / API Integrations

We’ll be retiring support for TLS versions 1.0 and 1.1 on all Twinfield sites, including Twinfield’s API. This change improves the security of the data sent between you and Twinfield, whether you’re accessing Twinfield through a browser or communicating directly with our API.

We strongly encourage any developers who are using the Twinfield API to ensure that their software supports negotiating TLS 1.2 connections, and to coordinate with their system administrators to update software to take advantage of newer TLS versions. In addition, we recommend proactively switching over to TLS 1.2 when communicating with Twinfield’s API by modifying your API client software to enforce TLS 1.2 negotiation.

Please refer to the compatibility guidelines below:

Platform or Library Compatibility Notes
Java (Oracle)

Compatible with the most recent version, regardless of operating system

Java 8 (1.8) and higher Compatible with TLS 1.2 by default.
Java 7 (1.7) Enable TLS 1.2 using the https.protocols Java system property for HttpsURLConnection. To enable TLS 1.2 on non-HttpsURLConnection connections, set the enabled protocols on the created SSLSocket and SSLEngine instances within the application source code. Switching to IBM Java may be an effective workaround if upgrading to a newer Oracle Java version isn’t feasible.
 
Java (IBM)
Java 8 Compatible with TLS 1.2 or higher by default. You may need to set com.ibm.jsse2.overrideDefaultTLS=true if your application or a library called it by it uses SSLContext.getinstance(“TLS”).
Java 7 and higher, Java 6.0.1 service refresh 1 (J9 VM2.6) and higher, Java 6 service refresh 10 and higher Enable TLS 1.2 using the https.protocols Java system property for HttpsURLConnection and the com.ibm.jsse2.overrideDefaultProtocol Java system property for SSLSocket and SSLEngine connections, as recommended by IBM’s documentation. You may also need to set com.ibm.jsse2.overrideDefaultTLS=true.
.NET

Compatible with the most recent version when running in an operating system that supports TLS 1.2.

.NET 4.6 and higher Compatible with TLS 1.2 or higher by default.
.NET 4.5 to 4.5.2 .NET 4.5, 4.5.1, and 4.5.2 do not enable TLS 1.2 by default. Two options exist to enable these, as described below.

Option 1:
.NET applications may directly enable TLS 1.2 in their software code by setting System.Net.ServicePointManager.SecurityProtocol to enable SecurityProtocolType.Tls12. The following C# code is an example:

System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;

Option 2:
It may be possible to enable TLS 1.2 by default without modifying the source code by setting the SchUseStrongCrypto DWORD value in the following two registry keys to 1, creating them if they don’t exist: “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319” and “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319”. Although the version number in those registry keys is 4.0.30319, the .NET 4.5, 4.5.1, and 4.5.2 frameworks also use these values. Those registry keys, however, will enable TLS 1.2 by default in all installed .NET 4.0, 4.5, 4.5.1, and 4.5.2 applications on that system. It is thus advisable to test this change before deploying it to your production servers. This is also available as a registry import file. These registry values, however, will not affect .NET applications that set the System.Net.ServicePointManager.SecurityProtocol value.

.NET 4.0 .NET 4.0 does not enable TLS 1.2 by default. To enable TLS 1.2 by default, it is possible to install .NET Framework 4.5, or a newer version, and set the SchUseStrongCrypto DWORD value in the following two registry keys to 1, creating them if they don’t exist: “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319” and “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319”. Those registry keys, however, may enable TLS 1.2 by default in all installed .NET 4.0, 4.5, 4.5.1, and 4.5.2 applications on that system. We recommend testing this change before deploying it to your production servers.

These registry values, however, will not affect .NET applications that set the System.Net.ServicePointManager.SecurityProtocol value.

.NET 3.5 and below Not compatible with TLS 1.2 or higher encryption
 
Python

Compatible with the most recent version when running on an operating system that supports TLS 1.2.

Python 2.7.9 and higher Compatible with TLS 1.2 by default.
Python 2.7.8 and below Not compatible with TLS 1.2 or higher encryption
 
Ruby

Compatible with the most recent version when linked to OpenSSL 1.0.1 or higher.

Ruby 2.0.0 TLS 1.2 is enabled by default when used with OpenSSL 1.0.1 or higher. Using the :TLSv1_2  symbol with an SSLContext’s ssl_version helps ensure that TLS 1.1 or earlier is disabled.
Ruby 1.9.3 and below The :TLSv1_2 symbol does not exist in 1.9.3 and below, but it is possible to patch Ruby to add that symbol and compile Ruby with OpenSSL 1.0.1 or higher.

 

| | Categories: Blog, Software Updates

February 2018 Software update

Before I take you through the changes in this month’s software update, you may be interested to know that due to popular demand we are bringing back our monthly webinars in 2018.  The format of these webinars will change slightly however, and will become an opportunity for you to ask questions in a live Q&A session on a monthly basis. 

The webinar presenters will also change from time to time.  Rather than just me presenting the webinars, there will be other members of our team sharing their knowledge with you. 

We will continue to demonstrate the changes in each month’s software update, but we encourage you to use these webinars as an opportunity to ask questions about anything to do with your use of Twinfield.  Full details are available by searching for ‘webinar’ and selecting ‘Twinfield webinar schedule’ within the Twinfield knowledgebase.

 

What’s in the February software update?

In our first software update for 2018 we have four changes that I wanted to document for you.  These are:

  • New Audit Trail listing
  • New report: VAT overdue invoices
  • Neo sales invoices VAT in base currency
  • New VAT list screen

 

Audit Trail

The new Audit Trail is a list view that initially enables you to list all changes to supplier bank accounts.  This will be enhanced in the future to enable reporting on other changes within Twinfield.

To run the Audit Trail, click the new ‘Audit Trail’ icon on the Reports screen:

In this release the listing will display all supplier bank account changes made within the last 12 months.  This can be filtered in many ways:

We will advise when more functionality is added to this new screen.

 

New report: VAT overdue invoices

Due to a change in Dutch VAT legislation a new report has been added to the VAT category which may be of interest to other users as well.

The new report enables you to report on the VAT content of outstanding sales and purchase invoices as follows:

  • Select the new VAT Overdue Invoices report from the VAT reports menu
  • Enter selection criteria:
  • The result will be a list of both sales and purchase invoices which meet the specified criteria, grouped by VAT code:

This report is available to all users in Level 1, 2, 3, and 4 roles.

 

Neo sales invoices VAT in base currency

If you process a sales invoice in a foreign currency and the invoice includes VAT, the VAT Summary section now displays the VAT exclusive and VAT amounts in both base currency and transaction currency as required by European law.

 

New VAT list screen

As a part of our ongoing work to update our list screens we have now updated the VAT rates screen to bring it into line with other screens.  Please see example below:

 

 

The above is all I wanted to cover this month.  Don’t forget our monthly webinars which start on the 23rd February.  Search for ‘webinar’ within the Twinfield knowledgebase for full details and links to register.

 

Richard McChesney
Product Manager for Twinfield and Basecone in the UK and Ireland

| | Categories: Blog, Software Updates

December software update

It’s almost Christmas and I expect that your mind is on other things right now, and not Twinfield.

But our development team are still hard at work, and whilst most of the recent work has been ‘behind the scenes’ and on new functionality that won’t be released until 2018, there are two changes in the December release that will be of interest to you.

These are:

  • New Sales Quotes list screen
  • New Timeline for sales invoices and quotes

New Sales Quotes list screen

During the course of 2017 we have been upgrading our list screens and this month we have updated the sales quotes screen to bring it into line with the other screens.  Please see example below:

01SalesQuotesListScreen

 

New timeline for sales invoices and quotes

When viewing a sales invoice or a quote, we now have a new design to the timeline.

By default it will open minimised and look like this:

02Timelineminimised

And if you click on the menu icon in the top of the timeline, you will see an expanded timeline that provides additional information:

03Timelinemaximised

 

We would like to take this opportunity to wish you an enjoyable Christmas break, and we look forward to talking to you again in the New Year.

Please note that our office will be closed for all support between Christmas and New Year.

 

Richard McChesney
Product Manager for Twinfield in UK and Ireland

| | Categories: Blog, Software Updates

November Software Update

In our penultimate software update of 2017 we only have a few changes that I want to highlight in this blog, but as always, a full history of changes is available by clicking the ‘Release History’ button on the Twinfield home screen.

Changes this month include:

  • Changes to the way VAT is displayed on Neo Quotes
  • Removal of the discount percentage when discount is an amount
  • HMRC VAT Gateway change

 

Changes to the way VAT is displayed on Neo Quotes

Last month we released a change to the Neo sales invoice which hides all mention of VAT when invoice lines have a VAT code of ‘No VAT’.

This month we have added this same functionality to the Neo quote document:

01Quoteimage

 

Removal of the discount percentage when discount is an amount

In August we released a change to Neo sales invoices to enable you to enter a discount amount or percentage at the bottom of your sales invoice.

Since then we have received some great feedback and as a result, we have implemented a small change – in that now, if you enter an amount discount, Twinfield no longer displays the calculated percentage discount as well as the discount amount.  This change has been made thanks to direct feedback from users, so thank you for the feedback.

Sales invoice as it appeared before this change (user entered a discount amount of £100.00 which Twinfield then displayed as 8.89%):

02Invoicediscountamount-olddisplay

The percentage is no longer displayed when the discount is entered as an amount:

02Invoicediscountamount-newdisplay

If you enter a percentage discount during data entry, then both the percentage and the amount will be displayed on the invoice.

 

HMRC VAT Gateway change

Lastly, HMRC are in the process of making some changes to their systems, and as a result, we have made a small change to ensure that Twinfield users can continue to file their VAT returns electronically.

If you are not currently filing your VAT returns electronically, and would like to learn how to do this, please click here to view our two videos about reporting and filing your VAT. 

| | Categories: Blog, Software Updates

October Software Update

This month we only have two main changes to tell you about.  These are:

  • Changes to the way VAT is displayed on Neo sales invoices
  • Payment and Collection schedule reports now display bank account number of payment transaction

As always, there are a number of other minor changes which you can read about by clicking the ‘release history’ button within the Twinfield home screen, and there are a number of other larger projects that are keeping our developers busy, but nothing that is ready for release just yet.

 

Changes to the way VAT is displayed on Neo sales invoices

In August we released the new VAT summary section on the Neo sales invoice, and in this month’s software update we have made further improvements with respect to how VAT is displayed.

Firstly, we have switched the order of the VAT Rate and Line Total columns in the body of the sales invoice, so that the line total is now on the right hand side of the invoice.

And for entities who process invoices that don’t have a VAT component, all mention of VAT on the sales invoice is now hidden.  This could be for one-off sales which are ‘out of scope’ or entities that are not registered for VAT.

In summary, if you process a sales invoice that contains VAT, the lower section of the invoice will look like this:

01 VAT sectionon invoice with VAT

And if you process a sales invoice where all lines of the sales invoice have the VAT rate of ‘No vat’, the lower section of the invoice will look like this:

02 VAT sectionon invoice without VAT

Note 1: During data entry, the invoice input screen will show the VAT column and summary as per normal.  It is only when you click the ‘send’ button that Twinfield formats the emailed/printed invoice based on the VAT content.

02a VAT section on invoice without VAT

NOTE 2: the ‘VAT not applied’ can be hidden by editing the default setting within the template.  To do this, select ‘Invoice Template’ from the ‘Related Items’ menu on the right hand side of your sales invoice data entry screen, and scroll down to the bottom of the template.  Click on the words ‘VAT: reverse charge’ (which is where reverse charge text will be displayed if you are issuing sales invoices subject to reverse charge VAT) to display the ‘Hide’ button.  Click this to supress this text from being displayed on future invoices.

03 Hide VAT not applied text

And whilst on the subject of Neo sales invoices, you may have experienced a problem previously whereby if using Google Chrome to create Neo sales invoices, and your ‘zoom’ setting was set to either a low or high percentage, your sales invoice would process as a multi-page invoice, even if you only had one line on the invoice.  The work-around for this was to set your ‘zoom’ setting to either 90% or 100% but this is no longer a problem, and you can use whatever zoom setting you like.

 

Payment and Collection schedule reports now display bank account number of payment transaction

Previously, if you re-ran an historical payment schedule report, the bank account number displayed for the supplier/customer was the current bank account number for that supplier/customer and not the account number used in the actual transaction.  This report has now been modified to show the historical bank account number from the transaction – although as you will note below, the wording still indicates that this is the current ‘default’ bank account number.  This will be corrected in next month’s software update.

04 Payment schedule bank account number

 

Monthly webinars:

Don’t forget, every month we demonstrate the changes that have been released and answer any questions that you have.  Search for ‘webinar’ within the Twinfield knowledgebase to register for the next webinar or to watch recordings of previous webinars.