Invoice Types

Invoice Generators select dispatches to be billed together in an invoice. There are four methods of selecting dispatches for inclusion:

If you have not yet read the Invoicing guide, or understand the postprocess workflow, go and read about those first.

Differential Invoices

A differential invoice gathers up all dispatches waiting at  Billing office  for invoicing, regardless of date.

Differential invoice

This will include:

Gather all of the
calls waiting in
the invoicing bucket

The aforementioned items are "in the invoicing bucket", meaning they have a balance owing and the customer needs to be billed. It makes no difference what date the dispatch was originally run; a differential invoice empties out the entire bucket.

It does NOT include dispatches still working their way through QA, because the QA process can change the service provided, the billable mileage driven, and the billable standby time spent.

Anything  Awaiting payment  is Excluded

Differential invoices do not include dispatches that are already marked  Awaiting payment , on the understanding that those dispatches have already been claimed / billed / invoiced and so there is no need to mention them again. Hence the name "differential": it includes only the differences from the previous invoice. Therefore, the receipient of a differential invoice must understand that it extends, rather than replaces, any prior invoice.

Complete Invoices

Complete invoice

A complete invoice gathers up all dispatches over a date range, without regard to postprocess status or to previous invoices.

This will include:

Gather all calls
that were run during
a specific date range

Because it includes dispatches still working their way through QA, prices can change after invoicing. When that occurs, the invoice will (when paid by the customer) overpay or underpay the dispatch in question. The dispatch will therefore go back to the Billing office again for re-invoicing, instead of advancing to  Finished .

The recipient of a complete invoice must understand that it supercedes any prior invoice for the same date range, because it will be including all the same dispatches as before (with updated balances due).

Complete invoices are usually requested by facilities, rather than patients, in order to book their transport expenses by month. If a previous month's invoice was not paid in full, then that month must be invoiced again -- a hassle which does not occur when using differential invoices to vacuum up all unfinished dispatches.

Collections Invoices

A collections invoice gathers up all dispatches that have been previously invoiced too many times without payment in full. You can decide the number of times invoiced as the cutoff; the default is three times.

Collections invoice

The collections invoice gathers up aging receivables, so that the necessary data can be easily exported for use by your collections agency. There are two different collections data formats; one or the other should suit your collections agency.

After exporting that collections data, mark the invoice as "Sold"; AngelTrack will then automatically move all included dispatches to  Finished .

Custom Invoices

A custom invoice allows you to explicitly control the selection filters, in order to choose dispatches for inclusion by any rhyme or reason you desire.

It is a good way to calculate quick mockups, if a facility or a salesperson calls in to ask for an estimate or a projection. You can even include items marked  Finished  if the customer is asking for a total statement for the date range.

AngelTrack Help Index - Training Portal - AngelTrack Support