Human translation Secure document handling Managed review

Blog

How to Translate a Spain Payslip (Nómina) into English: Fields, Layout and QA

First confirm that the file is an individual salary receipt from Spain rather than a payroll list, employment letter, contract or bank payment record. Then inventory every selected pay period, page and attachment; preserve the employer and worker blocks, settlement dates, earnings and non-salary groupings, deductions, contribution and withholding-base labels, percentages, amounts, totals and source-visible notes in the same relationships. Translate labels in context, but copy identifiers and printed values exactly and keep each period separate. Do not calculate gross or net pay, reclassify an item, interpret tax or Social Security treatment, decide which months prove income, verify employment or authenticity, give legal, tax, employment or recipient advice, or promise acceptance.

Scope

Who this Spain payslip production guide is for.

Use this post when one or more Spain-issued individual salary receipts have already been selected for Spanish-to-English translation. It owns document classification and field-level production: title and document function, employer and worker blocks, settlement period, earnings, salary and non-salary groupings, deductions, contribution and withholding-base labels, rates shown in the source, totals, repeated months, attachments, visible marks and bilingual QA. The pay-slip document page remains the broad service overview, while the date, scan and security guides own their cross-document workflows. This guide does not decide which records or periods are required, whether an item is legally salary, what a withholding or contribution should be, whether totals reconcile, whether employment or income is sufficient, whether the source is authentic or whether any receiving organization will accept it.

Employees and households with the exact Spain payslips already selected for an English translation.

HR, accounting and administrative teams sending a defined salary-receipt set to a translator.

Translators and bilingual reviewers preserving dense payroll fields across several periods.

Step-by-step explanation

Confirm that nómina names the individual salary receipt in this file.

Nómina can refer to a list or payroll concept as well as pay received, so do not classify a file from that word alone. Read the complete heading and function: a Spain individual salary receipt commonly identifies an employer and worker, a settlement period, earnings, deductions and a net amount, and may include a separate contribution-base block or continuation. A company-wide payroll register, employment certificate, contract, bank transfer proof or annual tax certificate is a different source and should keep its own document label and quote line. Classification comes before terminology, page counting and pricing.

Original fictional example: secure upload contains a one-page document headed “Recibo individual de salarios — abril de 2026” plus a second sheet of contribution bases. The manifest records one April payslip with two source parts. A separate bank credit labeled “Abono nómina” is inventoried as payment evidence, not merged into the salary receipt.

01

Classify the document by heading, parties and function.

Record the complete non-personal title and confirm whether the file reports one worker and one settlement period. Keep a payroll roster, employment letter, contract, bank payment record, severance document or tax certificate separate even if it contains the word nómina or repeats some amounts. Use Payslip, Pay Slip, Wage Statement or Individual Salary Receipt only when the complete source and the project glossary support that choice.

Original fictional example: “Listado de nómina — Planta Norte” contains twelve employee rows, while “Recibo individual de salarios” contains one worker block. The first becomes a payroll register in the manifest; the second is the payslip.
02

Build a period, page and attachment manifest.

Create one manifest row per selected pay period. Record a privacy-safe employer label, month or start and end dates, source page count, whether a contribution-base block is on the same page or a separate part, and any appendix, correction or duplicate. Do not place employee names, national or Social Security identifiers, bank accounts, salary amounts or full source text in ordinary quote notes.

Original fictional example: three files are labeled “Employer A / Jan / 2 parts,” “Employer A / Feb / 2 parts” and “Employer A / Feb / duplicate.” The quote covers two periods and four source parts, not three payslips.
03

Lock employer, worker and settlement-period fields.

Map employer name and address, tax or contribution-account labels, worker name, identification labels, Social Security affiliation number, professional group, contribution group, settlement dates and total days exactly where they appear. Translate the labels and preserve the printed values, punctuation and masking. Do not expand a partial identifier, standardize a name without an approved instruction or infer that two similar labels hold the same number.

Original fictional example: the worker block prints “N. Afiliación S.S.: ••••4821” and the employer block prints a different “C.C.C.: ••••9034.” The English version keeps two labeled masked fields and never merges them as one Social Security number.
04

Preserve the earnings hierarchy and source classifications.

Keep Devengos as the governing earnings block and preserve the source distinction between percepciones salariales and percepciones no salariales. Translate each printed concept, such as salario base, complemento, horas extraordinarias or a source-specific allowance, in context and retain its amount and subtotal relationship. Keep horas complementarias as additional hours under a part-time arrangement when that is the source label; do not silently merge it with overtime. Do not decide that an unclear item is a bonus, expense reimbursement, benefit or legally salary merely because its amount resembles another month.

Original fictional example: “Plus transporte” appears under “Percepciones no salariales,” while “Complemento puesto” appears under “Percepciones salariales.” The translation preserves those two source groupings and does not move either line after comparing tax treatment.
05

