Published October 9, 2026
A scanned bill of lading becomes useful eBOL data when its information is captured, checked against the carrier’s rules, mapped into the agreed API structure and accepted by the receiving workflow. Reading the document is only the first step. A missing account reference, duplicate shipment identifier or rejected submission still needs an owner.
ARDEM connects document automation with managed validation and exception handling. This guide explains how to plan the path from BOL receipt to a defined billing handoff, whether you run an LTL carrier operation or build the technology that supports it.
Understand eBOL | Follow the workflow | Use the readiness checklist | Review integration questions
What is the NMFTA eBOL standard?
The National Motor Freight Traffic Association (NMFTA), through its Digital LTL Council, publishes an electronic bill of lading API standard for exchanging LTL shipment information. Its official eBOL documentation describes the common data framework and implementation guidance for carriers, shippers, third-party logistics providers and technology providers.
A scanned BOL is an image of a document. An eBOL API exchange uses structured shipment data. Converting one into the other requires more than saving the image as a different file type.
Start with the receiving carrier’s supported standard version, interface documentation and business rules. NMFTA lists LTL and full-truckload standards separately; do not assume one implementation covers every freight mode or API.
How does a BOL-to-eBOL workflow work?
1. Define the input and the completion event
Identify how BOLs arrive, which document types are in scope and where completed information must go. Include representative scans, digital files, multi-page records and difficult examples. Agree whether completion means validated data, receiving-system acceptance, a completed billing record or an issued invoice.
2. Capture information without inventing missing values
Document automation can extract the required information. Review unclear handwriting, incomplete pages and conflicting values before they move forward. Preserve the connection to the source document so a reviewer can investigate a field rather than guess.
3. Apply carrier-specific validation
Define checks for shipment references, account matching, required addresses, billing terms and duplicate records where relevant. Normalization should follow approved rules. A required value that cannot be established belongs in an exception queue, not in an apparently complete record.
4. Map the record into the agreed API structure
Document how each source field maps to the receiving system, including required and optional fields, permitted values and formatting. Confirm the supported schema and test environment. A correctly formatted message can still contain the wrong business information, so schema checks do not replace operational validation.
5. Handle rejected and uncertain submissions
Define how the workflow records successful acceptance, rejected data, unavailable systems and responses that require investigation. NMFTA’s eBOL implementation FAQs address bad-data rejections and implementation-specific errors. The operating design should specify correction, escalation and resubmission responsibilities, including how to avoid duplicate records when an earlier submission’s status is uncertain.
6. Complete the billing handoff
An accepted eBOL is not automatically an issued invoice. Rating, additional documentation, customer requirements and approvals may sit further downstream. Keep pending and rejected items separate from completed work, and verify the endpoint the engagement is responsible for delivering.
7. Review production performance
Review accepted records, turnaround, corrections, backlog and unresolved exceptions together. Test approved changes against difficult documents as well as routine ones. An operating review should identify recurring causes of delay and the action needed to address them.
Where does automation stop and managed review begin?
Use automation for repeatable capture and configured checks. Use trained review where information is missing, inconsistent or requires judgment. Your organization retains pricing policy, business decisions and approvals unless specific operational authority is separately agreed.
Illustrative exception: A scan contains a legible shipment reference but no reliable bill-to account. The reviewer checks the approved reference source and escalates an unresolved match to the designated owner. The record remains pending until the required information is established. This example describes a workflow decision, not a customer result or a promised turnaround.
BOL-to-eBOL implementation-readiness checklist
Use these questions to prepare an operations and technology working session:
- Documents: Which inputs, image qualities and document variations must the workflow handle?
- Destination: Which TMS or billing system receives the data, and what event confirms acceptance?
- Interface: Which standard version, endpoint, authentication method and test environment are approved?
- Mapping: Which fields are required, which are optional, and what formatting rules apply?
- Reference data: Who supplies and maintains account, shipment and customer-rule information?
- Exceptions: Who researches missing data, makes business decisions and verifies corrections?
- Resilience: How are rejected submissions, outages, uncertain responses and duplicates handled?
- Capacity: What are the normal volumes, peak arrival patterns, cutoffs and coverage needs?
- Controls: What access, retention, change-control and review-evidence requirements apply?
- Acceptance: Which representative and difficult test cases must pass before production expands?
How should BOL-to-billing speed be measured?
Agree the start and completion events before comparing turnaround claims. Document receipt, field extraction, API acceptance and invoice issuance measure different portions of the process.
Report the measurement period, transaction count, typical and slower-case turnaround, and how exceptions or outages were treated. Track records completed without manual intervention separately from those requiring review. Do not substitute extraction speed for the time needed to complete a bill.
How ARDEM supports the operating workflow
ARDEM uses the NMFTA eBOL standard in working carrier workflows and combines its Transportation Manager technology with process design, integration work and managed delivery. The agreed scope can connect BOL capture, validation, exception handling and structured data delivery into the carrier’s systems.
For carrier operations, explore ARDEM’s managed BOL-to-billing approach. For technical evaluation or potential collaboration, review logistics technology and integration opportunities.
Published LTL workflow and billing and POD cases provide separate examples of managed operations. They should not be read as eBOL conformance tests or evidence of a universal automation rate.
Common BOL-to-eBOL integration questions
Does converting a scan to JSON make it a compliant eBOL?
No. The output must meet the agreed schema and carrier requirements. Required checks, receiving-system responses and unresolved exceptions still need to be handled.
Does this require replacing our TMS?
Not necessarily. Review the existing system’s permitted interfaces, access and acceptance requirements first. ARDEM designs the engagement around the approved environment rather than assuming a TMS replacement.
Can a TMS provider work with ARDEM?
ARDEM welcomes discussions about combining a provider’s platform or integration offering with document processing and managed exception handling. The customer workflow, interfaces, responsibilities and commercial arrangement must be defined together.
Is eBOL acceptance proof that billing is complete?
No. It confirms only the acceptance represented by the receiving system’s response. A completed billing record or issued invoice requires its own verification when included in the engagement.
Put the eBOL standard to work in your billing operation.
Bring the documents, systems and exception patterns your team works with today. ARDEM can help define a practical starting scope and the checks needed for a controlled rollout.
Discuss your BOL-to-billing workflow
For a broader business evaluation, read Freight Invoice Automation: AI-Powered Document Processing. For supporting delivery records, explore proof of delivery processing.