Who this is for: AP admins who tune how a vendor's invoices are read and coded.

What it is: per-vendor rules that turn invoices into NetSuite bills — and how each bill's Approver, Class, and Location are coded. The Default ruleset applies to any vendor without its own row.

Finding a vendor

Open Vendor Setup from the top nav. Search by vendor name or NetSuite id. Each row shows chips: default (the fallback rule), vendor {id} (a bespoke rule), and {n} drafts (how many bills we've seen). Per page controls how many show at once.

Editing a rule

Click a vendor row to expand its editor. It's grouped into sections:

Approver routing

• Default approver — the fallback (service / unknown bills).
• Commercial approver — used for commercial jobs (optional).
• Route to ATTN employee (on by default) — if the invoice prints an ATTN/Attention name that matches an employee, route to them (highest priority).
• Residential → regional ROM — residential (non-DLL) bills route to the Regional Operations Manager for the bill's location.

Class & location

• Default class / Default location — fallbacks when the invoice doesn't say.
• Commercial location — the location for commercial jobs.

For residential/service bills, the Project's market sets the Location automatically (see AP — Coding Bills to NetSuite Projects). These fields are the fallbacks.

Line coding

• Generic fallback item — the item used for lines that don't match a real inventory item (e.g. a “BOM BOS” bucket).
• Expense-default account — set this to code the whole bill to one GL account (expense/staffing vendors). When set, item matching + history suggestions are skipped.