Net Guarantees in Three Countries: A Blended Gross-Up That Cost 22% More Than Accrued
Caldera Pharma granted retention awards of '€20,000 net' to 12 key employees in Japan, Brazil and France, and gross awards to 48 others. Payroll applied a single blended gross-up factor of 1.45 to all 12 and paid them in the July off-cycle. Six weeks later the picture is messy. Brazil cost 22% more than accrued, because the award was treated as indemnity for accrual purposes but as salary for withholding, pulling it into the progressive monthly table and the INSS base and adding FGTS and a thirteenth-salary effect. The French payment attracted forfait social on top of CSG and CRDS. The Japanese payments were converted at the budget rate of ¥158/€ rather than the payment-date rate, and Japan withholds through progressive tables with a reconstruction surtax. Three employees were paid twice because the award was also picked up by an earnings element in the regular run. Finance is asking who bears the 22% overrun, and Legal confirms the contracts say nothing about tax.
1. Explain why the blended factor failed and set out a defensible gross-up methodology.
Read the worked answer
A net guarantee means the employer bears the tax, so the gross must satisfy G minus tax(G) equals N. A single factor can only be right for one marginal rate, and the twelve employees span three progressive systems with different bases, ceilings and surtaxes. The 1.45 factor was a forecast, and forecasts do not satisfy an equation.
A defensible method has three parts.
Define the base. 'Net' must be defined in the contract. Net of income tax only? Net of income tax and employee social security? Net of everything including any local surtax? The Japanese reconstruction surtax and French CSG/CRDS sit in different places in that answer, and the absence of a definition is the root cause here.
Iterate, do not multiply. Compute tax at an assumed gross, compare the resulting net to the guaranteed amount, adjust the gross by (N minus net) divided by (1 minus the marginal rate), and repeat until convergence. This handles the tax-on-gross-up loop: the gross-up is itself taxable, so a one-pass calculation always under-provides. Where the gross crosses a band boundary, iterate rather than using one marginal rate.
Apply local quirks explicitly. In Brazil, establish whether the award is salarial or indemnity before accruing, because that single classification drives the progressive table, the INSS base, the 8% FGTS deposit and the thirteenth-salary effect. In France, confirm whether forfait social applies at all before accruing it. In Japan, use the payment-date rate with a documented source, not the budget rate.
Retain the workings per employee; the defensibility of a gross-up is its audit trail, not its factor.
2. Who should bear the 22% overrun, and how do you handle the contractual and employee-relations exposure?
Read the worked answer
The employee does not bear it. The promise was €20,000 net, and clawing back tax from employees who received exactly what they were promised would be both legally fragile and reputationally damaging across a retention population you are trying to keep.
Accounting treatment. The 1.45 factor was an estimate. The difference between the estimate and the actual is a correction of an estimate, recognised in the period it becomes known, not an employee recovery and not a reclassification of the award. Segment it: how much is Brazil classification, how much is France forfait social, how much is FX, how much is pure rate iteration. Only after that split can Finance see whether it is a one-off or a recurring estimating error.
Contractual exposure. Legal says the contracts are silent on tax, which cuts both ways: the employee cannot claim more than €20,000 net, but the employer also cannot easily argue that later awards are gross. Check each local contract for a net-pay clause - a contractual net entitlement is difficult to change unilaterally and may require consultation. For future awards, move to a stated gross value with a tax-neutral communication, or keep net but attach a defined gross-up policy as an appendix.
Employee relations. Tell each affected employee the gross value and the tax withheld, in local language, before the payslip lands unexplained. Silence is what converts a cost problem into a trust problem, particularly with a retention cohort. Three employees paid twice should be contacted individually with a recovery plan and an agreed schedule rather than a unilateral deduction, which in several jurisdictions is unlawful without consent.
3. What controls would you put in place to prevent duplicate payments and off-cycle leakage?
Read the worked answer
Duplicate payment is a process design failure and is preventable with cheap controls.
A payment instruction register. Every award gets a unique identifier, a gross and net value, an approval, a scheduled cycle and a status. Nothing is paid that is not on the register, and nothing is paid twice from the same identifier.
Lock the earnings element. The retention award element should be configured to accept a single payment per employee per award ID, with a system-level block on a second entry. Configuration beats training.
Pre-run duplicate detection. A report that flags the same employee, element, amount and date appearing in more than one cycle, run and reviewed before every off-cycle and every regular run. The July failure is exactly what this report catches.
Separation of off-cycle and regular. Off-cycle requests require dual approval, a reference to the award register, and reconciliation back to that register before the next close. If the award was loaded as a pending element in the regular run and also paid off-cycle, the reconciliation shows it in days rather than months.
One owner for the gross-up. Tax signs off the methodology, the provider calculates, payroll executes - but a single named person reconciles actual cost against the accrual within five working days of payment. The 22% surfaced six weeks late, which is the most expensive part of the whole episode: by then the FX rate had moved and the accrual was closed.