Skip to main content
GullySystem
AI for Procurement · Solutions

See what you buy, from whom and at what price, across every branch.

It reads purchase orders, bills and goods receipts from every branch, gives each line a category and groups the same item bought under five different names. Nothing is bought for you. Price drift, split buying and purchases outside any contract come up as lists, and the procurement head decides what to raise with each supplier.

What it is

One branch types MS angle 40x40, another types angle iron forty, and accounts books both under general purchases, so nobody can say what steel cost the business. The data is all there.

The software connects the purchase and accounting records you already keep, cleans item and supplier names, and proposes categories that your procurement head confirms before any totals are trusted. Every branch reads the same table.

Where it goes wrong today

The problems this is meant to ease.

The same item has five names

Nobody can add it up. Branches type their own item names and accounts books purchases under general heads, so a question like what we spent on steel last year takes hours of sorting sheets.

Prices drift without anyone noticing

Old rate cards expire. After the old rate card lapses, a supplier’s price creeps up order by order, and each bill looks reasonable on its own because nobody lines the bills up.

Branches buy the same thing separately

Volume gets lost here. Three branches order cement from three suppliers in small lots, so no supplier sees the combined volume and nobody has a reason to offer a better rate.

Buying happens outside agreed terms

Contracts get bypassed quietly. A rate contract exists on paper, yet an order goes to a nearby vendor at a higher price, and nobody records the exception where a controller can find it.

Small orders hide a large total

Small orders add up. Many small orders to one vendor on nearby dates each pass without a second signature, though together they pass an approval limit the business set for good reason.

Management reports are rebuilt each month

Reports are rebuilt by hand. Each month someone copies exports from several branches into a sheet, fixes the names by hand and builds the same charts again, so the report arrives late each time.

Inside the module

What AI spend analysis does.

One purchasing table

Data is gathered once. Purchase orders, bills, goods receipts and ledger entries from each branch and your accounting export are loaded into one table, with branch and requester kept on every line.

Item names matched, categories proposed

A person approves each group. Lines that mean the same thing are grouped, such as bolts bought by the box in one town and by the kilo in another. Categories come from your own list.

Spend by vendor and category

Totals have a home. Spend by category, vendor, branch and month sits in one view, and the long tail of small vendors becomes visible for the first time.

Price differences on repeat items

Prices are compared month by month. The unit rate paid for the same item is plotted by month and by branch, so a quiet rise after a rate card expired is noticed. A buyer then asks why.

Loose and split buying

Loose buying is listed. Purchases from vendors with no rate contract, items bought separately by several branches and orders priced above a contract are listed with order number and date for the buyer.

Consolidation ideas

These are ideas only. Possible consolidations and supplier conversations are listed with the data behind each one, and the procurement head decides which are worth raising, since the software negotiates and orders nothing.

Dashboards and management reports

Management sees one screen. Dashboards show spend by category, vendor and branch with the filters a manager uses, and a monthly report is laid out for the finance controller and the directors.

Where it gets used

What this looks like in a working week.

A building material distributor

A building material distributor compares the rate paid for cement across yards, and the procurement head sees one yard paying a different rate for the same brand. The question goes to the supplier.

A group of clinics

A group of clinics buys gloves, syringes and cleaning supplies at each site, and the report lists vendors per item and the sites paying more for the same pack. One pooled order becomes possible.

A workshop making auto parts

A workshop making auto parts finds bearings from one supplier appear under six item codes, so the combined volume is finally counted before the next rate talk. Six codes become one line.

A department store chain

A department store chain sees stationery and packing material bought by store managers from local shops, and lists those purchases for the buyer to bring under one contract. Nothing moves without the buyer.

A contractor with six sites

A contractor with six sites lists vendors paid on nearby dates for amounts just under the approval limit, and the finance controller asks each site manager about the pattern. The answer may be innocent.

Who touches it

The people who open this every day.

Procurement head

Reviews categories, picks the suppliers worth a conversation and checks that every suggested saving is real before it is mentioned to anyone.

Branch purchase officer

Sees what other branches pay for the same item before placing an order, and can ask the procurement head to join several small requests into one.

Finance controller

Uses the grouped totals to compare budgets with what was actually bought, and asks each branch to explain gaps the season alone cannot account for.

How it is set up

