Work · 02 · Finance
4 days
from the start of development to a request that went all the way from an invoice to a payment order
Payment requests: a 10-company group in microfinance, leasing and car sales
Before.
A request by email
A reply saying “Approved”
A register kept by hand in a spreadsheet
After.
An invoice turns into a request by itself
The system checks payment details, budget and contract
An unposted payment order is created in the ERP
The path of one request.
- 1An invoice arrives
- 2 · systemRequest filled in
- 3 · systemEverything checked
- 4 · personApproved
- 5 · personPayment order signed
The system has checked.
- ✓ Payment details
- ✓ Budget
- ✓ Contract
- ✓ Not paid twice
A project for an external client. About 300 supplier payments a month, with requests coming from some forty employees. Requests used to arrive by email, were approved by replying "Approved", and the payment register was kept by hand in a spreadsheet. Now an invoice from an email or a phone photo turns into a request on its own: the payee, bank details, amount and paying company are filled in. The system checks the bank details, the budget and the contract, and warns if the invoice has already been paid. The payment order is created in the ERP unposted: an accountant posts it, and a person signs the payment in the bank.
Area: Finance process automation
Next piece of work: Court and enforcement documents for lawyers