Case study · Construction & professional services
Supplier payments brought end-to-end into the ERP
A once-weekly payment cycle run through spreadsheets, email chains and bank-portal approvals was redesigned around in-ERP workflow, automated reporting and direct bank transmission.
- Client
- Global construction and consultancy group
- Sector
- Construction & professional services
- Service
- Finance Process Automation
The challenge
Supplier payments for the construction division ran on a once-weekly manual cycle. Batches were created by hand, the payment summary was rebuilt in Excel, requests and queries travelled through email chains, approvals happened in the bank portal rather than the ERP, and the payment file was moved manually from the ERP to the bank.
Even with no backlog, the cycle took a full week. The system held little record of who had approved what, and the process depended on individual knowledge.
One weekly cycle that took the whole week became two shorter cycles, approved and released inside the ERP.
Our approach
We project-managed the redesign across people, process, technology and control:
- Process: a future state with two payment cycles a week, a published timetable and communication templates so each stakeholder group knew when to review, respond and approve.
- Technology: automated batch creation, an automatically generated and distributed payment summary report, one service-desk ticket per cycle for traceability, and a design for host-to-host transmission to the bank.
- Control: a three-stage approval chain inside the ERP covering AP management, Finance and Treasury, replacing email and bank-portal approvals.
- People: iterated the design with AP, Finance, Treasury, Digital and the bank. Where workflow constraints and business needs required it, we adapted the design rather than forcing one that couldn’t be sustained.
We delivered in deliberate steps: in-ERP approval and release first, with bank integration following, rather than waiting for a single big-bang go-live.
- 01Automated batchCreated on schedule
- 02Summary reportGenerated and distributed automatically
- 03AP managementApproves in the ERP
- 04FinanceApproves in the ERP
- 05TreasuryReleases in the ERP
- 06Bank transmissionHost-to-host design
- System / automated
- Control point
Every approval is recorded in the system. One service-desk ticket per cycle tracks queries and exceptions.
The outcome
- All of the division’s payments are now created, approved and released inside the ERP, with a full system record of authority
- Email-based approvals and manual payment creation outside the system removed
- Automated payment reports validated and built into new mid-week payment-run schedules
- A design that can be extended to other entities through master-data changes, without further development