Cloud Accounting Package Bulk Import / Export Utility (Local CSV file to XML / JSON)
- or -
Post a project like this3040
$$
- Posted:
- Proposals: 6
- Remote
- #983830
- Awarded
WordPress, Magento, PHP, Android, IOS, Responsive Design, SEO, Software Testing
Ahmedabad
Business Consultant, Website Design, Website Development, PHP, WordPress, Web App, Mobile App, Branding, Designer, Business Plans, Business Support, Presentation, Adviser, Analyst, Strategist, Advisor
City of London
Top Shopify Developer ,WordPress, React.js, Next.js, Node.JS, Laravel, Express.js, Vue.js, Mongo DB, Expert ( PHP MySQL ).
Dallas
759028344625579409803688815316887923
Description
Experience Level: Intermediate
Estimated project duration: 1 - 6 months
General information for the business: We are freelancers ourselves, tired of tedious time-consuming manual expense administration…
Description of requirements/functionality: A web-based bulk input / output utility (“the Utility”) is required to transfer new and changed EXPENSE and MILEAGE entries, in bulk, between an online accounting package (FreeAgent.com) and a locally-stored CSV file.
Key Functionality:
The Utility must be able to GET, ADD, UPDATE and DELETE one or many EXPENSE or MILEAGE entries within FreeAgent, using a CSV file as input, or output.
The Utility must include actions to:
- VERIFY ONLY - Do not change FreeAgent, but report the results of what would happen if submitted.
- STOP ON ERROR – Perform transactions, but STOP if a transaction error occurs.
- SKIP ON ERROR – Performance transactions, but SKIP invalid transactions.
During processing, provide progress feedback to the user.
On completion, report a summary of successful and/or skipped transactions.
A limited functionality must be available to non-paying users, to allow a "try before buy" capability, by limiting the number of bulk transactions within a single file to 3 (three).
Non-Functional Requirements:
- Must be provided to users via a web-interface. The Buyer has the means to host web apps.
- Must provide the Buyer a means to add / delete permitted users of the Utility.
- Users of the Utility are associated with their FreeAgent subscription.
ie. If one company has several people using FreeAgent, then any user within a permitted company may use the Utility for bulk transactions.
- Usage data must be available to the Buyer, in order to monitor uptake of the Utility. Include reporting on number of users, files processed per user, transactions per file, paid / trial user status, etc. Add stats if appropriate.
- Usage statistics to be summarised by day and month
- The Utility must be supplied with installation and maintenance guide.
- The design of the Utility should be an “extensible engine”, to support further types of bulk input & output of FreeAgent records (eg. Projects, Timesheets)
CSV file format:
- FORMAT Line 1: File format and version information, to support backwards compatibility.
- TEMPLATE rows – defining the order of attributes in subsequent rows. There must be at least 1 TEMPLATE rows within the file. There may be several TEMPLATE rows, redefining the order, presence or absence of attributes in the following block of DATA rows. The attributes permitted are defined by the FreeAgent API documentation. All attributes must be supported by the utility.
- DATA rows – one or many rows, with each row containing a single EXPENSE or MILEAGE item, with all attribute values required (date, project, cost, recharge, etc...) for the entry, as defined by the preceding TEMPLATE rows.
- COMMENT rows – optional, starting with “%%”
Specific technologies required: "The FreeAgent API uses OAuth 2.0, supports XML and JSON responses and organises resources according to REST." A developers' sandbox and forum are available. The API is mature and reliable, with many other applications already integrated into FreeAgent. See https://dev.freeagent.com/docs
Extra notes: This development is intended to be agile. This is to say, demonstrate functionality as it is developed, seek feedback on the User Interface layout before coding the entire utility.
The file format is initial guideance. As no-one is currently using this format, if it can be improved, to make the utility more flexible, or future-proof, then that should be considered and agreed with the Buyer.
Description of requirements/functionality: A web-based bulk input / output utility (“the Utility”) is required to transfer new and changed EXPENSE and MILEAGE entries, in bulk, between an online accounting package (FreeAgent.com) and a locally-stored CSV file.
Key Functionality:
The Utility must be able to GET, ADD, UPDATE and DELETE one or many EXPENSE or MILEAGE entries within FreeAgent, using a CSV file as input, or output.
The Utility must include actions to:
- VERIFY ONLY - Do not change FreeAgent, but report the results of what would happen if submitted.
- STOP ON ERROR – Perform transactions, but STOP if a transaction error occurs.
- SKIP ON ERROR – Performance transactions, but SKIP invalid transactions.
During processing, provide progress feedback to the user.
On completion, report a summary of successful and/or skipped transactions.
A limited functionality must be available to non-paying users, to allow a "try before buy" capability, by limiting the number of bulk transactions within a single file to 3 (three).
Non-Functional Requirements:
- Must be provided to users via a web-interface. The Buyer has the means to host web apps.
- Must provide the Buyer a means to add / delete permitted users of the Utility.
- Users of the Utility are associated with their FreeAgent subscription.
ie. If one company has several people using FreeAgent, then any user within a permitted company may use the Utility for bulk transactions.
- Usage data must be available to the Buyer, in order to monitor uptake of the Utility. Include reporting on number of users, files processed per user, transactions per file, paid / trial user status, etc. Add stats if appropriate.
- Usage statistics to be summarised by day and month
- The Utility must be supplied with installation and maintenance guide.
- The design of the Utility should be an “extensible engine”, to support further types of bulk input & output of FreeAgent records (eg. Projects, Timesheets)
CSV file format:
- FORMAT Line 1: File format and version information, to support backwards compatibility.
- TEMPLATE rows – defining the order of attributes in subsequent rows. There must be at least 1 TEMPLATE rows within the file. There may be several TEMPLATE rows, redefining the order, presence or absence of attributes in the following block of DATA rows. The attributes permitted are defined by the FreeAgent API documentation. All attributes must be supported by the utility.
- DATA rows – one or many rows, with each row containing a single EXPENSE or MILEAGE item, with all attribute values required (date, project, cost, recharge, etc...) for the entry, as defined by the preceding TEMPLATE rows.
- COMMENT rows – optional, starting with “%%”
Specific technologies required: "The FreeAgent API uses OAuth 2.0, supports XML and JSON responses and organises resources according to REST." A developers' sandbox and forum are available. The API is mature and reliable, with many other applications already integrated into FreeAgent. See https://dev.freeagent.com/docs
Extra notes: This development is intended to be agile. This is to say, demonstrate functionality as it is developed, seek feedback on the User Interface layout before coding the entire utility.
The file format is initial guideance. As no-one is currently using this format, if it can be improved, to make the utility more flexible, or future-proof, then that should be considered and agreed with the Buyer.
Greg B.
100% (6)Projects Completed
3
Freelancers worked with
3
Projects awarded
33%
Last project
20 Jun 2020
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies