Invoices & Credits > Bureau Invoicing

Bureau Invoicing

Why:

Used to send parts invoices to a third-party supplier for printing and mailing.

 

Where:

At customer level a field ‘Print Method’ is available on the Point-of-Sale tab. This enables users to choose from Local, Bureau or Email. In order entry, an input-capable Print Method field is available on the overview tab. The method attached to the customer will be the default when opening a new order.

 

How to Use Bureau Invoicing:

At Order Completion, when the user chooses to complete the order, via the Invoice option or the Delivery Note option, the program will check that the option taken is compatible with the chosen Print Method. Additionally it will check that the chosen Print Method is compatible with the customer’s Payment Method.

When Parts Batch Invoicing, Parts batch invoicing will print an invoice locally, or output the invoice details to a new XML Invoice Extract file in accordance with the print method.

When the Daily batch runs, a program exists in the GDS Daily Batch, this will deposit an XML output in the Dealer Data Bank for onward transmission to the third-party supplier.

Depending on parameter settings the following functionality will take place:

Parts Batch Invoicing - If Bureau invoicing is not enabled and Print Method is Local all invoices will be processed and files updated in the normal way.

If Bureau invoicing is enabled: Where invoice header indicates that bureau invoicing is required, orders are processed and files updated in the normal way but invoices are not printed. The XML Invoice Extract file is updated with the invoice details, but not transmitted at this stage.

For collect customers only, the current customer file-held print method is applied to all orders for that customer in the current batch, the print method field on the header is overwritten with that value. However, if the customer file-held method is email these are printed locally.

Daily Batch: A batch program extracts data from the XML Invoice Extract file and deposits it in VIDB for onward transmission to the third-party supplier.