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.
Integrating on-call blocks into ERP and accounting
How to map on-call blocks for courier and direct deliveries into your ERP and accounting—covering API/CSV import options, reconciliation templates and reporting best practices.
Quick answer
In short: Model on-call blocks as service or stock items in your ERP, sync usage and remaining balances via API or scheduled CSV imports, and reconcile invoices using clear references (contract, call ID, service period). Use consistent posting accounts and reporting templates to show consumption, remaining blocks and cost allocation.
What are on-call blocks and why add them to the ERP
On-call blocks are pre-purchased volumes of courier runs or direct deliveries redeemable across a set period. Recording them in the ERP keeps consumption, remaining balances and invoicing consistent. Treat blocks as service items so transactions follow standard inventory or service flows.
Data model: fields to add
Suggested fields: block ID, customer, valid-from/to, volume (runs or hours), unit price, lump-sum price, remaining quantity, billing mode (prepaid/monthly), cost centre, internal reference. Add an external reference field for booking IDs from x25pronto.
Technical interfaces: API vs CSV import
API: Best for real-time sync of consumption, bookings and remaining balances. Check auth (OAuth2/API keys), endpoints for blocks, booking events and webhooks for consumption notifications. CSV: Good for scheduled bulk updates. Define a standard column layout (block ID, date, consumed units, booking ID, cost centre) and automate uploads with scripts or ETL tools.
Accounting: posting and invoice reconciliation
Define standard accounts for initial block booking (e.g. deferred revenue or prepayments) and for consumption postings (revenue or expense). Reconcile invoices against: customer contract, block reference, service period and recorded usage. Use a reconciliation sheet with one line per call and columns for date, service, unit price, total amount and remaining units.
Reporting & KPIs for finance and operations
Key metrics: consumption per customer, remaining blocks, cost per unit, utilisation by cost centre, reorder forecast. Build dashboards in your BI tool (Power BI, Tableau) showing monthly trends, top customers and alerts for low balances.
Templates and recommended processes
Provide: 1) CSV import template with sample rows; 2) monthly reconciliation template for accounting; 3) API endpoint spec with sample requests/responses. Processes: daily or event-based consumption sync, monthly invoice reconciliation, quarterly contract review. Assign roles: ERP admin, accountant, operations contact.
Frequently asked questions
How often should consumption be synced?
For operational visibility use daily or event-driven (webhook) sync. For pure billing, weekly or monthly updates may be sufficient.
What does accounting need for reconciliation?
At minimum: contract/block ID, service date, consumed units, unit price, total amount, cost centre and payment reference. These fields ease automated matching.
Can I import blocks by CSV if no API exists?
Yes. Define a clear CSV schema and automate uploads via script or ETL. Ensure unique block IDs and consistent date formats.
How do I treat remaining blocks in accounting?
Remaining blocks can be held as deferred revenue (liability) or as a prepaid asset until consumed. Confirm the approach with your accountant.