-
151
Projects submitted
-
109
Published projects
-
47
Comments left
-
66
Number of votes
-
52
days until voting ends
workFLOW: Governed Payment-to-SAP Workflow Automation for Fuel Retail
-
Project manager on customer side
Naeem Sardar Bhatti
Flow Petroleum
Dy. Group Head IT & Information Systems
-
Category
-
Nomination
-
Goals
Until October, customer payments were confirmed over WhatsApp, across a large number of chat groups. Deposit slips were shared as photos, Finance checked the bank, and Accounts keyed each receipt into SAP by hand before the order could move. Management had no single view of collections, and confirmation history was spread across chats.
Goals for this phase:
1. Capture every customer deposit slip once, at source, with the order it relates to.
2. Enforce segregation of duties between the person who submits, the person who verifies and the person who posts.
3. Remove manual data entry and receipt scanning from staff workloads.
4. Post verified receipts to SAP Business One automatically, one SAP document per slip, within 2 working hours and with zero duplicates.
5. Give management live visibility of collections and of every pending or overdue step.
6. Build a reusable platform for the other 10+ workflows on our list.
-
Timeline
september, 2026 — november, 2026 -
Project completion year
2026
-
Project scale
55 automated workplaces -
Results
workFLOW went live on 22 October 2026 for retail customer payments. In the first 10 days:
- Several hundred deposit slips processed
- 95% of retail receipts came through workFLOW
- Average time from submission to SAP posting: median 30 minutes, against hours before
- 50+ users live
What changed for the business:
- Chat-based payment confirmation removed from the process
- Manual receipt entry and slip scanning eliminated for staff
- Segregation of duties enforced between submission, verification and posting
- Management has live visibility of market collections and every pending or overdue step
- Complete audit trail, with evidence, behind every receipt in SAP
-
Project uniqueness
workFLOW sits on top of SAP Business One without modifying it. No custom fields were added to the production database. Every SAP posting goes through the standard Service Layer under the licence of the officer who approved it, so SAP records a real person as the document owner. Dashboards read directly from the database to keep the Service Layer free for postings.
Control is built into the design. Submission, verification and posting are separate roles held by different people. Each team sees only the data it is responsible for, while management sees everything in one place. Automatic checks run before a receipt can reach SAP, and every action is recorded with user and time.
Our platform managers can change workflows without a new release, and staff sign in with their existing company accounts. We built it in-house with AI-assisted development and went from design to production within weeks.
-
Software used
- SAP Business One for SAP HANA (ERP), with SAP B1 Service Layer for all postings
- workFLOW web application: .NET back end, React front end, mobile responsive
- Microsoft SQL Server for workflow state, configuration and audit trail
- Corporate single sign-on
- Web application firewall for secure external access by field staff
- Separate SAP test company and UAT environment for every release
-
Solution from the Global CIO catalog
The project does not use solutions from the Global CIO catalog
-
Project implementation complexity
Payments come in through several channels and banks, and responsibility for verifying and posting them is split across different teams. We had to route every slip to the right person, keep each team's data separate, and still guarantee one SAP receipt per slip so bank reconciliation stays clean.
The integration had to use standard SAP objects through the Service Layer only, with no changes to the production database. Evidence files had to be stored where SAP could reference them directly, across different server platforms.
Field staff had to reach the platform from outside the office without exposing internal systems. Go-live also could not disrupt the daily order cycle. We handled this with separate test, UAT and production environments, staged releases and a rollback plan for each one.
-
Description
Flow Petroleum is an oil marketing company in Pakistan. Payment confirmation is an early and critical step in our order-to-cash cycle. Until recently it ran on WhatsApp across a large number of chat groups. That meant deposit slip photos that had to be saved and scanned, receipts keyed into SAP by hand, and no single view for management.
workFLOW replaces this with one controlled path:
1. The sales officer / territory manager submits the deposit slip and order details from a phone.
2. The responsible Finance officer sees it in their queue, verifies it against the bank and attaches proof.
3. The Accounts officer posts the receipt to SAP from inside workFLOW. One slip creates one SAP receipt, with no re-keying.
4. Accounts confirms the payment and approves the order in the same step.
Three things changed as a result.
First, the system now enforces segregation of duties. Submitter, verifier and poster are separate roles.
Second, data is segregated. Each user sees only the customers and transactions assigned to them. Management sees all market collections in one view, including the step each payment is at and which steps are overdue.
Third, the audit trail is complete. Every submission, verification, posting and approval is recorded with the user, time and supporting evidence, and can be pulled up in the application at any time.
Automatic checks run before anything reaches SAP, so errors are stopped at the point of entry.
We treated this as a platform from day one. An Administrator manages encrypted SAP connections, and Platform Managers maintain users, workflow steps and dashboards without development effort. Every release is tested against a test SAP company and then in UAT. It then goes to production with a backup, scripted changes and a written rollback plan.
Rollout began with retail customers and is extending to our other sales channels. The next workflow is end-to-end sales order tracking, from payment coverage through dispatch planning, delivery and invoicing. In total we have 10+ workflows defined across finance, sales, supply chain, procurement and HR.
-
Project geography
Pakistan. Phase 1 covers Flow Petroleum's retail customers nationwide, with users in the field and at head office. Later phases extend to all sales channels.
-
Customer
Flow Petroleum
Only authorized users can comment.
We suggest you log in or register.
Arshad Manzoor
Pakistan Oxygen Limited - 200
CIO
Fakhar Mirza Mirza
ICT Integrators
Director Technical
His strategic insight, effective coordination, and collaborative approach across teams and stakeholders were instrumental in ensuring the successful execution of the project. I highly recommend him as a technically accomplished and effective IT leader.