Home / Insights / Trade effluent & bylaws
Water & Compliance 8 min read Published 26 June 2026

Trade effluent monitoring and municipal bylaws in South Africa

By Frank Guo · Technology & Product Leadership, addanode

TL;DR — If your factory discharges process effluent into the municipal sewer, you sit under a local-authority bylaw and a trade-effluent permit, not a DWS river licence — and you're billed on discharge volume and COD load. Continuous monitoring of pH, COD, conductivity, temperature, flow and fats/oils/grease at the connection point does two jobs: it proves you stayed inside the permit and catches a shock load before it leaves site, and it gives you your own measured volume and load to verify the effluent bill instead of trusting an estimate.

Who this is for

Environmental and utilities managers at South African factories that send process effluent down the municipal sewer rather than to a river — food & beverage plants, abattoirs, breweries, dairies, tanneries, metal-finishing shops and chemical works. If you receive a monthly or quarterly effluent charge from the municipality, and a connection-point permit sits in a drawer somewhere, this is your regime.

Discharge to sewer is a different regime to discharge to a river

This is the distinction that trips sites up, so it's worth being precise. There are two separate legal regimes, and many factories are under both at once:

  • Trade effluent to the municipal sewer is governed by the local authority's industrial-effluent bylaw and your trade-effluent permit. The municipality bills you on discharge volume and COD load, and holds you to limits on pH, COD, conductivity, temperature, fats/oils/grease, settleable and suspended solids and specific substances — all to protect the sewer network and the wastewater works downstream.
  • Effluent to the environment — a river, a stream or land — is governed by the National Water Act and your DWS water-use licence, with final-effluent limits set to protect the receiving water. That regime is covered in our companion article on effluent monitoring and DWS compliance.

A typical site has both: process effluent to the sewer under a trade-effluent permit, plus stormwater or a separate stream to the environment under a DWS licence. The same monitoring platform can measure each discharge point against the right set of limits — but you have to know which rules apply where, because the limits, the formulae and the consequences differ.

The bill is the differentiator. A DWS licence is about compliance only. A trade-effluent permit is about compliance and money — you're charged on volume and load. If you don't measure those yourself, you're accepting someone else's figure for what you owe.

What to measure at the connection point

Your permit and the bylaw are the definitive list, but trade-effluent monitoring at the point your effluent enters the sewer usually covers:

  • pH — the fastest-moving and most-breached parameter; an acid or caustic dump can be out of limit in seconds
  • COD (chemical oxygen demand) — organic load, which drives both your bylaw limit and your bill; critical for food, beverage, dairy and abattoir effluent
  • Conductivity / TDS — dissolved salts, often capped to protect the works' biological process and downstream reuse
  • Temperature — most bylaws cap discharge temperature; hot effluent from CIP, sterilising or process cooling is a common, easily-missed breach
  • Flow / volume — the metered discharge, which is half the bill and usually a permit condition in its own right
  • Fats, oils & grease (FOG) and settleable / suspended solids — slug-prone parameters that block sewers and breach permits fast on food and rendering sites

What a bylaw measures, and what to measure yourself

ParameterWhy it is in the bylawMunicipal methodYour continuous surrogate
VolumeThe multiplier on every strength chargeAssumed % of water intake, or a meterFlow meter at the connection point
CODTreatment cost driver — oxygen demand at the worksGrab sample, laboratoryOnline UV/TOC or conductivity-correlated surrogate, reconciled to lab COD
Suspended solidsSludge handling costGrab sample, laboratoryTurbidity / TSS probe
pHSewer corrosion and process upset; hard limitsGrab sampleContinuous pH probe with alarm
Oil, fat and greaseSewer blockagesGrab sampleTrap-level monitoring; periodic lab
TemperatureLimit in most bylawsSpot checkContinuous probe
Ammonia / nitrogen, phosphorusNutrient load at the worksLaboratoryPeriodic lab, correlated to process events

How the charge is computed — and why measuring it pays

Trade-effluent charges are typically calculated from two things you can measure: the volume discharged and the COD load (concentration multiplied by volume, sometimes with settleable-solids and other terms added). The exact formula is set by each municipality's bylaw and changes over time, but the shape is consistent — volume times load, plus components for the parameters that cost the works most to treat.

The practical problem is that if you don't meter your own discharge, the charge is often built on an assumed volume (a fraction of your water intake) and a periodic grab-sample COD. That estimate can run high. When you measure flow and COD continuously, you can do three things you couldn't before: check whether the billed volume matches reality, check whether the COD figure reflects your actual load rather than a worst-case sample, and — where pre-treatment is genuinely cutting your load — substantiate a lower charge with your own data. On a high-COD site the difference between an assumed and a measured load is real money every month.

Both terms of the charge are things you could have measured A trade-effluent charge is built from a volume and a COD load. Unmetered, both arrive as estimates — a fraction of intake for the volume and a grab sample for the load — and an estimate has no reason to be conservative. Measured, each term becomes checkable, and a genuine reduction in load becomes something that can be substantiated rather than asserted. If you do not meter your own discharge If you meter flow and COD continuously The volume term of the charge An assumption, often a fraction of your water intake Your own metered discharge volume The load term A periodic grab sample, which can easily be a worst case The load as it actually ran, hour by hour What you are able to check Nothing. The invoice is the only number in the room Whether the billed volume and the billed load match reality What pre-treatment earns you Nothing you can demonstrate A lower charge you can substantiate on your own data What a disagreement rests on The municipality's figure Two records, and the difference between them On a high-COD site The gap between assumed and measured is invisible It is real money, every month
Both terms of the charge are measurable Volume and COD load: unmetered they are estimates, metered they are checkable. The volume term of the charge Not metered An assumption, often a fraction of your water intake Metered Your own metered discharge volume The load term Not metered A periodic grab sample, which can easily be a worst case Metered The load as it actually ran, hour by hour What you are able to check Not metered Nothing. The invoice is the only number in the room Metered Whether the billed volume and the billed load match reality What pre-treatment earns you Not metered Nothing you can demonstrate Metered A lower charge you can substantiate on your own data What a disagreement rests on Not metered The municipality's figure Metered Two records, and the difference between them On a high-COD site Not metered The gap between assumed and measured is invisible Metered It is real money, every month
Both terms of the charge described above, with and without your own instrument. An estimate has no particular reason to be conservative — and on a high-COD site the gap between an assumed load and a measured one is money every month.

