Scope ERP functions: what pylotik covers, and what it leaves to financial management

An ERP brings together all of a company's management functions. pylotik covers part of them: the operational steering of contracts, projects, maintenance and teams, with the client. It covers neither financial management nor accounting: it interfaces with those of your ERP, through a connector built to your needs.

Where the line falls

Three zones: what is covered, what is not, and what it interfaces with.

An ERP is the sum of its functions, from sales to accounting. Financial management is only one part of it. The operational steering of a project, a contract or a team is another, and it is the part pylotik carries.

Covered

Operational steering

Projects and portfolio, commitment contracts, teams, time, leave, workload plan, margin, meetings, minutes, risks, roles and responsibilities, with free client access. The detail is in the eight families below.

Not covered

Financial management and accounting

Issuing invoices, credit notes and reminders, general and cost accounting. pylotik does not issue invoices and does not keep the books: they stay in your ERP's financial management, or in your accounting software.

Interfaced

The ERP's financial management

pylotik prepares the invoicing orders and sends them to the ERP's financial management, which issues the invoice, through a connector built to your needs. It connects in the same way to project ticketing tools such as Jira.

The functions covered

Eight families of ERP functions, from the project to the month-end close.

Each function links to the page that details it. “Production” here means the days produced by the teams on projects, not manufacturing on a shop floor.

Family 1

Projects and portfolio

  • Project management: work packages, tasks, phases, milestones and dependencies, read by the client as well as the team.
  • Portfolio management: all linked projects, those of your clients and your suppliers brought together, each party seeing only its own.
  • Production tracking: the days produced on each project, from which progress and the schedule of a time-and-materials contract are derived.
Family 3

Meetings, decisions and rituals

  • Agendas and meeting flow: the framework of a committee, its running order and its circulation deadline.
  • Minutes and approval: submitted to the client, approved or refused with a reason, then frozen.
  • Actions and decisions: one log per meeting, and the question of who closes each action.
  • Rituals: project committee (COPROJ), steering committee (COPIL) and reviews, held from the same history.
Family 4

Teams, time and capacity

  • Time tracking: entered at the source, on web and mobile, feeding workload and margin without double entry.
  • Workload plan: real capacity by resource and by week, and overload seen before it becomes a delay.
  • Leave and absences: known in advance and checked against the projects where the person is expected.
  • Management steering: everyone's workload visible, time entered weekly, the weekly review; nobody is rated.
  • Roles and responsibilities: the RACI matrix, including the one that binds the client and the supplier.
Family 5

Alerts, risks and trade-offs

  • Operational alerts: overload and underload spotted before they become delays.
  • HR alerts: an alert goes where its author directs it, including to the HR function alone, which protects the author.
  • Risk management: a shared register, with a chosen visibility: internal to the supplier, or shared with the client.
  • Schedule trade-offs: leave and interventions that require freeing a workload already planned are weighed against the projects.
Family 7

The client

  • Free client portal: the client follows progress, approves minutes and amendments, carries out its actions, with no licence to buy.
  • Client calendar: a client's meetings and interventions, readable by the client and by its supplier, with their location.
Family 8

Pre-sales, planned for December 2026

  • Pre-sales steering: coordinate the team against the clock, decide go or no-go, hand over to the delivery teams. Planned for December 2026.
Financial management

What stays in the ERP's financial management.

The line falls at the invoice: pylotik steers what happens before it, and sends it the invoicing orders.

Split between the ERP's financial management and pylotik
FunctionThe ERP's financial managementpylotik
Issuing invoices, credit notes, remindersYesNo It sends the invoicing orders, through a connector built to your needs
General and cost accountingYesNo
Accounting month-end closeYesNo
Project contract: fixed price or time and materials, scheduleDepends on the ERPYes Ordered, invoiced, paid, balance due
Margin at completion of a project or contractDepends on the ERPYes Computed from time entry
Monthly project closeDepends on the ERPYes Time entry, approval, billing calculation
Monthly billing preparationDepends on the ERPYes Instalments to invoice each month

“Depends on the ERP” describes the family, not a vendor: each ERP has its own scope, to be checked in its documentation. The choice between keeping a services ERP and relying on pylotik is detailed in ERP or steering software.

Frequently asked questions

What we are asked about scope.

Which ERP functions does pylotik cover?

Operational steering: project and portfolio management, commitment contracts, interventions, time, leave, workload plan, margin, meetings and minutes, risks, roles and responsibilities, and the client portal. The full list, family by family, is above. It covers neither financial management nor accounting.

What stays in the ERP's financial management?

Issuing invoices, credit notes and reminders, and general and cost accounting. pylotik sends them the invoicing orders, through a connector built to your needs, and tracks what is ordered, invoiced, paid and still due to compute the margin at completion.

Next

Going further.

Cover the steering, keep the financial management

A demonstration on a data set that is already filled in: a project, its contract, its invoicing orders, a team's workload plan, and what the client reads of it.