Keep deductions, bases, rates and employer contributions separate.

Map the deductions block row by row, then map any separate contribution-base and employer-contribution block without collapsing them together. Keep base, rate or type, worker contribution, employer contribution and withheld amount in their printed columns. Preserve labels such as prorrata pagas extraordinarias, contingencias comunes, AT y EP, desempleo, formación profesional, FOGASA and base sujeta a retención del IRPF; retain an abbreviation beside a supported expansion when the project glossary calls for one. The translation only renders and reproduces these fields: it does not interpret liability, check the applicable rate or calculate a missing value.

Original fictional example: a deduction line displays base EUR 1,800.00, rate 4.70% and amount EUR 84.60, while the second source part shows an employer contribution in another column. All printed values remain separate; the translator does not verify the percentage or recompute EUR 84.60.
06

Copy totals, currency and number conventions without reconciling.

Preserve Total earned, Total deductions and Net amount payable as separately labeled source totals, together with currency codes or symbols, decimal punctuation, negative signs and blank cells. The English layout may clarify decimal punctuation under a documented project style, but every value must remain traceable to the source. If A minus B does not appear to equal the printed net amount, keep and flag the source values instead of silently correcting them.

Original fictional example: the source prints A = 2.015,40 EUR, B = 315,30 EUR and net = 1.700,11 EUR. The translation copies all three and flags the apparent one-cent difference; it does not replace the net with 1,700.10 EUR.
07

Run cross-period, attachment and bilingual QA.

Compare every translated period with its matching source parts. Check title, parties, period, days, concept order, base-rate-amount relationships, subtotals, totals, repeated abbreviations, footer, signature or receipt lines, page sequence and visible redactions. Compare repeated employer and worker labels across months to catch transcription drift, but preserve a genuine source change. Request a secure replacement for a cropped or illegible field rather than inferring it from another period.

Original fictional example: May uses “Grupo cotiz. 07” and June clearly uses “Grupo cotiz. 05.” QA verifies both against their own sources and retains the change. A blurred July value is marked for replacement, not copied from June.

Decision table

Match the translation treatment to the payroll source.

What the source shows Translation treatment What to confirm
Nómina or recibo individual de salarios with one worker and one period. Classify as a payslip or individual salary receipt and translate every in-scope field.

Complete heading, employer, worker, settlement period, pages and attachments.

A two-part layout with deductions on one part and contribution bases on another. Preserve both parts and their distinct columns under one period manifest entry.

Whether the second part is on the reverse, a continuation page or a separate attachment.

Listado de nómina or a file with several workers in rows. Inventory as a payroll register, not as several individual payslips by assumption.

Title, purpose, row count, selected people, columns and privacy scope.

A bank line or receipt says abono nómina but has no earnings or deductions. Keep it as bank payment evidence with its own document label.

Bank, transaction date, displayed description and whether a salary receipt is separately supplied.

Devengos contains salary and non-salary subgroups. Preserve the source hierarchy, each concept and the subtotal relationships.

Exact group headings, wrapped descriptions, blank rows and amount columns.

A row contains a base, percentage or type and an amount. Keep all values in separate labeled columns and do not recompute them.

Decimal punctuation, percent sign, blank values and whether the amount is worker or employer side.

Several months use changed layouts, abbreviations or concept order. Keep each month source-faithful while applying one documented English glossary.

Which differences are source changes, duplicates, corrections or scan artifacts.

A field, edge, reverse side or attachment is cropped, blurred or visibly redacted. Request a secure replacement or use the approved visible notation; never infer hidden text.

All selected pages, content-bearing sides, redaction marks and whether the recipient permits that source.

Checklist

Payslip translation QA checklist.

The complete title and document function are identified before choosing Payslip or another English label.

Every selected period, page, reverse side, contribution block and attachment appears in the manifest.

Employer and worker labels, identifiers and visible mask characters match the source.

Settlement dates, total days and month labels stay attached to the correct period.

Earnings, salary and non-salary groupings preserve the printed hierarchy and concept order.

Deductions, bases, rates, worker amounts and employer amounts remain in distinct columns.

Total earned, total deductions and net amount payable are copied rather than recalculated.

Currency, decimal punctuation, percent signs, minus signs, blank cells and source notes are traceable.

Cross-period QA catches transcription drift without erasing genuine source changes.

Ordinary quote text contains no worker identifiers, bank details, payroll amounts or source images.

Official model and reviewed sources

The sources identify fields and terminology; they do not decide a recipient requirement.

Consolidated Order and individual salary receipt model

The consolidated official publication displays the updated annex across two images, with employer and worker blocks, settlement period, earnings, deductions, net amount, contribution bases, rates and employer contributions. This guide uses those visible labels to explain source mapping only. It does not claim that every employer layout or page arrangement is identical, interpret the figures or give employment, tax or Social Security advice.

