Transactions over £500 from December

The request was successful.

Dear Sir or Madam,

Thank you for publishing your spend data here:
However, I notice that you haven't published any spending data since November.

We understand that due to the COVID-19 pandemic it may not have been a priority to publish your spending data. However, we strongly believe that the spending data is critical to understanding how Government functions and this data is vital for our work. We would be extremely grateful if you could update this information as soon as reasonably possible.

We’ve decided to continue to use the FOI process to request data as this gives us both a formal structure for making and responding to requests. So, I'd like to make a request under the Freedom of Information Act for all transactions over £500 from December to at most a quarter in arrears from the date at which you publish in response to this request.

Please provide the data in a machine readable format (preferably csv). As a minimum, please make sure to include the date, value and recipient of each transaction. Please also provide details on the procurement category of each transaction if you have it.

Your team may also be interested in the guidance on producing spending data:

For the avoidance of doubt, I am making this request under the Freedom of Information Act. I await your response within 20 working days.

Yours Faithfully,

Zsofia Molnar

Spend Network

Information Governance Team,

Dear Zsofia Molnar,

Thank you for your request which was received on 14th March. The estimate
response date for your request is the 13th April.

Should you have any queries, amendments or additions relating to this
request, please remember to quote the reference number above in any future

Yours Faithfully

Information Governance Team
North Lincolnshire Council

Information Governance Team,

1 Attachment

  • Attachment

    Information Disclosure FOI2023 00417.odt

    638K Download

Dear Zsofia Molnar,

I am writing in response to your request for information, that was
received on the 14th March. Please find our Information Disclosure letter

If we can be of any further assistance with regard to this request please
let us know quoting the above reference number.

Yours sincerely,

Information Governance Team
North Lincolnshire Council

Dear Information Governance Team,

Thank you very much for your kind reply and for your cooperation!

Yours sincerely,
Zsofia Molnar
Spend Network

North Lincolnshire Council

2 Attachments

Your message to [email address] couldn't be delivered.
request wasn't found at
request-960291-f67b7. . . Office 365 request
Action Required Recipient
Unknown To address
How to Fix It
The address may be misspelled or may not exist. Try one or more of the
• Send the message again following these steps: In Outlook, open this
non-delivery report (NDR) and choose Send Again from the Report
ribbon. In Outlook on the web, select this NDR, then select the link
"To send this message again, click here." Then delete and retype the
entire recipient address. If prompted with an Auto-Complete List
suggestion don't select it. After typing the complete address, click
• Contact the recipient (by phone, for example) to check that the
address exists and is correct.
• The recipient may have set up email forwarding to an incorrect
address. Ask them to check that any forwarding they've set up is
working correctly.
• Clear the recipient Auto-Complete List in Outlook or Outlook on the
web by following the steps in this article: [1]Fix email delivery
issues for error code 5.1.10 in Office 365, and then send the message
again. Retype the entire recipient address before selecting Send.
If the problem continues, forward this message to your email admin. If
you're an email admin, refer to the More Info for Email Admins section
Was this helpful? [2]Send feedback to Microsoft.
More Info for Email Admins
Status code: 550 5.1.10

This error occurs because the sender sent a message to an email address
hosted by Office 365 but the address is incorrect or doesn't exist at the
destination domain. The error is reported by the recipient domain's email
server, but most often it must be fixed by the person who sent the
message. If the steps in the How to Fix It section above don't fix the
problem, and you're the email admin for the recipient, try one or more of
the following:

The email address exists and is correct - Confirm that the recipient
address exists, is correct, and is accepting messages.

Synchronize your directories - If you have a hybrid environment and are
using directory synchronization make sure the recipient's email address is
synced correctly in both Office 365 and in your on-premises directory.

Errant forwarding rule - Check for forwarding rules that aren't behaving
as expected. Forwarding can be set up by an admin via mail flow rules or
mailbox forwarding address settings, or by the recipient via the Inbox
Rules feature.

