Whew! It's been a busy day. I spent some of my morning interviewing payroll specialists about potential client candidates for a bridge application. Over the next month or so, we'll be adding several new clients, so anything the IT group can do to better facilitate payroll entry has been greatly appreciated.
Some clients use the web-based system to enter their payroll, which automagically shows up in the system. Other clients, however, fax a timesheet, either handwritten or otherwise. We may want to look at some way to use OCR for some of these payrolls.
But there were a few good candidates, and I'll be working on the bridge applications for them in the next week.
Most of my day today has spent diagnosing the application my coworker and I were developing yesterday and building a similar one for another client. The clients are trucking companies, and they have close to 200 active employees, most of which have been manually entered up to now.
One client is organized in such a way that they only have drivers. It turned out that, for the bridge application we were working on yesterday, we'd done everything but assign the number values to the individual payroll items. After adding code to do that, it worked fine.
The other client is similar to the first one, but they also have hourly employees that they report on via a separate file. The challenge here was to be able to set the program up with the flexibility and sophistication to know which file it was looking at, and subsequently, which layout to use.
Setting that up was a bit more of a challenge and required more customization than I've had to do in awhile, but I figured out what needed to be done, and, after testing it on the development and production side, everything worked.
Whenever I've set one of these bridge applications up, I always sent out an email to the relevant people to let them know. They all have gone home for the weekend, so it will hopefully be a very welcoming message they receive when they return!
Welcome to my online portfolio, the complement/substitute for my resume. The opinions included herein are my own and do not reflect those of any client or employer, past or present. Please check out the new site: http://danieljohnsonjr.com
- 401(k) report (7)
- accounting (1)
- administrivia (11)
- ADO (1)
- announcements (6)
- audio (1)
- batch files (1)
- benefits audit (2)
- blogging (8)
- branding (7)
- bridge application (17)
- business intelligence (7)
- cincinnati (6)
- client relations (4)
- community (1)
- competitive intelligence (2)
- conference (3)
- conversions (2)
- dashboard (3)
- data warehousing (1)
- design (4)
- documentation (2)
- financial reporting application (3)
- first post (1)
- get that job blog (2)
- global consumer products company (3)
- idea generation (2)
- integration manager (2)
- jazzmania productions (1)
- lessons learned (3)
- meetup (9)
- mentoring (3)
- microsoft great plains (5)
- music (2)
- nafta (1)
- networking (2)
- new media (22)
- payroll (6)
- peo (33)
- podcamp (3)
- podcampohio (2)
- podcasting (8)
- presentation (1)
- programming (31)
- public relations (1)
- public speaking (1)
- questions (1)
- requirements (4)
- search tool (3)
- social media networks (7)
- SQL (9)
- testing (1)
- training (1)
- troubleshooting (7)
- trucking (2)
- twitter (9)
- uml (1)
- VB.NET (2)
- VBA (1)
- wikis (1)
Friday, January 12, 2007
New bridge applications for trucking companies to significantly reduce payroll processing time
Posted by Daniel at 6:20 PM
Topics: bridge application, peo, programming, troubleshooting, trucking
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment