MISC Is Not a Product
30 September 2026
The ticket says three landscape boulders, hand-picked off the shot pile with the 950. Your product list has never heard of them. So the clerk does the only thing the screen allows: she keys the line to MISC, types "boulders x3" in the description field, and types a price. The price comes from a sticky note the salesman left on the counter in June. It says $400. Close enough. The line goes out, the customer pays it, and everyone involved did their job.
Look closer at what just happened, though. Every other line in your billing system prices from somewhere you could point to: a rate sheet, a signed quote. That line priced from a sticky note, and the sticky note is already in the trash.
The line no rule can read
One ticket, one billable event. The principle has a quiet prerequisite: the event has to have a name. A ticket that says 24 tons of 3/4 minus can be checked, because 3/4 minus exists in your system with a rate attached. The weight can be wrong, the rate can be stale, the customer can be miskeyed, and every one of those errors leaves something for a rule to catch, because the line claims to be a specific thing at a specific price.
A MISC line claims nothing. The description is free text, so no rule can read it. The price is hand-typed, so no rate sheet can contradict it. Run every check you own against "boulders x3, $400" and every check comes back clean, because there's nothing to check it against. The line isn't wrong. It's unfalsifiable, which for a billing office is worse.
And notice who set the price. Not you. Whoever was at the keyboard, working from whatever scrap of paper or memory was closest. Pricing by proximity to the keyboard is a lottery, and the stake is your margin.
The code that eats the rate sheet
MISC would be harmless if it stayed rare. It doesn't, because it's the path of least resistance for everything your product list hasn't caught up with. The washout fee you started charging in March. The geotextile fabric the yard resells a few times a month. The second man on a tailgate spread. Winter conditioning on loads that would otherwise freeze to the bed. Each one is a real, recurring billable event that never got a code, so each one routes through MISC, priced fresh every time by whoever keys it.
Fresh pricing means inconsistent pricing, and inconsistent means low, because the direction isn't symmetric. Key the washout fee at $85 when the customer expected $60 and you'll hear about it by Friday. Key it at $60, or $45, or leave it off because the last ticket you saw didn't have one either, and the silence is permanent. The same service billing at three prices in one quarter is a discount program, administered by keystroke order.
There's a slower cost too. Your January price increase reached every coded product, because that's what an increase does: it rewrites rates. MISC lines have no rates to rewrite. Every one of them still bills at whatever number lived on the last sticky note, which means the fastest-growing corner of your invoice is the one corner your pricing decisions can't touch.
And when a customer disputes a MISC line in November, the defense file is empty. The invoice says MISC. The ticket says "misc, see desc." The clerk who keyed it has keyed nine hundred tickets since. That line gets credited, not because it was wrong, but because nobody can say what it was.
flowchart TD
A["Ticket: 3 boulders, no product code"] --> B{"How does it bill?"}
B -- "today" --> C["Keyed to MISC, price typed by hand"]
C --> D["No rule can check it, no report can find it"]
B -- "as a named product with a rate" --> E["Line prices from the rule"]
E --> F["Repeatable, and the next increase reaches it"]
Kill the code or demote it
Here's the claim your office manager will push back on: MISC's share of your keyed lines is a defect count, and the target is zero. Not zero one-offs, zero lines that reach an invoice unpriced by a rule.
The objections are fair. The window can't stall while somebody debates taxonomy with four trucks in line. You can't pre-build a code for every strange thing a quarry sells; someone will eventually buy the old conveyor belting, and no product list saw that coming. An escape valve is the honest design.
Keep the valve, then. Change where it empties. A MISC line should be able to leave the scale window in two seconds, exactly like today. What it shouldn't be able to do is reach an invoice in that condition. Between the window and the invoice, an unnamed line is non-compliant by definition, and it sits in a queue until someone names it and a rule prices it, even if that rule has to be written first. MISC stops being a destination and becomes a waiting room.
Do that and the code starts working for you. Every line that lands in the queue is a vote for a product or a fee your list doesn't have yet. Three washout fees sitting in it the same week are your cue to code the washout fee. Today those votes get cast into free text, where nobody reads them.
Name it once
Your product and service list is reference data, and the odd items, the boulders, the fabric, the second man, belong in it the first time they recur, not never. Their prices are billing rules with effective dates, so the next increase reaches them like everything else. Tickets get digitized at capture, and a line with no product code, or a price no rule supports, gets flagged as non-compliant that day, while the salesman still remembers what he quoted and the sticky note still exists. Invoice totals assemble only from lines that cleared.
That slice is what Termco builds: digitizing the tickets, flagging the ones no rule can price, structuring the billing rules, managing the reference data, assembling the totals. What the boulders cost stays your call. It just gets decided once, in a rule, instead of every time by whoever's closest to the keyboard.
Sizing this one takes a spreadsheet and an hour. Export six months of MISC lines and sort by description. Count how many descriptions repeat, then read the prices down each repeating group. The spread inside each group, highest keying minus lowest, times the times you billed low, is what the catch-all cost you. While you're in there, count the lines where the description wouldn't tell a stranger what was sold. Those are the ones you'll credit if they're ever questioned.
If you'd rather have a second reader on it, send 10-20 sample tickets to hi@termco.ai, ones that billed through MISC especially, and we'll send back what we find within 48 hours.
More from the Termco blog.
September 29, 2026
Ninety Minutes of Free Rock
When the scale system goes down, the trucks keep rolling. What leaves the gate during an outage is the purest revenue leak you have.
Read postSeptember 28, 2026
The Rent Nobody Invoices
Grain storage is rent that accrues from each ticket's date. Billed once at settlement, it shows up months old and easy to knock down at the counter.
Read postSeptember 27, 2026
Payroll Never Loses an Hour
Every hour a tech works lands in payroll, because he checks his stub. Whether it lands on an invoice depends on a ticket nobody audits.
Read post