UEP and TDABC share an instinct that most costing methods lack: both take the messy reality of a business and reduce it to one clean, comparable unit. That is where the resemblance ends. The UEP method (unidade de esforço de produção, the production effort unit) measures everything in a single abstract unit of effort and stops at the factory gate. TDABC (time-driven activity-based costing) measures everything in minutes and follows the work all the way to the customer. This page sets the two unit-based methods side by side and shows when each is the right tool.
UEP and TDABC both convert a complex operation into one comparable unit, but they pick different units and reach different distances. UEP measures all factory output in one abstract effort unit, costs only transformation, and is cheap to run once built, which makes it strong for multi-product shop-floor productivity and capacity. It is weak for services and for customer or channel profitability. TDABC, from Kaplan and Anderson, measures everything in minutes using two parameters per resource group, a capacity cost rate and time equations, surfaces unused capacity explicitly, and scales to thousands of transactions. Choose UEP for internal multi-product production control; choose TDABC for customer, order and channel profitability and capacity decisions. The two can coexist: UEP for the factory, TDABC for the customers. ---
The core difference
The cleanest way to see the difference is to ask what unit each method counts in, and how far that unit travels.
UEP
UEP counts in effort. It builds an abstract unit, the UEP, that captures how much transformation work a product demands as it passes through the plant's work centres. The unit is stable and money-independent, so a plant making dozens of different products gets one honest measure of how much it produced and how productively. But UEP deliberately stops at transformation. It excludes raw materials, which are added separately, and it excludes structural and selling overhead entirely. UEP has its roots in the French GP method devised by Georges Perrin and was developed in Brazil by Franz Allora and the production-engineering schools at UFSC and UFRGS.
TDABC
TDABC counts in time. Introduced by Robert Kaplan and Steven Anderson in the Harvard Business Review in November 2004 and set out in their 2007 book, it describes each resource group with just two parameters. The capacity cost rate divides the cost of a resource group by its practical capacity, usually taken at around 80 to 85 per cent of theoretical capacity. Time equations then estimate how many minutes each transaction consumes. Because everything is priced in minutes, TDABC reaches all the way to the customer, costing the order handling, support and service work that UEP never touches, and it shows unused capacity explicitly rather than burying it in a rate.
Side by side
| Dimension | UEP | TDABC |
|---|---|---|
| Origin | France (Perrin's GP method), developed in Brazil by Allora, UFSC and UFRGS | Kaplan and Anderson, HBR November 2004, book 2007 |
| The unit | One abstract effort unit (the UEP) | Time, in minutes |
| What it counts | Transformation effort on the shop floor | Every transaction, including support and service |
| Scope of cost | Transformation only (materials and overhead handled separately or excluded) | All resource cost the time equations reach, to the customer |
| Reaches the customer | No, stops at the factory gate | Yes, costs order, support and service |
| Unused capacity | Not surfaced | Surfaced explicitly |
| Best decisionKey row | Shop-floor productivity, capacity, output mix | Customer, order and channel profitability, capacity |
| Cost to run | Low once built | Moderate, scales to thousands of transactions |
| Handles services | Poorly | Well |
A worked contrast
Take an illustrative multi-product plant, CaP Manufacturing (figures illustrative). UEP would express its entire output in, say, 50,000 UEPs for the period, tell you that line 2 ran at 78 per cent of capacity, and let you compare this month's productivity with last month's on a single effort scale. It is an excellent answer to the question "how much did we produce, and how efficiently". What it cannot do is tell you which customers are worth serving.
TDABC starts from the other end. It sets a capacity cost rate for each resource group, say EUR 0.856 per minute (illustrative), and writes time equations for the work each order demands: so many minutes to pick and pack, so many more if the order is small and fiddly, so many to handle a return or chase a payment. Cost each order to serve this way and a loss-making small-order customer appears that UEP, by design, cannot see. The customer looked acceptable on output and gross margin, but once the minutes of support and service are priced in, it destroys value. That is TDABC's home ground, and it is precisely the ground UEP was never built to cover.
When to choose which
Reach for UEP when you run a multi-product manufacturing plant, your products are physically very different, and your central questions are about output, productivity, capacity utilisation and the relative effort of different products. UEP gives you a single, stable, cheap-to-run measure that physical units cannot, and it does so without dragging in the rest of the business.
Reach for TDABC when your central question is profitability by customer, order or channel, or when you need to see and act on unused capacity. TDABC prices the support and service work that decides whether an account makes money, and it scales to the thousands of transactions that customer-level analysis demands. Most modern cost-to-serve and customer-profitability work runs on TDABC for exactly this reason.
In practice the two are not mutually exclusive. A multi-product manufacturer might run UEP for shop-floor control and output comparison, and a TDABC model for customer and channel profitability. Each answers a question the other does not, so let the factory have its effort unit and let the customer analysis have its minutes.
Frequently asked questions
Is UEP a kind of TDABC?
No. They are different methods with different units and different reach. UEP measures transformation effort in one abstract unit and stops at the factory gate; TDABC measures everything in minutes and reaches the customer. They can be used together, but neither is a version of the other.
Which is more accurate, UEP or TDABC?
It depends on the question. For comparing the output and productivity of different products in a multi-product plant, UEP is both accurate and efficient. For the true cost of serving a particular customer, order or channel, TDABC is far more accurate, because it prices the support and service work UEP excludes.
Does TDABC surface unused capacity and UEP does not?
Yes. TDABC sets its capacity cost rate against practical capacity, usually around 80 to 85 per cent of theoretical, so any gap between what you paid for and what you used appears explicitly as unused capacity. UEP does not surface idle capacity in this way.
Can I use both UEP and TDABC together?
Yes. A common pattern is UEP for production control and output measurement on the shop floor, plus a TDABC model for customer, order and channel profitability. Each answers a question the other does not.
Why does so much customer-profitability work run on TDABC rather than UEP?
Because customer profitability depends on support and service cost that sits outside the factory, and TDABC prices that work in minutes all the way to the customer. UEP costs only transformation, so it cannot see the cost to serve that decides whether an account is profitable.
Go deeper
Want to know which of your customers actually make you money? Start with a Profit Check.
Start a Profit Check