Agencia Estatal Boletín Oficial del Estado, Spain

Open the consolidated order and current annex

Correction to Order ESS/2098/2014

The official correction fixes the misnumbered second principal heading in the model as “II. DEDUCCIONES.” It supports reproducing the heading and hierarchy from the operative source rather than carrying forward a publication error. It does not establish any amount, rate or recipient requirement.

Agencia Estatal Boletín Oficial del Estado, Spain

Open the official correction

Workers’ Statute, Article 29

Article 29 requires clear separation of the worker’s earnings and deductions. It allows another receipt model established by collective agreement or, failing that, by agreement between the employer and workers’ representatives. That is why this guide maps functions and relationships without claiming every Spain payslip has one identical layout.

Agencia Estatal Boletín Oficial del Estado, Spain

Open the current consolidated statute

Contribution bases and rates

The official explanation distinguishes the contribution base, contribution rate and resulting contribution. It supports keeping those source columns separate. This guide presents no rate as currently applicable and does not calculate, validate or interpret a customer’s figures.

Spanish Social Security portal

Open the official contribution explanation

Nómina — Diccionario de la lengua española

The current dictionary entry records list or roster senses as well as the pay received by a worker. It supports the guide rule that nómina alone does not classify the document: the complete heading, parties and function must control the English label.

Real Academia Española and ASALE

Open the RAE entry for nómina

Spanish Pay Slip Translation to English

The broad document page defines the pay-slip service, common Spanish titles, typical fields, secure upload and quote factors. It remains the general commercial owner; this post adds the Spain-specific field map, multi-period workflow and bilingual QA boundary.

SpanishToEnglishTranslations.com document library

Open the pay-slip service overview

Author and reviewer

Named ownership and review scope.

Content owner

SpanishToEnglishTranslations.com Editorial Team

Editorial reviewer

SpanishToEnglishTranslations.com Employment Document QA Team

Reviewed for an already-selected Spain individual salary-receipt scope; distinction from payroll registers, employment letters, contracts and bank payment evidence; employer, worker, period, earnings, deductions, bases, rates, contributions and totals; one-page, multi-page and multi-period layouts; eight original fictional examples; an eight-row decision table and ten-point checklist; the limited evidence of six official or reviewed sources checked on September 14, 2026; privacy-conscious quote intake; and explicit boundaries from payroll calculation, legal pay classification, tax or Social Security interpretation, income-sufficiency and required-period decisions, employment verification, authenticity, recipient advice and acceptance guarantees.

Blog FAQ

Questions about translating Spain payslips into English.

What is nómina in English on a Spain salary document?

Payslip or Pay Slip is usually clear when the complete file is an individual salary receipt for one worker and period. Individual Salary Receipt or Wage Statement may fit a documented project style. Nómina can also refer to a payroll list or pay generally, so classify the complete heading, parties and function before choosing the English label.

Should devengos be translated as earnings or accruals?

Earnings is often the natural payroll-block heading when devengos groups amounts earned or payable on the receipt; accrued amounts may fit a narrower accounting phrase. The complete block, individual line labels and approved glossary should control the choice. Preserve salary and non-salary subgroups and do not use the English term to reclassify the legal nature of a payment.

Are contribution bases and employer contributions part of the translation?

They are included when they appear on the selected source pages and fall within the agreed complete-document scope. Keep each base, rate, worker amount and employer amount in its printed relationship. The translator reproduces labels and values but does not check the applicable rules, calculate a missing amount or advise on Social Security obligations.

Will the translator recalculate gross pay, deductions or net pay?

No. Total earned, total deductions, net amount, bases, percentages and line amounts are copied as source values. Bilingual QA may flag an apparent mismatch for source comparison, but it does not calculate a replacement, decide the correct rate or offer a payroll, tax or accounting conclusion.

Can several monthly payslips be translated as one packet?

Yes, if the quote identifies every selected period, page and attachment. Each month should remain separately traceable even when the English delivery uses one combined file and one glossary. Cross-period QA can catch transcription drift but must preserve genuine changes in identifiers, groups, concepts, rates, amounts and layout.

Can a redacted or incomplete Spain payslip be translated?

A translation can reflect redaction already visible in the supplied source and mark unreadable or missing content with the approved notation. It must not reconstruct hidden text or silently omit a reverse side or contribution attachment. Whether a receiving organization permits a redacted or incomplete source is outside translation scope and should be confirmed with that organization.

What should I send for an exact Spain payslip translation quote?

In ordinary quote fields, share only the issuing country, generic document label, selected period count, page and attachment count, table density, legibility, recipient category, deadline, delivery format and certification preference. Keep names, identifiers, bank details, payroll figures, source text and images out of those fields. Use secure upload for every complete selected page, reverse side and attachment so the actual scope can be reviewed.