When this Field Ticket processing is activated in the
Invoice Parameters, a Field Ticket# is
required on every invoice.
On Account Field ticketed invoices do not post through the standard
Daily Close 1.
Then this billing utility can be used to identify, approve, and
compile charges to form a single invoice for the customer.
Billing the selected field tickets merges the invoices and
immediately posts them into Batch status ready for Daily Close 2.
e.g. An Engineer does work at several jobs, generating multiple invoice/tickets that need to be billed as a single invoice with engineer’s signature
This Field Ticket requirement can be set in the Company Invoice Parameters.
Note: To use this processing, deposits cannot be used to partially
pay an 'On Account' invoice, nor can an invoice be partly 'On
Account' and partly paid by any other method.
Field Ticket processing exceptions:
Cash invoices also require a field ticket# but cash invoices do
not require approval as payment is already received.
Cash invoices are posted through the standard Daily Close 1.
The prompts to bill Field Tickets are:
Uncheck this box if the invoice has not been approved and is not ready to be billed.
Uncheck this box to leave the invoice unbilled in the Current status.
Causes of errors include:
To fix the error, delete the invoice and re-enter it assigning a new Field Ticket#.
INVOICE xxxxxx IN USE BY AAAAA - caused if the invoice is currently locked.
To proceed with the billing, contact the user at the terminal identified in the error message, and request he exit the invoice.
INVOICE xxxxxx IS NOT ON ACCOUNT - caused if the invoice is a Cash invoice that should be posted through the standard Daily Close.
To fix the error, delete the invoice and re-enter it as a cash invoice to post through Daily Close 1.
INVOICE xxxxxx HAS A DEPOSIT - caused if a deposits from a contracts was used to pay part of the invoice.
Delete invoice with the refund deposit feature in Delete a Single Invoice and re-enter invoice fully On-Account.
INVOICE xxxxxx HAS PAYMENT DETAILS - caused when the invoice is
partially paid.
e.g. Cash, Credit Card, etc.
To fix the invoice, either change invoice to be fully paid in cash, or refund the payment and put it fully on Account.
INVOICE xxxxxx DOES NOT USE ENHANCED TAXING - caused if the
invoice was entered when Standard Taxing method was in use, and the
method has since been changed to Enhanced Taxing.
e.g. Invoice was created before turning Enhanced Taxing on
To fix the error, switch taxing back to the method previously used for this invoice and process all ‘old’ invoices before once more switching taxes back to the new method.
INVOICE xxxxxx USES ENHANCED TAXING - caused when tax methods are changed when invoices are not all posted. e.g. Invoice was created before turning enhanced taxing off
To fix the error, switch taxing back to the method previously used for this invoice and process all ‘old’ invoices before once more switching taxes back to the new method.
INVOICE xxxxxx TOTALS DO NOT MATCH DETAILS - caused when the invoice details are out of sync with the totals calculated.
To fix the error, re-access the invoice in Miscellaneous Invoices to force the totals to be recalculated.
When a field ticketed invoice is created from a contract by billing a Cycle Bill a Single Contract or from a Rental Return, a comment with the date and ticket number is printed on contract.
Converted from CHM to HTML with chm2web Pro 2.85 (unicode) |