Bank accounts

Register accounts (bank, branch, number, type). Every invoice settlement happens in an account; reconciliation imports the statement per account.

Each account is a real balance that has to match the statement. The opening balance is the starting point of the reconciliation: if it's wrong, the WHOLE reconciliation of that account is wrong, and the error doesn't show up as an error — it shows up as a stubborn difference.

Complete bank account record — bank, branch, account, type, currency, PIX key, collection agreement and ledger account — and, on the Transactions tab, a snapshot of what went through it: Inflows, Outflows, Realized balance and Open, with the linked entries line by line. Amounts follow the "Show Values" permission in the profile. The previous/next arrows move between accounts without going back to the list.

Opening balance and Balance date record the account's starting point in the system: enter the bank statement balance on the date the company began managing the account in Tenka — from there on, the transactions build the balance shown. Currency declares which currency the account operates in, which matters when the company's multi-currency is on. Default account marks the company's preferred account for day-to-day finance.

If two people edit the same account at the same time, the second save is blocked with a warning (record version control) — no one overwrites another without knowing.

Deleting an account briefly shows the Undo button; the account can also come back later from the recycle bin. Both paths go through the same check — and until 08/24/2026 they didn't: Undo brought back what the recycle bin refused, silently. If the restore is refused, the reason is shown in writing, instead of the account reappearing wrong.

Because its place has already been taken. If, after the deletion, someone registered another account with the same bank, branch and number, restoring the old one would leave TWO identical active accounts — and bank reconciliation would have no way of knowing which one to post the statement to. In that case the restore is refused with the reason. To bring the old one back, resolve the duplicate first.

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.

In a Family account, tick “Only I see it” on the card so the account (or card) and its entries show only to you and the household owner. Unticked, it belongs to the household: every member sees it. The owner always sees everything — that is how consolidated net worth adds up. The shared month snapshot never includes private items.

When you save, the system checks whether an identical account is already registered. If there is one, nothing is saved right away: a duplicate warning appears and the record is only saved if you confirm you really want the second account. This prevents the classic "two accounts at the same bank" created by mistake — without blocking the legitimate case (e.g. accounts for different operations at the same branch), because the final word is yours.

In the record's activity panel, each note has "Turn into request". The click creates a ticket with the note's text, who wrote it and the link to this record — nothing is retyped. Use it when the note is a request for action ("someone needs to review this"); the note stays where it was. The button only appears once the record has been saved; a read-only session (demo) doesn't create one.

No, and that's deliberate. It only appears for what's reversible: a regular deletion, which just sends the record to the recycle bin. Permanent deletion doesn't offer Undo, because there's no row left to bring back. And what the screen refuses to delete — a bill already settled or reconciled, for example — never gets deleted in the first place. Offering the button and then failing on click teaches people not to trust 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?".