ZATCA E-Invoicing for Logistics Companies: Practical Guide

ZATCA e-invoicing logistics defines the electronic billing rules followed by transport, freight, warehousing, distribution, and delivery companies in Saudi Arabia. Businesses must generate structured tax invoices, credit notes, and debit notes through compliant systems. Under ZATCA Phase 2, invoicing solutions connect with the Fatoora Platform to exchange invoice data, improve billing accuracy, reduce manual errors, and support stronger logistics invoicing compliance across complex operations and customer transactions securely and efficiently.

What Is ZATCA Fatoora and How Does It Apply to Logistics Companies?

ZATCA Fatoora is the electronic invoicing platform used to receive, validate, clear, and record invoice data. Companies reviewing e-invoicing Saudi Arabia requirements must understand the following invoice workflows:

Standard Tax Invoices

Standard tax invoices are generally used for B2B and B2G transactions. They must pass through the ZATCA clearance process before being presented to the buyer:

• Invoice generation: The compliant invoicing solution creates a structured XML invoice containing the supplier, buyer, service, pricing, tax, and invoice-total information.
• ZATCA submission: The system sends the generated XML document to the Fatoora Platform through the appropriate clearance API before issuing it to the buyer.
• Technical validation: ZATCA reviews the document against its required data, formatting, security, and calculation rules to identify missing or invalid invoice information.
• Invoice clearance: When the document meets the applicable requirements, ZATCA clears the invoice and returns the approved electronic record to the taxpayer.
• Buyer delivery: The logistics company can then provide the cleared invoice to the corporate or government customer in the required readable electronic format.

Simplified Tax Invoices

Simplified tax invoices are generally used for B2C transactions. They are presented to the customer first and then reported electronically to ZATCA:

• Invoice creation: The compliant solution generates the simplified invoice using the customer, service, pricing, tax, and payment details recorded for the transaction.
• QR-code inclusion: The system adds the required Phase 2 QR code and relevant technical elements before the invoice is presented to the customer.
• Customer issuance: The business provides the compliant invoice directly to the consumer after completing the delivery, transportation, or related logistics service.
• Invoice reporting: The structured XML document is reported to the Fatoora Platform within 24 hours of issuing the simplified invoice.
• Response recording: The invoicing solution stores the validation response returned by ZATCA for compliance monitoring, correction, and future audit purposes.

How Fatoora Applies Specifically to Logistics

Logistics invoices often combine several operational services within one transaction. Each service should appear as a clearly described invoice line with its relevant value and tax treatment:

• Domestic transportation: The invoice should describe the local transport service, related route or shipment, agreed charge, taxable amount, and applicable VAT treatment.
• Freight forwarding: Freight coordination and forwarding charges should be listed separately from transportation, customs, storage, or other third-party service costs.
• Warehousing and storage: Storage fees should identify the provided service, relevant period, pricing basis, applicable discounts, and calculated VAT amount.
• Handling and loading: Loading, unloading, terminal handling, and similar operational activities should be separated to create a clearer financial breakdown.
• Last-mile delivery: Final-delivery charges should be connected to the relevant customer order, delivery record, location, or completed service when applicable. Last mile delivery software can provide the delivery records and completion data needed to support accurate billing.
• Customs-related services: Customs-clearance service fees should be distinguished from government duties or other amounts paid on behalf of the customer.
• Additional operational charges: Waiting time, approved surcharges, special handling, or additional transport services should be itemized rather than included under a general description.

What Are the ZATCA Phase 2 Requirements for Logistics Invoicing?

The Integration Phase requires affected taxpayers to connect their compliant invoicing solutions with the Fatoora Platform. Each company should follow its official ZATCA notification and assigned integration deadline:

1. Mandatory Technical Integration

Phase 2 introduces technical requirements that allow invoice data to be exchanged securely between the taxpayer’s invoicing environment and ZATCA:

