Home (new version · pilot)
Pilot of the new front-end, rolled out in slices: shortcuts to your most-used screens, presented in a new, faster version that coexists with the current platform (same session, same menu). It is a proof of concept — the current home version remains available. It helps the team measure whether the n…
What you find on this screen
A portrait of the screen, read from the screen itself — it changes when the screen changes.
Available actions
Seed from my industry
Form fields
NomeComo o trilho da operação é chamado. É o nome que aparece quando um documento entra nele.
VerboA ação que o trilho representa (comprar, vender, produzir). É por ela que o documento é encaixado.
AtivoTrilho inativo para de receber documento novo, sem perder o que já passou por ele.
Start here
O que esta tela responde
Does each operation in my company run with the right rules — and does what was already posted keep reading the rules of its time? This is where the rails live: the name your company gives to each type of movement and the behavior it triggers. When posting an order, an invoice or a return, you choose the rail, and it takes care of the rest.
Tracks in a list, always in the current version
The list shows each active track with name, verb, what it does today — receivable/payable, provision, stock, lot, cost, tax document — and since when that version applies. "Seed from my industry", on the bar, creates your vertical’s tracks without duplicating existing ones.
How to
Se você integra um ERP, os trilhos são o de-para da operação
In the connector's configuration, each operation type in the source system is pointed to a rail here. That's what makes a transfer between branches remain a transfer in Tenka, instead of inflating revenue as if it were a sale. An operation type without a rail doesn't come in: it stays pending, in plain sight, until someone decides.
Rules
What a track decides
Whether that movement generates a revenue provision in finance (the order becomes a forecast, and the invoice converts it into actual); whether it calculates cost; whose stock is involved — own, own held by a third party, or a third party's held by you, the distinction Block K requires; whether it requires a lot; which tax document model and series; which accounting event it triggers; and where the flow can go next — a quote that only becomes an order, a shipment that waits for the return, a replenishment between distribution center and store.
Editar um trilho cria uma VERSÃO NOVA — de propósito
Saving doesn't overwrite the previous rule: it creates a version with an effective start date. Future postings start using the new version; everything already posted keeps reading the version that was in force on the day. That's what prevents a correction made today from silently changing how last year is read — past margin, cost and accounting remain explainable. The list always shows the version in force; the full history is one click away.
Save publishes a new version
On the record, each Save publishes a NEW VERSION of the behaviour, in force from now on: what has already been recorded keeps reading the rules and dates of its time — the History tab shows all versions. The verb is chosen only at creation.
Delete deactivates the track
Tracks do not go to the trash: deleting deactivates — it leaves the list and the choice for new entries, and what was already recorded keeps it. To change behaviour, publish a new version instead of deleting and recreating.
Where the document stalls, in each version of the track
Every time a sales order, an incoming invoice or a return changes status, Tenka records the change along with the version of the track the document was on. Ask Tenkai "where does the order stall on the sales track?" and it shows, per version, the status that holds the document the longest, where it goes back and what gets redone. Comparing the new version with the previous one tells you whether the rule you changed helped. The count is per step, with no names, and starts from this version.
Frequently asked questions
Do I need to register everything from scratch?
No. When the company is created, the typical rails for the chosen industry are already seeded — a knitting mill starts with production sales requiring a lot and shipment for processing; a services company starts with a service invoice and never even sees the lot question. The "Seed from my industry" button restores any that are missing, without touching what you've already adjusted.
Was this article helpful?
In the same module: Operations13
Ticket automations"When X, do Y" rules on tickets: assign, move, notify — without manual intervention.CalendarsWork schedule and holidays: the base calendar that defines business days, hours per day, and holidays (nation…Classificação do statusAs fases do fluxo em que cada status da demanda se encaixa (Triagem, Em execução, Aguardando…): definem as se…TeamsWork teams with an owner and members — the basis for the team agenda, routing, and manager approvals.Roles and costsTable of roles (dev, QA, PM...) with cost and hourly rate — the feasibility ruler of the Studio.SLA policiesDefine response and resolution deadlines by priority/type — the clock that governs the tickets.Prioritization (WSJF)The backlog in the order the calculation recommends: value, urgency, and risk reduction add up to the cost of…Readiness (DoR/DoD)What needs to be resolved for a demand to ENTER a stage, and completed for it to LEAVE. It becomes a checklis…
Tenka Academy
Explore the AcademyStep-by-step learning paths for your industry, inside the platform.