Custom fields

Add your own fields to documents and masters — vehicle number, LR number, batch, salesperson — and watch them flow to registers, print, and exports.

Every trade has its own paperwork quirks — a transporter wants an LR number, a pharma wholesaler needs batch details, a dealership tracks vehicle numbers. Custom fields let you add exactly those, without waiting for the product to change.

Where custom fields can live

Placement	Example
Sale / purchase header	Vehicle No, LR No, Salesperson — one value per document.
Sale / purchase line	Batch, Serial No — one value per item row, shown as a real column in the items table.
Account master	Route, Zone, Credit terms.
Item master	Shelf location, Brand line.

Create a field

1
Open the designer
Go to Administration → Setup → Custom Fields and choose New field.
2
Pick where it lives
Choose the target (sale, purchase, account, item) and — for documents — header level or line level.
3
Define the field
Name, kind of value (text, number, date, choice), an optional default, and an optional pattern the value must match.
4
Choose visibility
Decide where the field shows: on the entry form, on printed documents, and in exports. Set the display order among your other fields.
5
Save and use
The field appears on the relevant form immediately. Values typed there flow to registers (as optional columns), print layouts, exports, and import mappings.

Numeric header fields can join the bill maths

A numeric header field may be linked to a bill sundry. Its value then appears as that sundry on the document, participating in totals the same audited way every other charge does.

Deactivate, don't repurpose

When a field outlives its use, switch it off — old documents keep their values for history. Renaming a field to mean something new rewrites the past; avoid it.

Keep line fields few

Up to four line-level fields render as inline columns in the items table, which keeps entry fast. Past that, ask whether the data really belongs on every line.

Was this page helpful?

PreviousConnections & messages NextPrint setup

Custom fields

Add your own fields to documents and masters — vehicle number, LR number, batch, salesperson — and watch them flow to registers, print, and exports.

Where custom fields can live

Placement	Example
Sale / purchase header	Vehicle No, LR No, Salesperson — one value per document.
Sale / purchase line	Batch, Serial No — one value per item row, shown as a real column in the items table.
Account master	Route, Zone, Credit terms.
Item master	Shelf location, Brand line.

Create a field

1
Open the designer
Go to Administration → Setup → Custom Fields and choose New field.
2
Pick where it lives
Choose the target (sale, purchase, account, item) and — for documents — header level or line level.
3
Define the field
Name, kind of value (text, number, date, choice), an optional default, and an optional pattern the value must match.
4
Choose visibility
Decide where the field shows: on the entry form, on printed documents, and in exports. Set the display order among your other fields.
5
Save and use
The field appears on the relevant form immediately. Values typed there flow to registers (as optional columns), print layouts, exports, and import mappings.

Numeric header fields can join the bill maths

A numeric header field may be linked to a bill sundry. Its value then appears as that sundry on the document, participating in totals the same audited way every other charge does.

Deactivate, don't repurpose

When a field outlives its use, switch it off — old documents keep their values for history. Renaming a field to mean something new rewrites the past; avoid it.

Keep line fields few

Up to four line-level fields render as inline columns in the items table, which keeps entry fast. Past that, ask whether the data really belongs on every line.

Was this page helpful?

PreviousConnections & messages NextPrint setup