• API connectivity: The invoicing solution must communicate with the Fatoora clearance and reporting APIs to submit invoice data and receive validation responses.
• Solution onboarding: Each applicable electronic invoice generation unit must complete onboarding and obtain the Cryptographic Stamp Identifier required for production use.
• Structured invoice format: Invoices must be generated as structured XML documents or as PDF/A-3 documents containing an embedded XML invoice.
• XML submission: The structured XML version is submitted to ZATCA for clearance or reporting rather than uploading a standard PDF invoice.
• Invoice identification: The system should generate UUIDs, invoice references, issue timestamps, and continuous counter values for traceability and validation.
• Security controls: Invoice hashes, cryptographic elements, and anti-tampering controls should prevent or reveal unauthorized changes to electronic invoice records.

A transport management system can transfer completed trips, transportation services, customer details, and approved charges directly into the invoicing workflow without repeated manual entry.

2. Logistics Operational Data

ZATCA applies the same general electronic-invoice standards across industries. Logistics platforms provide the operational information required to describe and support each invoiced service:

• Shipment or order reference: This reference connects the financial invoice to the customer order, transport request, or shipment created in the operational system.
• Trip information: The invoice workflow may retain the related trip number, route, service date, and transportation status for reconciliation purposes.
• Vehicle or driver reference: A fleet management system can maintain internal vehicle and driver references that help operations and finance teams identify the resources used to complete the relevant transport service.
• Container or cargo details: Container numbers and consignment references can improve transparency when invoices relate to freight or cargo movements.
• Bill of lading: The bill-of-lading number may be stored as an operational reference when the transaction involves sea, air, or freight-forwarding services.
• Pickup and delivery records: Locations, delivery dates, and proof-of-delivery information can confirm that the billed logistics service was completed.
• Bayan reference: A Bayan document or cargo-manifest number may be retained when used by the business, but it is not automatically a mandatory ZATCA field.

3. Different B2B and B2C Workflows

Standard and simplified invoices follow separate validation processes. The invoicing solution must identify the transaction type and direct it to the correct workflow:

Standard Invoices for B2B and B2G Services

The standard-invoice clearance workflow usually includes the following steps:

• Generate the invoice: The compliant solution creates the standard invoice as a structured XML document using verified customer and service information.
• Submit for clearance: The XML invoice is transmitted to the Fatoora Platform through the clearance API before being presented to the buyer.
• Receive validation: ZATCA validates the document and returns the relevant clearance, warning, or rejection response to the invoicing solution.
• Store the cleared XML: The approved electronic invoice and related response are stored within the company’s financial or document-management environment.
• Present the invoice: The logistics company provides the cleared invoice to the corporate or government customer in an accepted readable format.

Simplified Invoices for B2C Services

The simplified-invoice reporting workflow usually includes the following steps:

• Generate the invoice: The system creates the simplified invoice after completing the relevant delivery, courier, transportation, or consumer logistics service.
• Apply the signature: The onboarded solution signs the structured invoice using the Cryptographic Stamp Identifier associated with the invoicing unit.
• Add the QR code: The compliant Phase 2 QR code is generated before the invoice is provided to the customer.
• Present the invoice: The customer receives the invoice at the point of sale or after completing the relevant logistics service.
• Report the XML: The system reports the structured invoice to ZATCA within the required 24-hour reporting period.
• Record the response: Validation results, warnings, or reporting errors are stored for monitoring and corrective action.

4. Advanced QR Code Requirements

QR-code handling in Phase 2 differs depending on whether the transaction requires a standard or simplified tax invoice:

• Standard invoice QR code: ZATCA adds the required QR-code information during the clearance process before returning the cleared electronic invoice.
• Simplified invoice QR code: The taxpayer’s onboarded invoicing solution generates the QR code before presenting the invoice to the consumer.
• Validation support: The QR code contains technical and invoice-related information that supports basic electronic validation of the issued document.
• XML record requirement: The QR code does not replace the complete structured XML document that must be generated, stored, cleared, or reported.

What Information Must a ZATCA-Compliant Logistics Invoice Include?

A compliant invoice combines ZATCA’s technical and tax requirements with an accurate description of the transport, delivery, freight, or warehousing service. The exact fields depend on the invoice type:

1. Mandatory ZATCA Technical Elements

The technical elements create a traceable and secure electronic record for each invoice. Depending on the document type, they may include:

