Evenbead docs
Contents

Locations and custom fields

Split the books by where the work happens, and keep your own details on customers, vendors, products and documents. (Dated 2026-10-18; ADR-0202.)

Locations

A location works like a class: a shop and a field crew, a second town, a rental property. Locations come with the Business plan and up, unlimited. Add them in Settings, Locations and custom fields. A location is never deleted: deactivate it and it keeps its history but is no longer offered; renaming keeps every tag.

  • One location per transaction (the default, the way QuickBooks Online does it): choose the location on an invoice, bill, expense, check, sales receipt, estimate or journal entry, and every line of its entry carries it. An invoice made from an estimate takes the estimate's location.
  • A location per line: switch this on in the same settings page to share a journal entry's costs across locations (through the API: location on each line of POST /v1/journal-entries/propose).
  • Bank lines and rules: pick a location when you categorize a bank line, or let a rule set one. When an AI agent codes a line that a rule of yours matches, the database gives the coding the rule's location and refuses one that names another.

Every report that takes a class takes a location too (trial balance, profit and loss, balance sheet, general ledger, comparative statements, sales by customer, expenses by vendor, and the drill-down behind each amount). Reports, P&L by location shows a column per location and a No location column; the columns add up to the company's profit and loss, on the accrual or the cash basis. Download it as CSV or Excel. A balance sheet for one location shows the lines tagged with it; payments and transfers carry no location, so read it as a partial view.

Custom fields

Custom fields are unlimited on every plan. Add them in Settings, Locations and custom fields, on customers, vendors, products and services, invoices, bills or estimates, as text, a number, a date or a dropdown with its options.

  • Show as a list column puts the field in the list (invoices, bills, customers, vendors, products), with a filter: equal for numbers, dates and dropdowns, contains for text.
  • Print on the PDF (invoices, bills, estimates) prints the field under the document's dates, e.g. a building Permit #.
  • A field's type and what it is on never change; rename it, change a dropdown's options, or deactivate it (its values stay readable and in your export).

Changing a value on a posted invoice or bill does not touch the books: it is saved on its own and recorded in the audit log.

AI agents

Agents read locations and custom fields and tag their proposals with a location. Only people add or change locations and fields. An agent's custom field values wait for a person: they ride inside its invoice or bill proposal, or arrive as a Set custom fields request in Proposals.

API and MCP

  • GET /v1/locations, POST /v1/locations, POST /v1/locations/{id}/update, POST /v1/locations/scope
  • GET /v1/reports/profit-and-loss/by-location?from=&to=&basis= (and format=csv or xlsx); location= on every filtered report
  • GET /v1/custom-fields, POST /v1/custom-fields, POST /v1/custom-fields/{id}/update, POST /v1/custom-field-values
  • custom_fields on customers, vendors, items, invoices, bills and estimates; custom_field and custom_value filters on their lists
  • MCP: list_locations, get_profit_and_loss_by_location, list_custom_fields, set_custom_field_values (and the people-only steps)

The full shapes are in the API reference.