1. Understand expenditure and commitments separately
IT financial visibility is more than a total from the accounts ledger. SaaS expenditure can include subscriptions, usage charges, add-ons, support and purchases made outside central procurement. Licence counts alone do not explain those costs, while invoices rarely explain which employees or business processes depend on a service.
Separate paid expenditure, invoiced amounts and future contractual commitments. An annual prepayment, a monthly invoice and a multi-year agreement represent different timing and decision constraints. Without this distinction, teams can mistake a lower monthly payment for a lower total obligation or overlook a renewal that has already become binding.
- Agree reporting periods, currencies and treatment of tax with finance.
- Record source documents and flag estimates rather than presenting them as booked expenditure.
2. Connect finance to the technical inventory
The finance view describes suppliers, payments and commitments. The technical inventory describes services, accounts, licences and observed assignments. Connect them through reviewed relationships: one supplier may provide several products, and one application may be purchased through several entities or resellers. Matching names alone can create misleading totals.
Lojycal brings finance, licences, procurement and operational records into a connected workplace context. That can help teams investigate who owns a service and what a purchase relates to. It does not mean every payment, application or usage event is discovered. Coverage depends on connected sources, permissions, mappings and manual records.
- Match invoice lines to services and contract references, not just supplier names.
- Distinguish purchased, assigned and observed licences; these are different measures.
- Keep unmatched charges visible with an investigation owner and review date.
3. Establish cost ownership and renewal decisions
Each material service needs a business owner who can explain its purpose and a cost owner who can approve the budget. These may be different people. Shared services also need an agreed allocation method, such as assigned seats or departmental usage where reliable. Label allocations as management estimates when they are not accounting entries.
Renewal planning should start from the actual agreement: renewal date, notice deadline, committed quantities and permitted changes. A calendar reminder is insufficient if nobody is responsible for gathering requirements and authorising a decision. Verify terms against the current contract rather than assuming monthly billing allows monthly cancellation.
- Assign an owner and deputy for each significant renewal.
- Collect business requirements, available usage evidence and alternatives before the notice deadline.
- Retain the approved decision and confirm that the supplier accepted any contractual change.
4. Reconcile discrepancies before calling them savings
Financial reconciliation compares invoices, contract terms, licence entitlements and operational records. Investigate quantity differences, unexplained price changes, credits and duplicate-looking charges. Two payments to the same supplier may cover different periods or products; apparent duplication is a review signal, not proof of waste.
In a fictional example, two departments purchase collaboration tools with overlapping functions. One supports external client work under specific requirements, while the other supports internal teams. The review checks dependencies, contractual restrictions and migration effort before proposing consolidation. An unassigned licence may be a reserve for planned recruitment rather than immediately removable expenditure.
- Separate confirmed billing errors from potential optimisation opportunities.
- Estimate transition costs and operational risks before recommending a change.
- Only recognise a reduction when the relevant commitment or payment has actually changed.
5. Measure task time without overstating financial value
Automation can reduce manual reconciliation work, but time saved is not automatically cash saved. Establish a baseline for a defined task, including data gathering, exception handling and review. Compare equivalent task samples after the change, using the same scope and quality checks. Record ongoing administration and correction effort too.
For a fictional illustration, not a measured Lojycal result, reducing a task from 60 to 30 minutes means 50% less task time. Across 20 comparable tasks, that releases 10 hours. It does not demonstrate 50% higher overall productivity, a reduced payroll bill or a guaranteed return on investment.
- Report task-time changes separately from realised expenditure reductions.
- If valuing released capacity, disclose the hourly-rate assumption and whether that capacity is actually reused.
- Include implementation and ongoing operating costs when comparing options.
6. Evaluate with a small, financially meaningful scope
Start with a manageable set of services that includes a shared subscription, a usage-based product and an approaching renewal. Ask finance and IT to reconcile the same sample together. The objective is not a polished dashboard alone, but a traceable explanation from charge to commitment, service and accountable owner.
Confirm supported sources, available fields, permissions and workflows for your Lojycal plan and workspace. Organisation membership and roles restrict operations; a financial reviewer should not need unrestricted technical privileges. Use /pricing for current public pricing and /contact to clarify requirements rather than assuming commercial terms.
- Assess unmatched expenditure, ownership gaps and renewal-decision completeness.
- Agree who reviews discrepancies and how accepted corrections reach the relevant records.