Enterprise DNA

Instead of Unit4 Spend Analytics

Stop renting Unit4 Spend Analytics. Own your purchasing analysis.

We build your version around your supplier names, business units and purchasing rules, bring your Unit4 purchasing records across, and run it for you.

Unit4 quotes its current service through sales. Bring your annual bill and the modules you use so we can compare the work your version must cover.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

Read the annual bill

Which parts of the spend service do you use?

Unit4 Spend Analytics covers company-wide purchasing visibility and data preparation. Match the scope of your subscription to the work your team does each week.

groups

Supplier visibility

Unit4 groups purchasing information to show supplier dependencies. Your own version can preserve the name mappings and the reason each name was matched.

category

Category analysis

Classification makes the purchasing record useful. Keep your categories and review who assigned each invoice line to them.

fact_check

Purchase-order reporting

Unit4 provides purchase-order compliance views. An owned record can flag missing references against the policy for each business unit.

sync

Source connections

The vendor offers manual tabular uploads and automated connections. We agree which sources need importing and which connections your version needs.

bar_chart

Management reporting

Unit4 offers preconfigured and custom reporting. Your version puts the weekly supplier review and its supporting evidence under your control.

manage_accounts

The wider sourcing suite

Spend analysis sits within a broader source-to-contract service. Separate the purchasing analysis you need from other modules when reviewing the bill.

Your purchasing record

From supplier totals to evidence you can inspect

Supplier week

One supplier, all its recorded names

Match source names deliberately and keep the reason for every change. Review purchasing without losing the original invoice wording.

  • check Keep the original supplier name on every line
  • check Group matched names under the agreed supplier
  • check Separate business units and currencies
  • check Show gross purchases and net spend after credits

Price review

Compare like purchases before claiming a saving

Find different unit prices for the same item, unit and currency. Review the terms before treating a difference as an opportunity.

  • check Exclude credits from unit-price comparisons
  • check Keep unlike units and currencies apart
  • check Show the lower observed price beside each comparison
  • check Assign a review with an owner and due date

Evidence

Keep the explanation beside the number

Retain source details, classification reasons and invoice references. Give Monday’s review a list of records needing attention.

  • check Flag missing purchase-order references under your policy
  • check Keep category changes and supplier matches in the activity history
  • check Review invoice evidence and recorded retention dates
  • check Find stale purchasing data and overdue actions

Savings

Separate a proposal from a verified result

An estimate stays a proposal until a reviewer records the realised amount and its supporting evidence.

  • check Record the basis for each estimate
  • check Require evidence before marking a saving verified
  • check Keep rejected proposals with their reason
  • check Draft supplier reviews and savings working papers in your brand

Make it yours

Design your own Unit4 Spend Analytics replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Unit4 Spend Analytics. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Unit4 Spend Analytics replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Unit4 Spend Analytics data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Spend Analysis for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Spend Analysis for Claude Code

Connected to your own database

Who did we buy from, after matching supplier names?

KORU

Supplier
Southern Bolt Supply
Currency
NZD
Lines
3
Net spend
480.00
Gross purchases
500.00
Gross share pct
46.30
Supplier names
2
Supplier key
BOLT

KORU

Supplier
Unknown Industrial
Currency
NZD
Lines
1
Net spend
400.00
Gross purchases
400.00
Gross share pct
37.04
Supplier names
1
Supplier key
unit4:Unknown Industrial

KORU

Supplier
Harbour Freight Services
Currency
NZD
Lines
1
Net spend
180.00
Gross purchases
180.00
Gross share pct
16.67
Supplier names
1
Supplier key
FREIGHT

KORU

Supplier
Southern Bolt Supply
Currency
USD
Lines
1
Net spend
90.00
Gross purchases
90.00
Gross share pct
100.00
Supplier names
1
Supplier key
BOLT

TASMAN

Supplier
Southern Bolt Supply
Currency
AUD
Lines
1
Net spend
210.00
Gross purchases
210.00
Gross share pct
100.00
Supplier names
1
Supplier key
BOLT

Ask it anything

Ten questions this version answers today

These are real reads from the free version. Unit4 also offers custom reporting; this comparison is about owning the record and its rules.

chat_bubble Which source names have we matched to the same supplier?
chat_bubble Which suppliers account for most purchases within each currency?
chat_bubble What did each category cost after credits?
chat_bubble Which comparable item purchases have different unit prices?
chat_bubble Which invoices lack a required purchase-order reference?
chat_bubble Which supplier names still need matching?
chat_bubble Which records look like the same invoice line twice?
chat_bubble Which business unit has the oldest purchasing data?
chat_bubble Which proposed savings are overdue and still unverified?
chat_bubble Which invoices lack evidence or a reviewed retention date?

