Blog
When a Spain-issued albarán records goods sent and received against an order, “delivery note” is often a useful English title. Confirm its function from the complete page before choosing that term. Preserve supplier and customer roles, albarán and order references, item rows, units, quantities, dispatch and receipt dates, and every signed, stamped or handwritten receipt or discrepancy mark. Keep ordered, dispatched and acknowledged quantities in separate source columns. Translate every legible reservation without treating a signature as proof of complete or satisfactory delivery. An invoice, packing list, carrier record or picking slip needs its own classification. An exact quote requires all pages, reverse sides and attachments through secure upload.
Scope
Use this post when a selected Spain-issued delivery record must be translated into English for a buyer, supplier, operations team, auditor or business reviewer. It covers document classification, order-to-delivery rows, visible receipt marks and bilingual review. It does not determine whether an order was fulfilled, goods were accepted, a signature is genuine, a discrepancy has legal effect, an invoice is valid or a particular recipient requires certification. Ask the recipient for current format instructions.
Procurement and customer-service teams comparing a selected delivery note with an English order file.
Warehouse, supplier and buyer teams that need item rows and receipt annotations to remain traceable.
Translators handling dense tables, handwritten reservations and multi-page copies.
Table of contents
Step-by-step explanation
Spanish records may use albarán, nota de entrega or justificante de entrega. “Delivery note” often fits a supplier-to-customer list of ordered and delivered items. A carrier proof of delivery emphasizes transport handoff; a packing list maps packages and contents; a picking list directs warehouse selection; an invoice records charges. Classify from the full title, parties, table and footer. Keep companion documents as separate sources.
Fictional example: “Albarán A-104” lists order PO-72, three rows and “recibido con falta de 2 unidades.” Translate the shortage note without changing an attached invoice.
Record title, albarán number, page count, issue date, revision, continuation and any terms or receipt block on the reverse. A cropped scan can omit the recipient’s note. Ask for the complete current set if versions conflict.
Fictional example: page 2 of 2 contains a handwritten shortage and receipt date.Preserve proveedor, cliente, destinatario, delivery address and carrier labels as printed. One company may fill several roles. Do not infer that the payer and physical recipient are the same.
Fictional example: customer Río Sur orders the goods while another warehouse is the delivery location.Copy albarán, order, customer, dispatch and invoice identifiers character for character with their labels. Flag an apparent mismatch; never substitute a number from a companion file.
Fictional example: “Pedido PO-72 / Albarán A-104” remains two references even if an invoice says A-140.Keep codes, descriptions, lots, ordered, dispatched and received quantities and units in their source columns. Distinguish blank, dash and zero. Do not calculate a shortage or convert units unless the source prints that result.
Fictional example: 12 cajas sent and 10 received remain separate figures, each labeled “boxes.”Keep the printed label and value for every event. Use an unambiguous English date style. Do not replace a handwritten receipt date with the issue date or infer a time from a stamp.
Fictional example: issued 4 September, sent 5 September, signed 6 September.Render legible recibido, conforme, pendiente de revisión, faltan, dañado, stamp text and signature labels. Mark unclear handwriting without guessing. Describe a signature without authenticating it or assigning an unnamed signer.
Fictional example: “caja 3 golpeada” remains a receipt reservation; it is not a finding of liability.Check headings, codes, rows, digits, units, dates, notes and marks against their source positions. Flag contradictions without repairing them. Give only generic scope details in ordinary quote text and upload complete files securely for exact review.
Fictional example: a two-page albarán with 18 rows and a faint note is quoted after both sides are reviewed.Decision table
Supplier, recipient and receipt-block function.
Whether it directs picking or maps packages.
Any visible reservation; do not derive a missing figure.
Whether an authorized replacement is supplied.
Do not add an acceptance statement.
Ask for a clearer complete scan if uncertain.
Every page and side is present.
Current written instruction and delivery format.
Checklist
The source functions as a delivery note, not a packing list, invoice or carrier record.
Every page, reverse, continuation, revision and attachment is inventoried.
Supplier, customer, recipient, delivery address and carrier roles remain distinct.
Albarán, order, dispatch and invoice references keep their labels and characters.
Codes, rows, quantities, units, blanks, dashes and zeros match the source.
Issue, dispatch, delivery and receipt dates stay with their own events.
Legible reservations and stamps are translated; uncertain spans are marked.
A signature is represented without inventing identity, acceptance or authenticity.
Companion-document differences are flagged, never silently repaired.
Quote text excludes private source data; complete files use secure upload.
Official and reviewed sources
Its glossary defines albarán as a delivery note signed by the person receiving goods. This supports the delivery-record classification, not a legal conclusion about any actual signature.
INCUAL, Government of Spain
Open the reviewed sourceThe standard describes comparing received quantities with the albarán. It supports preserving source quantities and discrepancies; it does not authorize a translator to decide which quantity is correct.
INCUAL, Government of Spain
Open the reviewed sourceThe toolkit gives context for distinct business and shipping document exchanges. It does not set case-specific receipt, signature or translation-certification rules.
International Chamber of Commerce and World Trade Organization
Open the reviewed sourceDocument-specific translation and quote intake support the review path, not any claim about a customer’s delivery.
SpanishToEnglishTranslations.com
Open the reviewed sourceThe bilingual QA workflow supports row checks and legibility review without silent source-data changes.
SpanishToEnglishTranslations.com
Open the reviewed sourceThe private upload route supports document review while keeping source details out of ordinary inquiry text.
SpanishToEnglishTranslations.com
Open the reviewed sourceAuthor and reviewer
Reviewed for a selected Spain-issued albarán; classification apart from invoice, packing list and carrier record; party roles, references, item rows, quantities, units, dates and receipt marks; eight fictional examples, eight decisions, ten QA checks, six sources checked September 19, 2026, secure quote intake, and boundaries from delivery, acceptance, authenticity and legal judgments.
Blog FAQ
No single English label fits every document. “Delivery note” often fits a supplier-to-customer record of ordered and delivered items. Check the whole title, parties, columns and receipt block; a carrier proof of delivery or warehouse picking list has another job.
No. An albarán records an order-linked delivery or handoff; an invoice records charges and a packing list maps packages and contents. They may repeat references but remain separate sources. Flag differences instead of importing values between documents.
Keep each printed quantity in its labeled row and column with the unit. Distinguish a blank, dash and zero. Do not calculate a missing quantity or rewrite the sent value from a handwritten reservation.
The translator cannot infer that from a signature alone. Show the signature, printed label, date, stamp and legible note. Translate “conforme” or “faltan 2” only when those words appear. The parties determine the transaction’s meaning.
Ask for a complete clearer scan and reverse before finalizing. If a span remains unreadable, mark that span as illegible without inferring it from the invoice or nearby text. Include scan condition in secure quote review.
That depends on the recipient’s current written instruction. Ask about standard translation, signed certification and digital or printed delivery separately. Certification describes the translation; it does not authenticate the albarán, validate quantities or guarantee acceptance.
Use ordinary fields for generic type, country, approximate pages and rows, scan quality, handwriting, recipient category, deadline and certification preference. Keep names, addresses, order numbers, products and source images out of free text. Securely upload every page, reverse and attachment for exact review.