The e-document is born from the invoice itself
E-invoices, e-archive invoices and e-waybills are generated as UBL-TR from the invoice and shipment in the ERP; sending goes through the private integrator you already use.
E-document list: type, number, date and status
From generation to sending, complete
Your accounting and shipping team’s e-document tools, on one screen.
E-document detail: profile, document number and amounts
E-invoice and e-archive
UBL-TR 2.1 documents from the sales invoice; basic and commercial invoice and e-archive profiles.
Buyer validation
Tax and national ID numbers are validated with their checksum BEFORE a document number is used; export buyers are supported.
Numbering per company
Each company uses its own series and sequence; no gaps within a series.
Integrator connection
Each company works with its own private integrator; credentials are stored encrypted and never shown on screen.
Test and live mode
In test mode documents don’t reach the tax authority and a warning band is shown; without a configured connection, sending is rejected rather than faking success.
Stock transfer detail: loaded units and e-waybill panel
E-waybill
E-waybills for customer shipments and transfers between your own sites, with a packing list of the SSCCs of loaded cartons and pallets.
Five steps from invoice to document
The document is generated from the ERP record; nothing is exported to a second program.
Invoice
A sales invoice is ready for e-documents the moment it is posted.
- Lines, taxes and amounts come from the invoice
- The profile is chosen by recipient
- No second document for the same invoice
Source sales invoice
Check and number
The buyer is validated before a document number is used.
- Checksum validation of tax and national ID numbers
- An invalid buyer uses up no number
- The number comes from the company’s own series
Customer list: tax number column
Sending and status
The document is sent through the company’s integrator and its status is queried.
- Integrator and credentials per company
- In test mode nothing reaches the tax authority and a warning is shown
- Status queries run per company in bulk
Integrator in company settings: test/live badge and warning band
E-waybill
The waybill document is generated at goods issue.
- Delivery lines and batches
- SSCC list of loaded cartons and pallets
- Document as UBL-TR DespatchAdvice
Delivery detail: cartons (SSCC) and e-waybill panel
Between your own sites
Transfers between plants leave with a waybill too.
- A separate series with its own sequence
- Same tax number for sender and receiver, different addresses
- No document at planning; only when goods leave
Stock transfer list: route, status and quantity received
Which record each e-document comes from
The same record in every module; no interim transfers.
- Sales & DistributionThe sales invoice becomes an e-invoice or e-archive invoice; the shipment produces an e-waybill.
- Finance & AccountingThe document is generated from the posted invoice; amounts come from the same record.
- Warehouse ManagementThe packing list comes from the SSCCs of loaded cartons and pallets.
- Procurement & InventoryE-waybills are generated for stock transfers between your own sites.
About e-invoices and e-waybills
The most common questions before going live.
No. Documents are generated in Hadron as UBL-TR and sent through the private integrator you use; the connection is set up for your integrator during onboarding.
Yes. The integrator connection is per company; because the tax obligation belongs to the tax number, each company works with its own contract and credentials. Number series are per company too.
No. The buyer’s tax or national ID number is checksum-validated before a document number is used; if invalid, no document is generated and no number is used up.
No. In test mode documents don’t reach the tax authority and a warning band is shown. If no integrator is configured, sending doesn’t fake success; it is rejected explicitly.
Yes. An inter-plant transfer generates an e-waybill in a separate series when the goods leave; sender and receiver share a tax number with different addresses. The packing list comes from the loaded units.
An incoming e-invoice can be parsed, matched to its supplier and linked to the supplier invoice approval flow. An inbox screen and automatic pulling from the integrator aren’t available yet; they are on our roadmap.
See Hadron with
your own data
In a 30-minute demo, we set up your processes on Hadron together.