Settings → System
System Settings is where district-wide Accounting options are turned on or off and controls which product capabilities every campus in the district can use.
Who changes these? System options are usually owned by a district finance admin or CFO — not individual school bookkeepers. Changing a toggle affects every school on the district Accounting tenant.
Object Codes
Object codes can be used for classification for transactions and fund accounting.
Enable Object Codes — when on, requires object-code selection when recording transactions
The actual code list (Code, Description, Type, Status) is maintained under Settings → Object Codes. See Object Codes.
Purchase Orders
Sets Purchase Orders workflow for the district.
Enable Purchase Orders — when on, shows the Purchase Orders tab and allows creating and approving POs
Vendor Approval
Sets the requirement for central-office approval before bookkeeper-created vendors become active.
Enable Vendor Approval — when on, new vendors land in Pending until a central-office user approves or denies them
Approver email — where approval requests are sent (notifications are a follow-up; the address is stored here now)
Pair with day-to-day vendor management under Disbursements. See Vendors: Managing Who You Pay.
Vendor Tax ID
Sets the requirement for a Tax ID (EIN/SSN) when creating or updating vendors.
Require Tax ID — when on, Tax ID is required on vendor files; when off, the Tax ID field is optional.
Requiring Tax ID supports 1099 readiness and year-end vendor reporting.
Why these toggles are district-level
Object-code dictionaries, purchase-order policy, and vendor master controls are governance decisions. Making them school-by-school would produce inconsistent reporting and weaker audit trails. Setting them once for the district gives you:
Consistent reporting categories across campuses
One vendor-approval standard for multi-school controls and 1099 work
A clear on/off line for features that involve extra staff workflow
System vs. other Settings pages
Organization — school name, fiscal year start, time zone, currency (per campus)
Approvals / Notifications / Fund Authorization — who can act and when they are alerted
Account Setup / Account Groups / Object Codes / Fund Accounts / Bank Accounts — structure and doorways for money
Users & Permissions — who has which role
System — which product capabilities the whole district is running
If a feature appears missing on a form (for example no Object Code field on a receipt, or no Purchase Orders tab), check System Settings first — the district may simply have that capability turned off.
Changing a live district’s toggles. Turning Object Codes, Purchase Orders, Vendor Approval, or Tax ID requirements on after schools are already posting will change existing workflows overnight. Plan a short internal announcement, update any local desk procedures, and confirm staff know which fields are newly required before you flip the switch mid-period.