A clear path from load to settlement.

Set up your workspace

Sign in to your own account. Open Settings to enter your company’s invoice details. Add brokers and drivers before entering loads. Your signed-in account controls access to its records.

Import or enter loads

Settings accepts your weekly Excel format. Read the preview, choose whether to skip or overwrite matching Load IDs, then approve the exact proposed values. Paid status never invents a receipt. Source Driver Pay, including zero and 777, remains unchanged unless you approve a correction. Recent Imports lists completed batches. Undo Import checks for later changes before undoing a batch.

Import failures restore the device copy. Cloud writes are separate batches, so an interrupted import may need review.

Review discrepancies

Needs Review stores warnings and your resolution notes. Correcting a value leaves its warning open until you Resolve or Ignore it. Reopen is available when another review is needed.

Load → Validation compares Imported, Working and Approved values. Suggested fee calculations require explicit approval. Opening the app never applies these suggestions.

Record broker payments

Open a load and select Broker Payment to add or edit actual payments. Keep partial payments separate. Check the method, date and reference. The invoice price and Driver Pay are separate values; a full gross payment can legitimately exceed Driver Pay.

Approved accounting values preserve a separate snapshot. Unlocking or re-approving that snapshot requires confirmation.

Review a driver’s week

Weekly Earning shows gross, dispatch, insurance, LogBook, COD, deductions and net. On a phone, use settlement cards and open Loads and details. On the Load’s Driver Settlement tab, the period follows that load’s delivery or pickup week.

Paid/Confirmed settlement status records the driver payment workflow. It does not create a broker receipt.

Follow the history

Audit Log shows recent cloud changes and their before/after values. Load → History includes its load, payment and warning events. Future events record the authenticated actor; older events may show “Not recorded.”

Protect and recover your books

Daily cloud archives run at 02:15 Tbilisi time with 14 daily copies retained. They capture cloud records even when the app is closed. Download JSON for a copy outside the database; device edits that have not synced need a device backup too.

Recovery previews show current and proposed changes. Approve the exact changes before applying them. A safety snapshot is created first. Recovery merges records and keeps cloud-only records; concurrent changes are deferred for a fresh review.

Use it on your phone

On iPhone, open the app in Safari, choose Share, then Add to Home Screen. On Android, use the browser’s Install or Add to Home Screen option. Cloud updates require a connection. Check the sync status before closing the app.

If sync fails, pending edits stay on the device. Reconnect and retry; download a device backup if browser storage reports an error.