In order to facilitate decentralized control of the billing and collection processes, the system supports the ability to set up multiple customer accounts for an individual customer record. While this allows the control of billing and collection functions at the department and even the unit level, it can also result in individual customers receiving multiple statements if that customer is associated with more than one customer account. To prevent customers from receiving multiple statements, the system provides the option of generating consolidated statements and consolidated past due statements that includes all transactions for the accounts for a customer.
You can distinguish whether a statement activity is associated with a central statement or an individual statement as follows:
A Central Statement Billing Profile field is displayed on the accounting lines of Receivable (RE), Cash Receipt (CR), Referral to Collection Agency (CL), Write-Off (WO), General Accounting Expenditure (GAX), Internal Exchange Transaction (IET, IT), and Internal Transaction Agreement (ITA) transactions. If this is a new transaction that involves statement activities, and central statements are enabled for the customer, or if this modifies, cancels, or references a central statement transaction, then the Central Statement Billing Profile field is populated to indicate the Billing Profile record that controls the statement billing options.
A Central Statement Billing Profile field is displayed on the Statement Detail table. This field is populated by the system from the transactions.
A Central Statement flag is displayed on the Statement, Statement History, and Accounts Receivable Correspondence History tables. If a record on these tables is associated with a central statement or central past due statement, the Central Statement flag is checked, and the Billing Profile, Department, and Unit field values correspond to the associated Central Statement Billing Profile record.
The Statement and Past Due Statement batch jobs process activities associated with a central statement based on statement billing options (for example, statement dates, remittance information, due date lag, collection cycle, minimum billing thresholds, and so forth) defined on the Central Statement Billing Profile record rather than the Billing Profile record corresponding to the Billing Profile code. The jobs also look to the Vendor/Customer table rather than the Customer Account Options table to determine if Statement or Past Due Statement is suppressed for activities associated with a central statement.