• Universally Unique Identifier: A UUID is generated by the compliant solution to provide each electronic invoice with a separate technical identity.
• Invoice reference number: The commercial invoice number helps the company, customer, and finance team identify the document within normal business operations.
• Sequential counter value: The system maintains a continuous counter that supports invoice sequencing and prevents the reuse or resetting of previous values.
• Previous-document hash: Where required, the invoice includes a cryptographic reference that connects it to the previous electronic document in the sequence.
• Issue date and time: The XML document records when the invoice was generated and issued by the compliant invoicing solution.
• Invoice-type code: The system identifies whether the document is a standard invoice, simplified invoice, credit note, or debit note.
• Structured XML document: The invoice must be generated in the prescribed electronic structure for validation, clearance, reporting, and storage.
• Cryptographic elements: The applicable stamp or signature protects the integrity of the invoice and supports verification of its origin.
• Phase 2 QR code: The required QR code is added according to the workflow and technical requirements of the invoice type.
• Tax and invoice totals: The document includes taxable values, VAT amounts, discounts, line totals, and the final payable amount in the required fields.

2. Supplier and Buyer Information

Standard invoices require clear information about the supplier, buyer, and transaction. The main invoice details may include:

• Supplier information: The invoice should display the logistics provider’s registered legal name, business address, and VAT registration number.
• Buyer information: The corporate customer’s legal name, registered address, and VAT number should be included when required for the transaction.
• Invoice dates: The document should state the invoice issue date and the relevant supply date according to the transaction.
• Service description: Each line should clearly explain the transportation, delivery, warehousing, freight, handling, or related service provided.
• Taxable value: The invoice must show the value subject to VAT after applying any approved discounts or adjustments.
• VAT details: The relevant tax category, VAT rate, VAT value, and final invoice total should be calculated and displayed accurately.

An order management system can transfer verified customer, order, and service details into the invoice, reducing incorrect buyer information and repeated data entry.

3. Logistics and TGA Operational References

Operational references help connect the financial document with the completed logistics service. The company may include the following information:

• Shipment reference: The invoice can include the shipment number used by the logistics platform to identify the relevant cargo or delivery movement.
• Trip number: The trip reference connects the billed charge with the vehicle movement, route, or completed transportation service.
• Cargo or consignment number: This number helps identify the specific freight, goods, or consignment connected with the invoice.
• Bill of lading: The document reference may be included when the invoiced service relates to international freight or cargo transportation.
• Container number: Container information can improve reconciliation between freight operations, customer records, and the issued invoice.
• Customer order number: The order reference helps the buyer compare the invoice with the original service request or purchase order.
• Delivery confirmation: A proof-of-delivery or completion reference can confirm that the invoiced service was successfully performed.
• Bayan or manifest reference: The business may include this information as an internal or contractual reference when relevant to the physical shipment.

These details are generally operational references unless an applicable regulation, authority, or customer contract expressly requires them.

4. Financial Line-Item Breakdown

Each invoice line should describe one actual service instead of grouping unrelated charges under a general logistics description. A structured line may include:

• Service description: The invoice should clearly identify whether the charge relates to transportation, storage, delivery, loading, handling, or another service.
• Quantity and unit: The line may show the number of trips, shipments, pallets, storage days, kilometres, or other pricing units.
• Unit price: The agreed price for each service unit should be recorded before discounts, taxes, or additional charges are applied.
• Discount amount: Any approved commercial discount should be displayed clearly and deducted from the relevant taxable amount.
• Taxable value: The invoice line should show the amount on which VAT is calculated after applying the relevant adjustments.
• VAT category and rate: Each service must be connected to its applicable tax category and percentage based on the transaction.
• VAT amount: The calculated tax value should appear separately for each line or tax category as required.
• Exemption or zero-rate reason: Where applicable, the invoice should include the appropriate reason or code supporting the tax treatment.
• Line and invoice totals: Each service line should show its final value, while the invoice presents the combined subtotal, tax, and payable total.

Domestic taxable supplies generally follow the standard Saudi VAT rate of 15%. International transportation may qualify for zero-rating when the applicable conditions are met.

