Completed transport jobs not invoiced: how to find overlooked records

Define the control population before looking for missing invoices

A transport job is completed when the operational condition selected by the company has been met and can be verified: confirmed delivery, a consistent final status, proof of delivery received or another approved event for the relevant flow. A planned order, a screen merely marked “closed” or a date in the past may not be sufficient. The definition should specify accepted sources, excluded statuses and the date used to assign the record to a control period.

A job becomes billable when the commercial and documentary conditions required for invoicing have been met. It may be completed but not yet billable because a document is missing, a price requires validation or an exception awaits a decision. Conversely, a cancellation may involve no completed service yet still require treatment under an applicable rule. It should follow its own path rather than being mixed into the completed-job population.

Reconcile two populations without forcing artificial matches

The completed-service period and invoice period do not always align. A delivery at month-end may belong to an invoice issued the following month. The control therefore needs an explicit reference date, a tolerance window justified by the process and a cut-off date. Without them, the newest records will generate false missing-invoice alerts by design.

1. 01
   Build the completed population

   Extract records that meet the approved definition, including identifiers, dates, customer, sites, status and supporting evidence.

2. 02
   Build the invoiced population

   Collect invoices and their lines, including relevant credit notes or corrections, across a window that reflects the actual invoicing cycle.

3. 03
   Normalize matching keys

   Compare transport, order, route, invoice and customer references without discarding the original source values.

4. 04
   Find candidate matches

   Allow one invoice to cover several jobs and one job to generate several lines. Strict equality between two identifiers is not always the right test.

5. 05
   Classify unmatched records

   Review the record, documents, consolidation rule, period and history before assigning a status.

6. 06
   Verify the outcome

   Read the resulting state in the invoicing system and retain evidence of the classification or completed action.

Reconciliation table: five statuses that lead to action

This is a working template to adapt. Labels, conditions and responsibilities should be validated with synthetic data or approved anonymized extracts before use. A record may change status when a document arrives or a consolidated invoice is issued; its history should remain readable.

Handle consolidation, timing differences and cancellations without false positives

Consolidation changes the unit of comparison: several transport jobs may appear under one line, statement or periodic invoice. The control must reconstruct that composition and confirm the inclusion of every record. Simply comparing the number of jobs with the number of invoice lines would surface missing items that do not exist and could lead to duplicate invoicing.

A timing difference is acceptable only when it has an identifiable rule or decision, a target period and a follow-up date. Otherwise, “invoice later” becomes an ownerless state. A cancellation must likewise be connected to its timeline: no service, partial performance, potential charges and the applicable rule are separate questions. The absence of an invoice may therefore be normal, require review or call for a specific line, but it supports no conclusion before classification.

• retain the original level of detail and the composition of each batch;
• distinguish the completion date, billability date and issue date;
• detect credit notes and reissued invoices so a correction is not counted as a new invoice;
• place cancellations and partially performed services in an explainable status;
• run the check again on the scheduled date instead of permanently closing a deferred record.

Create a work queue that the team can actually act on

The useful output is not a raw list of unmatched identifiers. Each queue item should show its provisional status, completion evidence, matches already attempted, observed blocker, next action, owner and due date. Older records or those approaching an internal deadline may receive higher priority, but an estimated amount must not be presented as a confirmed receivable.

Vigilo can connect events, documents, rules and invoicing states, prepare the reconciliation and present ambiguous cases to the team. The company still configures and validates the scope, sources, billability rules and permitted actions. An invoice creation or correction is only complete after its actual state has been checked in the relevant system.