Twinfield blog

Read all
The latest news and software updates for users of Twinfield

September 2017 Software Update

Posted by Richard McChesney on 01-Sep-2017 13:41:00

This month we only have two new enhancements that will be of interest to UK and Irish Twinfield users, although we are working on some larger projects that will be released upon completion later this year or early next year.

As usual, there are also some smaller changes which are documented within the ‘Release History’ which can be accessed from within Twinfield, but the two new enhancements that I wanted to focus on here are:

  • Reimport failed bank statements
  • New BACS formats – BACS Standard 18 and Bankline

Re-import failed bank statements

If you are using Yodlee to automatically import your bank statements, you may have found that for one reason or another, your bank statement import has failed.  Yodlee has successfully extracted the bank statement data from your bank and sent it to Twinfield, but Twinfield rejected the import. 

The most common reason for this is that the accounting period does not exist.  For example, Friday was the first day of the new financial year, but the new financial year has not yet been created in Twinfield.  Today, Monday, you have arrived at work to find that Yodlee was unable to import Friday’s bank statement over the weekend (because the accounting period didn’t exist).

Another reason could be that you have just created a new bank account, but forgot to set the currency of the bank account.  You then linked Yodlee to the bank account, and the import of bank transactions failed.

Within the ‘Manage Feeds’ screen you can see that your Yodlee connection is valid.  The status says ‘Connected’ and the ‘Up to date as at’ date shows yesterday or today’s date:

Reimport01

But your bank statement does not appear in the electronic bank statement processing screen.

So the next place to check is the bank statement ‘History’ screen (the small ‘History’ button on the Cash and Banks screen).

Depending on the number of bank accounts you have, you may need to sort or filter the screen to find the bank statements for the respective bank account, but you will find something similar to the example below:

Reimport02a

To find out why the bank statement import failed, click anywhere on the bank statement line:

Reimport03a

Or:

Reimport03b

To re-import the failed bank statements, resolve the root cause of the problem – which in this case is simply to open the September accounting period (but if you need assistance, please call our support desk), and then select ‘Manage Feeds’ and from the quick access menu on the right-hand side of the respective bank feed, select ‘Retry import of failed bank statement’:

Reimport04

This will display the following screen – which tells you the bank account you have selected and how many failed bank statements Twinfield will attempt to reimport:

Reimport05

After clicking the ‘Import’ button, re-visit the bank statement History screen, and you will see that the bank statements have now been successfully imported (or if they failed, you will see why they have failed a second time):

Reimport06

Our intention is to improve this functionality further and enable a user to reimport a failed bank statement from the history screen.  We will let you know when we add this functionality.

And just another note about the history screen, you will notice in the above screenshots, that only the failed bank statements have a hyper-linked ‘action’.  If the import was successful there isn’t a hyperlink because there is no error log to view.

The exception to this is when a bank statement is imported with a warning, and the most common example of this is when the accounting period for the respective transactions exists, but is closed:

Reimport02

Click on the bank statement line to view the warning:

Reimport03

New BACS formats – BACS Standard 18 and Bankline

As you may be aware, different banks have different file formats for uploading payment requests from software such as Twinfield to the banks’ internet banking or desktop banking software.

In July we released a new BACS format to enable Bank of Scotland users to upload payments directly from Twinfield, and this month we have released two more formats: BACS Standard 18 and Bankline.

BACS Standard 18 is used by a number of banks including Bank of Ireland and HSBC, and Bankline if the format used by members of the Bankline group – RBS, NatWest, and Coutts Private Banking.

These have been added to the drop-down menu listing BACS formats (within the Cash & Banks maintenance screen) as per below.

NewBACSformats

Please note that we still have the old NatWest format listed because we believe that some users may still be able to use this format.  But if you have been using the old NatWest format combined with our Excel macro-enabled BACS payment converter spreadsheet to convert the format to the Bankline format, you may now edit your bankbook settings and change the format to either Bankline or Royal Bank of Scotland (both options produce the same format BACS file).

We don’t yet support all BACS formats for all banks, so if you have a requirement for a particular BACS payment format, please let us know via your account manager or our support desk.

Monthly Twinfield webinars

Just a quick reminder that on the penultimate Friday of every month we run a 60 minute webinar to demonstrate the new functionality released that month, and to answer any questions you might have.

Our August webinar was cancelled due to the delayed release of the software update, so in our next webinar we will cover both the September and August updates.

To register for the webinar, or any future webinars, please search for ‘webinar’ within the Twinfield knowledgebase.  This will provide links to the registration page for each webinar that we currently have scheduled as well as links to recordings of past webinars.

And as always, if you have any questions about this month’s software update, or Twinfield in general, please contact your account manager or call our software support team.