What Business Intelligence Means Inside an ERP
An ERP records thousands of transactions every day: sales invoices, purchase orders, goods receipts, stock transfers, payroll runs, journal entries. On their own, those transactions do not answer management's questions. A managing director does not want to scroll through 4,000 invoices. They want to know whether the month is on budget, which branches make money and which drain it, which customers pay late, and which items are tying up cash in the warehouse.
Business intelligence (BI) is the work of turning transactions into measures and analysis that support decisions. When it is embedded in the ERP or connected directly to it, reports are built on the same data the business operates on. No exports, no copy and paste into side spreadsheets. The number on the dashboard is the number in the ledger, and you can click through it to the invoices and entries behind it.
This guide covers the building blocks of BI in an ERP environment, six analyses most companies need, worked examples on customer profitability, collections, stock ageing and budget variance, a calendar of Saudi regulatory reporting, and a practical way to get started.
Why Spreadsheet Reporting Runs Out of Road
Excel is excellent for ad hoc analysis and will remain part of every finance team's toolkit. The trouble starts when it becomes the main management reporting system. The symptoms are familiar:
- Late reports. The weekly sales pack takes a day or two to assemble from several branches, so it arrives describing a situation that has already moved on.
- Silent errors. A deleted row or a formula that stops short of the last line produces a wrong figure nobody notices.
- Competing versions. Finance and sales bring different sales numbers to the same meeting because they extracted data at different times or with different definitions.
- No drill-down. You cannot click a cell to see the invoices it is made of.
- Key-person risk. One person understands the workbook. When they are on leave, the report stops.
The goal is not to ban spreadsheets. It is to have recurring reports come from one trusted source with fixed definitions, and keep Excel for one-off questions.
The Four Layers of ERP Analytics
- Transaction data. Invoices, entries and stock movements as recorded in the ERP. Quality depends on input discipline, such as choosing the right cost centre and posting expenses to the right account.
- Analytical dimensions. Branch, cost centre, project, item category, customer segment, sales rep. These are what let you slice the numbers. If a cost centre is not captured on the entry, it will not appear in any report. Our article on cost centre planning and analytics covers how to design them.
- Measure definitions. Is gross margin calculated before or after rebates? Do sales include returns? One written definition per measure ends the debate in every meeting.
- Presentation. Dashboards, scheduled reports and alerts. This is what users see, but it is worth little if the layers below are weak.
Six Analyses Most Companies Need
1. Financial performance against budget
Revenue, costs and operating profit by branch or business line, against budget and the same period last year. The value is not in displaying numbers but in surfacing the variances that matter. A hypothetical branch month:
| Line | Budget (SAR) | Actual (SAR) | Variance | % |
|---|---|---|---|---|
| Sales | 2,000,000 | 1,850,000 | -150,000 | -7.5% |
| Cost of sales | 1,400,000 | 1,332,000 | +68,000 | +4.9% |
| Gross profit | 600,000 | 518,000 | -82,000 | -13.7% |
| Operating expenses | 350,000 | 362,000 | -12,000 | -3.4% |
| Operating profit | 250,000 | 156,000 | -94,000 | -37.6% |
The useful reading: sales are only 7.5% short, but operating profit is 37.6% short, because gross margin slipped from the budgeted 30% to about 28%. The branch sold less and sold it at deeper discounts or with a weaker product mix. That is exactly where the dashboard should lead you: click into sales to see which items and customers explain the gap.
2. Customer profitability
A big customer is not automatically a profitable one. An account that buys heavily but demands special rebates, frequent small drops and pays at 120 days may earn less than a steady mid-sized account. The analysis starts with revenue and cost of goods, then deducts the cost to serve. A detailed example follows below.
3. Inventory analysis
Stock value by category and warehouse, ageing, slow and dead stock, and turnover. ABC analysis is the core tool here, ranking items by consumption value so control effort goes where the money is. A regular alert on items with no movement in 180 days starts the conversation about markdowns or inter-branch transfers before write-off is the only option left.
4. Receivables and cash flow
Receivables ageing by customer and rep, days sales outstanding, and expected cash in from invoices due in 30, 60 and 90 days set against supplier payments and payroll. A profitable company can still run short of cash when its profit is sitting in customer balances.
5. Purchasing and suppliers
Spend by category and supplier, supplier on-time performance and purchase price trends for key items. This analysis often reveals several branches buying the same item from different suppliers at different prices.
6. Compliance reporting
Assembling the data behind the VAT return, the zakat return and annual financial statements. BI does not file anything for you, but it shortens preparation and exposes discrepancies before the deadline, such as purchase invoices missing the supplier's VAT number, on which input tax cannot be recovered.
Worked Example: Two Customers, Two Different Stories
A hypothetical distributor with a large chain account (A) and a mid-sized store (B):
| Annual, SAR | Customer A | Customer B |
|---|---|---|
| Net sales after rebates | 3,000,000 | 1,200,000 |
| Cost of goods sold | 2,550,000 | 936,000 |
| Gross profit | 450,000 (15%) | 264,000 (22%) |
| Delivery cost (drops x cost per drop) | 208 x 450 = 93,600 | 52 x 450 = 23,400 |
| Listing fees and promotions | 120,000 | 0 |
| Financing cost of receivables (avg balance x 6%) | 986,000 x 6% = 59,160 | 148,000 x 6% = 8,880 |
| Returns handling | 45,000 | 6,000 |
| Customer net profit | 132,240 | 225,720 |
Average receivables come from payment behaviour: A pays at roughly 120 days (3,000,000 x 120 / 365) and B at 45 days. The 6% financing rate is an assumption. The smaller customer earns about 70% more net profit. That is not an argument to drop the chain; it is an argument to renegotiate, for example consolidating drops or tying extra rebates to faster payment. The analysis gives sales a factual basis for that conversation.
Worked Example: Days Sales Outstanding
DSO is usually calculated as closing receivables divided by credit sales for the period, multiplied by the days in the period. A hypothetical 90-day quarter:
- Closing receivables: SAR 4,500,000.
- Credit sales in the quarter: SAR 6,750,000.
- DSO = 4,500,000 / 6,750,000 x 90 = 60 days.
If standard terms are 30 days, customers are paying in twice the agreed time on average. Bringing DSO to 45 days on the same sales would cut receivables to about SAR 3,375,000, releasing SAR 1,125,000 of cash. The useful view breaks the figure down by rep, customer and branch so you know where to intervene.
Worked Example: Stock Ageing and the Write-Down Question
An ageing report spreads stock value by time since each item last moved. A hypothetical warehouse holding SAR 6 million:
| Last movement | Value (SAR) | Share | Suggested action |
|---|---|---|---|
| Under 90 days | 4,200,000 | 70% | Normal monitoring |
| 90 to 180 days | 1,050,000 | 17.5% | Review upcoming order quantities |
| 181 to 365 days | 480,000 | 8% | Promotions or transfer to another branch |
| Over a year | 270,000 | 4.5% | Assess net realisable value; sell or write down |
This report links operations to accounting. IAS 2 measures inventory at the lower of cost and net realisable value, and items idle for over a year are the first candidates for a write-down. If the team estimates the SAR 270,000 of old stock will fetch no more than SAR 100,000, a SAR 170,000 write-down is due, and it is far better to know that mid-year than at year-end close. When the same supplier's items keep appearing in the oldest band, the issue is buying decisions, not just the warehouse.
Build a Measure Dictionary Before the Dashboard
Nothing erodes trust in reporting faster than one measure with two definitions. Start with a table like this and have finance sign it off:
| Measure | Agreed definition | ERP source | Owner |
|---|---|---|---|
| Net sales | Sales after discounts and returns, before VAT | Sales invoices and credit notes | CFO |
| Gross margin | (Net sales - COGS) / net sales | Sales and cost of sales entries | CFO |
| DSO | Receivables / credit sales x days | Customer sub-ledger | Credit manager |
| Inventory turnover | Annual COGS / average inventory value | Stock movements and cost entries | Supply chain manager |
| On-time delivery | Orders delivered by promised date / all orders | Sales orders and delivery notes | Operations manager |
For the executive-level measures and how they connect to growth targets, see our piece on CEO KPIs.
Saudi Regulatory Reporting Calendar
| Report | Frequency | Deadline |
|---|---|---|
| VAT return | Monthly if taxable supplies exceed SAR 40 million a year, otherwise quarterly | Last day of the month after the period |
| Zakat and corporate income tax returns | Annual | Within 120 days of financial year-end |
| Financial statements on the Qawaem platform | Annual | Within six months of financial year-end |
A simple monthly reconciliation of output VAT in the ledger against e-invoices issued, and input VAT against tax invoices received, catches differences before the return is due. With late filing penalties of 5% to 25% of the tax due and late payment penalties of 5% per month, that report earns its keep quickly.
Month-End Close Is What Makes the Numbers Trustworthy
Real-time views are valuable for sales, stock and collections, but true profitability only appears after the monthly close. Before close, some supplier invoices are not yet posted, depreciation has not run, accruals for rent and utilities are missing and the end-of-service provision is not updated. A dashboard showing operating profit on day ten of the month without those entries flatters reality. Label every financial view clearly as an open period with provisional figures or a closed period with final ones, and run a fixed close calendar, such as closing within five working days, covering bank reconciliations, customer and supplier reconciliations, depreciation and accruals.
Getting Started
- Ask management for five decisions. Start with the monthly decisions on pricing, purchasing, collections and hiring, and what information is missing for each, not with a list of reports.
- Check the dimensions. Is branch, cost centre and rep captured on every transaction? Fix input before building anything.
- Write the measure dictionary. One definition and one owner per measure.
- Build one dashboard. Usually performance against budget. Use it in the monthly management meeting for three months before adding more.
- Add alerts. A customer over credit limit, a branch margin below threshold, a filing deadline approaching.
- Expand in steps. Customer profitability, then inventory, then purchasing.
Common Mistakes
- Dashboards with forty numbers. Five to eight measures per management level is plenty.
- Measures without owners. If margin drops and nobody is accountable for explaining it, the dashboard is decoration.
- Ignoring input quality. Costs dumped into a sundry expenses account ruin any cost analysis.
- Real-time everything. Daily sales, yes. Net profitability needs a closed month to mean anything.
- Weak access control. Salaries and item margins should not be visible to every user.
How Tranquil Fits
Tranquil is a cloud ERP that brings financial accounting, inventory, sales, purchasing, HR, payroll and projects into one database, which is the foundation for analysis you can trust because every figure has one source. Tranquil's customization services include custom reports and screens, and API integrations for connecting external analytics tools where needed, while the e-invoicing module provides scheduled reports and deadline alerts. Explore our financial management solution or contact us to talk through the reports your management team needs.
Frequently Asked Questions
What is the difference between ERP reports and business intelligence?
Standard ERP reports list transactions, such as a customer statement or an invoice register. BI aggregates that data into measures, compares them with targets and prior periods, and lets you drill from a total down to the detail.
Do we need a separate BI tool?
Not always. If the ERP's built-in or custom reports cover your main decisions, they may be enough. A separate tool helps when you need to combine data from several systems or run complex interactive analysis.
How many KPIs should an executive dashboard have?
Usually five to eight, covering growth, profitability, liquidity and operations. Each needs a target, an owner and a written definition.
Why do finance and sales report different sales figures?
Almost always definitions: order date versus invoice date, returns included or not, figures before or after VAT. An approved measure dictionary resolves most of these disputes.
Can BI prepare the VAT return automatically?
It can assemble the data, flag discrepancies and cut preparation time substantially, but review and sign-off remain the finance team's responsibility, especially for adjustments and unusual transactions.