Customs duties, port charges, and reimbursed payments should be reviewed individually because electronic invoicing does not automatically place every reimbursed amount outside the scope of VAT.

How Can Freight Invoice Automation Improve Compliance and Accuracy?

Freight invoice automation generates invoices from confirmed operational data rather than requiring finance teams to recreate order, shipment, and pricing information manually. Modern enterprise logistics software can support the following processes:

1. Capture Data from Completed Operations

The transport management system collects approved billing information after confirming that the logistics service has been completed. The captured information may include:

• Customer information: Verified legal, billing, contact, and VAT details can be retrieved directly from the approved customer record.
• Order details: The invoice can inherit the order number, requested service, quantities, locations, and customer instructions from the original request.
• Completed trips: Only confirmed transportation activities can be transferred into the billing workflow, reducing invoices for cancelled or incomplete trips.
• Delivered quantities: The system can use actual delivered units, weights, pallets, or shipments instead of relying only on estimated values.
• Contracted rates: Approved customer rate cards can be applied automatically according to the service, route, vehicle, or pricing unit.
• Additional charges: Fuel surcharges, waiting time, handling fees, or other approved costs can be added after operational confirmation.
• Delivery confirmation: Proof-of-delivery records can trigger invoicing and demonstrate that the relevant logistics service was completed.

This automated transfer reduces differences between the final invoice, operational records, customer agreements, and completed delivery information.

2. Apply the Correct Invoice Workflow

Configured rules can direct each transaction to the correct ZATCA process according to the customer, invoice type, and document status:

• Standard invoice clearance: B2B and B2G invoices can be sent to ZATCA for clearance before being presented to the buyer.
• Simplified invoice reporting: B2C invoices can be issued to consumers and reported through the required workflow within 24 hours.
• Credit-note generation: The system can create a linked credit note when a previously invoiced value needs to be reduced or cancelled.
• Debit-note generation: Additional approved amounts related to an earlier invoice can be recorded through a compliant debit note.
• Rejection management: Rejected documents can be isolated to prevent users from presenting them as valid cleared invoices.
• Corrected resubmission: The system can create a corrected document with the required identifiers, sequence values, and updated information.

3. Validate Data Before Submission

Automated checks identify incomplete or inconsistent invoice data before the document reaches the Fatoora Platform. These checks may detect:

• Missing VAT numbers: The solution can flag B2B invoices that require a buyer VAT number but do not contain a valid value.
• Incomplete addresses: Missing supplier or customer address fields can be identified before generating the final invoice XML.
• Incorrect totals: The system can compare line values, discounts, taxable amounts, VAT calculations, and invoice totals for inconsistencies.
• Missing VAT categories: Each invoice line can be checked to confirm that it contains the configured tax category and treatment.
• Invalid XML fields: Technical validation can identify formatting, code, or mandatory-field errors before API submission.
• Duplicate references: The system can prevent the same shipment, trip, delivery, or order from being billed more than once.
• Pricing differences: Contracted rates can be compared with invoiced amounts to identify unauthorized or incorrect charges.

Automated validation improves accuracy but does not replace professional tax review when the underlying transaction has a complex VAT treatment.

4. Reconcile Orders, Deliveries, and Invoices

The system compares the operational and financial records before the invoice is finalized. This reconciliation may include:

• Customer order: The original service request confirms what the customer ordered, the agreed locations, quantities, and commercial terms.
• Completed trip: The trip record confirms which vehicle or carrier completed the service and records the actual route and operating details.
• Delivery record: Proof of delivery confirms the completion date, delivered quantity, recipient, and any reported exceptions.
• Final invoice: The billing document should reflect the completed operation, contracted rate, approved adjustments, and correct tax calculation.

Differences in weight, distance, delivered quantity, waiting time, or approved surcharges can be routed to the appropriate team for review before submission.

5. Protect Invoice and Audit Records

A compliant invoicing environment should retain a complete and traceable history of each electronic invoice. The system should:

