Sector benchmark

Don't type invoices. Ask the supplier for the NF-e XML (or download it from the billing email), choose the file here and the system reads issuer, items, quantities and amounts straight from the official document. Manual typing is where stock discrepancies are born.

Import the purchase invoice XML: Tenka reads items and amounts (namespace-tolerant parser), you check it against the order and POST it — stock comes in (RECEIPT/PURCHASE per item, updating the average cost) and the payable is born. Recipient acknowledgement (SEFAZ) is gated (A1 certificate + parameter).

Every invoice issued to the company arrives here: those the tax authority distributes (with the A1 certificate), those from the group’s supplier network and the XML files someone uploaded — one, several or a .zip. Nothing needs to be typed: the invoice arrives, the system suggests the purchase order and the item for each line, and you post it.

The Data tab holds the supplier, number, series, 44-digit access key, issuer, dates and amounts (products, taxes, total) read from the XML. In the Invoice items tab, each line of the NF-e appears with its link to the stock item and to the purchase order: this is where you check whether what arrived is what was ordered, and the discrepancy column shows where it doesn't match.

Only .xml files, up to 20 MB. The DANFE PDF won't do — it's the printout, not the document; the XML is what holds the structured data.

When you link the supplier’s line "FIO 30/1 PENT CARD" to your own item, the link becomes a mapping. On the next invoice from the same supplier with the same code, the line arrives already matched.

If the goods came from a purchase order, select the order in the dropdown before choosing the XML. That link is what allows checking what arrived against what was ordered — price, quantity and item. Uploading the invoice on its own loses the check.

The receipt created appears in the list below; click the number to open it, check the items and complete it. It's the confirmed receipt that feeds the balance and the average cost of inventory — an imported and abandoned invoice doesn't become stock.

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.

The list reads the screen's dictionary, so you choose the columns, filter by any of them, save views and export the whole set (not just the page). The form shows the dictionary fields in the Data tab; what is specific to this document — items, checking, picking, quote map — is in the following tabs.

When the XML declares volumes (the invoice's qVol tag) and the item enters in KILOS, posting closes one roll per volume in the chosen warehouse, with lot "NF-" and weight = quantity ÷ volumes of that item. That is the case of fabric bought from the knitting mill: you import the XML, post, and the rolls appear on the Rolls screen for weighing and cutting — without typing a single roll. If the invoice has more than one item in kilos, the volumes are split proportionally to quantity (at least one per item). The weight is the invoice's; check it at weighing, which declares the difference.

An invoice enters only once: if the same supplier, number and series already have an entry (typed or imported), the new one is refused and Tenka points to the existing one. When checking, each item is compared with what the order still expects: more than pending (beyond a 2% tolerance for length and weight) is a discrepancy; less is a partial receipt. Status and manifestation are set by the Check, Post and Manifest buttons.

If your account was invited by a network supplier (anchor partner) and you accepted, every invoice they issue to your tax ID shows here as imported, with the supplier already registered. Nothing enters stock by itself: check the items, link each line to your product and post — posting is your acceptance. Only invoices issued after you accepted the invitation arrive.

"Save links" stores the connection of each invoice item to the item record and the order. "Check" compares quantities and prices with the purchase order and flags discrepancies. "Post" is the irreversible step: it receives the stock, creates the accounts payable and closes what was still to be received on the order. A posted invoice can't be edited; adjust through a return to the supplier or a new invoice.

The "Unit in the register" column matches the invoice unit (the commercial unit of the XML) to the item record: the primary unit or a declared purchase unit. If it matches on its own, it comes pre-selected and shows the factor; if not, choose the equivalent — while one is missing, posting is refused and says which line. Stock is received in the primary unit (1 CX12 = 12 UN) and the unit cost is the primary unit's (box price ÷ 12).

Inventory: goes into the warehouse balance and needs the linked stock item. Use and consumption: it is an expense, does not go into stock and needs no product. Fixed asset: when posted, it becomes the asset record, linked to the 1st installment of the payable; later fill in the useful life on the record so it depreciates. The warehouse is only required when there is an Inventory item. Posting twice does not duplicate stock, installments or asset records: the second attempt is refused.

It happens — counter purchase, urgency. Import without selecting an order: the receipt is born without a link and is equally valid. But if this is routine, the problem lies earlier: purchases being made outside the order flow, with no agreed price recorded.

"Have the purchase invoices that arrived already gone into stock and become accounts payable?" Importing the XML doesn't change anything yet: it's POSTING that turns the invoice into the real world — stock receipt item by item (RECEIPT/PURCHASE, updating the average cost) and a payable in finance. An invoice in the list that hasn't been posted is neither stock nor a recorded debt. Use the Discrepancy column to start checking: it points to where the invoice didn't match the purchase order.

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

Yes: send the invoice XML or a photo of the DANFE with the product table. Tenkai matches each item with your stock (first by the supplier mapping, then by NCM and description) and proposes the entry. With everything matched, CONFIRM posts it right away: stock into the warehouse and the bill to pay. If any line has no item, the invoice stays here in Incoming invoices for you to match and post — no item is ever made up.

Import the invoice XML as usual. In the Payment block, under "Who gets paid", pick yourself (the partner who paid). The card installments, the 1st due date, the financial category and the profit center appear, already filled in; adjust what you need. On each item, choose the Destination: Inventory, Use and consumption or Fixed asset. Check and post: the payable is created in installments in your name, the last one closing the cent, and the fixed asset item becomes the asset record. If you do not appear in "Who gets paid" yet, ask an administrator to check "Partner who gets reimbursed" on your supplier record.

Pick yourself in "Who gets paid" and check "Invoice under a third party tax ID (receipt only)". The invoice is kept only as a receipt for the reimbursement and the "Outside SPED" mark appears: it does not go into SPED, tax credit, the accountant folder or the recipient acknowledgment. The expense and the reimbursement installments stay in finance. The mark only works with a partner chosen in "Who gets paid".

Open the posted entry and click Reverse entry, writing the reason. Stock gets the return movement, open installments are cancelled and the fixed asset is written off — nothing is deleted and everything stays in the audit trail. If an installment was already paid, the reversal says which: undo its payment in finance and reverse again. An entry linked to a purchase order is returned through the purchase return.