What the Pretoria Contractor Needed
This client was a micro contractor based in Pretoria, handling small jobs for private customers and a few repeat commercial sites. The owner was doing too much by hand: supplier invoices were filed in different places, payments were matched late, and job costs were only clear after the month had already closed. That made it hard to see which jobs were paying, which suppliers were overdue, and where cash was going.
The brief was straight forward. Keep the books current, separate each job properly, and make payroll for the small site team easier to run. The business needed a system that could be maintained by a lean team, with no heavy software admin and no extra layers of reporting that nobody would read.
- Client type: micro contractor
- Town: Pretoria
- Problem areas: supplier tracking, job records, payroll admin
- Goal: simpler monthly control with fewer errors
Constraints We Had To Work Around
The contractor worked from a modest base and spent most days on site, so there was no time for long bookkeeping catch ups. Documents arrived in bits and pieces, often as photos on a phone, and some supplier statements only came through after payment reminders. Cashflow also moved in cycles, which meant wages, materials and fuel had to be watched closely or the month could get tight very quickly.
Load-shedding was another factor. Some records were kept on a shared laptop and the team needed a setup that would still work when power was out for a few hours. We also had to keep the process simple enough for a small office routine, while still giving the owner enough detail to see job-by-job performance. No fancy extras, just records that could actually be used.
- Irregular document flow from site work
- Mixed supplier paperwork and late statements
- Cashflow swings during busy and quiet weeks
- Need for a low-maintenance process during load-shedding
What We Put In Place
We set up a cleaner bookkeeping structure around the way the contractor already operated. Each supplier was assigned consistent naming, invoice capture rules were tightened, and job-based coding was introduced so costs could be linked back to the right project. That gave the owner a clearer view of labour, materials, fuel and sundries for every job rather than one lump figure at month end.
On the payroll side, we built a small-team process that handled weekly wages, leave tracking and termination pay when needed. Payslip processing was standardised and the owner received clear payroll reports before wages were released. We also put in a simple reminder routine for document submission, which reduced the back-and-forth that used to slow things down.
- Job-based bookkeeping codes for each site and contract
- Monthly supplier reconciliation and overdue follow-up
- Weekly wage payroll for site staff
- Payslip processing and payroll reporting
- Leave tracking and new employee setup when staff changed
Timeline And Working Rhythm
The initial clean-up took 3 weeks. Week one focused on document sorting, supplier list cleanup and the first pass through outstanding entries. Week two was used for job coding, payroll structure and fixing the payment categories that had caused confusion. Week three covered review, report formatting and handover of the monthly process so the client could keep it going without constant support.
After that, the working rhythm settled into a monthly cycle with weekly wage processing where needed. We kept the admin points short and predictable, because a contractor does not have time for long calls and back and forth messages. One or two practical checks each week worked far better than a full catch up at month end and it kept the books from drifting.
- Setup period: 3 weeks
- Monthly bookkeeping close: once per month
- Payroll cycle: weekly for wages, monthly for reporting
- Review points: short scheduled check-ins
Results For The Owner
Once the new process was in place, the owner could see which jobs were actually earning and which ones were being squeezed by material or supplier costs. Supplier balances were easier to manage, which reduced the surprise follow ups at month end. The payroll side also became steadier, with clearer leave balances and fewer corrections after wages were issued.
The biggest gain was time. The owner spent less energy chasing paperwork and more time on site and quoting for new work. There was also better confidence when speaking to suppliers, because the numbers were current and the records matched what had really happened on the ground. That matters in a small business, where one missed invoice can throw off the whole month.
- Cleaner supplier tracking
- Better visibility on job profitability
- Fewer payroll corrections
- Less time spent on admin and follow-up
What We Would Do Again
If we were starting the same project again, we would still begin with job coding and supplier discipline before touching anything else. For a micro contractor, those two steps give the fastest improvement because they affect both cashflow and decision making. We would also keep the reporting format short, practical and easy to read on a phone, since that is how many small business owners check things during the day.
For contractors in Pretoria and elsewhere, the lesson is simple. If the paperwork is messy, the margin gets hidden. A tidy monthly process gives the owner a better grip on what each job is doing and helps the business avoid expensive mistakes that only show up later.
- Start with job-based records, not end-of-month summaries
- Keep supplier follow-up part of the monthly routine
- Use short reports the owner will actually read
- Build a process that still works during power cuts and busy site weeks
Key facts
| Client type | Micro contractor |
|---|---|
| Town | Pretoria |
| Project duration | 3 weeks |
| Core focus | Supplier tracking and job-based record keeping |
| Payroll scope | Weekly wages, leave tracking, payslip processing |
| Outcome | Clearer costs, cleaner records and less admin pressure |
