Invoice Iteration Types

Invoice iteration types are referenced when entering general details for contracts and used when generating invoices to define the basic behaviour of the invoice.

There is a strict hierarchy to invoice iteration types, such that if an invoice iteration type with lower precedence is being generated, and more confident pricing exists in an invoice configuration of a higher invoice iteration type, the prices from the higher invoice iteration are applied. For example, if both a provisional and a final invoice iteration type are defined, when an invoice is created, the system always uses the invoice iteration type of best price that can be calculated. If final prices cannot be evaluated (for example, if the price series does not exist or the date period cannot be evaluated to determine the price), the final invoice is flagged as not able to be generated. If generating a provisional invoice, the final pricing is first evaluated, and if it evaluates successfully, it is then used in favour of the provisional pricing. However, it is possible to force pricing in an earlier quotation pricing configuration to be used if required.

The hierarchy of invoice iteration type is defined by the order of invoice iteration type on the Invoice Types screen, where the top of the list is of lowest precedence, and the bottom of the list is of highest precedence.

The Proforma, Prepayment, Provisional and Final invoice iteration types are default types and cannot be deleted.

Each contract must have a Final invoice iteration type configured.

Important: The invoice iteration types can only be edited if the Invoice Report Template Path has been specified in the MineMarket Service Config. See the MineMarket Installation Guide for more information.