Every payroll package expects data in a slightly different shape. A3Nom uses Spanish column labels for alta de trabajadores. TeamSystem expects Italian fields like codice fiscale and RAL. PHC GO follows Portuguese HR conventions. Moneysoft in the UK wants NI numbers, tax codes, and sort codes.

Inputo does not force you into one generic spreadsheet. It generates an Excel or CSV file in the exact layout each program's import assistant expects — Excel for A3Nom, TeamSystem and PHC GO; UTF-8 CSV for Moneysoft.

CountrySoftwareColumns (approx.)Key fields
🇪🇸 SpainA3Nom30DNI, NSS, IRPF, salary, contract dates, grupo arancelario
🇮🇹 ItalyTeamSystem24Codice Fiscale, IBAN, RAL, birth place, contract type
🇵🇹 PortugalPHC GO25NIF, Nº Seg. Social, morada, vencimento, IBAN
🇬🇧 UKMoneysoft28NI Number, tax code, sort code, pay frequency, dates (CSV)
🇫🇷 FranceSilae43NIR, matricule, civilité, adresse, dates d'entrée/sortie (Excel)

The column count varies because each vendor models payroll differently. What matters is that column names match what the import wizard shows — so you spend minutes mapping, not hours fixing mismatched headers.

Inputo maps extracted JSON fields to each format intelligently. Spanish national_id becomes A3Nom's DNI and PHC's NIF. social_security_number flows to NSS, Italian affiliation fields, or UK NI numbers depending on the export you choose.

One extraction, multiple destinations — ideal for multi-country practices. Upload once in any supported language (7-language OCR), then pick the export your client needs.

France is covered today via Silae; see the roadmap for PayFit, Germany and the Netherlands. Spanish IDC workflows pair well with the A3Nom extraction guide.

Try Inputo free → https://inputo.app

Ready to stop retyping information from documents?

Launch the app →