What we do

Pathfinder is being built to take the invoices a client receives from its waste and recycling vendors, check them, and report the results back. This page follows one delivery of invoices through that design.

Status: planned. Pathfinder is at design and specification stage. Nothing is live yet.

Illustration: A surveyed route with five stations. A bundle of paper marks enters at the first station, is read and checked at the second, is laid over a grid of expected services at the third, raises a flag at the fourth where one expected mark is absent, and arrives as one bound ledger at the fifth. A metaphor for the steps on this page, with no real data.

From delivery to report

Each step below is part of the design. None of it is live yet.

Arrive. Invoices arrive through the channel set up for that client.
Read and check. Each invoice is designed to be extracted and validated.
Compare. Each delivery is designed to be compared with the services expected at each property, by vendor, property and month. An invoice that should have arrived and did not is listed as missing.
Raise. Every missing or problem invoice is designed to become an exception with an owner, a reason and a target for closing it.
Report. The results are designed to be reported back to the client.

Set up for each client

Pathfinder is being built for more than one client from the start.

Each client is set up with its own list of properties, the services expected at each one, the way its invoices arrive, and the scope of its reports. A client is configuration, not custom code.

Illustration: Three survey sheets, one per client, each with its own parcels and its own legend of expected services. The same route runs across all three. A metaphor for one platform configured per client. The parcels are invented.

Why the comparison matters

The problem it is built around: the invoice that never arrives.

Last reviewed 2026-11-14.