Shadow Payroll Breakdown: Trailing Equity, Mid-Month Treaty Thresholds and an Unexplained $114,000
Northwind Software runs US home-country payroll and host-country shadow payrolls for 34 assignees in Germany (21) and Singapore (13). The shadow payroll is prepared by the mobility team in a spreadsheet and keyed into host providers' portals; tax equalisation is administered by an external tax firm that bills annually. Symptoms surfaced at the Q2 review. Equity vested for nine assignees during their German assignment, but no trailing income was reported in the German shadow payroll. Four Singapore assignees crossed 183 days mid-month and the provider applied a full-month exemption rather than a split. Hypothetical tax for US assignees still uses last year's state rates after a mid-year change. The shadow payroll balance sheet shows $412,000 accrued against $298,000 actually remitted, with the $114,000 difference unexplained. One assignee was deployed on six weeks' notice without a certificate of coverage under the US–Germany totalization agreement, so German social security is being withheld on top of US FICA.
1. Diagnose where this shadow payroll design fails and what risk each failure creates.
Read the worked answer
A shadow payroll exists to report and pay host-country income tax and social security on remuneration attributable to work performed in the host location, in step with the home payroll, and to give the employer a way to see whether what it accrued for assignee tax equals what it remitted. This design fails at each of those three jobs.
Trailing equity (Germany). The spreadsheet is keyed from the current month's cash payroll. Equity income is not cash payroll, so it never enters. Yet a vest during the assignment is generally host-sourced to the extent of workdays in the host country during the vesting period. The result is under-withheld German wage tax on which the employer is liable, plus penalty exposure and a tax equalisation settlement that silently shifts cost to the company.
Mid-month day count (Singapore). The 183-day position is not a switch that flips on the first of the month, and any exemption depends on the applicable year-of-assessment rules and residence status. Applying a full-month exemption to a split month is wrong on its face and produces under-withholding.
Stale hypothetical tax. Employees get a settlement surprise, and the company's cost estimate is wrong in the direction that matters for forecasting.
The $114,000. The number itself is less alarming than the fact nobody can explain it. Timing, FX and unremitted liability all hide in the same balance, which means you cannot distinguish tax risk from accounting noise - that is the most serious finding.
2. Prioritise the remediation. What do you fix first, and by what criteria?
Read the worked answer
Rank by four criteria: is a statutory deadline already breached or about to be; is the employer the liable party; how large and how irreversible is the exposure; and can the error still be corrected without a disclosure.
First - German equity income. Already breached and employer-liable. Do not merely fix prospectively; quantify per assignee for each vest and take local advice on voluntary correction versus waiting for assessment, because the penalty gradient differs sharply between the two. Pull the equity plan administrator's vest report and payroll workday calendars to allocate.
Second - Singapore day counts. Still correctable if caught in the current or immediately following period. Recompute days for all 13 assignees, correct the current month, and review year-to-date. Singapore penalties for late or incorrect filing are administrative and small if corrected early, which is exactly why this is cheap now and expensive in six months.
Third - the balance sheet reconciliation. Build a country-by-country, period-by-period bridge from accrual to remittance using authority receipts and provider reports. Until that reconciles, no tax equalisation settlement should be issued, because a settlement built on an unreconciled balance will be wrong and will be disputed by employees.
Fourth - hypothetical tax. Recalculate using current rates before the Q3 settlement cycle; this is a cost-forecast issue, not a compliance one.
Fifth - the missing certificate of coverage. Retrospective relief under the totalization agreement is usually obtainable, and the refund of German contributions plus US FICA offset is recoverable; the real fix is a deployment trigger, since six weeks' notice is entirely normal and should not break a process.
3. Design the permanent control that would have caught the trailing income omission, and say who owns it.
Read the worked answer
The omission is a data-flow control failure, not a competence failure, so the fix belongs in the data flow.
A single mobility data feed. The equity plan administrator's monthly vest and exercise report, the assignment start/end dates, and the workday calendar should flow into one mobility register, which is the sole authorised source for shadow payroll input. The spreadsheet is retired as a system of record and kept only as a reconciliation view.
A trailing-income trigger list. Any of the following during an assignment opens a mandatory review item: a share vest, a bonus or commission payment, a sale of shares, a exercise of options, a new grant, or a home-country pay change. The trigger is generated by the feed, not remembered by a person.
A three-way pre-payroll sign-off. Before each host payroll is released, the home payroll register, the shadow payroll register and the tax provider's calculation must be matched on total taxable remuneration per assignee, with variances explained. This is the control that would have caught the German gap in month one.
Ownership. Mobility owns the register and the trigger list; the host provider owns the calculation; the payroll director owns the reconciliation sign-off and reports the balance-sheet bridge to finance monthly. Name the individuals - shared ownership across three teams is how this happened.
Finally, add an independent annual review of a sample of assignees covering the full year, because every control above is operated by the same function that missed the error.