Shock loads, balancing and diversion

The breaches that hurt are rarely a slow drift; they're shocks. An acid or caustic dump from a process tank, a CIP cycle that sends hot caustic to drain, a grease slug from a fryer or rendering line — each can blow through a pH, temperature or FOG limit in minutes and be gone before the next grab-sample. Continuous monitoring with alerts is aimed squarely at these. The point of catching a shock at the connection point is that you still have options: divert to a balancing tank, hold and bleed it out slowly, correct dosing, or stop the offending process before the slug leaves site and becomes the municipality's problem — and your penalty.

Proving pre-treatment actually works

Most sites under a trade-effluent permit run some pre-treatment — neutralisation to bring pH into band, a balancing tank to flatten peaks, dissolved-air flotation (DAF) to strip FOG and solids, grease traps on kitchen and process lines. The trouble is that pre-treatment fails quietly: a dosing pump drifts, a DAF skimmer clogs, a grease trap fills. Before/after sensing across these units turns performance into a number — you see the load going in and the load coming out, so you know whether the unit is doing its job, you get warned before a failing unit causes a breach, and you size, dose and maintain on data instead of running blind between lab samples. It's also the evidence behind a lower-load bill: if your DAF is removing COD, the measured discharge proves it.

Penalties, disconnection and the value of a continuous record

The consequences of getting trade effluent wrong escalate. A breach typically starts with a penalty tariff or a surcharge; repeated or serious breaches can lead to a formal notice, prosecution under the bylaw, and ultimately disconnection of your trade-effluent connection — which for a wet process means stopping production. A continuous, time-stamped record is your defence at every step: it shows you stayed within permit, it shows you acted when something moved, and it lets you contest a charge or an allegation with your own data rather than the municipality's single sample.

Why load-shedding resilience matters here too

A gap in your monitoring record is not a neutral absence — it's exactly the moment a regulator or a billing dispute asks "what was happening here?" If your monitoring goes dark every time the grid does, your record is full of holes, and shock loads have a habit of arriving during outages when balancing pumps and dosing may also be down. Edge buffering — logging locally and syncing when power and connectivity return — keeps the discharge record continuous through load shedding, which is why we treat it as a permit requirement on South African sites, not a nice-to-have.

A necessary caveat

Trade-effluent bylaws, charging formulae and permit limits differ from one municipality to the next and change over time. Treat everything here as orientation, not a compliance instruction. Confirm the parameters, limits and the exact charging formula against your own trade-effluent permit, the applicable local industrial-effluent bylaw and your advisers before you act on them.

Continuous connection-point monitoring is the backbone of our trade-effluent monitoring solution, sits alongside our water quality & DWS compliance work for sites that also discharge to the environment, and runs on the addaNet platform so effluent sits next to your flow, energy and production data.

Frequently asked questions

What's the difference between a trade-effluent permit and a DWS licence?

A trade-effluent permit governs discharge into the municipal sewer under the local authority's bylaw — you're billed on volume and COD load and held to limits that protect the sewer and works. A DWS water-use licence governs discharge to the environment under the National Water Act. Many sites have both, and each discharge point is measured against its own regime.

Can monitoring really help me check my effluent bill?

Yes. Trade-effluent charges are typically calculated from discharge volume and COD load. If you don't measure those yourself, you can only accept the municipality's figure — often an assumed volume and a periodic grab-sample. Your own continuous flow and COD give you an independent basis to verify the charge, and where pre-treatment is reducing your load, to substantiate a lower one.

Which parameters get factories into trouble most often?

pH (acid and caustic dumps), COD (organic shock loads), temperature (hot CIP and process water) and fats/oils/grease are the usual culprits. They move fast and breach quietly between the municipality's own samples, which is exactly what continuous monitoring with alerts is built to catch.

We already have pre-treatment — what does monitoring add?

Proof that it's working, and warning when it isn't. Before/after sensing across neutralisation, balancing, DAF and grease traps shows real performance, flags a failing unit before it causes a breach, and lets you dose and maintain on data rather than running blind between lab samples. It's also the evidence behind a lower-load bill.

Will the monitoring keep recording during load shedding?

Yes, when it's designed for it. Edge devices buffer readings locally and sync when power and connectivity return, so your discharge record stays continuous through outages — important both for compliance evidence and for catching a shock load that happens to arrive during an outage.

Prove your discharge — and check your bill.

Send us your trade-effluent permit conditions and a recent effluent invoice. We'll scope the connection-point monitoring to match your limits, set the alerts that keep you compliant, and give you the data to verify what you're charged.

Book a Discovery Call See the solution →

Related reading

Solution

Trade Effluent Monitoring

Connection-point monitoring and bill verification.
7 min read

Effluent monitoring & DWS compliance

The discharge-to-environment regime.
Insight

Water-quality sensors explained

pH, COD, conductivity and what they measure.

Primary sources