Contribution and member/employee data in a payroll file
This example scenario is an investment fund that accepts member contributions via 'Contribution/Member/Employee' data embedded in payroll files from many different employers. Each employer can use a different payroll solution and so, typically, each payroll solution will produce files in their own format and type.
As the investment fund your system needs to extract the member/employee details and their contribution data from a myriad of different file formats and transform them into a standard format that your system can import/process.
There are a number of approaches you could take:
You could of course have staff manually hack away at these source files in Excel but that is very labour intensive (i.e. expensive) and prone to human error.
You could write your own bespoke translating applications, one for each file type. This would get very expensive very quickly and you have inadvertently committed your organization to the burden and costs of maintaining, bug fixing, and enhancing all of those translator code bases over time. It also places an impedance and delay to onboarding of new clients in cases where the data they provide is not covered by any existing translators. For some smaller clients the expected lifetime revenue may never exceed the costs involved in developing a bespoke translator required to onboard them.
You could set up an API connection from your app to Filegroove so that each file you receive is immediately sent to Filegroove for processing and then a fully transformed/normalized set of objects in the format and file type (e.g. Excel, CSV etc.,) required for importing into your system is returned to your application, ready for further processing.
To save money and provide painless onboarding pick option 3 .... everytime!
All it takes to implement Option 3 and introduce Filegroove data transformation seamlessly into your organization's workflow is to specify your target object definition (TOD) and then for each source file format, create a target object mapping (TOM) easily and quickly in the Filegroove Studio for data mapping.
