Skip to main content

Customer Billing Report

The report you hand to accounting: every billable line for one customer over a period, already resolved to GL codes.

Available to Sysadmin, Admin and Dispatch roles.

Running It​

Customer is required — the report is built per customer, and there is no all-customers view. Add a start and end date for the period you are invoicing.

Each row is one line item, flattened, carrying the customer, visit, asset, gate-in and gate-out times, dimension, billing code, quantity, unit, and any note. Rows come back ready to group by billing code for per-code and grand totals.

The Accrual Limit​

Assets still in the yard are not counted

The report reads completed visits only. An asset that is still on site has an open visit, and contributes nothing to the report until it leaves.

This matters most at month-end. A container that arrived on the 20th and is still in the yard on the 31st produces no storage line for that month, even though it has been accruing dwell for eleven days. Run the report mid-period and it will under-report every stay in progress.

Two ways to work with it:

  • Invoice on completed stays. The stay bills in whichever period it ends. Simplest, and self-correcting over time.
  • Check open stays separately. An asset's visit list shows its open visit with dwell accrued to now, so you can see what is outstanding — asset by asset.

There is currently no per-customer accrual view of open stays. If a mid-period accrual number matters to your close, raise it with your account manager — it is a known gap, not a misconfiguration.

Visit-Level Report​

Alongside the line-item report is a visit rollup — one row per visit rather than per line — with dwell, close reason, and a line-item count. Use it to sanity-check the billing report: an unexpectedly short dwell or a cluster of expired visits usually explains an odd invoice.

It can be filtered by customer, gate, asset type and date, and unlike the billing report the customer filter is optional.

Reading every page

The visit report is paged, and a page can come back empty while more rows remain. Keep following the next-page cursor until there is none rather than stopping at the first empty page — otherwise the report silently truncates. The UI does this for you; it matters if you are pulling the data directly.

Exporting​

Both reports download as Excel or CSV.

A spreadsheet export of the visit report requires both a start and end date. It reads the entire range rather than a page, so that a download never quietly stops at a page boundary.

Before You Invoice​

A short checklist that catches most surprises:

  1. Any UNMAPPED rows? Each is unbilled activity. See Billing Codes.
  2. Any expired visits? Departures that were not recorded at the gate — their dwell is an artefact, not a measurement.
  3. Any gate_out_without_gate_in exceptions? Arrivals bypassing the gate produce no visit at all, so they are invisible to this report rather than merely wrong on it.
  4. Anything still on site that should have left? Those stays bill next period, not this one.