Approval and reporting apps for finance
Invoice approvals, holds and aged debt on IBM Maximo, IFS and SAP.
An approvals inbox from one sentence
The invoice from SAP, the work order it paid for from IFS, on one screen. An illustrative app on a test landscape.
Describe your app
Build an approvals inbox for invoices on hold.
Web, at a desk
IFS Work ordersSAP Invoices
Phone, at the site
9:41
Approve INV-2210
- For work orderIFS
- 3391, pump P-114
- Invoice amountSAP
- 1,200
- PO price
- 1,000
- Note
- Extra seal fitted
Apps finance teams ask for
Each row is the sentence a team would type, the ERPs it reads and where it runs.
| The app, in one sentence | Reads | Runs on |
|---|---|---|
| “A view of open purchase commitments by project.” | IFSSAP | Web |
| “A report of aged receivables by customer.” | IFSSAP | Web |
| “An expense approval app for line managers.” | IFSSAP | Phone |
| “A list of invoices waiting on a goods receipt.” | MaximoIFSSAP | Web |
Controls that hold in every app
Official interfaces, the signed-in user’s permissions, a person’s review and checks on every commit, whichever team asks.
- Official interfaces
- Reads and writes go through each ERP’s official interfaces, never the database.
- Your users’ permissions
- Every call runs as the signed-in user, never a shared service account.
- Reviewed code
- A person reviews all AI-written code before it merges.
- Every commit checked
- Secret scanning and static analysis. A finding blocks the merge.
Questions from finance teams
Are finance apps permission-aware?
Yes. Every call runs under the signed-in user’s own ERP permissions, never a shared service account, so approvers see and do only what their ERP access allows.
Can an approval run the ERP’s own action?
Yes. On IFS the app calls the official approve and release actions, so IFS runs its own checks.
Who checks the code that touches our ledger?
A person reviews all AI-written code before it merges. Secret scanning and static analysis run on every commit, and any finding blocks the merge.
Describe the app your team needs
One sentence is enough to start: what the app does and who uses it.
We build it with you, live, in a safe test setup.