The problem
Supplier invoices arrive as PDFs in a shared mailbox. Someone types the details into a spreadsheet, someone else checks them against the purchase order by eye, and over-billing or a duplicate slips through when the team is busy.
What I built
An accounts payable desk that runs inside Microsoft Fabric. A clerk uploads the invoice and its header fields. The PDF is stored in the app's own storage in OneLake, and the invoice joins a review queue sorted by due date.
Every invoice is checked against its purchase order. Does the PO exist, does the supplier match it, is the amount within 2% (shown to the cent), and is it a duplicate? Failed checks are flagged in the queue.
The next step is obvious. A clean invoice is approved in one click. A failed check makes "Send a query" the main action, and approving anyway needs a written reason.
Separation of duties. Whoever uploads an invoice can't approve it, and only named AP reviewers' decisions count. Decisions are recorded by the server and can't be edited.
The real document beside the data. The stored PDF opens in the middle of the screen, next to the checks and the decision.
Keyboard shortcuts for the reviewers (J/K to move, A to approve, Q to query, R to reject), light and dark mode.
How it works
Fabric Apps (preview) with file storage (preview): Fabric sign-in with Microsoft Entra ID, the app's SQL database for invoices and decisions, OneLake storage for the documents, and access rules enforced on the server. Suppliers and purchase orders are reference data.
Status
Live on Microsoft Fabric, tested with real uploads. Corvane Logistics, its suppliers and every figure shown are invented for this demo.
Good fit if your team approves invoices, expenses, claims or any document-plus-decision process by email and spreadsheet today.
0 likes · 2 views · Nov 12, 2026
A Microsoft Fabric app for accounts payable. Invoices are uploaded to OneLake storage and checked against their purchase orders; failed checks are flagged, and
