Case study · Scout
Scout: passing purchases to accounting already coded and checked
Scout is a B2B procurement platform that connects property organisations, which manage properties made up of flats, with product suppliers and service providers. So that these purchases reach accounting with the information it needs, we built a journey in Scout, a platform built with Medusa and Mercur, that codes each expense to its accounts, its property and its flats. This journey has invoices checked, then produces a single export covering both goods and services.
A property organisation using Scout can order both supplies for its homes and service providers’ work there. For its accounting, an expense is only usable if several pieces of information are brought together: the account it is coded to, the property and flats concerned, the supplier as known in the accounting records, and assurance that the invoice matches what was received or carried out. If these elements are missing at the time of purchase, they have to be tracked down after the fact, invoice by invoice. We therefore ensured that this information is entered during the purchase and checked by the right people. It is then passed on in a single file. When the organisation uses the RealPage ERP, the progress of its invoices also comes back into Scout.
The organisation’s chart of accounts, carried over into Scout
Each organisation classifies its expenses in its own way. Rather than imposing a common classification, Scout allows the organisation’s Master, its highest level of authority, to create and maintain its accounting codes. These are general ledger accounts, often referred to by the abbreviation GL. They use the codes and labels that accounting already works with. The coding done on the platform thus uses the vocabulary of the department that will receive it.
The same types of purchase often recur, such as cleaning products, taps and valves, or paint. So that the account does not have to be chosen for every order, the Master can associate a default account with a product category, at the most specific level of the catalogue. An item in that category then arrives with its usual coding. This setting avoids a repetitive choice, but it does not remove the need for the check provided for later in the journey.
Each expense attached to its property and its flats
In residential property, the type of expense is not enough: it is also necessary to know where it was incurred. An expense may concern an entire property or be split between several flats. Purchases made in Scout therefore carry a split between the accounts and the units concerned, which the accounting review checks before anything is passed on.
For services, this split is set as soon as the service purchase order is prepared. The person preparing it splits each line between accounts and units, and Scout checks these splits. When the provider’s invoice arrives, a manager or an accountant can reallocate its lines if the cost code or home actually concerned differs from what was planned. The coding thus follows what was actually done.
As a fictitious illustration, the same residence may be the subject of an order for seals and mixer taps for three of its flats, and of a plumbing job in its communal areas. The two purchases follow different journeys, but each reaches the review with its property, its units and its accounts.
Matching the invoice against what was received before marking it as reviewed
For goods, the supplier uploads its invoice as a PDF to Scout. The person following the purchase views the comparison between the invoiced lines and the quantities actually received, then confirms the matches. They can preview a manual match before approving it. They also confirm the property and the amounts on a specific version of the document: if it has changed in the meantime, the approval does not silently apply to data they have not seen. The approval records the identity of the person who gave the go-ahead.
If the invoice is wrong, the buyer can ask the supplier for a replacement invoice. The original documents are retained. For their part, each supplier states in its settings whether it accepts such replacements. For services, the invoice can be accepted, or rejected when it is incorrect; the rejected document is set aside without being lost.
Next comes the accounting review. People with the accountant role in the organisation check the splits on an order, then mark it as reviewed. Service invoices go through an equivalent step. This marking separates two checks: the purchase matches what was received, and its coding is ready to go to accounting. Only reviewed documents are included in the export.
Suppliers recognised by their accounting code
In Scout, a supplier is a marketplace vendor. In the organisation’s accounting, it is known by a code in its supplier records. To link the two, the accountant can assign a vendor the supplier code given to it by their ERP. This code then accompanies that vendor’s invoices. The person receiving the export does not have to work out which accounting third party lies behind the name shown on the platform.
A single export for goods and services
Products go through a basket, service work through a service purchase order. These two ways of buying could have produced two separate accounting outputs. We brought them together: the accountant exports reviewed invoices for goods and services together, in the same CSV file.
An export that has already been produced remains available. It can be downloaded again, for example if the transfer to the accounting tool has to be redone, without rebuilding the file. Where the defined conditions allow, an export can also be cancelled. The correction then remains visible, instead of erasing the transmission as if it had never happened.
This file has a precise scope. It prepares the entries for import into the accounting system, but it does not create the invoice in the ERP and does not trigger any payment. Recording and settlement remain the responsibility of accounting and its tools.
Tracking the progress of invoices in RealPage from Scout
Once the invoice has been passed on, the people who made the purchase want to know where it stands. For organisations that use RealPage, the Master can check from Scout that the saved connection is working. Scout reads the status of invoices from RealPage: Posted, Partially Paid or Paid. These statuses reflect what RealPage records. Scout neither creates nor settles the invoice in RealPage, and an imported “Paid” status is not a payment executed by the platform. Everyone can thus follow the accounting progress of a purchase in the tool where they ordered it.
Organisations that do not use RealPage have another way of keeping this tracking up to date: the buyer can record that a purchase order has been paid. This declaration updates the tracking in Scout, but it does not transfer any funds. The payment itself is made outside the platform.
An expense incurred in Scout thus reaches accounting already coded to its accounts, its property and its flats. It has been matched against what was received or carried out, then reviewed. This coding work is done during the purchase, by the people who know it, instead of being pieced together after the fact.