You asked
Which customers owe us the most?
It understood
- Who
- each customer, by name
- Measure
- invoiced, less what they have paid
- Which
- open invoices only, cancellations out
- When
- all of it, across financial years
- Order
- largest amount first
Product
How it works
Four steps. The useful part is not that any of them is clever — it is that you can open each one up and check it, which is the only reason finance will ever sign off on a number a machine produced.
It reads the shape of your database, not what is in it
The first thing it does on connection is walk the table and column metadata and keep a snapshot. That snapshot is how it knows that at your site OINV holds sales invoices, that INV1 holds their lines, and which of your fields somebody added later. Not one row of your data is involved in this step.
It turns the question into a query
The question and that snapshot together produce one SQL statement. When a question could fairly mean two things it comes back and asks instead of picking one — “gross, or net of credit notes?” is a far better answer than a confident wrong number that nobody catches until the board pack.
It runs read-only, on your own server
The statement executes against your HANA database from your own deployment, as a database user with nothing but select rights. There is no write path to your ERP, and that is a property of how it is installed rather than a switch an administrator can flip.
It shows the whole working
What comes back is a short summary, a sortable grid, a chart when the data has a shape worth drawing, and the working — the rows behind every figure, the checks they passed, and the milliseconds it took. Your finance team can tick those rows off against the ledger and disagree with us. Good.
Checked
Also in the box
The parts that decide whether people keep using it
A clever answer that lands in an unsortable table, or that a controller cannot send to her auditor, gets used twice and then quietly abandoned. These are the unglamorous things that stop that happening.
One result, four shapes
Any answer is a table until you want it otherwise
Every result carries its own numbers, so changing the form changes the drawing and nothing else. No re-query, no second trip to the server, and the figures underneath stay the ones the query returned.
- Rajhans Polymers₹41,20,880
- Deccan Auto Spares₹28,64,110
- Sunbeam Pharma₹19,05,400
- Kaveri Textiles₹12,88,250
- Orbit Engineering₹9,41,700
Customizable Grid Layout
Sort, filter, page. Send the whole result set out to Excel, CSV or PDF, with the charts on their own labelled sheets rather than pasted in as pictures.
Lucid Charts
Scroll to zoom, drag to pan, open to full screen. The chart and the grid are drawn from one result, so they can never quietly disagree.
Simpler Access Controls
Three roles and a per-dashboard grant on every user. A credit controller gets ageing and collections and nothing adjacent to payroll.
Context-based Followups
Ask for the top ten after a chart of outstanding amounts and it keeps outstanding amount as the measure instead of silently switching to invoice count.
Clear Fiscal Periods
Fiscal periods are not an afterthought here. Year, quarter and month slicers are wired through every board, and Q1 means April to June.
Transparent Deployment
Your infrastructure or ours. Either way the database connection stays inside your network, because it is made from inside your network.
Try it on a copy of your own database
A sample company proves nothing except that somebody tidied the sample company. An hour on yours tells you the truth.