AR glossary: autoaccounting, aging buckets, approval limits

adjustment A Receivables feature that allows
you to increase or decrease the amount due
of your invoice, debit memo, chargeback,
deposit, or guarantee. Receivables lets you
create manual or automatic adjustments.
aging buckets In Oracle Receivables and
Oracle Payables, time periods you define to
age your debit items. Aging buckets are
used in the Aging reports to see both
current and outstanding debit items. For
example, you can define an aging bucket
that includes all debit items that are 1 to 30
days past due. GL Desktop Integrator uses
the aging buckets you define for its Invoice
Aging Report.
aging buckets In Oracle Cash Management,
aging buckets are used to define time
periods represented in the forecast.
Examples of aging buckets are date ranges
or accounting periods.
applied Payment in which you record the
entire amount as settlement for one or more
debit items.
approval limits Limits you assign to users for
creating adjustments and approving credit
memo requests. Oracle Receivables
enforces the limits that you define here
when users enter receivables adjustments
or approve credit memo requests initiated
from AR Online. When users enter
adjustments that are within their approval
limit, Oracle Receivables automatically
approves the adjustment. When users enter
adjustments outside their approval limit,
Oracle Receivables assigns a status of
pending to the adjustment.

AutoAccounting In Oracle Projects, a feature
that automatically determines the account
coding for an accounting transaction based
on the project, task, employee, and
expenditure information.
AutoAccounting In Oracle Receivables, a
feature that lets you determine how the
Accounting Flexfields for your revenue,
receivable, freight, tax, unbilled receivable
and unearned revenue account types are
AutoAdjustment A feature used to
automatically adjust the remaining balances
of your invoices, debit memos, and
chargebacks that meet the criteria that you
AutoAssociate An option that allows you to
specify whether you want Oracle
Receivables to determine the customer
using invoice numbers if the customer
cannot be identified from either the
magnetic ink character recognition (MICR)
number or the customer number. Oracle
Receivables checks the invoice numbers
until it finds a unique invoice number for a
customer. Oracle Receivables then uses this
invoice number to identify the customer.
You can only use this feature if your bank
transmits invoice numbers and if the
AutoLockbox Validation program can
identify a unique customer for a payment
using an invoice number. Otherwise,
Oracle Receivables treats the payment as

Leave a Comment