Work · Built and running

Two tools. Both finished, both run in seconds.

Two reporting apps that read straight from a company's ERP, the business system that holds its accounts, stock and orders, and run inside the Prudeon portal, where your people open, filter, download and print them. They show the shape of what we build, not a fixed package: what goes into your portal is scoped in your assessment. Everything below is a real run, with the numbers it produced and the finished output itself, which you can open and use right here.

Read this first

The data on this page is generated, not a client's. Both tools were run against a demonstration ERP database filled entirely with invented data: invented company, invented sites, invented stock codes, invented customers. No client data of any kind appears here and none ever will. What is real is the software and the run: these are the figures the engine produced on 09 November 2026, in the times stated, not a mock-up drawn to look convincing. Both finished files are linked below in full, exactly as the engine wrote them, so every figure on this page can be checked against the file it came from.

01  /  Month end pack

What happened last month, and what needs a decision.

The question it answers: the month is closed, so what is in the numbers that somebody should act on? Not a folder of exports for a finance manager to read through on a Sunday, but a ranked list of what crossed a threshold, ordered by what it is costing, each one opening to the lines behind it.

One command. It reads the client's own financial calendar out of the ERP, works out which period actually closed, and reports on that one.

Time to build the pack
17 seconds
From one command to a finished 57 KB file: the general ledger, the sales ledger, twelve trading periods and every stock position at six sites.
Findings on this run
7 findings
Three critical, three serious, one warning. Each is a rule against a configurable threshold, so the same code finds whatever is wrong at the next site, including nothing.
Largest single finding
R 15.6m
Sitting in 84 stock lines with no sale in twelve months. Nobody asked the system for this. It appeared because a threshold was crossed.
out/month-end-pack.htmlOpen the full file
The month end pack: six headline figures across the top, then the ranked list of findings, each one expandable to the stock lines behind it.

// Screenshot of out/month-end-pack.html, generated 09 November 2026 against the demonstration database. Invented data throughout.

Try the working report The picture above is a preview. Click it and the real report opens in a new tab, the same one a finance team would use, and you can work with it.

An income statement that ties

Month and year to date, actual against budget, built from stored period balances rather than re-aggregated transactions, so it agrees with what the ERP itself reports.

Revenue against plan

Twelve trading periods: actual, budget and the same months last year. Actual stops at the last closed period. Budget runs the full year, because a budget is approved before the year opens.

Where the margin goes

Margin by product group, turnover by site, customer concentration. On this run two groups were selling below cost and one customer was 18.5% of turnover.

Three reconciliation checks

Ledger revenue against invoiced sales, ledger history against ledger transactions, stock in transit against open transfers. Run on every build and printed whether they pass or not. All three agreed on this run.

02  /  Stock allocation

What should move where, this week.

The question it answers: one site is drowning in stock and another cannot fill its orders, so what goes on the truck? The month end pack reported that Durban was holding three times the cover of everywhere else. This is the tool that does something about it.

It reads every stock position at every site, works out what each site should be holding against its own demand rate and its own lead time, and writes a transfer list somebody can action before Friday. The method is printed on the dashboard itself, with the value every setting ran at, because a planner will not act on a number they cannot reproduce.

The plan it produced
653 lines
Worth R 7.6m at cost, 95 278 units, 291 stock codes across 27 routes. Read from 4 162 stock positions at six sites in 7 seconds.
Orders released
R 5.2m
422 back order positions cleared by moving stock the group already owned. Scarce stock goes to whoever runs out first, not to whoever asked for the most.
Durban cover, before and after
208 to 154
Days of cover. The plan takes it as far as transfers honestly can: the rest of that excess is stock no other site has demand for, and the dashboard says so.
out/stock-allocation.htmlOpen the full file
The stock allocation dashboard: six headline figures, then days of cover by site shown today against after the plan runs.

// Screenshot of out/stock-allocation.html, generated 09 November 2026 against the demonstration database. Invented data throughout.

Try the working dashboard The picture above is a preview. Click it and the real dashboard opens in a new tab, with all 653 transfer lines, and you can work with it.

A fair share engine, not a pro rata one

Where surplus does not cover need, back orders are cleared first, then every site is lifted to the same number of days of cover, and nobody is taken past their own requirement.

The honest other half

Need that no site can fill is not quietly dropped. It becomes a buy list: on this run R 2.8m across 114 codes nobody holds, with R 1.7m of orders behind them.

Dead stock is reported, not moved

84 codes have no demand at any site, so every transfer of them would be a lorry trip that changes nothing. The dashboard says that plainly rather than leaving a planner to work out why the engine ignored them.

Three reconciliation checks

Group stock value is conserved, no site ships more than it had available, value despatched equals value received. All three agreed on this run.

// How they are built

One portal. Your sign-in. Checked on every run.

Both apps run on one server and live in one portal, which your people reach with their Microsoft work accounts. Every app added later goes into the same portal and runs on the same engine, which is why the second costs a fraction of the first.

Behind your Microsoft sign-in

People log in with the work accounts they already have. Each person sees only the reports and apps they are allowed to, and there is no separate password to manage.

Runs where you decide

The server sits on your own premises, with a managed host, or somewhere else, decided company by company. Your IT team can set it up with our guidance, or we can put you in touch with specialists who handle the server and backups from day one. No tracking, no analytics and nothing reported anywhere.

Read only against your ERP

Every query against the ERP is read only and carries NOLOCK, so a report running at month end does not block the people trying to close the month. The only tables we write to are the portal's own.

Configured, not rewritten

Everything that differs between installations sits in one settings module: company code, ledger groups, warehouses, financial calendar, thresholds, branding, planning assumptions. A new client gets their own copy of that one file, not new code.

Your data, our engine

You own your data and everything in it. We keep the engine and license it per company database: unlimited users, support and new versions, with every app in the portal included while the licence runs.

Two outputs, one engine

They share a connection layer, a financial calendar, a settings module and a visual identity. A client who has seen one recognises the other as the same product, and the next app costs less to build than the first.

// Beyond the ERP

Not every problem lives in the ERP.

These two are reporting tools because that is where most mid-size companies lose the most time. They are not the limit of what goes into the portal. We also build custom apps for the job your off-the-shelf software will not do: booking and tracking systems, workflow and approvals, internal tools, and AI assistants that work on your own documents and data. Same portal, same sign-in, same licence.

If the thing you need has never been built before, that is what the assessment is for.

Want one of these pointed at your own data?

A paid assessment comes first: a fixed scope look at a copy of your own database and what is worth building against it. You get written findings in your own figures, every data quality problem ranked, and a fixed price for the build.

You talk to the person who writes the code. There is no account manager.