Custom Fields
How to add your own fields to customers, vendors, invoices, bills, items, and jobs.
Custom fields let you capture the data your business cares about that isn’t in the standard forms.
How to use them
Choose the record type (customer, vendor, invoice, bill, item, or job), give the field a key and label, pick a type (text, number, date, boolean, or select), and mark it required if needed. The field then appears on that record type throughout your books.
Custom fields are great for tracking things like PO numbers, license numbers, warranty dates, or internal codes.
Reporting on custom fields
Once a custom field is in use, it becomes available as a filter and column on the relevant list views, so you can slice records by whatever you decided mattered — not just the built-in fields.
Naming fields for the long run
Pick a clear, stable field key up front — renaming a key later can break saved filters and reports that reference it. The display label is safe to change any time.
Frequently asked questions
Can a custom field be required?
Yes — mark it required and the record can’t be saved without it, useful for something like a PO number your business always needs captured.
Can I delete a custom field later?
Yes, though removing a field also removes it from future forms and reports — consider whether you need the historical data it captured before deleting it.
Can a custom field have a default value?
Where supported, yes — a sensible default saves time on records where the value is usually the same, while still letting you override it when needed.
Do custom fields sync with QuickBooks?
Native QuickBooks fields map during sync, but a Seayora-specific custom field generally stays local unless QuickBooks has an equivalent field to map it to.