Regional waste operators
Subscriber accounts, billing services and dispatch. Connect contracts and payments to sites, routes and confirmed collections.
Review the operator’s taskExplore the scopePreserve ownership of each source: billing, dispatch and contractor data.
Accounts, addresses and contracts. Data history, ownership changes and duplicate handling.
Accounts, addresses, service locations and contracts for individuals and organisations. Handle ownership changes, duplicate merging and the history of source data.
Billing exchange: periods, arrears and documents. The process owner provides calculation rules.
Exchange with the existing billing system: periods, approved calculation parameters, balances and documents. The billing process owner supplies the calculation rules.
Sites, schedules and route assignments. Planned and actual collections, with deviation reasons.
Mapped container sites, schedules, route assignments and vehicle events. Compare planned and actual collection; deviations have a reason and an owner.
Charges, payments, requests and documents. Subscribers see their account and resolution history.
Charges, payments, requests, documents and notifications. Customers see their own account and history; staff see the data needed to respond and the action outcome.
A vehicle coordinate alone does not prove collection. Define the events and records required to accept a completed assignment.
Sites, containers and service locations have separate identifiers. Changes must preserve route history.
Agree the evidence: crew record, photo, weighing operation or equipment event. Incomplete evidence goes to review.
Preserve the original event time if connectivity is lost. After reconnection, match it to the assignment and flag inconsistencies.
Billing, payment acceptance and collection control are checked separately. A status in one process should not substitute for the outcome of another.
| Source / scope | What we define | Outcome |
|---|---|---|
| Billing system / 1C | Accounts, contracts, charges and adjustments | Reconciled balance and document history |
| Payment provider / bank | Payment identifiers, statuses, refunds and registers | Reconciliation with the customer account |
| GLONASS/GPS and equipment | Positions, events, weight and task records | Verifiable completion record |
| GIS Housing — where applicable | Information within organisation functions and authority | Format and acceptance-result validation |
Choose a service area and operating period. Check customer data, billing and route events before expanding the scope.
Collect the contract model, billing rules, site registers and telemetry documentation. Identify duplicates and unmatched locations.
Define identifiers, reference-data owners and update rules. Agree collection evidence and payment reconciliation.
Check routine and exceptional cases: missed trip, wrong site, duplicate payment and billing adjustment.
Provide instructions for dispatch, billing and support teams. Expand after the pilot reconciliation is approved.
Yes, where the required interfaces are available. We check configuration, versions, restrictions and its role as the billing source.
Check the telemetry supplier, data rights and event format. Agree transmission rules and responsibility for data quality.
Scope depends on the organisation’s functions and task. Check applicability, registration, authority and current formats; define this connection separately.
First reconcile identifiers, addresses, contracts and balances. Prepare a control sample, discrepancy report and switch-over plan.
Tell us about the billing system, service area, vehicles and the process that needs manual reconciliation. We will start there.
Review the operator’s task