• Detect unauthorized changes: Security controls should identify invoice records that have been modified outside the approved invoicing workflow.
• Maintain invoice sequences: Counter values and document references should be preserved without resetting, duplication, or unauthorized deletion.
• Store XML documents: Submitted, cleared, reported, rejected, and corrected XML files should remain accessible for future verification.
• Save ZATCA responses: Clearance, reporting, warning, and rejection responses should be linked to the relevant electronic invoice.
• Retain corrected records: Original documents and their related credit notes, debit notes, or corrected submissions should remain traceable.
• Maintain audit logs: The system should record relevant user actions, submission times, invoice statuses, errors, and technical responses.

Build a Connected Logistics Billing Workflow with Tachyon

Tachyon brings orders, shipments, trips, vehicles, drivers, deliveries, warehouses, and operational charges together within one digital logistics platform.

Its TMS, OMS, FMS, WMS, YMS, Bullet, and Insights modules can provide the verified operational data required to prepare accurate billing records and reduce duplication between logistics and finance teams.

Tachyon can supply this logistics information to an approved ERP or compliant invoicing engine. The connected solution should complete XML generation and ZATCA submission unless a verified direct integration is available.

Request a Tachyon demo to organise shipment data, reduce manual billing work, and build a more controlled logistics invoicing workflow.

How Can Logistics Software Integrate with the ZATCA Fatoora Platform?

Integration connects verified logistics information with the approved invoicing component responsible for generating and submitting electronic invoices. The workflow should preserve ZATCA’s technical, validation, sequencing, and security requirements:

1. Define the System of Record

The company should identify which platform owns and maintains each category of data used throughout the logistics and invoicing process:

• Customer and contract data: The selected system should maintain approved customer details, VAT information, service agreements, and pricing conditions.
• Orders and service requests: Each logistics request should have an identifiable record containing the required service, locations, quantities, and customer instructions.
• Trips and shipments: The operational platform should retain the trip, shipment, carrier, vehicle, driver, and status information connected to each service.
• Delivery confirmations: Proof-of-delivery details should confirm when the service was completed and whether any exception affected the final charge.
• Pricing and surcharges: The responsible system should control contracted rates, approved additional charges, waiting fees, and other pricing adjustments.
• Tax configuration: VAT categories, tax rates, exemptions, and zero-rate reason codes should be managed within the approved financial environment.
• Accounting records: Posted invoices, receivables, adjustments, and customer balances should remain controlled by the relevant accounting or ERP solution.
• Invoice records: The compliant invoicing engine should maintain XML files, identifiers, hashes, statuses, and ZATCA responses.

2. Onboard the E-Invoicing Solution

Each applicable invoicing unit must complete the required Fatoora onboarding process before exchanging production invoice data with ZATCA:

• Start the onboarding request: The taxpayer initiates the process for the relevant electronic invoice generation unit through the Fatoora environment.
• Generate the OTP: The required one-time password is created and used to connect the invoicing unit with the onboarding process.
• Submit the certificate request: The technical solution sends the relevant certificate-signing request and device information for validation.
• Complete compliance checks: The invoicing unit is tested against the required invoice types, technical rules, and compliance scenarios.
• Obtain the production CSID: After successful onboarding, the unit receives the production Cryptographic Stamp Identifier required for live invoice processing.

3. Map Logistics Data to Invoice Fields

The integration transfers verified operational information into the appropriate electronic-invoice fields. The mapped information may include:

• Supplier details: The logistics provider’s legal name, address, VAT number, and other required registration information.
• Customer details: The buyer’s legal identity, address, VAT number, and customer reference where required.
• Service descriptions: Clear descriptions of transport, warehousing, delivery, handling, freight, or other invoiced logistics activities.
• Quantities and prices: Actual service units, contracted prices, and approved rates transferred from the operational or commercial system.
• Discounts and adjustments: Approved discounts or pricing corrections applied to the relevant invoice lines before tax calculation.
• Additional charges: Confirmed waiting time, handling fees, fuel surcharges, or other operational charges added to the invoice.
• VAT information: Applicable categories, rates, tax values, and supporting exemption or zero-rate codes when required.
• Operational references: Shipment, order, trip, container, delivery, or bill-of-lading references transferred for reconciliation.
• Invoice and supply dates: Relevant dates are recorded according to the service completion and electronic-invoice requirements.

