Author

Topic: Batch Payment/Payroll System with Database Management (Read 67 times)

sr. member
Activity: 566
Merit: 250
CurioInvest [IEO Live]
Hello. Novice coder/developer here so please be kind.

If it's possible, I'd like to solicit all available info the community can provide that can in a way provide some specific/helpful direction for my vision on how I could go on with the payroll system that I am developing in case my proposal to my superiors to consider crypto payments instead of fiat is given a go signal.

The system that I've developed has been developed purely in Python3 using a pre-existing .mdb accounts database (that I think should definitely be migrated to SQL/MySQL). It basically processes an input list of payees entitled to receive a given payment/wage/incentive for a certain period. Since every batch of payments being processed involve thousands up to millions of payments, initial validation of input list of payees (provided by an independent source) is an integral part of the system with the management of a database of payroll accounts. After validation, automated per account identification for every payee found in the input list follows before a payroll file is generated. With the limits of my coding knowledge, this is how I was able to make my CLI payroll system function so far. I got stuck after database migration since I'm still orienting myself with all these database syntaxes and commands for the report-generation part of the system.

My vision for the development of the system is to later convert the accounts to crypto wallet addresses with obfuscation of names and amounts. After generating/downloading a periodic report, authorized personnel/super-users should however be able to disable obfuscation by using a private/public view key (offline only maybe?) for report or audit purposes.

Would highly appreciate any advice on development or paying for already existing secure online services that could cater to the payroll management requirements above (and maybe more that I am not able to foresee right now).
Jump to: