Express courier. Direct.
Also overnight.
x25pronto Switzerland takes goods direct to the destination. Small loads go by car. Larger loads go by van or Van XL. Direct, express and overnight trips run Monday to Sunday when a slot is free. Free times are shown in the booking calendar. This keeps the plan clear.
Data mapping between ERP/billing and courier systems
Clear field mapping and solid error handling are key to syncing shipment and invoice data between ERP systems and courier platforms. This guide lists typical fields, rules and checks.
Quick answer
Data mapping links your ERP or billing system with the courier platform so shipment details, costs and invoice references match automatically. Start by defining core fields (customer, address, weight, service, cost centre, invoice number) and simple validation rules. Automated invoice matching works when courier records include a unique invoice or order reference. Add validation checks, error routines and logs so mismatches are detected early and remain easy to correct manually.
Why correct mapping matters
Mapping errors cause wrong invoices, delayed deliveries and extra back‑office work. Clean mapping reduces manual work, speeds up billing and improves transparency between sales, accounting and the courier.
Typical fields to map
Define these minimum fields: customer ID, invoice number/order reference, pickup and delivery address (street, postal code, city, canton), recipient name, weight, volume or item count, service type (e.g. overnight), cost centre, shipment date. Optional: delivery window, recipient phone and internal notes.
Field formats and rules
Standardise formats. Postal codes as 4 digits, dates in ISO format (YYYY‑MM‑DD), phone numbers with country code (+41). Use fixed field lengths and UTF‑8. Set required fields and defaults for optional values.
Error handling and validation
Run checks before dispatch: plausibility (weight > 0), address validation (valid postal code/canton), reference uniqueness (invoice number). On error: return clear messages, allow retries and escalate to back office. Log failed attempts for audits.
Automated invoice matching
Ensure each shipment carries an invoice or order reference. Match courier charges to ERP invoices using that reference. For partial deliveries use position IDs or split IDs. Set rules for rounding, currency fields and VAT tags so accounting can post items automatically.
Practical integration patterns
Use REST APIs for real‑time communication or batch interfaces (CSV/EDI) for high volumes. Implement webhooks for status updates (pickup, delivery). Create a sandbox for testing and version your API specs.
Frequently asked questions
What reference does a shipment need for automatic invoice matching?
At minimum a unique invoice or order reference. For multi‑line orders include position IDs or split identifiers so partial costs map correctly.
How do I avoid wrong Swiss delivery addresses?
Validate postal code/canton pairs, use address validation against Swiss Post or local databases and require street plus house number. Provide clear error messages in the mapping layer.
What about currency or VAT mismatches between ERP and courier data?
Include a currency field and VAT flags in the mapping. Define rounding rules and threshold checks that trigger manual review on discrepancies.
How do I test the mapping before going live?
Use a sandbox with test data, automated unit and integration tests and sample runs. Test error cases, partial deliveries and different service classes.