Transaction detail from LBG APIs

Description

Hi OBIE

Xero would appreciate your advice on the following information that has been provided with LBG in relation to the transaction detail available on their Accounts & Transactions API.
Our customers are finding that the information is different from the information they see in their online banking (payment references missing) and this makes it difficult for them to accurately reconcile their incoming and outgoing transactions in Xero with for example invoices they have issued or bills they have paid.

Xero's understanding was that the data provided from APIs should be equivalent to what a user can see in online banking. Images attached in thread below show this is not the case.
Is this understanding correct?

Thanks

Aimee

---------- Forwarded message ---------
From: $OB Response team <OBResponseteam@lloydsbanking.com>
Date: Mon, Jul 15, 2019 at 9:27 PM
Subject: RE: Transaction detail from LBG APIs
To: Aimee Ferguson <aimee.ferguson@xero.com>
Cc: $OB Response team <OBResponseteam@lloydsbanking.com>, Mark Towndrow <mark.towndrow@openwrks.com>, Mitul Sudra <mitul.sudra@openwrks.com>, James Taylor <james.taylor@xero.com>, Jonathan Kassan <jonathan.kassan@xero.com>

Classification: Limited
Hello Aimee,

I have spoken to our support labs and they have advised.

The missing details are part of the transactions merchant details. We can’t share these at the moment. It will be available when we move to the strategic platform. This is planned for the end of the year.

Please let me know if you have any further questions.

Kind regards

Charlie

From: Aimee Ferguson aimee.ferguson@xero.com
Sent: 11 July 2019 10:30
To: Moore, Charlie (Group Transformation) <Charlie.Moore@lloydsbanking.com>
Cc: $OB Response team <OBResponseteam@lloydsbanking.com>; Mark Towndrow <mark.towndrow@openwrks.com>; Mitul Sudra <mitul.sudra@openwrks.com>; James Taylor <james.taylor@xero.com>; Jonathan Kassan <jonathan.kassan@xero.com>
Subject: Re: Transaction detail from LBG APIs

– This email has reached the Bank via an external source –

Thank you Charlie, look forward to hearing from you.

On Thu, Jul 11, 2019 at 9:17 PM Moore, Charlie (Group Transformation) <Charlie.Moore@lloydsbanking.com> wrote:
Hi Aimee,

Thanks for the email below.

I have copied in the OB Response Team at Lloyds and I am going to reach out to the support labs.

Let me take this away and see what I can find out.

Kind regards

Charlie

From: Aimee Ferguson aimee.ferguson@xero.com
Sent: 11 July 2019 09:08
To: Moore, Charlie (Group Transformation) <Charlie.Moore@lloydsbanking.com>
Cc: Mark Towndrow <mark.towndrow@openwrks.com>; Mitul Sudra <mitul.sudra@openwrks.com>; James Taylor <james.taylor@xero.com>; Jonathan Kassan <jonathan.kassan@xero.com>
Subject: Transaction detail from LBG APIs

– This email has reached the Bank via an external source –

Hi Charlie

I hope you are well?

This week Xero entered our Alpha testing phase of our Open Banking solution and we have been getting feedback from Lloyds and Halifax bank users that the transaction details your API is providing is missing important information for them to be able to do their accounting. Particularly reference information.

The missing information can be seen in online banking and is currently available to them through the Yodlee screen scraped solution in place, and so moving to the Open Banking API to them feels like they are losing important functionality.

I'm wondering if we can work with your team to see if the additional reference information seen within online banking can be exposed through your API for TPP's such as Xero to consume as we currently see this as a barrier to adoption for our users.

I've attached some screenshots below to illustrate the differences.

Thank you

Aimee

(SCREENSHOTS NOT ADDED TO TICKET AS CONTAIN PERSONAL INFORMATION)

Technical Impact

None

Workaround

None

Resolution Notes

None

Impact Assessment

None

Status

Assignee

Unassigned

Reporter

Service Desk

Reference

None

Service Desk Reference

OBSD-9773

ASPSP

Query Type

None

TPP Impact

Medium

TPP

OB Environment

None

Business Impact Severity

None

Share

Yes
Configure