---
title: "Know your margin before the job ends: job costing that sticks"
description: "Job costing without enterprise software: tag every cost to its job at capture, include the payouts and fees QuickBooks misses, and read margin while you can act."
url: "/blog/job-costing-without-enterprise-software/"
date: "2026-07-17"
author: "Valeria Vahorovska"
tags: ["Guides","Cash Flow"]
---

# Know your margin before the job ends: job costing that sticks

Job costing without enterprise software comes down to three habits: a code for every job the day it's quoted, every cost captured against that code *at the moment it happens*, and the forgotten costs — payout splits, card fees, channel spend — included from day one. Do that, and margin per job stops being a post-mortem and becomes a dial you read while the job is still running.

The alternative is the pattern every trades community describes: [QuickBooks](/docs/integrations/how-does-the-quickbooks-connection-work-and-what-syncs/) holding the money but not the job context, margins *"worked out by hand in a spreadsheet every week"* from *"rounded ballpark numbers, not itemized,"* and the owner's real question — *which jobs actually make money?* — answered only after the job ships, when the answer can't change anything. Meanwhile the exterior job at 9% margin looks exactly like the repaint at 27% until the money's already spent.

## Why job-level margin stays invisible

**The books know amounts, not jobs.** Your accounting sees £4,300 to the timber merchant. Which job the timber was for lives in someone's head, then in a spreadsheet, then nowhere. Every cost needs a human to tag it after the fact — and after-the-fact tagging is the first casualty of a busy week.

**The costs that decide margin are the ones nobody tags.** Materials get remembered. What gets missed: the three-way [crew/PM/sales split](/home-services/), the card fee on the customer's payment, the fuel, the ad spend that won the lead. Jobs that look profitable on materials-and-labour quietly aren't once the real cost stack lands.

**The timing kills the value.** A margin number after the job closes is an autopsy. The same number in week two — while you can still re-scope, re-price the change order, or swap the crew mix — is management. *"Know your margin before the job is done, not after"* isn't a slogan; it's the entire difference between job costing that pays for itself and job costing that's homework.

## The three habits (and the one test for tooling)

**1. A code per job, from the quote.** Job #4821 exists before any money moves, so there's never a cost with nowhere to go. Estimate lives against the code too — margin is always *actual vs quoted*, which is how pricing improves.

**2. Capture at the source.** The materials receipt is [scanned at the counter](/blog/receipt-hell-expense-system/) and tagged to the job; crew hours logged the day they're worked; the customer's [stage payment](/blog/deposits-and-stage-payments/) lands against the job it funds. The rule that makes it stick is the one a contractor community coined: *the truck isn't loaded until the receipt is scanned.*

**3. Count the whole cost stack.** Splits, payment fees, channel spend. This is also how you learn *profit by channel* — which lead source produces the 27% jobs and which produces the 9% ones that drain the crew. The channel answer routinely surprises more than the job answer.

The tooling test is a single question: **does tagging take seconds, automatically, at the moment of the transaction?** If job costing depends on someone's evening discipline, it will die — in QuickBooks, in a spreadsheet, or in enterprise software, equally.

## Where Fynex changes the mechanics

Fynex passes that test structurally, because it sits on the money itself. The customer's payment arrives against its job. The crew, PM and salesperson are [paid their split](/docs/split-payments/how-do-split-payments-work/) **on job close, by rule** — so the biggest cost books itself the moment it exists. Fees are attributed to the payment that caused them; scanned receipts land tagged; everything [reconciles to QuickBooks](/features/invoicing/) behind the flow, which keeps your accountant's world intact while the job-level view lives where you can see it.

The result reads like the dashboard the spreadsheet was always trying to be: margin by job, channel and crew, live — the £8,400 repaint showing its 27%, the Maple St exterior flagging its 9% while the job still has weeks to run, and [the cash forecast](/features/cash/) already knowing which stage payments land next week.

Enterprise job costing failed the trades not because the maths is hard but because the data entry was a second job. Put the tagging where the money moves and the maths runs itself — and "which jobs actually make money" becomes something you check on Tuesday, not something you discover in December.
