What your field buys at the counter, and when you find out

Thursday, 6:40 in the morning. Your foreman is two couplings short of finishing a riser the inspector is coming to look at Friday.

He stops at the supply house on the way in, puts $214 on the company account, signs a will-call ticket, and is on the job by 7:15. The inspection passes. Nobody did anything wrong. That is the correct decision and you would be furious if he made a different one.

Six weeks later a statement arrives with forty-one of those tickets on it. None of them says which job.

The arithmetic, because it is not what people assume

Call it eleven counter stops a week across four crews, at an average of $240. That is $137,000 a year, bought by people with no price list, no quote, and no approval, and landed on your cost report in a lump nobody can take apart.

It is never the $200,000 equipment order that breaks a material budget. That one gets quoted three ways, argued about, and watched. It is the spend that sits under every threshold anybody looks at, which is exactly why nobody looks at it.

And the counter price is not your price. The sheet number you negotiated in January applies to orders. The counter applies whatever is on the screen that morning, and on commodity material that is routinely well above the number in your estimate.

Why “stop doing it” is the wrong answer

The obvious policy is: no purchase without a PO. It fails in week two, every time.

A foreman who cannot buy a $90 part waits for the office. The office is in a meeting. The crew stands around for two hours, which at six people costs you more than the part did and loses a day on the schedule you cannot buy back. Then the foreman buys it anyway and does not tell you, because telling you now means explaining why.

So the convenience is real and worth paying for. What you are trying to stop is not the purchase. It is the unknown — a cost with no job, no price check, and no date you can see it on.

The four things a counter purchase destroys

Attribution. The ticket names the branch and the person, not the job. By the time the statement arrives, the only record of where that material went is in somebody’s memory, and he has been on three jobs since.

Price. No quote, no price lock, no comparison. You find out what you paid when you are no longer in a position to do anything about it.

Timing. A card charge posts in days, a statement in weeks, and it reaches your job-cost report after the month it belongs to has closed. Your PM makes a decision in week four on a number that is missing six weeks of counter buying.

Authority. Anybody with a badge and a branch relationship can commit the company. Not maliciously — the commitment is just invisible until it is a statement.

The habit that costs nothing

One line, the day it happens. Who bought it, what it was, which job, roughly what it cost.

That is it. Not a form, not an approval, not an app a foreman has to learn. The daily log is the one document in your company that is written the day the thing happened, by somebody who was there, and that is worth more than accuracy.

In SubMark the daily log has a materials section, and a material row carries five things: the material typed in free text, a quantity, a unit, an action — delivered, used, returned or damaged — and a note. There is no picker and no material list to maintain, which is the right trade for something a foreman fills out at the end of a day. A counter pickup is a “delivered” row with a note saying where it came from. Be clear-eyed about what that is and is not: it records a quantity, not a dollar figure, and it is not a purchase record. What it is, is a dated line written by the person who knows the answer, sitting on the job it belongs to. Six weeks later that line is the difference between coding the statement and guessing at it. Our foreman daily log template article covers the rest of what a log has to carry to be worth anything in a dispute.

Field users in SubMark are free and unlimited, so this costs you nothing per foreman.

Three things to ask your supply house for

None of this is software, and all of it works.

1. A required job or PO field on the account. Most branches can set the account so a counter sale will not ring up without something typed in that box. Ask for it. The ticket then names the job, in the field’s own handwriting, at the moment they know the answer.
2. A weekly statement grouped by that field, instead of a monthly one grouped by nothing. A week of tickets is reconcilable on a Friday morning. A month is not, which is why nobody does it.
3. A name on the account who is allowed to buy, and a short list of who is not. Branches will enforce it if you give it to them in writing. It is the only spend authority you will ever get on a counter account.

The threshold, written down once

Pick the number and tell everybody.

• Under it: counter purchase is fine, and the only obligation is the job on the ticket and the line on the log.
• Over it: an order gets written before anyone gets in a truck.

The number matters less than the fact that it exists. Below $500 in a shop your size, the PM time to administer a PO exceeds anything the PO could save. Above $2,000, the absence of an order is the reason your material line is wrong. Somewhere in between is yours.

In SubMark: what it does, and the limit on the page

We say this one on the purchase orders page itself, so there is no reason to be coy about it here: “A counter purchase has no order. A foreman’s will-call ticket at the supply house is a real cost with no PO behind it, and SubMark has no mobile capture for the ticket. It reaches the job only if the charge is coded to the job in QuickBooks and comes back with the cost pull.”

