Customer map

The progress of each field service call: what was agreed, who performed it, what was logged in hours and material, and what state the order is in. This is where service billing comes from, when automatic billing is turned on.

At the top of the record is for whom and on what: the customer, the installed equipment and the contract — the service deadline comes from the contract and is shown alongside. The Data tab keeps the rest of the header (technician, equipment, hourly cost, whether billable). Once the order is saved, Materials, Hours and Schedule and field appear.

The list runs on the standard engine: the search accepts ?q=text directly in the URL and any dictionary field filters by ?fd_=value (e.g., fd_status=ABERTA) — links like that arrive already filtered, perfect for pasting into a chat. Saved views keep your favorite filter combinations ("my service orders today"), the visible columns are your preference per screen, and Excel, PDF and CSV export includes the ENTIRE filtered set, not just the page on screen. Deleted records stay in the recycle bin (?excluidas=1).

Three groups of fields tell the story of the visit: check-in and check-out record, by geolocation, when the technician arrived at and left the customer — and travel (km) measures the way there. The total cost is consolidated on closing: materials applied (which reduce stock) plus labor from the hours worked and the hourly rate. If the service order is billable, the billed amount is the other side of the equation — the difference between the two is that visit's margin.

If automatic service order billing is turned on in the Parameters and the order is billable, closing the order creates a RECEIVABLE in finance, due in 30 days, for the sale amount, already linked to the order's customer. Closing again does not duplicate: the existing receivable is updated.

For the receivable to be created, the company needs a REVENUE financial nature and a document type configured. If either is missing, the order still closes, but the receivable is NOT generated — and from this version on the system says so on screen, with the reason, instead of closing silently. It is worth checking the warning: until this version the failure only appeared in the server log, and it was possible to close a whole month of orders without any of them becoming revenue.

When you save a view with the Views button, it stores four things: the search text, the applied filters, which columns appear (and in what order) and which column the list is sorted by. Applying the view restores everything at once — including resetting the sort and the page you were on, so the result is exactly what the view describes. Views saved before this version remain valid: whatever they didn't store simply doesn't change when applied.

Nas fichas, sair de um campo já dispara a conferência do que dá para conferir na hora: campo obrigatório deixado em branco e e-mail mal formado. O aviso aparece embaixo do campo e desaparece quando você começa a corrigir. Campo numérico não precisa de aviso: ele simplesmente não aceita letra enquanto você digita. Isso é conforto, não a validação final: ao salvar, o sistema confere tudo de novo do lado do servidor.

Every Save on the record recalculates the service deadline from the chosen contract. So an order created on its own and linked to a contract later gets a deadline. Without a contract, the record says "no contracted deadline" in full — a blank would look like "on time".

The status appears on the Data tab but read-only: it changes when scheduling, at the mobile check-in, when recording the report and when closing. Closing is what deducts the materials from stock and consolidates the total cost — that is why material already deducted cannot be removed.

Na aba Agenda e campo da OS, informe a habilidade pedida e clique em Sugerir técnico: os técnicos de campo vêm ordenados por habilidade, distância da base até o local da OS, prazo do atendimento e carga do dia, com o motivo de cada um. Usar põe o técnico no agendamento; Confirmar com o cliente manda a data pelo WhatsApp da empresa.

Open the record and look at the Timeline on the right: it shows each change as "from one value to another", with the person and the date. When there are many changes, use the two filters at the top of the timeline — one by field, the other by person. The search runs in the database, so old changes show up just the same. You can also ask Tenkai: "who changed contract 482?".

Service is a consultant's execution: you link the work order to the project and the phase, set the consultant and log the hours. It has no GPS check-in, materials or on-screen sign-off. Field is the technical visit: check-in, materials, report and customer sign-off, as always. To save a service work order, set the consultant and a project, a request or a contract. Every work order that already existed is field.

Work order hours start as pending. In the Hours tab, approve them (one by one or with "Approve pending"): once approved they draw down the contract hour bank and enter profitability right away. The contract is the work order's, or the project's, or the request's. Waived or non-billable hours do not draw down. If the work order came from a request, its hours replace the hours logged on the request — the same hour never counts twice. Hours imported from another system come in already approved, with the name of who imported them.

An hour worked counts only once. When the service work order and the request describe the same work, the work order's hour is the one that counts: the request's hour stays out of the contract and margin totals, and the contract's hours list shows the reason for each line. If the contract requires customer sign-off, the work order's hour only draws from the bank after the customer accepts; until then it already weighs on the project cost.

Export the executed work orders report from Sankhya (number, date, consultant, hours, phase, project, description) and use Import spreadsheet here. If the header differs, choose in the preview which column is which and click Apply and remember. First register the Sankhya connector in Integrations (no password needed). Rows with an unlinked consultant, project or phase come in as pending; resolve them in the connector mapping.

Because it came from Sankhya through the import of completed work orders, and that is the number the consultant and the customer know. Every imported work order shows the source system number, with its name next to it, in the list, the record, the P&L cost by phase and the project timeline. To find one, type that number in the list search. The Source column says where each work order came from; one opened here shows Tenka and the in-house number.