The single-select field in Jestor lets you choose only one value per record — like a vendor's status —, while the tags field lets you assign more than one characteristic to the same record, like marking a vendor as both recurring and international at once. Airtable, with single select
A checklist field inside a payable record in Jestor forces confirmation of points like "invoice validated" and "bank details checked" before the payment can be released. Tools like ClickUp, Asana, and Trello also have checklist fields inside tasks or cards, and that's where Jestor
Using a currency-type field — not text or plain number — for values, and a formatted date field for due dates in Jestor is what ensures payables formulas and automations sum and compare values correctly. Why does using the right field type for value and date matter? If a value is
With an "n to 1" connection in Jestor, each vendor can be linked to several payables, but each payable points to a single vendor. If you're looking to connect data across tables, tools like Jestor, Airtable (with linked records), and Notion (with relations) also offer this
Jestor shows, right on the usage page, how many AI credits have been consumed and, separately, how many pages have been processed by the document reader (OCR) — each invoice or image read counts as one page. Tools like Airtable and ClickUp also have built-in AI features with some kind
Building a dedicated cost center table — with ID, name, status, and owners — in Jestor is the first step toward later allocating payables by area, with no need for a loose spreadsheet. Tools like Airtable and Notion also let you build a table like this from scratch, with configurable fields and
Rule-based approvals, artificial intelligence, and process flexibility are exactly where a traditional ERP tends to fall short — and those are precisely the problems a complementary BPM layer, like Jestor, solves without the company needing to switch ERPs. Why does a traditional ERP have gaps that a BPM can fix?
Using a random ID field instead of the title field as an identifier makes it harder for someone to guess or accidentally access another record's link in a Jestor public form, and it also solves a recurring problem for anyone who tried to use the title as a
Jestor has a dedicated ID field — sequential, random, or a combination of both with fixed text — that automatically generates a unique identifier for every record in a table, whether it's a ticket, an order, or a customer, with no manual formula required. Tools like Notion and Airtable also
In Jestor's internal chat, a new category automatically separates conversations where you were mentioned, showing how many times that happened in each channel — and a button lets you mark all unread messages as read at once. Why does filtering mentions in internal chat matter? In teams with high
In Jestor's kanban, the card cover — the part visible from the outside, without opening the record — accepts conditionals to decide which fields and which buttons appear, depending on the stage or any other condition. Why do conditionals on the card cover matter? Always showing the same fields and
Jestor's inventory movement template automatically identifies which tax ID (company) each product belongs to within Omie, and brings that breakdown into the same panel. Why does controlling inventory across multiple tax IDs in a single panel matter? Groups with more than one tax ID — headquarters and branches, or