Switching

How to switch from Unit4 Spend Analytics

The move involves exporting transaction-level history, mapping it to the new database, checking the imported records and comparing the weekly reviews before you switch over.

  1. 1

    Get a transaction-level extract

    Ask Unit4 for a transaction-level extract from your Spend Analytics report. Unit4 supports tabular source data, but its published material does not define one standard export layout. Export what your account allows, usually CSV or Excel, and check with Unit4 if you need help. Include line-level purchasing records, not summaries. If the report is incomplete, use the original purchasing extract from your finance source.

  2. 2

    Map and preview the import

    Match the extract's headings to the fields used by the new system, including a source key that uniquely identifies each line. Run the import's test or preview first, before loading the records for use. This gives you a chance to check the mapping and spot issues with the source data before they affect the imported history.

  3. 3

    Check the import results

    Review any rows or issues the import flags, then reconcile the imported records and totals against the source extract. Check business units, currencies, credits, supplier names and categories. Unit4 does not publish a universal Spend Analytics export layout, so confirm that the headings and totals make sense for your own data. Resolve gaps before relying on the analysis.

  4. 4

    Run both side by side

    Keep Unit4 available while you run the same weekly spend review in the new system for a short period. Compare supplier spend by business unit and currency, price comparisons, missing purchase order references and savings evidence. Check that credits and supplier mappings are handled as expected, and resolve differences before asking your team to use the new system as its main review.

  5. 5

    Switch off Unit4 Spend Analytics

    Once the records and weekly reviews have been checked, move your team to the new system and switch off Unit4 Spend Analytics. Keep the original extract and any referenced invoice evidence accessible. The database holds purchasing records, but referenced evidence needs to be backed up separately. Make sure the people responsible for the weekly review know how to carry it out in the new system.

construction

Where the real effort goes

The main work is usually mapping your own source fields, supplier names and category rules, then deciding how much transaction history to bring across. You also need to reconcile headings and totals, and check the evidence linked to records. If Enterprise DNA installs and runs your version, it handles the field mapping and reconciliation as part of the setup.

Not ready for a call?

Get your Unit4 Spend Analytics switch plan by email

We will send you the step-by-step plan for moving your business off Unit4 Spend Analytics, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Do it yourself, have it customised, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, install dependencies and run npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and try the purchasing review
  3. 3 Map a transaction-level export, preview the import and reconcile totals
  4. 4 Use a fresh database for business records and configure your own access and backups
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your supplier names, categories, cost centres and review rules
  • check Your Unit4 or source-finance extract mapped and reconciled
  • check Your required connections and a team screen if you want one
  • check Your preferred technology and ownership of the finished system
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with agreed access, backups and evidence storage
  • check Purchasing reviews and working papers prepared for your team
  • check Source changes and reporting rules maintained as the business changes
  • check Operated through Omni by Enterprise DNA alongside your other systems
Book a discovery call

Questions

Instead of Unit4 Spend Analytics, answered

Does this replace every Unit4 sourcing module? expand_more

The free version covers purchasing analysis, supplier names, review actions and savings evidence. We scope your version around the work you use today, including any connections, team screens and other workflows needed for the changeover.

Can you bring across our Unit4 history? expand_more

Yes, from a transaction-level extract after its headings and totals are checked. Unit4 describes tabular data support but does not publish one universal spend export layout in the sources we checked. If your report is incomplete, we use the original purchasing extract from the finance source. Supplier mappings, categories and invoice evidence are reconciled as part of the work.

Are the price differences guaranteed savings? expand_more

No. The comparison checks like items, units and currencies across the imported history. Delivery terms, tax basis, rebates and quality need review. A proposed saving is only marked verified when a reviewer records a positive realised amount and supporting evidence.

Can it work across business units and currencies? expand_more

Yes. Each business unit and currency stays separate, with credits included in net spend. We agree any currency conversion and reporting-period rules for your version before combining results. The free version never invents exchange rates.

What does Enterprise DNA charge, and who owns the result? expand_more

One setup fee, then a retainer for the version we customise and run. We agree the scope after reviewing your annual bill, sources and weekly work. Your records stay in a database you own, and the free base is open source.

Bring the bill and a purchasing extract

Spend 30 minutes with Sam. We look at your Unit4 annual bill, the supplier questions you need answered and the source records behind them. Then we agree what your own version needs to do.

Book a discovery call Get the free version

Spend Analysis for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Unit4 Spend Analytics?

Get your version built