Recipient has a valid license - Make sure the recipient has an Office 365
license assigned to them. The recipient's email admin can use the Office
365 admin center to assign a license (Users > Active Users > select the
recipient > Assigned License > Edit).

Mail flow settings and MX records are not correct - Misconfigured mail
flow or MX record settings can cause this error. Check your Office 365
mail flow settings to make sure your domain and any mail flow connectors
are set up correctly. Also, work with your domain registrar to make sure
the MX records for your domain are configured correctly.

For more information and additional tips to fix this issue, see [3]Fix
email delivery issues for error code 5.1.10 in Office 365.
Original Message Details
Created Date: 4/12/2023 8:19:11 PM
Sender Address: [FOI #960291 email]
Recipient Address: [email address]
Subject: Re: Freedom of Information - Ref: FOI2023/00417
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[email address] not found by SMTP address
Message rejected CWXP265MB1768.GBRP265.PROD.OUTLOOK.COM
Notification Details

Message Hops
4/12/2023 local (Exim 4.94.2) (envelope-from
1 8:19:12 foi <[FOI #960291 email]>) 1 sec
4/12/2023 esmtps (TLS1.3) tls
2 8:19:12 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim *
PM 4.94.2) (envelope-from
<[FOI #960291 email]>)
4/12/2023 Microsoft SMTP Server (version=TLS1_2,
3 8:19:12 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
4/12/2023 Microsoft SMTP Server (version=TLS1_2,
4 8:19:13 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
4/12/2023 Microsoft SMTP Server (version=TLS1_2,

Original Message Headers

Received: from CWLP123CA0166.GBRP123.PROD.OUTLOOK.COM (2603:10a6:401:88::34)
by CWXP265MB1768.GBRP265.PROD.OUTLOOK.COM (2603:10a6:400:34::12) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6298.30; Wed, 12 Apr
2023 20:19:14 +0000
Received: from
(2603:10a6:401:88:cafe::a7) by
(2603:10a6:401:88::34) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6298.30 via Frontend
Transport; Wed, 12 Apr 2023 20:19:13 +0000
Authentication-Results: spf=pass (sender IP is; dkim=pass (signature was verified);dmarc=pass action=none;
Received-SPF: Pass ( domain of
designates as permitted sender); client-ip=;; pr=C
Received: from ( by ( with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6298.31 via Frontend Transport; Wed, 12 Apr 2023 20:19:12 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;; s=2020a.mysociety; h=Content-Transfer-Encoding:
bh=4YfksU79V9jwX4Nhz4wtKJnruOtwMLZ/XDWIUj3FvPY=; b=LYCp6lkPIqeRrmS7vuxQfYUhax
Received: from ([2a00:1098:82:dd::10:1]:34976)
by with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
(Exim 4.94.2)
(envelope-from <[FOI #960291 email]>)
id 1pmgvw-000OKg-Bm
for [email address]; Wed, 12 Apr 2023 20:19:12 +0000
Received: from foi by with local (Exim 4.94.2)
(envelope-from <[FOI #960291 email]>)
id 1pmgvw-002cMa-0y
for [email address]; Wed, 12 Apr 2023 21:19:12 +0100
Date: Wed, 12 Apr 2023 21:19:11 +0100
From: Spend Network <[FOI #960291 email]>
To: Information Governance Team <[email address]>
Message-ID: <[email address]>
Subject: Re: Freedom of Information - Ref: FOI2023/00417
MIME-Version: 1.0
Content-Type: text/plain;
Content-Transfer-Encoding: 7bit
Return-Path: [FOI #960291 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 586655ed-2cff-4089-8197-b4c10b7b3da3:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: CWLGBR01FT031:EE_|CWXP265MB1768:EE_
X-MS-Office365-Filtering-Correlation-Id: 7960fb02-16c2-47c2-f42e-08db3b932e80


Visible links