Step-by-step explanation
Start with the requested fact or record—not with a generic “company documents” label.
Record the recipient category, review purpose and exact written list of requested facts or documents. A reviewer may ask for evidence of formation, a current registry extract, present officers, signing authority, articles, a tax identifier, a published corporate act or a complete transaction packet. Match each requested item to the source actually supplied and mark anything unresolved for customer confirmation. Do not select a Spanish registry product, declare two records equivalent or add an entire corporate archive merely because the request uses an unfamiliar English label.
Original fictional example: North Harbor Procurement asks Sol Mar, S.L. for an English packet showing the entity’s registered name, registration details, and the representative and acting mode stated in a dated certification. The scope maps those requests to the supplied certification and excludes old articles and annual accounts unless the buyer requests them.
01
Create a request-to-source matrix.
List each requested fact or document in one column and the candidate source, issuer, source date, page range and status in the others. Use statuses such as supplied, needs confirmation, outside translation scope or not provided. Keep the business request distinct from legal sufficiency: the matrix organizes translation work but does not decide whether the selected evidence meets a legal, compliance or transaction standard.
Original fictional example: a lender’s list has four lines—formation, registered address, officers and tax ID. The matrix pairs the first three with registry sources and the last with an AEAT NIF card, without treating the card as formation evidence.
02
Build a page-level corporate source manifest.
Assign neutral file IDs and record the complete visible title, issuing body, country or registry, issue or publication date, reference number category, page and side count, language mix, version label, attachments and relationship to other files. Separate documents that share one PDF, flag duplicate scans and identify missing pages, cropped seals or unreadable codes before quoting.
Original fictional example: one 31-page upload contains a four-page registry note, a 17-page incorporation deed, six pages of articles, a two-page BORME notice and a two-page Apostille. The manifest records five components instead of pricing the file as one unnamed certificate.
03
Classify each corporate source by its visible function.
Distinguish an informational registry note from a certification, a BORME publication from the underlying filing, an incorporation deed from current articles, a resolution from a power, and a NIF card from company-status evidence. Use the source title and issuer rather than a convenient English assumption. If the destination label has no safe one-to-one match, describe the source neutrally and ask the customer to confirm which record was requested.
Original fictional example: a file named “good-standing.pdf” is visibly titled “Nota Informativa Mercantil.” The production record uses the visible Spanish title and a careful English description; it does not relabel the note as a certificate of good standing.
04
Lock entity names, legal forms and identifiers.
Create a controlled register for the exact registered company name, trade name when present, legal-form abbreviation, NIF, registry office, tomo, libro, folio, hoja, inscripción, EUID or other displayed identifiers, registered address, formation and filing dates, capital and currency. Preserve source punctuation and leading zeros. Do not translate the registered company name or convert S.L., S.A. or another legal form into a U.S. entity type unless an approved terminology instruction requires an explanatory note.
Original fictional example: “Luz del Norte, S.L.” remains the registered company name in every output, with S.L. preserved and explained only if the agreed terminology note calls for it. It is not rewritten as “Northern Light LLC.”
05
Map officers, representatives and acting modes without inferring authority.
Record each displayed role—administrator, board member or director, attorney-in-fact, member or shareholder, secretary, liquidator or auditor—together with the source, date, appointment or cessation wording and whether the source describes a sole officeholder or joint, several or another acting mode. Keep defined roles consistent within each source and flag cross-file differences. A translation can preserve stated powers and dates; it cannot verify that an appointment or authority remains current or sufficient for a transaction.
Original fictional example: a 2022 resolution appoints Ana as apoderada, while a 2026 registry certification lists two current administrators acting jointly. The translation preserves both dated statements and flags the difference; it does not decide who can sign today.
06
Preserve document hierarchy, official marks and attachment links.
Retain headings, clause and resolution numbering, tables, footnotes, marginal notes, filing and publication references, signature blocks, seals, stamps, barcodes, CSV or CVE verification codes and attachment statements in a traceable layout. Translate legible text and label non-text marks consistently. Keep a BORME notice, registry certification, NIF card and Apostille as separate components even when they reference the same company.
Original fictional example: a BORME notice cites issue number, page, section and publication date, while an attached certification carries its own registry reference and seal. The English packet preserves both reference systems instead of merging them into one registration number.
07
Run cross-file bilingual QA and deliver a scope manifest.
Compare every content-bearing source page with the English output and recheck names, forms, identifiers, addresses, dates, capital, currencies, roles, acting modes, defined terms, version labels, references, marks and attachment boundaries. Record visible differences without silently harmonizing them. The delivery manifest should identify translated sources and page ranges, intentionally excluded files, documented scan limitations, terminology decisions and the certification mapped to each translation.
Original fictional example: the incorporation deed shows an earlier address than the later registry note. Final QA preserves each address under its own source date, confirms all 28 translated sides and lists one untranslated annual-account appendix as intentionally excluded.