logo

View all jobs

E-invoicing consultant LS Central - August 2024

Remote, Remote
For one of our clients in the fashion sector we are looking for a E-invoicing consultant LSC 

BACKGROUND TO THE ASSIGNMENT
As part of the project, the Client plans to decommission the old version “RBO” (NAV 2009) and update it to the new Version “aLS” (NAV 2015 & LS Central) This includes, among other things, analysis of existing fiscal & legal laws in the country from the technical perspective, translating these requirements into technical specifications, guiding developers or developing the code necessary to fulfill these requirements. Consequently, the Client does not have own employees with sufficient expertise in connection with the design & implementation of the e-invoicing modules. The contractor must have expertise in managing similar implementations with LS Retail software for other fiscal countries therefore the contractor has a unique position and provides significantly different services than the internal staff.
 
SERVICE DESCRIPTION
The services are provided within the framework of an agile method. The concrete activities required in each case to implement the services commissioned are agreed iteratively between the parties within the framework of sprint meetings and implemented by the Contractor within the respective sprints following the sprint meetings. Prior to each sprint meeting, the contractor checks independently on the basis of its professional expertise, which individual services are reasonable and feasible within the scope of the assignment in the respective sprint. The sprints each have a duration of two weeks, so that the sprint meetings take place at intervals of Daily check in for 15 min. Within the individual sprints, the contracting parties shall coordinate the respective technical requirements for the services to be provided in daily meetings in order to achieve the compatibility of the individual components of the software aLS (NAV 2009, NAV 2015). The technical requirements for the services to be provided are assessed by the Contractor on the basis of their own technical assessment. After completion of a Sprint, the Parties conduct a "Sprint Review'' in which the Contractor reports on the feasibility and status of the services performed by it in the previous Sprint and makes a recommendation on how to proceed with regard to the services that proved to be unfeasible in the respective Sprint. All of the meetings and exchanges described above take place exclusively in the presence of a central contact person named by the Client, who coordinates the project on the Client's internal side. The organization and scheduling of the meetings described above in which the Contractor is involved are carried out by the Contractor.
Within this agile set up the contractor will take over the role of a developer (focusing on designing & implementing/configuring the e-invoicing solution).
The scope of services includes the following tasks, which are independently 
performed by the contractor: 
 
  • Provision of detailed delivery plan via JIRA Tickets, which is drawn up based on the contractor's own expertise. The plan is approved by the Client.
  • To keep JIRA up to date by processing Tickets based on contractors’ own expertise. This includes giving a project related update within the agile ceremonies on the process of the tickets to discuss progress and identify blockers.
  • Definition of the technical specifications based on the fiscal & legal requirements based on own expertise based on the upfront provided by the Client's legal, fiscal and client's-own requirements.
  • Inclusion of Content is available via the Jira and Confluence. The content to be processed is made available to the contractor to discuss progress and identify blockers via agile updates (named above). Content will be saved on confluence pages to be picked up for working on in Jira Tickets.
  • To process the tasks provided via ticket:
Every approaching ticket in Jira needs to be tested. Developer can be an Client's internal or an external. If it is an external, the contractor will act as an external consultant. If an error occurs during the testing another ticket will be raised against the other Client's internals testers. The testing takes place in an testing environment provided by the Client
  • Creation of a process description based on your own expertise. The creation process description is provided by the contractor via Confluence and accepted by the Client.
  • To compile detailed unit testing report to present to the Client's for review/approval
Review meetings are once in four weeks. There the test process will be shown to the whole team. The contractor can choose how to present it to the team. Possible via PowerPoint or as a demo in the coding tool itself (provided by the Client).
  • To compile a basic testing report to present to the Client for review/approval needs to be documented in the testing Jira ticket. Presented to the Client via the production Environment from LS Central in agile Ceremony meeting (mentioned above).
  • To point out dependencies and potential problems which occur in design or testing process via Jira. Reporting this to the Client to get input or advice within in agile Ceremony meeting (mentioned above). In case of an error issues to be solved based on own expertise. In case of dependencies hand over to the Client is needed

The performance of the contractor has the goal:
To provide software code for updating RBO to LS Central.
 
TIMELINES:
The following timelines are to be adhered to by the external during the performance of the service:

Depending on sprint and LS Central timelines which will be shared with contractor upfront.

Start: 01.08.2024 
Duration: 1 year+
Capacity: 40hrs/week
Location: 100% Remote
 

Share This Job

Powered by