Movimento do parceiro

Anchor screen of the detail dictionary. It does not appear in the menu. — this is the role of the "Partner movement" screen within the platform.

Each row is a credit or debit in the sales partner's account (calculated commission, advance, settlement). It is what forms the balance payable to them — that is why posting here changes how much the partner has to receive.

Each row is an entry in the partner's statement: Type states the nature of the entry, Date marks when it happened, Amount is the value, Status tracks the entry's situation, and Description/Notes keep the context. Read in sequence, the rows tell the financial story of the partnership — and they are what is used to work out what is still open with the partner, without relying on a parallel spreadsheet.

Here you see and fix loose child records, one by one. In day-to-day work, however, the right thing is to create and edit them inside the parent record's form: that is where the business rules run (recalculated totals, validations, numbering, history). Editing directly here is useful for auditing and for correcting a specific case — but it can leave the parent record with an outdated total, and that raises no error on screen.

The Partner portal reads this statement to show the partner the commission receivable: the balance is the commission credit not yet deducted. In other words, what is entered here shows up outside — a recorded credit goes into the balance the partner sees, and the corresponding deduction reduces it. That is why the normal path is to keep the statement through the partner record (Transactions tab), where the entry is born with the partnership's context.

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.

"Where do I see partner transactions?" — whenever that question comes up, this is the screen that answers it.

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?".