Personnel master data from multiple sources: Resolve conflicts before payroll takeover

A company wants to transfer its payroll to your office. Personnel information is held in an HR application, an operational list and by the previous payroll provider. Some details differ for the same employee. A specific preparatory task therefore matters for your quotation: who confirms which facts should apply, and who prepares that confirmed position for transfer? Discussing conflicting sources individually helps the customer identify the clarification remaining within the business and the work your payroll service should actually undertake.

The starting point is a data conflict rather than a blanket preference for the supposedly newest system. A file exported later can contain older information. Another value might describe a planned change that has not yet occurred. Your team therefore needs more than a preferred filename. It must connect origin, meaning, relevant period and confirmation before preparing technical processing within the scope actually agreed.

First identify the differing detail precisely

Choose a generally described or entirely fictional conflict for the discussion. Which detail differs, and which sources state each value? Saying personnel documents do not match is too broad. If the assignment to a business organisational unit differs, you can examine that particular information. Your office does not need a complete list of real employees or an indiscriminate collection of personal documents for the first quotation discussion.

Initially record the two values side by side. Add who supplies each source and what is actually known about its position. Do not change either value simply to produce a tidy combined list. The difference should remain visible until the responsible person explains the facts. A colleague can later understand which question was open and which answer supported the subsequent preparation.

Also ask whether both entries describe the same information. A cost centre, an organisational department and an actual work location can serve different purposes. Similar labels do not automatically make them the same attribute. Ask the business to explain each column’s meaning. Only then can you assess whether there is a real contradiction or two different details would accidentally be combined in the intended transfer.

Confirm the assignment to the correct person

Before comparing contents, check how the same employee is recognised across sources. Different applications may use different internal identifiers. A similarly spelled name is not a confirmed match. Ask about the linking attribute actually intended and the person confirming its accuracy. In a fictional discussion case, use two invented identifiers and have the customer explain why they should refer to the same person.

Consider cases where an old identifier was reused or used differently. Your team does not establish a universal technical recognition rule; it clarifies the particular facts with the responsible customer representative. An accidentally merged record can generate many apparent conflicts. Confirming the person match first lets you investigate the remaining difference deliberately instead of prematurely attributing differing contents to one employment relationship.

Separate export date from the information’s applicability

Ask when a detail was entered and what work position it describes. These may differ. An overview generated today can show a previous position; a list prepared earlier can already include a planned change. For comparison, your office needs the expressly confirmed reference of the information. The file’s arrival time does not answer that question, although it may help track the delivery.

Walk through the transition between two positions with an invented example. A person is to belong to another business unit in future. One source shows the previous assignment, the other the intended new one. Ask who can explain the actual facts and their confirmed applicability. The organisational note does not determine tax or employment-law effects. Any required professional decision remains with the person responsible for the individual case.

Separate the facts from the technical data route

Determine with the customer who provides the substantive answer. Someone able to create an export may not know the reason for a change. The HR manager may explain the facts without supplying the file personally. Both roles are needed for transfer but answer different questions. A technically successful export does not turn unresolved content into a confirmed starting position for your payroll team.

Agree how professional confirmation reaches the preparation stage. A brief explanation associated with the conflict could identify the source to use for that detail and confirmed position. Describe the specific scope of the decision. Approval of one attribute is not blanket confirmation of every column in a large file. Other unresolved differences remain individually recognisable and receive their own clarification route.

Determine a leading source for each confirmed purpose

Discuss whether a particular source should supply the confirmed detail in future cooperation. This can vary by attribute. The customer need not move all information into one application to describe an understandable transfer route. What matters is that your team can identify which confirmed information reaches the agreed process from which responsible person, and how a later change is identified.

Check whether an overview compiled only for initial setup should be maintained afterwards. It might be intended to cease being a separate maintenance route after transfer. In that case, establish where future changes actually originate and who reports them to your office. Otherwise, a once-cleaned list could become an additional, soon divergent source alongside the systems still in use. Explicitly describe its intended purpose.

Check technical transfer against the real procedure

Once contents are clarified, assess technical preparation specifically. Which information can the system in use supply, and which procedure does your actual payroll software support? The current DATEV Lohnimportdatenservice description mentions exchanging master and transaction data from selected third-party systems and requires a suitable interface. That does not imply universal import of arbitrary files or automatic decisions about conflicting contents.

