delivery_notes_create
Creates a draft delivery note documenting physical delivery of goods or services, with optional deputy and e-Transport details, for later conversion to invoices.
Instructions
Create a new delivery note in draft status. Delivery notes document physical delivery of goods or services and can later be converted to invoices. Include deputy information for proof of delivery. A default delivery_note series is auto-assigned if neither seriesId nor documentSeriesId is provided.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lines | Yes | Array of line items (minimum 1 required) | |
| notes | No | Public notes about the delivery | |
| dueDate | Yes | Due date for invoicing (YYYY-MM-DD) | |
| clientId | Yes | UUID of the client | |
| currency | Yes | Currency code (e.g., RON, EUR, USD) | |
| issuerId | No | UUID of the issuer user | |
| mentions | No | Additional mentions or instructions | |
| seriesId | No | UUID of the delivery note series (uses default series if not provided) | |
| companyId | No | Company UUID (overrides configured default) | |
| issueDate | Yes | Date of issue (YYYY-MM-DD) | |
| deputyAuto | No | Vehicle registration number used for delivery | |
| deputyName | No | Name of person who received the delivery | |
| issuerName | No | Name of person issuing the delivery note | |
| salesAgent | No | Sales agent name | |
| exchangeRate | No | Exchange rate to base currency (default: 1.0 for RON) | |
| internalNote | No | Internal note (not visible to client) | |
| deliveryLocation | No | Full address where goods were delivered | |
| documentSeriesId | No | UUID of the document series to use (alternative to seriesId; uses default delivery_note series if neither is provided) | |
| projectReference | No | Related project or order reference | |
| deputyIdentityCard | No | ID card number of the deputy | |
| etransportTrailer1 | No | First trailer registration number | |
| etransportTrailer2 | No | Second trailer registration number | |
| etransportEndCounty | No | End county code (1-52). Required for e-Transport (BR-211) | |
| etransportEndNumber | No | End street number | |
| etransportEndStreet | No | End street name (2-100 chars) | |
| etransportEndLocality | No | End locality name (2-100 chars) | |
| etransportStartCounty | No | Start county code (1-52 per ANAF nomenclature, e.g., 4=Bacau, 40=Bucuresti). Required for e-Transport (BR-210) | |
| etransportStartNumber | No | Start street number | |
| etransportStartStreet | No | Start street name (2-100 chars per BR-215) | |
| etransportEndOtherInfo | No | End additional address info | |
| etransportPostIncident | No | Post-incident declaration (after the transport was completed) | |
| etransportEndPostalCode | No | End postal code | |
| etransportOperationType | No | Operation type code: 10 (intra-community acquisition), 12 (intra-community delivery), 20 (transaction in national territory between two different entities with goods moving domestically), 30 (domestic transport document TTN), 40 (import), 50 (export), 60 (goods not released for circulation) | |
| etransportStartLocality | No | Start locality name (2-100 chars per BR-214) | |
| etransportTransportDate | No | Transport start date (YYYY-MM-DD) | |
| etransportVehicleNumber | No | Vehicle registration number (e.g., "BC01ABC"). Schematron BR-031: 3-20 uppercase alphanumeric chars | |
| etransportStartOtherInfo | No | Start additional address info | |
| etransportStartPostalCode | No | Start postal code | |
| etransportTransporterCode | No | Transporter CUI/CIF (numeric only, e.g., "31385365"). Must match ANAF format per BR-002 | |
| etransportTransporterName | No | Transporter legal name (e.g., "UNIVERSAL EQUIPMENT PROJECTS SRL") | |
| etransportTransporterCountry | No | Transporter country code (ISO 3166-1 alpha-2, e.g., "RO"). For TTN (opType 30) must be "RO" per BR-005 |