For each customer invoice, the current balance is recalculated from the original invoice amount plus any payment transactions made against the invoice.

If there is any change to the current balance, a line is printed for the invoice indicating that a change has been made.

In addition, the next payment number for each invoice is recalculated based on the number of payments on file for the invoice.

For each customer, the current balance is recalculated from the sum of the current balances of the invoices on file as follows:

All outstanding invoice are added up for the customer and compared to the customer's balance. When a difference is found, the current customer balance is adjusted to equal the sum of the invoices. A balance correction line is printed indicating the customer to which the change was made.

All customer balances are then accumulated to give the AR Control balance.

The aged balances held against each customer are updated. These balances can be viewed within the Customer Query program.

Refer to Invoice Ageing for examples of how aged balances are calculated.

The current Accounts Receivable balance on the control record is recalculated from the sum of the current balances of all customers on file.

If there is any change to the current Accounts Receivable balance, a line is printed indicating that a change has been made, and the change made is added to the control record month-to-date balance corrections field.

For each customer, the average number of days it takes the customer to pay an invoice is recalculated. This is determined by dividing the total number of zero balance invoices against each customer into the total number of days it took to pay those invoices.

An invoice/debit note is included in the calculation if:

If an invoice/debit note meets all these criteria, then the difference in days is calculated between the transaction journal date and the invoice date.

The total number of zero balance invoices included in the calculation and the total age of all zero balance invoices included in the calculation are stored for each customer and used to calculate the average days to pay. The average days to pay value can be viewed in the Sales Order Entry and Customer Query programs.

For each customer, the age of the oldest invoice with a positive balance is calculated and saved together with the applicable invoice number against the customer. Depending on which options are selected, these fields may be used when credit checking is performed or when running the Credit Management report.

The oldest invoice is calculated by determining the difference in days between the Run date and each invoice date until the oldest invoice is established.

	If the Invoice ageing method is By invoice due date (Accounts Receivable Setup – General tab) then the difference in days between the Run date and each invoice date is reduced by the due days against the terms code attached to the invoice.

If you selected the option: Reset customer credit status, then invoices are aged into buckets to establish the highest bucket with a positive balance. This then corresponds to a credit status, which is saved against the customer (Browse on Customers – General 2 tab). Depending on which options are selected, the credit status may be used when credit checking is performed or when running the Credit Management report or the Credit Letter Extract program.

Refer to Credit Status for information on how a customer's credit status is determined.

For all customer invoices, if an invoice has a zero balance, but the tax portion of the invoice is not zero, then the tax portion of the invoice is set to zero.

The 24 months sales figures on each customer record are rolled one month.

The month-to-date sales value for the customer is copied to the previous month 1 sales value.

All month-to-date values for each customer are reset to zero.

The credit status for each customer is reset.

Refer to Credit Status for information on how a customer's credit status is determined.

The aged balances held against the customer are updated.

Refer to Invoice Ageing for information on how the aged balances for a customer are determined.

For all customer invoices, if an invoice has a zero balance, but the tax portion of the invoice is not zero, then the tax portion of the invoice is set to zero.

If you enabled the option: Consolidate brought forward customers at month end (Accounts Receivable Setup) then the invoices of each balance forward customer are sorted into buckets according to their age, based on the ageing method. For each group of invoices, the invoice balance for the current and two previous periods and the original discount amount are accumulated. All original invoices and their associate payments, adjustments, credit notes, debit notes, invoice and POD multimedia and POD notepad notes are then deleted (see Balance Brought Forward).

A new single invoice is then created for each aged bucket, with an asterisk (*) as the first character of the invoice number followed by a number, starting from 00001 upwards. Each aged bucket is associated with one of the last seven statement dates and the invoice date is set to the applicable statement date. The accumulated discount amount and invoice balances are written to the new invoice. The original invoice amount on the new invoice is also updated with the accumulated invoice balance for the current month.

