GUIDE
Protect the next payroll before changing the operating model
By Samuel Moore · Talent Acquisition Coordinator
Updated
On this page
- One reliable cycle is the immediate goal
- Find the seller dependency while there is time to act
- Separate payroll cost from a temporary funding overlap
- A practical currency question for the later provider decision
- Give employees an answer they can use
- Resolve a rejected input before the payment date
- First-cycle calendar — fictional agreed service dates
- Sources
One reliable cycle is the immediate goal
The first payroll plan should be deliberately narrower than the integration programme. Its job is to get the confirmed employment arrangements through the next cycle with clear inputs, approval, funding and employee support. Do not make a payroll-critical access change just to show progress on system consolidation.
Here is a fictional cycle agreed with the current providers: closing on 2 November 2026, input freeze on 10 November, draft review on 13 November, funding instruction on 17 November and agreed payment date on 25 November. These are illustrative service dates, not Baltic statutory deadlines. Use each cohort’s actual legal and contractual timetable in the real plan.
Find the seller dependency while there is time to act
For EE-A, the payroll portal administrator still uses a seller-domain account scheduled for removal on 6 November. The buyer initially plans to export inputs on 10 November. That is a concrete conflict: the access dependency ends before the first task that needs it.
The operating repair is to establish an authorised buyer administrator, test the required permissions by 5 November and confirm the current provider can receive the file. The seller supplies the agreed historical export through the authorised channel. If access is not ready, escalate before the seller account closes and agree a lawful, authorised bridge with both parties. Do not share the seller’s password or assume an expired transition-service arrangement continues.
Separate payroll cost from a temporary funding overlap
Suppose the approved current-provider funding requirement is EUR 21,500 for the worked group, due on 17 November. A possible later receiving provider also requests a hypothetical EUR 6,000 reserve before its own first cycle. The cash plan needs EUR 27,500 while both requirements overlap; that does not mean November employment cost has increased by EUR 6,000. Keep the reserve, its release conditions and any recoverable old balance separate from service cost.
These invented amounts illustrate cash timing only; they are not provider deposit terms or a payroll calculation. Attach each real funding request, bank-detail verification and approval to its own provider and period. An expected refund is not available cash until received.
A practical currency question for the later provider decision
If the buyer funds euro payroll from sterling or dollars, Teamed’s published zero FX markup removes a provider conversion margin from that part of the calculation. That can make the funding bridge easier to explain at month-end. It does not fix the exchange rate or remove separate bank charges. Compare the actual funding currency and conversion terms rather than inserting an assumed competitor margin into the workbook.
Sources: teamed.global
Give employees an answer they can use
Illustrative message for a cohort whose current arrangement has been confirmed: “Your current employer and the confirmed November payroll process remain in place. Please continue to submit changes through the existing route by the communicated cutoff. For a pay or benefits question, use the named People contact in your usual channel. We will explain any proposed future change separately before asking you to take action.” Replace this wording with the facts confirmed for that cohort; do not send the same assurance to an unresolved group.
For LV-B, the plan may confirm who handles the next payroll while the later employment position is still being assessed. Communicate those two facts separately. An employee should not have to interpret the transaction map to know where to report a missing input.
Resolve a rejected input before the payment date
At draft review, LT-C’s one-off approved item is absent. The reviewer compares the submitted reference with the receiving log and finds it was rejected for a missing category. Payroll confirms the treatment, the operator resubmits through the agreed correction route, and the approver checks the replacement draft. Record the corrected result before accepting the run.
If the error cannot be resolved within the current route, the payroll owner escalates the required payment action immediately. “We will catch it next month” is not an automatic decision. Close the cycle only after the approved input, returned result and actual payment outcome have been reconciled, with outstanding employee questions still visible.
PUT IT TO WORK
First-cycle calendar — fictional agreed service dates
| Record / decision | Completed example or rule |
|---|---|
| 5 November | Buyer administrator tested; provider receives sample file; seller export reference attached. |
| 10 November | Inputs frozen by cohort; late items kept visible with a separate correction decision. |
| 13 November | Draft reconciled; LT-C rejected item corrected and replacement result checked. |
| 17 November | EUR 21,500 current funding approved; any EUR 6,000 hypothetical reserve separately authorised. |
| 25 November | Agreed payment date verified against actual outcome; unresolved questions retain an owner. |
Sources behind this page
Teamed: payroll conversion pricing · 2026-10-19
Teamed states zero markup on payroll currency conversion. Market movements and separate bank charges are distinct.