A/R items collect balance impacts from the type of event reflected in their name.įor information on the general ledger (G/L) impact of the events that contribute to bill items and A/R items, see See "About Collecting General Ledger Data" in BRM Collecting General Ledger Data. See "About Bill Items" in BRM Configuring and Running Billing.Ī/R items include adjustment items, dispute items, settlement items, payment items, refund items, payment reversal items, write-off items, and write-off reversal items. See "How A/R Actions Affect Account Balances".īill items include cycle forward items, cycle arrears items, usage items, and custom items. BRM manages A/R by transferring amounts between A/R items and bill items. To understand BRM accounts receivable, think of two types of items: bill items, which contribute to the total amount stored in a bill, and A/R items, which reflect actions on the A/R of an account or account bill, such as payments or adjustments. When you are ready to request a payment, you run the appropriate BRM utility to generate a printed invoice and then mail the invoice to the customer. For example, it might specify the 5th as the billing day of month (DOM), the next billing date as January 5, and an invoice payment method.Ī /bill object is generated on January 5 that includes all billing information, such as a list of billable events that occurred during the cycle, any adjustments or credits made by customer service representatives (CSRs), any customer payments, and the total amount due. One /item object stores the $20 cycle forward fee and another /item object stores the $50 in usage fees.Ī /balance_group object stores the total cost of all bill items ($70).Ī /billinfo object stores information about when and how to generate a bill. BRM stores the A/R data in the following objects: When you are ready to request a payment from the customer, the billing utilities read the /bill object and generate one of the following:Īn invoice that can be mailed or emailed to the customer.Ī credit card transaction that is sent through a credit card processor.Ī direct debit transaction that is sent through a payment processing service.įigure 1-1 shows a typical event to invoice billing cycle.ĭescription of ''Figure 1-1 Billing Cycle''įor example, a customer accumulates the following charges in one billing cycle: a $20 cycle forward fee, a $10 email usage fee, and a $40 SMS text messaging usage fee. All information necessary to create a payment request is stored in a /bill object. All administrative information for creating a bill, such as the payment method, billing cycle length, payment collection date, and account hierarchy information, is stored in the /billinfo object. For example, one balance group could store the total balance of all GSM charges and another balance group could store the total balance of all GPRS charges. You can create multiple balance groups to track balance totals by service type. The total balance is stored in a /balance_group object. Total balance due from all billable events in a billing cycle. This information is stored in an /item object. To bill an account, BRM must track and store the following information for each billing cycle: ![]() If you have any questions regarding an intended use or modification of this product, contact Oracle.įor information about the procedures for managing payments, see "About BRM-Initiated Payment Processing" and "Managing Externally Initiated Payments" in BRM Configuring and Collecting Payments.įor information about configuring adjustments, disputes, and settlements, see "Configuring Adjustments, Disputes, and Settlements".įor basic information about BRM and billing, see the discussion on BRM in BRM Concepts and "About Billing" in BRM Configuring and Running Billing. ![]() See your software license agreement for more details. Use or modification of this software product in any manner or for any purpose other than as expressly set forth in this documentation may result in voidance or forfeiture of your warranties and support services rights. Assumptions should not be made about functionality that is not documented or use of functionality in a manner that is not documented. Do not use or modify this product except as explicitly instructed in this documentation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |