When structuring a financial BPO in Jestor, the vendor's name, email, and phone fields are usually marked as required, ensuring no vendor gets registered without the minimum data needed for contact and identification. Why setting required fields from the start matters If the registry allows saving a vendor
In Jestor, creating a single-select field (like status) and turning on log metrics makes the system automatically track how long each card stays stuck in each phase, and how long it takes to move between stages. Why measuring this time matters Without this metric, it's hard to
In Jestor, the checklist field lets you choose from ready-made styles — like green/red, yes/no, happy/sad face — or customize it with your own emojis for each item on the internal approval checklist. Why customizing the checklist's style helps An audit or approval checklist is easier
In Jestor, a date-and-time field makes sense when the deadline needs a specific time of day, like "by 3 PM"; a date-range field works better when the payment can happen anytime within a period, with no set time. Why this choice affects deadline control Using
In Jestor, a currency field stores the value as a number, letting formulas and automations sum those values; a text field stores the content as a string of characters, which can't be added up mathematically. Why this technical difference matters Typing "$100" into a text field
Yes. In Jestor, when filling in the vendor connected field on an accounts-payable entry, you can click "add new" and register the vendor right there, without leaving the form you're filling in. Why this avoids interrupting the flow Without this option, the team would need
In Jestor, AI credit consumption and the number of pages processed by OCR show up separately on the account's usage page, each with its own metric. Why these metrics were split Before, document reading by AI (OCR) was counted together with general AI credits, which made it unclear
In Jestor, a cost center can have a sequential ID (like a numeric code) and a name as its main label, letting you split costs by ID internally while everyone else sees the cost center's name, which is easier to understand. Why just the ID or just the
If the tax and accounting side of the current ERP works well, but flexible approvals, automation, and AI are missing from the process, the company likely doesn't need to switch ERPs — it just needs to add an operational layer on top, like Jestor. The most common sign the
Jestor fills common gaps in a traditional ERP around approval flows, AI use, and operational flexibility — areas where the accounting side of an ERP is usually solid, but the day-to-day process layer falls short. Why the ERP alone doesn't solve everything An ERP is strong on
In Jestor, the random ID field can be used in the subject line of automated emails as a ticket identifier, instead of exposing the customer's name, amount, or other sensitive data directly in the message's subject. Why avoid sensitive data in the email subject The email
In Jestor, a sequential identifier follows a predictable order (1, 2, 3...), which lets someone try to guess other records on a public form; a random ID instead generates a pattern-free code, making that kind of improper access much harder. Why this matters on public forms Public forms used