QASWAThe problem
Finance had clear rules for which supplier purchases deserve a second look — invoices over a threshold, counter sales and returns, restricted items, the same item bought at different prices by different communities. Applying them by hand across thousands of invoice lines is slow, and a price gap between two communities is invisible when you read one line at a time.
What we built
A read-only review platform inside Heritage's own Azure subscription. It applies ten review rules to every purchasing line, scores each invoice and ranks them into one prioritized queue — critical, high, medium — with a status, an owner and notes on every invoice. Each threshold shows who set it and when.
“Qaswa has delivered five platforms for us across four departments, all running inside our own Azure environment. What stands out is the discipline: every number ties back to the source, and nothing changes in our systems unless one of our people approves it.”
Farhan Khan, CEO, Heritage Communities · 
How it works
- Ten rules, from invoice and line thresholds to same-month price differences between communities, unusual quantities and possible duplicates
- One prioritized queue — critical, high, medium — with a status, an owner and notes on every invoice
- Every threshold shows who set it and when
Numbers the finance team can trust
- Reconciles to the source to the cent on every refresh; integrity problems are reported, never silently corrected
- Read-only against a single database view — it never writes back to the finance system
- Sign-in through Heritage's own identity provider, limited to a named list of finance users
- Every settings change is audited, before and after
No AI in it, on purpose
This one is rules and computed figures only. Its built-in analyst answers only from computed figures, shows the calculation, and says "can't answer that yet" when it can't. Not every problem needs a model — this one needed rules the finance team could read, own and audit.