What is monetary unit sampling?
On a typical receivables balance of €40M with 12,000 line items, the engagement team needs a sampling method that automatically concentrates testing on high-value items without requiring manual stratification. That's the problem monetary unit sampling (MUS) solves, and it's the reason most firms default to MUS for substantive testing of overstatement assertions.
MUS treats each individual monetary unit (each euro or dollar) in the population as a separate sampling unit. The auditor calculates a sampling interval by dividing the population's recorded value by the sample size, then selects every nth monetary unit using systematic selection with a random start. The physical item (invoice, journal entry, or balance) that contains the selected monetary unit becomes the item tested. A line item worth ten times as much contains ten times as many sampling units and therefore has ten times the probability of selection. This built-in weighting eliminates the need for separate stratification.
Evaluation uses Poisson-based probability tables. When errors are found, the auditor calculates a tainting percentage (the proportion of the item that is misstated) and uses it to compute an upper error limit. This projected misstatement is compared against tolerable misstatement. MUS is designed for overstatement testing only. Because selection is proportional to recorded value, items that are understated or missing from the population receive little or no coverage.
Key Points
- Each monetary unit has equal selection probability, so larger items receive proportionally greater coverage without separate stratification.
- MUS is structurally unsuitable for completeness (understatement) assertions because selection is proportional to recorded value.
- ISA 530 .A22 requires two comparisons: projected misstatement against tolerable misstatement, and an assessment of whether the nature and cause of errors suggests systematic issues.
- A clean sample reduces the upper error limit but doesn't eliminate sampling risk. The confidence level defines the residual probability that errors exist but were not selected.
Why it matters in practice
In our experience, the most common practical error is teams performing only one comparison (projected misstatement against tolerable misstatement) while omitting the second comparison to expected misstatement. ISA 530 .A22 requires the auditor to also consider whether the nature and cause of identified misstatements suggest the actual misstatement in the population may exceed expected misstatement. If it does, the sample design assumptions were wrong and the conclusion can't stand.
What actually happens on a lot of engagements is that teams just roll it forward: they copy last year's MUS parameters, update the population total, and move on. That works when the risk profile hasn't changed. It doesn't work when an acquisition or a change in credit terms has altered the error rate. I think this is where most MUS failures originate. The method itself is fine. The inputs are stale.
A second recurring issue is applying MUS to completeness testing. MUS selects proportional to recorded value, so items missing from the ledger or recorded at zero have no chance of selection. If you're testing the completeness assertion (unrecorded liabilities, revenue cut-off understatements), use variables sampling or a non-statistical approach that gives every physical item, not every monetary unit, an equal chance of selection. Remember: PIOOMA (put it on one more audit). If the sampling method can't detect the misstatement type you're worried about, pick a different method.
Key standard references
- ISA 530.5 –15 sets out core requirements for audit sampling, covering design, selection, evaluation, and documentation.
- ISA 530 .A10–A15 provides application guidance on statistical and non-statistical approaches, including MUS as a probability-proportional-to-size (PPS) method.
- ISA 530 .A22 requires the auditor to evaluate the nature and cause of misstatements and compare results against both tolerable and expected misstatement.
- ISA 530.14 addresses extending the sample or performing alternative procedures when results are inconclusive.
Related terms
Related tools
Related reading
Frequently asked questions
Why does MUS automatically weight toward high-value items?
Because each monetary unit is a separate sampling unit. A €500K invoice contains 500,000 sampling units while a €10K invoice contains only 10,000. The larger invoice has 50 times the probability of containing a selected monetary unit, so high-value items are automatically covered without stratification.
Can MUS be used for completeness testing?
MUS is structurally unsuitable for completeness (understatement) testing. It selects proportional to recorded value, giving low-value and zero-value items minimal coverage. If items are missing or understated, MUS will not catch them. Use variables sampling or a non-statistical approach instead.
What happens when a single MUS error pushes the result above tolerable misstatement?
This is common and counterintuitive. Even one error with moderate tainting can push the upper error limit above tolerable misstatement when the tolerance is tight relative to population size. The correct response is to extend the sample, request management adjustment, or both.