For payment deadlines in Jestor, a plain date field is usually more suitable than a date-and-time field — since payment can happen at any time on that day — while a date-range field is used to represent a period during which the payment can be made. Why can date-
In Jestor, a currency-type field lets formulas and reports sum values automatically, something a plain text field doesn't support, since text can't be used in math operations. Why not just use a text field with the value? Typing "$100" as text might look
Yes. In Jestor, when filling out a linked-record field — like the supplier on an accounts payable entry — you can create a new supplier on the spot, without leaving the form you're filling out. Why does this avoid interrupting the entry? Without this option, the person would need
In Jestor, AI credits and processed pages (OCR) are separate metrics: credits cover general AI use on the platform, while processed pages specifically count the document reader's usage, in a more predictable way. Why does separating these two metrics make tracking easier? Before, reading images counted as variable
When building a cost center table in Jestor, using a sequential ID field together with a name field lets you keep code-based organization — common in companies that number their cost centers — without losing the name's readability during allocation. Why doesn't the ID or the name
Before deciding to switch ERPs, it's worth evaluating whether what's missing isn't the accounting or financial module itself, but rather a complementary operational layer — like approvals, AI, and more process flexibility — that the ERP wasn't designed to cover. Why doesn't
In Jestor, the Random ID field lets you build friendly codes, combining a fixed process-related prefix (like "AG" for appointment) with a sequential or random part, in a format the customer will actually recognize. Why does a friendly code matter in customer communication? An identifier like "
In Jestor, the Random ID field can be used in the subject line of automatic ticket emails, giving the customer a unique, recognizable identifier without relying on a sequential ID that exposes the total volume of records. Why can a sequential ID be a problem? With sequential IDs like 1,
Yes. In Jestor, the Kanban card cover's conditionals don't need to depend only on the stage — they can also be configured to react to any field value, like showing information only when a number exceeds a certain threshold. Why do value-based conditionals go beyond stage-
In the stock movement template integrated with Omie, Jestor automatically checks the tax ID linked to each product to identify which company it belongs to, with no need for the person to select it manually. Why is this automatic identification necessary? Companies with multiple tax IDs and separate stocks need
In Jestor, the field used as a linked table's label defines what shows up when you select that record from another table — and the ideal choice is a field with unique, recognizable information, like a name, instead of a generic identifier. Why isn't the default field
In Jestor, the formula field with the date add function lets you add days or months to an existing date, useful for automatically generating a due date from an issue date. Why calculate deadlines automatically instead of typing them manually? Typing the due date by hand on every new record