5 min read

Freight Invoice

Name: DocuRift Document Extraction
Brand: DocuRift
Price: 4 INR
Availability: InStock

Extract structured data from freight invoices including carrier details, shipping parties, itemized charges, and total amounts.

Overview

The Freight Invoice document type enables automated extraction of billing information from freight and shipping invoices. These documents are issued by carriers, freight forwarders, and logistics providers to bill for transportation services.

DocuRift can process freight invoices from:

Trucking companies (LTL and FTL carriers)
Ocean freight forwarders
Air cargo carriers
Intermodal logistics providers
Third-party logistics (3PL) companies

Extracted Fields

| Field | Type | Description | |-------|------|-------------| | invoiceNumber | string | Unique invoice identifier | | date | string | Invoice date (ISO 8601 format) | | carrier | object | Carrier/service provider details | | carrier.name | string | Name of the carrier company | | carrier.address | string | Carrier's billing address | | carrier.scac | string | Standard Carrier Alpha Code (if applicable) | | shipper | object | Shipper/sender details | | shipper.name | string | Name of the shipping party | | shipper.address | string | Shipper's address | | consignee | object | Consignee/receiver details | | consignee.name | string | Name of the receiving party | | consignee.address | string | Consignee's address | | charges | array | List of all line item charges | | charges[].description | string | Description of the charge | | charges[].amount | number | Amount for this charge | | freightCharges | number | Base freight charges | | fuelSurcharge | number | Fuel surcharge amount | | accessorials | array | Additional service charges | | accessorials[].type | string | Type of accessorial service | | accessorials[].amount | number | Charge for the service | | total | number | Total invoice amount |

Example Request

POST/v1/documents/process

curl -X POST 'https://api.docurift.com/v1/documents/process' \
  -H 'X-API-Key: your_api_key' \
  -F 'file=@freight-invoice.pdf' \
  -F 'documentType=freight_invoice'

Example Response

{
  "success": true,
  "data": {
    "id": "doc_fi_3e9c8b7a6d5f",
    "documentType": "freight_invoice",
    "result": {
      "invoiceNumber": "FI-2024-00892341",
      "date": "2024-01-15",
      "carrier": {
        "name": "FastFreight Logistics Inc.",
        "address": "1200 Transport Way, Dallas, TX 75201, USA",
        "scac": "FFLI"
      },
      "shipper": {
        "name": "ABC Manufacturing Co.",
        "address": "500 Factory Lane, Chicago, IL 60601, USA"
      },
      "consignee": {
        "name": "Retail Distribution Center",
        "address": "8800 Warehouse Blvd, Atlanta, GA 30301, USA"
      },
      "charges": [
        {
          "description": "Line Haul - Chicago to Atlanta",
          "amount": 1850.00
        },
        {
          "description": "Fuel Surcharge (18%)",
          "amount": 333.00
        },
        {
          "description": "Liftgate Delivery",
          "amount": 75.00
        },
        {
          "description": "Inside Delivery",
          "amount": 125.00
        }
      ],
      "freightCharges": 1850.00,
      "fuelSurcharge": 333.00,
      "accessorials": [
        {
          "type": "Liftgate Delivery",
          "amount": 75.00
        },
        {
          "type": "Inside Delivery",
          "amount": 125.00
        }
      ],
      "total": 2383.00
    },
    "confidence": 0.94,
    "processingTimeMs": 1890
  }
}

Field Definitions

invoiceNumber

The unique identifier assigned by the carrier to this invoice. This is essential for payment reconciliation and dispute resolution.

date

The invoice date in ISO 8601 format (YYYY-MM-DD). This is typically the date the invoice was generated, which may differ from the shipment date.

carrier

Details of the transportation service provider:

name: The legal name of the carrier company
address: The carrier's billing or headquarters address
scac: The Standard Carrier Alpha Code, a 2-4 letter identifier unique to each carrier (primarily used in North America)

shipper

The party that originated the shipment:

name: Company or individual name
address: Origin address from which goods were shipped

consignee

The party receiving the shipment:

name: Company or individual name
address: Destination address where goods were delivered

charges

A comprehensive array of all charges appearing on the invoice. Each charge includes:

description: Text description of the charge
amount: Numerical value of the charge

type: The service category (e.g., Liftgate, Inside Delivery, Detention, etc.)
amount: The charge for each service

Common accessorial types include:

Liftgate pickup/delivery
Inside delivery
Residential delivery
Detention/waiting time
Re-delivery
Notify prior to delivery

total

The sum of all charges on the invoice, including freight, surcharges, and accessorials.

Best Practices

Complete Invoice Submission: Include all pages of multi-page invoices. Supporting documents like BOLs attached to invoices help improve accuracy.
Carrier Format Recognition: DocuRift recognizes invoices from major carriers automatically. For custom or unusual formats, the first few invoices may have slightly lower confidence as the system learns.
Charge Categorization: The system automatically categorizes charges into freight, fuel surcharge, and accessorials based on common industry terminology.
Amount Validation: Verify that the extracted total matches the sum of individual charges. Minor discrepancies may indicate additional fees or taxes not explicitly itemized.
Date Handling: If multiple dates appear (invoice date, ship date, delivery date), DocuRift prioritizes the invoice date for the date field.
Integration with AP Systems: Use the extracted invoiceNumber as the primary key when integrating with accounts payable systems for three-way matching with POs and receiving documents.
Currency Handling: All amounts are extracted as numbers. If invoices contain multiple currencies, ensure your system handles currency conversion appropriately.