Winning Your First National Account: What Changes in Your Operation

Winning a national account changes 5 things at once: work arrives through a portal instead of the phone, an NTE cap replaces your quote, invoices go to a head office on their terms, compliance paperwork becomes a condition of trading, and your equipment list stops fitting in one person's head.

The short version

The first national account is usually treated as a bigger version of a local customer. It is not. It is a different operating model that happens to arrive as a contract.

Local work is a relationship. Somebody calls, you go, you invoice, they pay. National account work is a process, and your job is to fit it.

That is not worse, and for most service companies it is genuinely good business. It is a different thing, and the service companies that struggle are the ones that discover the differences one at a time after signing.

What to expect:

• Work arrives as a ticket with a clock already running
• You get an authorization ceiling instead of an approved quote
• Their invoicing process governs, including their reference numbers
• Payment terms are longer than anything you set locally
• Insurance and compliance documents are a precondition, not a formality
• Reporting becomes part of the work

The clock starts when the ticket lands, not when you see it

This is the change that surprises people most and it is the one with a penalty attached. A local customer's urgency starts when you answer the phone. A portal ticket's clock starts when it is created, whether or not anyone at your service company has logged in.

Response time is usually measured against that timestamp, and it is often the metric your performance is judged on rather than whether the repair was good. A service company that checks the portal twice a day is losing time it never spent.

Three practical consequences:

• Somebody owns the portal, by name, with a checking rhythm. Not "we all keep an eye on it". Most service companies discover this after the first missed acknowledgment.
• Acknowledging is separate from attending. Many programs measure acknowledgment, on-site arrival and completion as three different clocks with three different targets.
• A ticket you cannot cover has to be declined quickly. Sitting on a ticket outside your coverage area damages your score more than declining it does.

If you serve more than one of these programs, this is where the phrase portal juggle comes from. Each has its own login, its own field names and its own definitions of the same words. Getting those tickets into the same place as the rest of your work is the difference between a scalable arrangement and a part-time data entry job.

An NTE cap replaces your quote, and it binds the technician

Under a not-to-exceed authorization you are not quoting a price. You are reporting a diagnosis and asking for a ceiling.

That inverts the normal sequence. Locally you diagnose, price the job, and get a yes. Here you diagnose, request an NTE, and work up to it. If the repair turns out to need more, you stop and ask again.

The failure mode is a technician who finishes the job because finishing the job is the right instinct. The invoice then exceeds the authorization, and it gets short-paid or disputed months later, usually after the technician has forgotten the visit.

What has to be true operationally: the cap has to be visible to whoever is doing the work, not just to whoever requested it. A number that lives in an email in the office is a number the technician does not have.

Two habits that prevent most of it. Request the NTE with the diagnosis attached rather than as a bare figure, because a diagnosed request gets approved faster and at a higher number. And treat a second authorization as a normal step rather than an admission of a bad estimate.

Your invoice has to fit their process, not yours

National account invoices get rejected for administrative reasons far more often than for disputed work.

What they typically require, and it varies by program so ask rather than assume:

What they want	Why it matters to you
Their work order or ticket number on every invoice	Without it the invoice cannot be matched and goes to a queue
The purchase order number they issued	Their accounts payable pays against the purchase order, not against your invoice
The site identifier in their format	Your customer name for the site is not their store number
Equipment identification, often with the serial number	Used to attribute cost to an asset in their own system
Labor and parts separated, sometimes with their codes	Blended lines get queried, and a query costs weeks

The purchase order row is the one that catches service companies used to local work. Locally you create purchase orders with your suppliers. Here your customer creates one with you, and your invoice has to carry it. Both kinds of purchase order now exist in your business and they point in opposite directions.

Payment terms stretch, and the float is yours

The work is done in a day and paid on their cycle, which is longer than the terms you set locally. Net 30 and net 60 are ordinary in this kind of arrangement, and the clock usually starts when the invoice is accepted rather than when it is sent.

Meanwhile you paid the technician at the end of the week and the supplier billed you for the part. Both happened long before the money arrived.

So the operational change is a cash flow change, and it is worth modeling before signing rather than discovering in month three. Two things worth doing:

• Work out the gap in weeks, not in days. Time from work performed to cash received, including the invoice acceptance step. That figure is what you are financing.
• Keep local work in the mix deliberately. Local invoices pay faster and they fund the float on the account work. Service companies that convert entirely to national accounts sometimes find growth and cash pressure arriving together.

Getting invoices accepted first time is the highest-return thing you can do here, because a rejected invoice restarts the whole cycle.