From first conversation to daily use.

  1. Map the purchasing records

    Start with what you hold. The procurement head and the finance controller list the branches, the accounting system, the purchase order source and the spreadsheets in use, and name who owns each one.

  2. Load and clean the data

    Clean the names first. A year of purchase orders, bills and goods receipts is exported from each branch, names are cleaned, and gaps such as missing units are listed for the owners.

  3. Trial on one category

    Try one category first. One category such as steel or packing material is categorised and grouped first, and the procurement head compares the groups with what a buyer would have done by hand.

  4. Check with the buyers

    Buyers check the output. Branch purchase officers read the price and split-buying lists for their own branch and mark each line as correct, explained or wrong, and wrong ones change the matching.

  5. Switch on the reports

    Go live with the reports. Dashboards and the monthly report are opened to the finance controller and the directors, exports from each branch are scheduled, and one person approves category changes.

  6. Review after a quarter

    Look back after a quarter. The procurement head reviews the lists that led nowhere, the groups that needed correction and the categories branches disputed, and decides which rules to change.

Measuring it

How you would know it is working.

Record where you stand before it goes live, so the change is measured against your own figures.

  • Addressable spend is the part of total purchases that falls in categories with competing suppliers, counted from the category map once the procurement head has confirmed it.
  • Cost savings are recorded only when a buyer logs a change, as the difference between the unit rate paid before and after, using the earlier bills as the baseline.
  • Spend visibility is the share of purchase lines that carry a confirmed category, vendor and branch, and the baseline is the share found in the sheets before go-live.
  • Price variation is the gap between rates paid for the same item in a month, measured against the bills of the year before go-live.
  • Unmanaged spend is the amount bought from vendors with no rate contract, taken from the contract list and bill history as they stood before go-live.
Used responsibly

Where a person stays in charge.

People decide categories and suppliers

The software only proposes. Groups, categories and consolidation ideas are drafts until the procurement head accepts them, and no supplier is contacted and no order is placed by the software.

Ideas are not results

No saving is promised. Consolidation and price ideas rest on past bills, so they ignore delivery risk, relationships and stock position, and the buyer must weigh those before acting.

Data quality limits what is seen

Gaps show as gaps. Lines with missing units, branch codes or vendor names are counted and shown as unclassified, so a dashboard states how much spend it could not place.

Supplier rates are confidential

Supplier rates stay private. Supplier prices and contract terms are commercial information, so branch users see only the branches and categories their role allows, and exports are logged by user.

How it fits

It is one part of a system, not an island.

A module earns its place by what it passes to the next one. These are the connections we set up most often.

  • Purchase order management
  • Vendor management
  • Goods receipt
  • Finance and accounting reporting
  • Your ERP or accounting export
Common questions

Questions owners ask about AI spend analysis.

How much history is enough to see patterns?

A year gives a fair base. Fewer months still give category totals, though price trends are thin and the buyer should read them with care, since one season can distort a short record.

Our item names are a mess. Can it still work?

Cleaning them is the first job. A person confirms each proposed group on the first load, which is the slow part, and later only small corrections arrive as new items appear.

Does it tell us to switch suppliers?

No, it does not. It shows rates, volumes and delivery history side by side, and the choice stays with your buyers, because relationships and risks matter and the data does not hold them.

Is it worth it for one shop with one buyer?

Probably not for one buyer. A sorted spreadsheet does the job while one person knows every order and every supplier by name, face and phone number in town. Value appears with several branches, several buyers or a long list of active vendors, when memory stops being a reliable way to compare prices.

What does it connect to?

It starts from exports. Purchase orders, bills and goods receipts come from your ERP or accounting software through exports or a connection that depends on what that software opens up. We check this first.

Who can see supplier rates?

That is set by role. Branch users see their own branch and categories. Finance and procurement see every branch. Each export is logged under the user who ran it.

How wrong can the categories be?

Some will be wrong. Proposed categories are drafts that a person confirms, starting with big spend areas, and any line left unconfirmed shows as unclassified in every report instead of being counted quietly.

What effort should we expect?

Effort goes into the clean-up. Cost depends on how many branches and data sources are involved, and the buyers’ time on the first clean-up is the larger share of your effort.

Talk to us

Tell us how you handle AI spend analysis today.

A spreadsheet, a register or another system: say which, and we will tell you plainly what is worth changing.

  • No obligation
  • A reply within one business day
  • Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements