> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Which Fields of a Vendor Registry Should Be Required When Structuring a Financial BPO?
- URL: https://blog.jestor.com/required-fields-vendor-bpo-jestor/
- Published: 2026-07-22T15:52:00.000Z
- Updated: 2026-07-22T15:52:00.000Z
- Author: Bruno Bannach

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 without an email or phone, for instance, the team may struggle later to reach out when there's a payment issue to resolve. Setting requirements avoids that kind of gap.

### Common fields marked as required

- Vendor name, used as the main identifier
- Email, essential for communication and sending documents
- Phone, for more direct contact when needed
- Vendor status, to know if it's active, inactive, or blocked

### How to set required fields in the vendor registry

1. Create the needed fields on the vendor table
2. Mark each essential field as required
3. Test the form by trying to save without filling in a required field
4. Adjust as needed for your financial BPO's actual process

### Process automation with complete data

Making sure the essential fields are required is the foundation of reliable financial **process automation** in Jestor, since formulas, automations, and **ERP** integrations depend on complete data to work correctly.

### Table Summary

| Field     | Why it's required                   |
| --------- | ----------------------------------- |
| **Name**  | Vendor identification               |
| **Email** | Communication and sending documents |
| **Phone** | Direct contact when needed          |

### Video Tutorial: Step by Step

*Video: Ep 11: Structuring the Vendor Registry for Financial BPO — video tutorial showing this feature in practice, right inside the Jestor interface.*

## Frequently Asked Questions

**Does every field on the vendor registry need to be required?** No, only the ones essential for contact and identification; others can stay optional, like notes.

**What happens if I try to save without filling in a required field?** The system blocks saving and flags that field as needing to be filled in.

**Does this requirement pattern apply to other tables in the financial BPO?** Yes, the same logic can be applied to other tables, like accounts payable, on [jestor.com](https://jestor.com/?ref=blog.jestor.com).

## Get to Know Jestor

With Jestor, you can automate workflows, connect different areas, and build internal systems your way — all without code and with AI support. Check out Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and discover how to take your company's management to a new level of efficiency and integration.