4 kinds of paperwork become a condition of trading

These are gates rather than formalities, and missing one stops tickets arriving.

1. Insurance certificates at the limits they specify. General liability, auto, workers compensation, sometimes with them named as additional insured. Ask for the requirements in writing before you price anything, because the limits may cost more than you expect.
2. Vendor onboarding. Tax forms, banking details, sometimes a supplier portal of its own with its own renewals.
3. Technician requirements. Background checks, food safety awareness, site induction, uniform and identification standards.
4. Coverage commitments. Which sites, which hours, what after-hours response looks like. This is where service companies overcommit, because the map looks smaller than the drive.

Renewals are the part that gets missed. An expired insurance certificate can stop ticket flow with no warning and no conversation, and it is nobody's job until it happens once.

The equipment list stops fitting in one head

A local customer has a kitchen you know. A national account has dozens of sites with equipment you have never seen, and the account is judged on how well you know it.

This is where asset records go from useful to load bearing. When a ticket arrives naming a unit at a store number you have not visited, the questions are immediate: what is it, has it failed before, is it under a manufacturer agreement, and did someone already replace the part they are asking about.

Holding manufacturer, model, serial number, service history, location history and warranty agreements against the equipment rather than against the address is what makes those answerable. Equipment records matter more here than anywhere else, because a group expects one view of every unit it owns.

The reporting side follows from the same records. Programs commonly ask for repeat-failure reporting, spend by site and asset, and recommendations for replacement. If your history lives under customer names, producing that is a weekend. If it lives on the equipment, it is a report.

What to fix before the first ticket arrives

The gap between signing and the first ticket is usually short, and it is the only quiet period you get.

Six things, in order:

1. Name the portal owner and set a checking rhythm. Twice a day at minimum, with a backup person.
2. Get the invoicing requirements in writing. Every field they need, with an example of an accepted invoice.
3. Decide how their tickets reach your job list. Rekeying works at five tickets a month and fails at fifty.
4. Make the NTE visible to technicians. On the job, on the phone, before they start.
5. Start asset records at the first visit to each site. Nameplate photo, serial number, position in the kitchen.
6. Model the cash gap. Weeks from work to cash, and what that means at the volume they are promising.

Moving upmarket also changes who your customer is, and multi-site operators have been reshaping this market for a while. Roopairs has written about how new formats of multi-site operator are opening up customers for service companies, which is the demand side of the same shift.

Planned maintenance is often where these accounts become genuinely profitable rather than merely large, and their piece on selling PM contracts in the field covers how that usually starts.

If you want to see portal work, equipment records and purchase orders sitting in one place before the first ticket lands, Roopairs runs a product tour where you can walk through it with your own sites.

What service companies in the trade say

“Ease of use and on onboarding process is seamless.” — Matt Brunty, President, Restaurant Equipment Diagnostics LLC

Also worth reading

• One Dispatch Board, Five Customer Portals: Keeping Them in Sync
• Purchase Orders in Field Service Software: What Commercial Kitchen Service Companies Actually Need
• Why field service technician productivity starts on the job site

Frequently asked questions

What is a national account in field service?

A customer with sites across many locations, buying service centrally rather than site by site. The work is usually dispatched through a portal or a third-party facilities management company, measured against response and completion targets, and paid centrally on longer terms than local work.

How do national accounts find service companies?

Mostly through facilities management companies, trade association directories and referrals from manufacturers whose equipment you already service. Being an authorized service company for a manufacturer is a common route in, because the manufacturer needs coverage in your area and the account needs somebody approved.

What does NTE mean in field service?

Not to exceed. It is an authorization ceiling rather than an approved price. You may spend up to that figure without asking again, and exceeding it without a fresh authorization is the most common cause of a disputed invoice on this kind of work.

Are national accounts profitable for a small service company?

They can be, and the profit is usually in planned maintenance and in density rather than in the break-fix rate. The risks are concentration, the cash gap and overcommitting on coverage. Model the cash flow and the drive times before agreeing to a site list, because the arithmetic is where these arrangements succeed or hurt.

What insurance do national accounts require?

They specify their own limits and requirements, and those vary enough that guessing is a waste of time. Ask for the certificate requirements in writing during negotiation rather than after signing, and check whether they need to be named as additional insured, because that changes what your broker quotes.

Should I take a national account if I only cover one metro?

Often yes, as long as you commit to the sites you can actually reach. Programs would rather have reliable coverage of twelve sites than unreliable coverage of forty. Declining sites outside your radius during onboarding costs nothing. Missing response targets on them costs the account.