Annex OrbisELD integration guide
Connecting an external ELD provider
A driver experience and an ELD provider can be separate products. A connection must be agreed, authorized and tested as a complete configuration before it is used for ELD operations.
Two directions, clear responsibilities
Annex Orbis and General ELD can connect for limited manual driver records. General ELD is a separate product, not an Annex Orbis-owned service. A complete operational ELD integration depends on the provider’s supported interface, the parties’ agreement and testing of the full configuration.
In the other direction, the General ELD backend may support qualified driver applications from other companies. See General ELD’s driver-app guide and homepage for its approach.
General ELD’s driver-app guide · General ELD homepage
General Software Company LLC and Annex Orbis Inc. are separate companies with separate contracts. General provides backend software and registration assistance; its clients are the registering ELD providers for their offerings.
What works today
After a company connection and individual driver confirmation, a driver can review their own General ELD manual records, enter a current manual duty status, add annotations and certify a day in Annex Orbis. Historical corrections and provider administration remain in General ELD. This does not switch the operational recorder or enable automatic engine recording, hours-of-service calculations or electronic inspection transfer.
A General ELD administrator creates a one-time company connection key. An Annex organization owner or role administrator enters it in ELD settings to link the company, and can check or remove the connection there. The key proves company connection setup; it is not a driver sign-in or permission to access driver records.
Connect your driver account
Ask your General ELD administrator to set up your driver account and invite you to claim it. Sign in to General ELD and claim your own driver account. In “Connect Annex Orbis”, choose the connected company and create a one-time invitation; it is shown once and expires in 10 minutes.
Sign in to your own Annex Orbis account, open General ELD driver records, paste the invitation and select “Connect my account”. Return to General ELD, refresh your links, and confirm that the displayed Annex account and membership belong to you. Refresh in Annex to open your records. Either side can revoke the link.
Current status entries use the time you provide and must reach General within five minutes. Make backdated entries and historical corrections in General ELD. Device recording, HOS calculations, electronic transfer and offline recording are not enabled by this link.
Open General ELD · Open General ELD driver records in Annex Orbis
What an operational integration must establish
Before a driver relies on a connected ELD, the parties must agree on a supported, complete and tested configuration. The provider retains the authoritative log and its edit workflows. The complete solution must deliver the driver’s required review, edit, annotation and certification functions, including appropriate driver review of proposed changes.
Each driver link is separate from the company connection and can be revoked. Additional capabilities, such as device capture, hours-of-service calculations and inspection transfer, require an agreed and tested complete configuration; they are not enabled by the manual driver link.
Registration and technical guidance
The registering provider is responsible for its offering, including registration and self-certification. FMCSA’s white-label FAQ explains registration identifiers and says branding partners may use certification performed by the white-label company. Self-certification is not FMCSA approval.
The provider portal offers registration, testing and technical resources.