<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Estelle on Medium]]></title>
        <description><![CDATA[Stories by Estelle on Medium]]></description>
        <link>https://medium.com/@estelle_19448?source=rss-62e83e8ddf03------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Z5gbyBUL5gf_YJbsaY1hGA@2x.png</url>
            <title>Stories by Estelle on Medium</title>
            <link>https://medium.com/@estelle_19448?source=rss-62e83e8ddf03------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:22:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@estelle_19448/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The exceptions that slow invoice processing]]></title>
            <link>https://medium.com/zahara-software/the-exceptions-that-slow-invoice-processing-a9f42b1b2e74?source=rss-62e83e8ddf03------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9f42b1b2e74</guid>
            <category><![CDATA[delivery-note]]></category>
            <category><![CDATA[invoicing-software]]></category>
            <category><![CDATA[missed-delivery-note]]></category>
            <dc:creator><![CDATA[Estelle]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 13:21:54 GMT</pubDate>
            <atom:updated>2026-11-16T15:00:47.122Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yrA8l1VYfzYT8bhI_1Zk8A.png" /></figure><p><em>Why one missing delivery note can create more work than entering the invoice itself.</em></p><p>Ask an AP team how long an invoice takes. It could be quick: a few minutes to enter it, provided that the supplier details are right and the coding’s obvious. If an invoice gets stuck though…? Your question will open the floodgates.</p><p>A delivery hasn’t been confirmed, a price that doesn’t match the order, an approver who’s on leave, or who isn’t sure the cost is theirs can lead to more work than entering the invoice did.</p><p>Most of that time goes on finding out what’s happening. Here’s why.</p><h3>One invoice, 5 people</h3><p>AP teams deal with this kind of thing every week. You’ll probably recognise bits of it. Here’s how it goes:</p><p>A facilities supplier sends the head office an invoice for £2,340. It covers a maintenance visit and replacement parts at a regional site. There’s a purchase order, so the AP clerk goes to match it.</p><p>Order: there.</p><p>Invoice: there.</p><p>Goods received record: missing.</p><p>The clerk emails the site manager, who’s out for 2 days. When she replies, she says the visit happened but she’s not sure about the parts. The engineer brought some and ordered the rest.</p><p>She forwards the question to the operations lead.</p><p>Meanwhile, the clerk spots that one part is priced £86 higher than on the order. It could be a supplier error or an agreed change, but it’s hard to say. The invoice gets put aside, with a note in a spreadsheet: “query with site”.</p><p>Then the approver gets involved. The budget holder wants to know whether the parts belong under the site’s maintenance budget or a central one. Another email.</p><p>A week later the supplier calls to ask when they’ll be paid. A colleague takes the call, digs through the inbox, finds half the thread and emails the site again. The site manager replies that she’s already answered.</p><p>By the time the invoice is approved, 5 people have handled it and the same questions have been asked 4 times.</p><p>Everyone did their bit but the invoice didn’t have a clear owner or a record of why it was stuck.</p><h3>Where the time actually goes</h3><p>Very little of that (substantial) effort went into fixing anything. Confirming the delivery took 1 conversation and checking the price against the supplier’s quote took 10 minutes once someone looked.</p><p>The rest got eaten up by:</p><ul><li>working out who to ask</li><li>waiting on replies with no follow-up date</li><li>re-reading threads to piece together what had already happened</li><li>explaining the issue again every time it changed hands</li><li>answering the supplier without knowing the status</li></ul><p>Stuck invoices may be the exceptions, but they wear AP teams down. The work is scattered across inboxes and usually lives in one person’s head (and leaves with them when they go).</p><p>Month-end makes it worse. Parked invoices become accruals someone has to take a guess at, and the controller wants to know why a supplier’s sitting on the aged creditors report with a query that takes 3 emails to explain.</p><h3>Write down why it’s stuck</h3><p>The cheapest fix won’ t cost you a thing. When an invoice can’t be processed, record the reason from a short, fixed list. A note like “query with site” tells the next person very little.</p><p>For most teams, there are 6 common reasons that should cover your bases:</p><ul><li>no goods or service receipt</li><li>price or quantity differs from the order</li><li>missing or wrong PO reference</li><li>approver unclear or unavailable</li><li>supplier details or VAT issue</li><li>possible duplicate</li></ul><p>With half a sentence, anyone picking up the invoice can see the problem at a glance.</p><p>Then after a month or two, patterns begin to show up. If most of your holds are missing receipts from 2 particular sites, it’s time to address their delivery confirmation system.</p><h3>Give every exception an owner</h3><p>Every invoice on hold needs 1 named person who moves it forward, plus a next action and a follow-up date.</p><p>The owner’s job is chasing and closing the loop. In the example we shared, the site manager had to confirm the delivery and whoever raised the order had to check the price. AP owned the invoice, kept the supplier posted and got it over the line.</p><p>Agree upfront who answers which kind of query. Receipts belong to the site that ordered and price differences go to whoever raised the order or manages the supplier.</p><p>Budget questions go to the approver, with a clear rule for which budget a cost lands in. If an approver’s going on leave, name a stand-in before they go.</p><p>Spend 10 minutes a week on open exceptions, oldest first, so you can see what’s stuck and why.</p><h3>Where automation helps</h3><p>Once the reasons and owners are agreed, software can take on a lot of the legwork.</p><p>Invoice automation can match invoices against orders and receipts as they come in (the [three-way matching] most AP teams already do by hand). Clean invoices go straight through, and only the exceptions land on someone’s desk.</p><p>It can route a query to the right person based on its reason. It keeps the whole history in one place, so whoever takes the supplier’s call can see where things stand.</p><p>It nudges people when a follow-up’s due.</p><p>It won’t decide who owns a problem, or get a site to confirm deliveries on time. Those are process decisions that should be settled before automation has something solid to run on.</p><h3>Where to start</h3><p>Pull up the invoices on hold right now. For each one, write down the reason, the owner and the next step.</p><p>Wherever you can’t fill in all 3, you’ve found your delay.</p><p>Most teams find a handful of causes behind most of their exceptions. Pick 1 and fix it and you’re on your way to fewer supplier calls asking where their money is.</p><p><em>Zahara is purchase-to-pay software for multi-site finance teams. If you’d like to see how matching and exception handling work in practice, there’s more on the </em><a href="https://www.zaharasoftware.com/blog"><em>Zahara blog.</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9f42b1b2e74" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zahara-software/the-exceptions-that-slow-invoice-processing-a9f42b1b2e74">The exceptions that slow invoice processing</a> was originally published in <a href="https://medium.com/zahara-software">Zahara Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>