During setup, you define business fundamentals such as the activities you process and their accounting distributions, your accounting structure, and various control features. Setup is also the time to define comprehensive defaults that Receivables uses to make data entry more efficient and accurate. In addition, setup lets you customize Receivables to employ the policies and procedures that you use in your business.
You can set up Receivables a number of different ways. For a complete description of each setup step, see: Setup Steps.
If you use the Oracle Applications Multiple Organization Support feature, please refer to the Oracle Applications Multiple Organizations Implementation Guide before proceeding.
If you plan to use Oracle Cash Management with Oracle Receivables, additional setup steps are required. For more information, refer to the Oracle Cash Management User Guide.
Related Topics
Oracle Financials Concepts Guide
Oracle Financials Implementation Guide
The following steps may need to be performed to implement Oracle Receivables. These steps are discussed in detail in the Setting Up sections of other Oracle product user guides.
In addition to the setup steps that follow, be sure to set up underlying Oracle Applications technology, including:
performing systemwide setup tasks such as configuring concurrent managers and printers
managing data security, which includes setting up responsibilities to allow access to a specific set of business data and complete a specific set of transactions, and assigning individual users to one or more of these responsibilities.
setting up Oracle Workflow
Refer to the Setup Checklist in the General Ledger Implementation Guide to complete the setup steps listed below.
Define Chart of Accounts
Define Currencies
Define Calendars
Define Calendar Periods
Define Calendar Period Types
Define Document Sequencing
Define Ledger
Assign Ledgers to a Responsibility
Define Daily Conversion Rate Types
Define Multiple Reporting Currencies Ledgers
Define Ledger Specification
Define Accounting Flexfield and Accounting Flexfield Combinations
Refer to the Overview of Setting Up section in the Oracle Inventory User's Guide to complete the setup steps listed below.
Define Inventory Organizations
Define Items
Define Item Catalog
Define Item Category
Define Units of Measure and Unit of Measure Classes
Refer to the Oracle Applications System Administrator's Documentation Set to complete the setup steps listed below.
Define Audit Trails
Define Printers
Define Security (for example: users, responsibilities, and concurrent programs)
See: Subledger Accounting Setup for Receivables.
Refer to the Oracle HRMS Implementation Guide to complete the setup step listed below.
Define Organizations (single or multiple organization)
Related Topics
Oracle Applications System Administrator's Documentation Set
Oracle Workflow Documentation Set
The following table lists Oracle Receivables setup steps. A reference to whether the step is optional or required is provided. After you log on to Oracle Applications, complete these steps to implement Oracle Receivables:
Related Topics
For each step, we include a Context section that indicates whether you need to repeat the step for each ledger, set of tasks, inventory organization, HR organization, or other operating unit under Multiple Organizations.
Important: If you use the Oracle Applications Multiple Organization feature, please note the steps that you must perform for each operating unit in your multiple organization environment. These steps are marked with the text "Perform this step for each operating unit" in the Context section.
If you previously defined your ledger or ledgers while setting up a different Oracle Applications product, proceed to the next step.
You need to define at least one ledger before you can implement and use Receivables.
When defining a ledger, you also need to:
Assign your Ledgers to a Responsibility
Define your Accounting Flexfield Combinations (Optional)
Context: Perform this step for each installation.
See: Defining Ledgers, Oracle General Ledger Implementation Guide.
Tip: If you use the Oracle Applications Multiple Organization Support feature, you can use multiple ledgers for one Receivables installation. See: Using the Multiple Organization Support Feature.
The Account Generator ensures that Receivables substitutes the correct balancing segment values during various accounting activities against transactions and receipts. You must review the default process that Receivables uses to see if it meets your accounting requirements. You can optionally customize the Account Generator for each ledger that you have defined.
Additionally, you can disable balancing segment substitution for receivable activities using the AR: Disable Receivable Activity Balancing Segment Substitution profile option. If you set this profile option to Yes, then you must define a suspense account to ensure that the transfer to General Ledger succeeds in the event that your activities and original transactions do not post to the same balancing segment value. This profile option does not affect the gain, loss, and rounding accounts that you define at the system options level.
Context: Perform this step for each ledger.
See: Using the Account Generator in Oracle Receivables.
If you are not using AutoInvoice, proceed to the next step.
If you use AutoInvoice to import information from an external system and create transactions in Oracle Receivables, define Transaction Flexfields to uniquely identify these transactions. Because Transaction Flexfields are unique, you can also use them to link and reference other transaction lines.
Context: Perform this step for each installation.
See: Transaction Flexfields, Oracle Receivables User Guide.
Tip: To query your Transaction Flexfield, update the Transaction Flexfield information for previously entered transactions.
Tip: Create indexes on your Transaction Flexfield columns if you want to query Transaction Flexfield information in your invoice headers and lines. Additionally, without indexes the validation portions of the AutoInvoice program can be slow. For more information about defining Transaction Flexfield indexes, see: Importing Invoice Information Using AutoInvoice, Oracle Receivables User Guide.
For Receivables, you need to define both key and descriptive flexfields. For key flexfields, you define the flexfield structure, specifying the number and function of segments, and then select the structure. For descriptive flexfields, you define the global data element context, any additional contexts that you might require, and then the structure of these contexts. Key flexfields do not use contexts.
Define Key Flexfields (Required)
You can use the Territory flexfield for recording and customized reporting on your territory information. Receivables provides a default structure for your Territory flexfield. You can associate Territory flexfields with salespeople, invoices, commitments, and customer business purposes.
Note: You must enable at least one segment of your Territory flexfield. See: Territory Flexfield.
Proceed to the next step if you previously defined your System Items Flexfield while setting up another Oracle Applications product.
If you have not installed Oracle Inventory or Oracle Order Management and you want to report on item information, define your System Items flexfield. You must define your System Items flexfield before defining items in Oracle Receivables.
All Oracle products that reference items share the System Item Flexfield and support multiple segment implementation. Oracle provides a seeded System Item Flexfield for you (Code = 'MSTK'). Define a structure for this flexfield rather than creating a new flexfield.
After you define your System Item Flexfield structure, specify your Item Flexfield profile options. Set the OM: Item Flexfield profile option at the site level to specify the System Item Flexfield structure that you want to use. Set this to System Items, which is the System Item Flexfield structure that you just defined.
Next, set your AR: Item Flexfield Mode profile option to choose your preferred method of entry for this flexfield within Receivables. This default value is concatenated segment entry.
See: Setup Steps, Oracle Inventory User's Guide.
Define Descriptive Flexfields (Optional)
Define a descriptive flexfield if you want to capture information that is not otherwise captured in a Receivables form. You can define descriptive flexfields during your initial setup or at a later time.
See: Descriptive Flexfields.
See: Planning Your Descriptive Flexfield, Oracle Applications Flexfields Guide.
Context: Perform this step for each installation.
You must define at least one organization to use Receivables. This organization lets you use the inventory forms in Receivables if you do not have Oracle Inventory installed.
Define the control options and account defaults for your organization before you can define items or perform any transactions. You must assign a unique short code to your organization and use this code to identify the organization with which you want to work.
After you define your organizations and items, you must select the item validation organization in the Order Management Parameters window. The item validation organization, which must be an item master organization, indicates the organization that Receivables uses to validate items.
Context: Perform this step for each business group.
See: Organizations.
If you are using AutoCash, define your AutoCash rule sets before defining system parameters or customer profiles classes. AutoCash rules determine the sequence of application methods Receivables uses when applying receipts imported using AutoLockbox to open debit items.
Context: Perform this step for each installation.
See: AutoCash Rule Sets.
Receivables provides several default lookups which are used throughout the application to provide validated default values and list of values choices. You can add or update these to customize your list of values and speed data entry. For example, you can define additional reasons for creating credit memos or enter the names of each freight carrier used by your business.
Context: Perform this step for each installation.
See: Defining Receivables Lookups.
Demand classes are categories you can use to segregate scheduled demand and supply into groups, so that you can track and consume the groups independently. You can then assign demand classes to customers in the Customers windows. Use the Demand Class Lookups window to modify existing or define new Lookups for your shared demand classes.
Context: Perform this step for each installation.
See: Demand Class Lookups.
If you are using AutoInvoice, define invoice line ordering rules to specify how you want to order and number transaction lines after AutoInvoice groups them into invoices, debit memos, and credit memos. Receivables provides many attributes that you can use to define your line ordering rules.
Context: Perform this step for each installation.
See: AutoInvoice Line Ordering Rules.
If you are using AutoInvoice, define grouping rules to indicate how you want to group transaction lines imported by AutoInvoice. For example, to include specific transaction lines on a single transaction, certain attributes must be identical. Receivables provides many attributes that you can use to define your grouping rules.
Context: Perform this step for each installation.
See: Grouping Rules.
Define Application Rule Sets to control how Receivables reduces the balance due for your open debit items when you apply payments using either the Applications window or Post QuickCash. You can define your own application rule sets, assign them to transaction types, and specify a default rule set in the System Options window.
Context: Perform this step for each installation.
Default - If you skip this step, Receivables uses the rule set Line First - Tax After as the default. This rule set first applies the payment to the line amount and then applies the remaining amount to any associated tax.
See: Receivables Application Rule Sets, Oracle Receivables User Guide.
Define your accounting, discount, and invoice system options to control how Receivables works. System options determine your accounting flexfields, whether you use header or line-level rounding, and control the default operation of the AutoInvoice and Automatic Receipt programs.
Important: If you use the Oracle Applications Multiple Organization Support feature, you need to define system options for each of your operating units. For more information about multiple organizations, refer to the Oracle Applications Multiple Organizations Implementation Guide.
Context: Perform this step for each operating unit.
See: Defining Receivables System Options.
To enter customer, supplier, bank, check, and remit-to addresses in country-specific formats, set up flexible address formats. For example, if you have customers in Germany, you can enter German addresses in the format recommended by the Bundespost, or enter addresses for customers in the United Kingdom in the format recommended by the Royal Mail.
Context: Perform this step for each installation.
See: Setting Up Flexible Addresses.
Use the address style field to assign address styles to countries if you want to use the Flexible Address Formats feature.
You can identify which countries are part of the European Union (EU) by entering a VAT Member State Code for these countries. The Receivables European Sales Listing report uses this information to produce a listing of all sales to customers in European Community member states other than your own.
Context: Perform this step for each installation.
Define payment terms to determine the payment schedule and discount information for customer invoices, debit memos, and deposits. You can also define proxima payment terms to pay regular expenses such as telephone bills and credit card bills that occur on the same day each month and create split payment terms for invoice installments that have different due dates.
Context: Perform this step for each installation.
See: Payment Terms.
Default - If you skip this step, Receivables uses 30 NET as the default. This payment term indicates that payment is due within 30 days.
If you are not using Multiple Reporting Currencies (MRC) functionality, skip this step.
To maintain transactions and account balances in multiple currencies, assign your reporting ledger to your primary ledger. This enables you to generate reports in each of your reporting currencies. For example, you can maintain a primary ledger in USD (US dollars) and have Oracle General Ledger maintain reporting ledgers in CAD (Canadian dollars) and EUR (euros).
Context: Perform this step for each ledger.
If your accounting method is Accrual, define accounting rules to create revenue recognition schedules for your invoices. Accounting rules determine the number of periods and percentage of total revenue to record in each accounting period.
When you use accounting rules, you also need to define the appropriate periods to which your rule refers. You enter these periods in the Calendar window and they must refer to the same period type as your accounting rule. For example, if you are using an accounting rule that recognizes revenue monthly from Jan-99 through Jun-99, you must define periods from Jan-99 through Jun-99 where the period type is Month. These periods must be defined in the same calendar as your accounting periods. You define Calendars in Oracle General Ledger.
Important: If you have an accounting period type that is not Month and you use AutoInvoice with Oracle Order Management, you should update the Period field for the predefined IMMEDIATE accounting rule to the same period as your accounting period type.
Context: Perform this step for each installation.
See: Accounting Rules.
Open or close periods in your accounting calendar to control the recording of accounting information for these periods. Receivables uses the status of these accounting periods to control transaction entry and journal entry creation to your general ledger. You cannot enter an activity in a closed accounting period. Receivables provides the following period statuses: Not Opened, Future, Open, Close Pending, and Closed.
Note: Define your Receivables calendar in the Accounting Calendar window in Oracle General Ledger.
Context: Perform this step for each operating unit.
See: Opening and Closing Accounting Periods, Oracle Receivables User Guide.
Define AutoAccounting to specify the general ledger accounts for transactions that you enter manually or import using AutoInvoice. AutoAccounting uses this information to create the default revenue, receivable, freight, tax, unearned revenue, unbilled receivable, bills receivable accounts, and AutoInvoice clearing (suspense) accounts.
Context: Perform this step for each operating unit.
See: AutoAccounting.
Important: If you use the Oracle Applications Multiple Organization Support feature, you need to perform this step for each of your operating units. For more information about multiple organizations, refer to the Oracle Applications Multiple Organizations Implementation Guide.
If you are not using the Cash Basis accounting method, skip this step.
If you are using the Cash Basis accounting method, you must set your Accounting Method system option to Cash Basis, define transaction types, set up an Unallocated Revenue account, and run a script to make the GL Transfer and Journal Entry Reports incompatible with each other.
Context: Perform this step for each operating unit.
See: Using Cash Basis Accounting, Oracle Receivables User Guide.
Oracle provides default seeded account derivation rules and journal entry descriptions. Attach seeded application accounting definitions (AAD) to a new subledger application method. You can create new account derivation rules and journal descriptions. In cases where multi-fund accounts receivable (MFAR) account pairs are needed, you can create mapping sets. Oracle does not provide default mapping sets for multi-fund accounts receivable.
If you set up Oracle Receivables to create accounting entries when receipts are cleared in Oracle Cash Management, then you must set the AR: Activate Multi Fund Accounting Extract profile option to Yes for MFAR.
Define the transaction types that you assign to invoices, debit memos, commitments, chargebacks, credit memos, on-account credits, and bills receivable. Receivables uses transaction types to default payment term, account, tax, freight, creation sign, posting, and receivables information. Receivables provides two predefined transaction types: Invoice and Credit Memo.
Context: Perform this step for each operating unit.
See: Transaction Types.
Important: If you use the Oracle Applications Multiple Organization Support feature, you need to perform this step for each of your operating units. For more information about multiple organizations, refer to the Oracle Applications Multiple Organizations Implementation Guide manual.
Define the transaction sources that you assign to invoices, debit memos, commitments, credit memos, on-account credits, and bills receivable. Receivables uses transaction sources to control your transaction and transaction batch numbering, provide default transaction types for transactions in batch, and to select validation options for imported transactions. Receivables provides the following predefined transaction sources: MANUAL-OTHER, DM Reversal, and Chargeback.
Context: Perform this step for each operating unit.
See: Transaction Batch Sources.
Important: If you use the Oracle Applications Multiple Organization Support feature, you need to perform this step for each of your operating units. For more information about multiple organizations, refer to the Oracle Applications Multiple Organizations Implementation Guide.
Define collectors to assign to your customers through credit profile class assignments. Collectors can use the Collections windows and Receivables collection reports to keep apprised of a customer's past due items. Receivables provides a predefined collector called DEFAULT.
Context: Perform this step for each installation.
See: Collectors.
Define approval limits to determine whether a Receivables user can approve adjustments or credit memo requests. You define approval limits by document type, dollar amount, reason code, and currency. Approval limits affect the Adjustments, Submit AutoAdjustments, and Approve Adjustments windows as well as the Credit Memo Request Workflow.
Context: Perform this step for each installation.
See: Approval Limits.
Context: Perform this step for each operating unit.
Define all of the banks and bank accounts you use to remit your payments. You define banks and bank accounts in Oracle Cash Management.
You can define as many banks and bank accounts as you need and define multiple currency bank accounts to accept payments in more than one currency.
Proceed to the next step if you already defined your remittance banks in Oracle Cash Management.
See: Defining Internal Banks.
Define distribution sets if you enter non-invoice related receipts and you want to use a predefined revenue distribution set. Distribution sets are predefined groups of general ledger accounting codes that determine the credit accounts for positive miscellaneous receipt amounts and the debit accounts for negative receipt amounts.
Context: Perform this step for each operating unit.
See: Distribution Sets.
Define Receivables Activities to provide default accounting information when you create adjustments, discounts, late charges, miscellaneous cash transactions, and bills receivable. Receivables also uses Receivables Activities to account for tax if you calculate tax on these activities.
Context: Perform this step for each operating unit.
See: Receivables Activities.
To create Automatic Receipts, define additional receipt or remittance format programs that you use to send paper and electronic documents to your customers and remittance banks. You can define as many receipt programs as you need.
Context: Perform this step for each installation.
Default - If you skip this step, Receivables uses the Automatic Receipt print program 'Print Created Receipts' (ARXAPFRC.rdf).
See: Automatic Receipt Programs.
Define receipt classes to specify whether receipts are created manually or automatically. For manual receipts, you can specify whether to automatically remit it to the bank and/or clear your accounts. For automatic receipts, you can specify a remittance and clearance method, and whether receipts using this class require confirmation.
Context: Perform this step for each installation.
See: Receipt Classes.
Define the receipt methods to account for your receipt entries and applications and to determine a customer's remittance bank information. When defining receipt methods, you must enter a receipt class, remittance bank information, and the accounts associated with your payment receivables type. You can also specify accounts for confirmation, remittance, factoring, bank charges, and short-term debt.
Context: Perform this step for each installation.
See: Receipt Methods.
Define receipt sources to provide default values for the receipt class, receipt method, and remittance bank account for receipts in a batch. Receipt Sources also determine whether the numbering for receipts in a batch is automatic or manual.
Context: Perform this step for each operating unit.
See: Receipt Sources.
Important: If you use the Oracle Applications Multiple Organization Support feature, you need to perform this step for each of your operating units. For more information about multiple organizations, refer to the Oracle Applications Multiple Organizations Implementation Guide.
Define aging buckets to review and report on open receivables based on the number of days each item is past due. For example, the 4-Bucket Aging bucket that Receivables provides consists of four periods: -999 to 0 days past due, 1 to 30 days past due, 31-61 days past due, and 61-91 days past due.
Context: Perform this step for each installation.
See: Aging Buckets.
Define statement cycles to control when you create customer statements. You assign statement cycles to customers in the Customer Profile Classes window.
Context: Perform this step for each installation.
See: Statement Cycles.
Define standard messages to customize the content of customer statements. Standard messages automatically print on the bottom of your statements. Use the Print Statements window to assign statement messages and submit statements for printing.
Context: Perform this step once for each installation.
See: Standard Messages.
If you defined a Territory Flexfield and want to create customized reports based on territory information, define Territory Flexfield combinations. You can assign Territory Flexfields to salespersons, invoices, and customer business purposes.
Context: Perform this step for each installation.
See: Territories.
Define salespersons to allocate sales credits to invoices, debit memos, and commitments. If you do not want to assign sales credits for a transaction, you can enter No Sales Credit. If AutoAccounting depends on salesperson, Receivables uses the general ledger accounts that you enter for each salesperson along with your AutoAccounting rules to determine the default revenue, freight, and receivable accounts for transactions.
Context: Perform this step for each operating unit.
See: Salespersons.
Important: If you use the Oracle Applications Multiple Organization Support feature, you need to perform this step for each of your operating units. For more information about multiple organizations, refer to the Oracle Applications Multiple Organizations Implementation Guide.
Define profile options to provide default values for some Receivables operations, specify how Receivables processes data, and control which actions users can perform.
Context: Perform this once for each installation.
See: Overview of Receivables User Profile Options.
Note: For more information, see: Overview of Setting User Profiles in Oracle Applications System Administrator's Guide - Maintenance.
Define customer profile classes to categorize customers based on credit, payment terms, statement cycle, automatic receipt, late charge, dunning, and invoicing information. When you initially set up your customers, you assign each customer to a profile class. To customize the profile class for a specific customer, use the Customer Profile Classes window.
Context: Perform this step for each installation.
Default - If you skip this step, Receivables uses the profile class DEFAULT.
See: Defining Customer Profile Classes.
Proceed to the next step if you defined customers while setting up another Oracle Applications product.
Define customer accounts and customer site uses to enter transactions and receipts in Receivables. When you enter a new customer, you must enter the customer's name, profile class and number (if automatic customer numbering is set to No). You can optionally enter customer addresses, contacts, site uses and telephone numbers.
Context: Perform this step for each installation.
See: Entering and Updating Customer Information, Oracle Receivables User Guide.
Define remit-to addresses to inform your customers where to send payments. Associate each remit-to address with one or more state, country, and postal code combinations. For example, if you want your customers in California and Nevada to send their payments to a specific address, enter the remit-to address and associate the states CA and NV with this address. Remit-to addresses are assigned based on the bill-to address on the transaction.
Context: Define remit-to addresses for each installation. For each operating unit, associate each remit-to address with a state and country.
See: Remit-To Addresses.
Tip: It is a good idea to set up a default remit-to address, even if you have other remit-to addresses defined, because Receivables can use this address if the bill-to location on the transaction is not covered by any other remit-to address assignment. This may happen, for example, when you create transactions for a new customer.
Important: If you use the Oracle Applications Multiple Organization Support feature, you need to perform this step for each of your operating units. For more information about multiple organizations, refer to the Oracle Applications Multiple Organizations Implementation Guide.
You can define two types of relationships in Receivables:
Customer account relationships
Party paying relationships
Define Customer Account Relationships (Optional)
Define customer relationships to enable customers to apply receipts to related customer transactions. To restrict receipt application to only related customers, define relationships between your customers and set the system option Allow Payment of Unrelated Invoices to No. Receivables lets you define one way and reciprocal relationships between your customers.
Context: Perform this step for each operating unit.
See: Defining and Updating Account Relationships, Oracle Receivables User Guide.
Define Party Paying Relationships (Optional)
If you want to provide one party with access to another party's accounts and transactions, then define party paying relationships.
You use Oracle Trading Community Architecture Relationship Manager to define party paying relationships.
Context: Perform this step for each installation.
See: Using Party Paying Relationships, Oracle Receivables User Guide.
See: Creating Relationships, Oracle Trading Community Architecture Implementation Guide.
To import receipts from a bank file using AutoLockbox, define lockboxes. For each lockbox, enter the lockbox number, bank name, batch source, bank account, bank origination number and cash account.
Context: Perform this step for each operating unit.
See: Lockboxes.
If you use AutoLockbox to import receipts, define a transmission file format. Transmission formats specify how data in your lockbox bank file is organized so it can be successfully imported into the Receivables interface tables. Receivables provides several standard transmission formats you can modify to meet your needs.
Context: Perform this step for each installation.
See: Transmission Formats.
Proceed to the next step if you defined units of measure classes while setting up another Oracle Applications product.
Use the Units of Measure Classes window to define and update groups of units of measure with similar characteristics (for example, Volume or Length). A class consists of a base unit of measure and other assigned units of measure. Use this window to define the base unit of measure for each class.
Context: Perform this step for each installation.
See: Unit of Measure Classes.
Proceed to the next step if you defined units of measure while setting up another Oracle Applications product.
Use the Units of Measure window to define one or more units of measure. Each item that you define in Receivables must have a primary unit of measure that you will have defined in this window. The number of units of measure that you define in this window depends on the variety of physical characteristics of your organization's inventory.
Context: Perform this step for each installation.
See: Units of Measure.
Define standard memo lines to enter predefined lines for debit memos, on-account credits, and invoices. When you define standard memo lines, you can specify whether a line is for charges, freight, line, or tax. Receivables also lets you define one chargeback and one debit memo reversal line.
Context: Perform this step for each operating unit.
See: Standard Memo Lines.
Important: If you use the Oracle Applications Multiple Organization Support feature, you need to perform this step for each of your operating units. For more information about multiple organizations, refer to the Oracle Applications Multiple Organizations Implementation Guide.
If your organization needs to apply receipts to transactions in different currencies, set up Receivables for cross currency receipts. To do this, define a cross currency rounding account in the System Options window, and define a suspense account in Oracle General Ledger.
Context: Perform this step for each operating unit.
See: Setting Up Cross Currency Receipts, Oracle Receivables User Guide.
Oracle Receivables uses Oracle E-Business Tax as its tax engine.
See: Setting Up Tax.
Context: Perform this step for each operating unit.
If you are not using a tax vendor with Oracle Receivables, skip this step.
Oracle E-Business Tax provides a tax vendor extension that integrates external tax calculation programs with Oracle Applications. This extension performs complex tax calculations to create and store tax data. You can implement either the Taxware Sales/Use Tax System or Vertex Q-Series with Oracle Receivables.
Context: Perform this step for each operating unit.
See: Oracle E-Business Tax: Vertex Q-Series and Taxware Sales/Use Tax System Implementation Guide.
By assigning unique numbers to documents, you can account for each transaction you enter and the document that accompanies it.
To enable sequential numbering, set the Sequential Numbering profile option to either 'Always' or 'Partially Used'. You must then define and assign categories and sequences for each transaction type, receipt method, adjustment, and late charge activity that you use.
Context: Define categories and sequences for each installation. Assign sequences to categories for each ledger.
See: Implementing Document Sequences.
Use balance forward billing to print a single bill that includes all of a customer's transactions for the billing period and any balance carried forward from the previous billing period. This lets you send one consolidated bill to a customer, instead of a separate invoice for each transaction.
See: Setting Up Balance Forward Billing.
You can calculate late charges against past due debit items for each customer, account, or site. Late charges are calculated according to your organization's late charge policy.
Your late charge policy indicates if you assess late charges against your customers and, if so, how those late charges are calculated.
See: Setting Up Late Charges.