Case study · Scout
Scout: matching supplier invoices to orders and services
A property organisation that buys supplies and orders jobs for its properties then receives invoices as PDFs, each laid out in its supplier’s own way. For Scout, a B2B procurement platform built with Medusa and Mercur, we developed a multi-step flow. It starts from this document and extracts its data using the Reducto service. For a service, it suggests the matching service provider and purchase order; for goods, it compares the invoice with what was received. A person then validates the match.
Scout connects property organisations, which manage properties made up of apartments or units, with product suppliers and service providers. On the platform, an organisation orders materials for its buildings and places service orders for works or call-outs. After the order comes the invoice. It usually arrives as a PDF, laid out according to each supplier’s habits, with its own labels and its own breakdown into lines. Before giving its approval, the organisation must establish what this document corresponds to: which supplier issued it, which order or service it relates to, and whether each invoiced line matches what was delivered or carried out. In Scout, we built the flow that supports this check, from uploading the document through to a traceable validation. The decision remains in the hands of the people responsible for making it.
The supplier document remains the starting point
Matching begins with the document itself. On the organisation side, a service invoice can be uploaded to Scout. The original PDF file is kept and remains attached to the file. On the supplier side, an order’s invoice can be sent from the supplier’s own document system, as a file or as a link to the document. A supplier that already produces its invoices in another tool therefore does not have to re-enter them on the platform.
Keeping the original serves a simple purpose: data extracted from a PDF remains a reading of the document, and it is the document that is authoritative. While matching a service invoice, the person doing the matching can open the source PDF alongside the extracted information. They can thus check an amount or a label against the document itself, without having to search for it in a mailbox or a shared folder.
Extraction handled by Reducto, suggestions to be checked
Reading an invoice means finding information whose position changes from one supplier to the next: issuer, references, dates, lines and amounts. To extract these fields, Scout relies on Reducto, a service specialising in document extraction. We did not develop this reading engine. Our work consisted of integrating it into Scout’s flow and using what it returns in the context of the organisation’s purchasing.
From the extracted data, Scout suggests the supplier and the service order that appear to match, followed by matches between the invoice lines and the order lines. These suggestions save starting from a blank page, but they do not amount to validation. An extraction may misread a label, a line may combine two tasks, a reference may be missing from the document.
Take a case by way of illustration, unrelated to any real file. A service provider invoices a maintenance job in three lines: labour, travel and minor supplies. The order, for its part, described the work as two tasks. The suggestion matches what it can. The person reviewing then decides whether the minor supplies belong to the first task, the second, or warrant a question to the service provider.
For services, each invoiced line is linked to the work ordered
A service order describes tasks. The invoice that follows must be allocable to those tasks, line by line, so that the actual cost of the job is linked to what was ordered. The review consists of going through the suggested matches, correcting them if necessary, then confirming them. The suggestions then become validated allocations.
This check is not always done in one sitting. It is sometimes necessary to wait for clarification from the service provider or a colleague’s opinion. The match can therefore be saved as a draft and resumed later. Each save corresponds to an identified version. If someone else has updated the file in the meantime, resuming does not overwrite their work without them knowing.
For goods, the invoice is compared with what was received
For a product order, the question is about quantities. A delivery may be partial, an item may be missing or arrive later, whereas the invoice sometimes covers everything ordered. Scout presents a comparison between the invoiced lines and the recorded receipt. The organisation thus checks the amounts against what actually arrived at its properties.
The person then confirms the matches between invoiced lines and received lines. Before making this match effective, they can display a preview of it, without publishing it, to review the allocations. When giving their approval, they also confirm the property concerned and the amounts. This confirmation applies to a specific version of the invoice: if the data has changed since they reviewed it, their approval does not hold for the new version.
On the supplier side, the tax on an order can be specified before its amounts are locked: by rate, by amount, or by indicating that no tax applies. The order thus carries the tax treatment chosen by the supplier.
Duplicates, ambiguous documents and invoices to be replaced
The same document may arrive twice: resent by the supplier, sent through two channels or uploaded by two people. Scout flags invoices identified as possible duplicates and allows them to be viewed, to avoid validating the same document twice. This detection is an aid. It draws attention to the cases it detects, without guaranteeing that all duplicates will be identified.
For invoices received by email, the platform’s administration has a review step that avoids automatically processing an ambiguous document. An administrator can accept a document, reject it or mark it as a duplicate. They can also set aside an invoice that should not be processed, provided they state the reason. The file is then closed, and the explanation remains attached to the document instead of depending on the memory of the person who decided.
That leaves the case of an incorrect invoice: wrong amount, missing line or wrong reference. The organisation can then ask the supplier for a replacement invoice. The correction goes through a new document, and the previous documents are kept. Each supplier decides, according to its own document policy, whether or not to allow its invoices to be replaced.
A traceable validation, with no automatic payment
Validating a match amounts to giving financial approval. Scout records the identity of the person who validated it. It is thus possible to find out later who accepted which invoice, and on which version of the data.
This approval does not trigger any transfer. In an organisation that does not use RealPage, an authorised buyer can declare in Scout that an order has been paid. This declaration moves the order’s tracking forward, but it does not move any funds: payment takes place outside the platform.
The supplier PDF thus becomes the starting point for a documented human decision. Extraction and suggestions prepare the reading, then the person doing the matching makes the call. The decision to pay remains with the organisation’s teams.