Reports that print detailed information on invoices and the transactions processed against them (e.g. AR Trial Balance, Statement Print and Credit Management) will only report on the consolidated invoices once the month end has been processed. Invoices for foreign currency customers are not consolidated, because each invoice can have its own fixed exchange rate. Future invoices (i.e. invoices that have an invoice date in the future) are not consolidated.

Permanent entries that have not expired have their posted this month indicator reset to N.

The Accounts Receivable control record is updated as follows:

The period-to-date and month-to-date taxable, tax exempt, and tax amounts on the tax control records in the company tax control file are reset to zero.

All the month end steps are processed.

For each customer, the year-to-date sales and profit fields are set to zero after the figures therein have been moved to the previous year-to-date sales and profit fields.

The Accounts Receivable control record is updated as follows:

The year-to-date taxable, tax exempt, and tax amounts on the tax control records in the company tax control file are reset to zero.

Ledger distribution records are processed as follows if Accounts Receivable is linked to General Ledger in detail or summary (General Ledger Integration):

Permanent entries are deleted from the file once the entry is expired. Temporary entries are deleted from the file once the entry has been posted. (see AR Permanent Entry Maintenance)

All customer notes are deleted for customers no longer held on file. Similarly, all invoice notes are deleted for invoices no longer on file.

Customer movements are processed as follows:

Invoices that reach a zero balance in a financial month and year before the cut-off date specified, are removed. Payment details for these invoices in the payment detail file are also removed.

Payment journals are deleted if they match the following conditions:

Any payment history records that were created in a financial month and year before the cut-off date specified, are removed.

If you selected to print discount credit and debit notes (Accounts Receivable Setup - Terms Discount tab), then discount credit and debit note records are deleted if they are older than the specified number of months specified to retain discount notes (Accounts Receivable Setup - History tab).

Sales transaction records are processed as follows:

Records are written to the sales transaction file each time an invoice is created within either the Accounts Receivable or Sales Order modules. For each invoice detail line, the following records are written to the file: a detail sales transaction record (referred to as a D record) a Canadian GST tax record, if Canadian GST is in use (referred to as an F record) For each invoice, the following records are written to the file: an invoice summary record (referred to as an S record) a foreign invoice summary record, if Foreign currency sales is in use (referred to as an s record) a tax summary record (referred to as a T record)

A report is printed with a summary for each file processed as follows:

"acc no" invoice count raised by n (where "acc no" indicates the customer account number and n indicates the value by which the invoice count was raised.

This error occurs when the actual number of invoices found against the customer account number does not agree with the value in the InvoiceCount field of the ArCustomer table/file. The InvoiceCount field is amended.

Sub/Ac - No details allowed

This occurs when the system finds invoices against a sub-account, which should be on the master account.

If a sub-account is linked to a master account so that the sub-account's invoices are attached to the master account, there should be no invoices or balances on the sub-account.

If the invoice is 120 days old or more, then the invoice balance is added to the 120 Day Invoices bucket. In this example, this bucket's balance is 571.00.

The following table illustrates this ageing:

If the invoice is 120 days old or more, then the invoice balance is added to the 120 Day Invoices bucket. In this example, this bucket's balance is 332.00.

The following table illustrates this ageing:

If the invoice is 120 days old or more, then the invoice balance is added to the 120 Day Invoices bucket. In this example, this bucket's balance is 452.00.

The following table illustrates this ageing:

If the invoice is 91 days or more overdue, then the invoice balance is added to the 120 Day Invoices bucket. In this example, this bucket's balance is 332.00.

The following table illustrates this ageing:

Period 1 - Invoice for 150.00 is posted using the AR Invoice Posting program. The cost value is zero.

Period 1 - Payment of 25.00 received from customer and processed using Payments and Adjustments program.

Period 1 - Month end is executed using the AR Period End program.

Period 2 - Payment of 32.00 received from customer and processed using Payments and Adjustments program.

Period 2 - Month end is executed using the AR Period End program.

Period 3 - Payment of 60.00 received from customer and processed using Payments and Adjustments program.

Period 3 -Month end is executed using the AR Period End program.