<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on Reamline</title><link>https://reamline.com/blog/</link><description>Recent content in Blog on Reamline</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Sun, 02 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://reamline.com/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>The payment that vanished</title><link>https://reamline.com/blog/the-payment-that-vanished/</link><pubDate>Sun, 02 Aug 2026 00:00:00 +0000</pubDate><guid>https://reamline.com/blog/the-payment-that-vanished/</guid><description>&lt;p&gt;Here is a customer statement, as the accounts system printed it:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;14/04/2026 00153140 I 2071.30
14/04/2026 00153141 I 517.82
15/04/2026 ON A/C P -1294.56
19/05/2026 00153235 I 1176.00
23/06/2026 00153320 I 2589.12
 ────────
 5059.68
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Five lines. The script reading it produced four.&lt;/p&gt;
&lt;p&gt;The missing one is the payment. The customer had paid £1,294.56 and the
statement they received showed four charges adding to £6,354.24 above a total of
£5,059.68. A £1,294.56 hole with nothing to explain it, and what was missing was
&lt;em&gt;their money&lt;/em&gt;.&lt;/p&gt;</description></item></channel></rss>