4. Generate the Required Invoice Format

The compliant invoicing component transforms the mapped business data into the required electronic documents and technical records:

• Structured XML: The solution creates the XML document that is submitted to ZATCA for clearance or reporting.
• Readable invoice: A PDF/A-3 document with embedded XML may be created when a human-readable invoice copy is required.
• Invoice identifiers: The solution generates the UUID, commercial invoice reference, and other required document identifiers.
• Counter and hash values: Sequential counter values and invoice hashes are generated to support document security and traceability.
• QR-code elements: The required QR-code, cryptographic stamp, or signature elements are created according to the invoice type.

5. Route Standard Invoices for Clearance

Standard tax invoices must receive ZATCA clearance before they are presented to the corporate or government buyer:

• Submit the XML: The compliant system sends the standard invoice XML through the Fatoora clearance API.
• Wait for validation: The invoice remains within the clearance workflow until the system receives the ZATCA technical response.
• Record the result: Clearance, warning, or rejection information is stored against the relevant invoice and operational transaction.
• Present the cleared invoice: Only the successfully cleared invoice is provided to the buyer as the valid tax document.

6. Route Simplified Invoices for Reporting

Simplified invoices are presented to customers before being reported to ZATCA through the relevant API workflow:

• Generate and sign the invoice: The onboarded solution creates the structured document and applies the required cryptographic elements.
• Add the QR code: The compliant QR code is embedded before the invoice is presented to the consumer.
• Present the invoice: The customer receives the invoice after completing the relevant service or transaction.
• Report the XML: The structured document is submitted to ZATCA within the required 24-hour period.

7. Store Responses and Manage Exceptions

The company should retain complete invoice records and establish a clear workflow for warnings, rejections, and corrected submissions:

• Submitted XML files: Every electronic document sent to ZATCA should remain stored and connected to its operational transaction.
• Cleared invoices: Approved standard invoices and their related ZATCA responses should be retained for customer service and audit purposes.
• Validation responses: API responses should be recorded to confirm whether each invoice was accepted, cleared, reported, or rejected.
• Warning messages: Technical warnings should be monitored to prevent recurring issues and improve future invoice quality.
• Rejection messages: Rejected documents should be isolated and directed to the responsible finance or technical team.
• Resubmission records: Corrected documents and their new identifiers should remain connected to the original rejected submission.
• Credit and debit notes: Adjustments should be linked to the original invoices to maintain a complete financial history.
• Audit logs: User activity, submission dates, invoice statuses, errors, and system responses should remain available for review.

Well-designed logistics integrations connect operational data with compliant invoicing systems without allowing users or connected platforms to bypass ZATCA controls.

Connect Logistics Operations with Tachyon

Tachyon centralises operational information from transportation, orders, fleets, deliveries, warehouses, and yards within one connected platform.

Verified information can then be transferred through APIs to the company’s ERP or approved e-invoicing solution, helping reduce duplicate records, disconnected processes, and manual billing errors.

Talk to Tachyon about building a connected logistics and invoicing workflow designed to support scalable operations in Saudi Arabia.

Frequently Asked Questions About ZATCA E-Invoicing Logistics

1. Do all logistics companies need to join ZATCA Phase 2?

Only companies included in a ZATCA implementation wave must integrate by their assigned deadline.
Each company should follow the official notification received from ZATCA.

2. Can logistics companies submit PDF invoices to Fatoora?

The compliant solution submits structured XML files for clearance or reporting.
PDF/A-3 may be used as a readable copy when it contains the embedded XML.

3. Is a Bayan waybill number mandatory on every ZATCA invoice?

A Bayan number may be added as an operational or contractual reference.
It is not a universal mandatory ZATCA field for every logistics invoice.

4. What happens when ZATCA rejects a logistics invoice?

The invoice should be reviewed and corrected before a new document is submitted.
A rejected standard invoice must not be presented to the buyer as cleared.

5. Can logistics software automate ZATCA invoice preparation?

Yes, it can transfer verified order, shipment, pricing, and delivery data to the invoicing system.
The compliant billing solution must still generate and submit the required electronic invoice.