Home > Solutions
EFS Transfer Service
Brief Overview
This solution automates the transfer of money from checking accounts to fuel / cash cards for transportation companies. In doing so, many of the delays and human errors were eliminated while the processes were completed much faster.
On This Page
Overview
Background
Technical Details
Development Cycle
Additional Information
See Also
Overview
One of our clients provides brokerage type banking services for thousands of trucking companies. One of the services they provide is offering fuel/cash cards to it's customers.
EFS Transfer Service automates the process of transferring funds to fuel/cash cards and provides email and web-based reporting to monitor the status of transactions.
Background
A process that occurs hundreds of times each day in our client's business is the need to transfer money from customer checking accounts to their fuel/cash card. Prior to the EFS Transfer Service solution developed by GL2, two companies had to manually participate in the process of transferring those funds. This often led to delays and was subject to human error.
This process is now automated using the EFS Transfer Service removing the need for human intervention.
Technical Details
| Platform: |
Windows Server 2003 |
| Technologies: |
VB.Net, SQL Server, Lotus Notes, Proposion N2N, XML, Windows Services, ASP.Net, FTP, IPWorks |
The EFS Transfer Service solution consists of the following components:
- Windows Service to handle scheduled transfers
- Windows Control Panel to manage settings and view status
- ASP.Net web application for adding transfers and monitoring status
- Email Transfer Reports
Staff enter transactions using a web-based interface. The transactions are held in a queue for 30 minutes at which time they are prepared as a single batch and sent to a secure FTP server where they are picked up by the vendor and processed. A reply is posted to the FTP server and processed by the EFS Transfer Service. After batches are processed a summary report is emailed to the client where it is automatically printed and used to reconcile accounts by the staff.
Development Cycle
Development from start to initial release was four weeks. Minor bug fixes and enhancements continued for five minor revisions. The solution has been in production since October 2006.
Total Development Time: 195 Hours including updates
Additional Information
See Also
|