In some cases, an invoice may be received after an allocation's been completed.  There may even be cases where the invoice is received after the journal entries have been made in your company's financial system.  This creates a complicated scenario:

1. You want to apply the late invoice in the next journal cycle
2. You want to apply the late invoice to the flight activity that took place in the invoice's time period

Because of this, you won't want to simply place the invoice in the next month's batch, because the invoice costs will be applied to the next month's flight activity.  So how to handle the late invoice?

This scenario is the reason Helipass allows you to create an invoice allocation independent of your batch allocations.  Using this feature, you can generate a structured export or journal allocations for a single invoice outside of a completed batch.  For information on creating a single invoice allocation and/or export, please see http://faq.phihelipass.com/m/66477/c/201664

Another potential scenario would be receiving a number of late invoices that require journal adjustments after initial allocations have been made.  In this scenario, you would simply create a new batch containing only the late invoices, and specify the appropriate date range for the new adjustment batch.  The date range for the adjustment batch should match the date range for the invoices, to ensure the invoice information is applied to the appropriate flight activity.