Ask your specialist team to check the precise intended route. If additional preparation is needed, describe its result and limits. Transferring confirmed information into a checked format differs from deciding which information is substantively correct. Keep both tasks separate in the quotation. The customer can then compare supplying the confirmed compilation themselves with having your office perform preparation it actually offers.

Relate new deliveries to the confirmed position

Discuss what happens when another file arrives after clarification. Should it replace the previous delivery, change one detail or merely add an explanation? The sender must make the intended relationship understandable. A new attachment is not automatically a new complete approval. Your team should recognise which confirmed decision still applies and which particular item needs reconsideration.

If the same unresolved difference repeatedly arrives, look for its origin in the agreed maintenance process. The transfer list may have been corrected while the source still in use remains unchanged. Clarify with the responsible person what change is needed there and actually commissioned. Processing an export file does not itself make your office responsible for maintaining every upstream system. The customer needs a clear assignment of that remaining task.

Distinguish missing information from deliberate omissions

Include an attribute filled in one source and empty in another. An empty space may indicate information not maintained there or a question still unanswered. Do not infer substantive cancellation from it. Ask the responsible person for its actual meaning and record that beside the comparison concerned. The effect of an empty value in a specific import procedure is subsequently checked technically.

Distinguish missing content from a missing person. If an employee appears in only one supplied list, clarification begins with that list’s scope. It may deliberately cover only part of the business, or a record may not yet have been added. The business confirms which people and position belong to the intended transfer. Your office can then identify whether an addition is required or the smaller list serves another purpose.

Also ask whether an explanatory addition replaces original information or simply describes it more precisely. A more detailed designation may mean the same business unit or express a new assignment. Wording alone does not decide that. Have the specific relationship confirmed and retain the explanation for preparation. The technical handler then need not guess whether they are standardising spelling or preparing a substantive change.

Finally, check the confirmed selection in reverse: a colleague points to the detail intended for transfer and explains its source and the feedback justifying its use. The customer must recognise the same connection. If only the final value is traceable but its confirmation is not, part of the handover is missing. Add that specific reference instead of describing all source files as checked wholesale.

Follow a fictional conflict through to transfer

An explicitly fictional company supplies two different organisational assignments for the invented identifier E-17. The HR system shows the previous department; a parallel list shows the planned new one. First, the responsible person confirms that both identifiers concern the same employment relationship. They then explain which position each detail describes. The information actually needed for the intended transfer scope is expressly confirmed and the affected entry traceably assigned.

Your colleague then checks only the technical preparation of confirmed contents. During the rehearsal, another file arrives containing the old assignment. The colleague can explain why that delivery receives a query rather than silently replacing the confirmed position. The customer also identifies who will correct the original list still in use. The case thus shows contents, preparation and future maintenance as three different tasks concerning the same specific discrepancy.

Describe the cleansing work clearly in the quotation

Summarise the intended work as a separate part of intake. Which sources are compared, who answers substantive queries and which confirmed details does your office prepare? Place open prerequisites beside the affected information. A general sentence about data cleansing leaves it unclear whether the customer expects technical format conversion or a complete professional clarification of every employment relationship. The shared description makes the agreed scope assessable.

Deliberately include later processing. Which difference should the business resolve itself before reporting, and when should your office query it? This agreement describes a traceable data route. It is no guarantee of error-free payroll and no legal assessment of a particular personnel decision. The customer receives a practical basis for connecting their own preparation with the support offered and jointly confirming actual transfer readiness.

Meet new businesses for your payroll service

Payroll leads from webRichtung connect you with companies in Germany seeking external support. Employee-number bands, current organisation, desired start, business location and contact provide the starting point. Discuss conflicting master data, specific source systems and preparation scope personally. Register your office and prepare your order in webRichtung Customer; the current price is shown before a binding order.

Sources

The current DATEV Lohnimportdatenservice description supports the limited interface connection, not automatic substantive conflict resolution. The webRichtung payroll page describes the actual enquiry service. Both read on 25 October 2026. The proposed conflict clarification is an editorial organisational aid; individual payroll and legal questions are not decided.