QuickBooks Online Custom Fields: Plan Limits Explain Most Setup Trouble
Users adding custom fields in QuickBooks Online hit plan caps and form limits; the accepted fix maps each subscription to its field allowance.
Custom fields are a recurring sore point in QuickBooks Online community threads. A user adds a field to an invoice or a bill, then finds the option capped, missing, or silent on the one form that matters. An answer published by Intuit and marked as the accepted solution traces most of the trouble to subscription limits rather than user error.
The feature is the draw for shops that want extra data on their paperwork: a job code, a salesperson, a delivery note reference. The fields feed detailed reports, which is the point of adding them. The issue touches QuickBooks Online across Simple Start, Essentials, Plus, and Advanced, and it reaches both sales and purchasing forms. Invoices, estimates, credit notes, bills, cheques, purchase orders, and supplier credits all sit in scope.
The symptoms users report
The pattern is consistent across reports. The Add field option is present, yet a new field refuses to appear on a purchase order. The Category dropdown that other users describe simply never shows. A field that works on screen never reaches the printed invoice a customer receives. None of this points to a damaged company file. Each symptom traces back to plan allowances or to a setting that governs the feature.
The numbers behind the confusion
The accepted answer opens with the allowances, and they explain most complaints. Simple Start permits one custom field per transaction. Essentials permits four, and so does Plus. Advanced permits twelve. The ceiling applies per transaction rather than per account, so there is no cap on how many transactions carry a field. A Simple Start subscriber can place a single field on every sale in the books. Dropdown fields can offer up to one hundred values to pick from.
The steps that resolve it
Once the arithmetic checks out, the fix is a straight setup walk. Open Settings from the gear icon and choose Custom fields. Select Add field; on a first visit the button reads Add custom field, and it does the same job. Name the field, then choose its data type from the dropdown.
Next, assign a category such as Customer, Transaction, Supplier, or Project. The vendor notes this choice may appear only on the Advanced plan. Tick every form the field should appear on. Turn on Print on form if the field must reach printed or delivered copies; left off, it stays inside the software. Save to finish.
Purchase orders carry a catch
Purchase orders need the purchase order setting switched on before any custom field can touch them. Essentials subscribers cannot take that step at all, because that plan excludes purchase orders. A Plus or Advanced user who skips the setting will blame the field, when the form itself is switched off. The accepted answer calls this out before anything else.
Edits, hidden fields, and recovery
Management happens from the same Custom fields screen. The list shows which forms each field appears on, with a print icon marking fields that customers or suppliers can see on a delivered form. An edit applies everywhere at once: renaming a field on one form renames it on every form that uses it.
Making a field inactive is not deletion. Existing data survives, past forms keep showing the field, and only new forms go without it. To revive a hidden field, switch on Include inactive, then choose Make active from the Actions column. Nothing needs to be rebuilt.
The takeaway
Most custom field trouble in QuickBooks Online is arithmetic rather than error. Count the fields a transaction already carries, compare that count against the plan allowance, and confirm the target form is enabled. Reports resolved on this pattern needed no repair to the company file, only the right plan and the right switches. Advanced subscribers have a wider allowance and their own extended workflow for the feature.