There is no will-call capture in SubMark, on a phone or anywhere else. What there is:

The quantities-only order, which is the nearest thing. Pricing is a switch on each purchase order. Turn it off and the order is quantities only — the list shows “Qty only” where the total would be. That is the order you hand a foreman to pick up material with, without putting your material margin in front of the gate guard. A line still carries its material type, description, quantity and unit, and each material type carries the unit it is normally counted in, so the quantity means the same thing to you and to the counter.

Used deliberately, that is a will-call ticket you wrote in advance. The foreman is not asking the counter to decide anything. He is handing over a numbered document that names the job.

And the honest catch on it: a quantities-only order does not go to QuickBooks. The push needs prices on the order — which is consistent enough, since a purchase order carrying no dollar figure is not something an accounting system can book — but it means the version your foreman carries is not a version your bookkeeper ever sees. If you want both, the order carries prices and you hand the field the PDF with the understanding that it has numbers on it.

The invoices inbox, if the branch bills you. When the supply house sends an invoice rather than putting the charge on a card, that PDF can go in the optional invoices inbox, tagged to the job and the vendor, with an optional link to an order. That module is off until a company switches it on in settings, so a new trial does not have it. What to do with that bill once it is in there — and every way a supplier invoice goes wrong before it gets there — is matching supplier invoices to purchase orders.

The chain that gets a card charge onto a job

This is the part worth reading slowly, because it is three links and all three are manual.

A foreman’s $214 at the counter goes on a card or an account. It becomes a transaction in QuickBooks — a bill, or a check or credit-card purchase. For that money to appear on the job in SubMark, every one of these has to be true.

1. QuickBooks is connected and the hourly cost pull is switched on. Connecting QuickBooks alone never starts it; the pull is its own setting, and with it on, bills and purchases come across hourly. You can also bring them in on demand.
2. Somebody set the Customer/Job on that expense line in QuickBooks. Line level, not transaction level — one card charge can carry six lines on four jobs, and SubMark reads them line by line. Only expense lines carry cost; tax and linked-transaction lines are skipped.
3. The SubMark job is linked to that QuickBooks customer/job. One link per project, set once.

Break any one of the three and the charge exists in your accounting and nowhere on your job. And there is no way to re-point it from inside SubMark — that is deliberate. QuickBooks is the system of entry for costs, so an unassigned line means the bookkeeper job-codes it in QuickBooks and the next pull picks it up. The one kindness in the design: if you link a project after the lines were already pulled, the orphaned lines attach themselves on the next pull without the transaction having to change in QuickBooks at all.

Two more details that will matter the first time you read the report:

• The cost category is the QuickBooks account or item name, verbatim. If your chart of accounts calls it “Materials - Jobs,” that is what the row says. There are no cost codes in SubMark: there is no library, no import and no mapping. Material belongs to the job, and the category you see is the one your bookkeeper chose. Our article on cost code structure for subs is about the accounting side of that decision, which is where it lives.
• Card credits come through as negatives. A return at the counter that goes back on the card reduces the job’s cost on the next pull, which is the behavior you want and worth knowing before you see a minus sign.

Where it lands on the report

Job costing in SubMark breaks live cost out by where it came from, and counter buying lands in one of those and skips the one you would expect.

It shows up as “From QuickBooks (bills & purchases),” once the chain above holds. It does not show up under “Materials (committed POs),” because there was never an order, so the committed figure tells you nothing about counter spend. And the job’s cost total, its over-budget alert and its margin alert include QuickBooks costs, so a counter purchase does reach them — the month after it happened.

Which is the whole problem restated in one sentence: the spend with no order behind it is the spend that arrives late and cannot be forecast. Everything above is about shortening that lag, not eliminating it.

The week-one version

If you do nothing else:

1. Call the branch and ask for the required job field on the account. Fifteen minutes, free, and it fixes attribution at the source.
2. Tell your foremen the threshold, in one sentence, with a number in it.
3. Add the counter pickup to the daily log as a delivered material line with a note. It is five fields, none of them a dropdown you have to set up first, and it is the only dated record you will have.
4. Write quantities-only orders for anything that was going to be a counter stop anyway. Picking up is fine. Picking up without a document is what costs you.

A sub who knows what the field bought within a week instead of within a quarter is not a tidier company. It is a company whose PM can still do something about it.

See how purchase orders work in SubMark, what job costing shows, how SubMark protects margin, or what it costs.