Académique Documents
Professionnel Documents
Culture Documents
Use For
#AUTOMNT
Processing automatic
maintenance only.
The algorithm group
#AUTOMNT has a very
specific purpose and you
cannot use it for
payment processing.
MATCH
Matches negative and positive items of
the same amount for a customer.
OLDEST
Matches open debits to open credits in
oldest first order by debit due date.
Important! This algorithm group should
have only one of its respective algorithms
enabled at one time.
#BALANCE
BALGR
Selects all open items.
BALNET
Selects all open items minus earned
discounts.
UNDISGR
Selects all open items that are not in
dispute.
UNDISNT
Selects all open items that are not in
dispute minus earned discounts.
#COMBOS
DEBITGR
Selects a single unique open item.
DEBITNT
Selects a single unique open item minus
earned discount.
ANY2GR
Selects any two unique open item
balances combined.
#OLDEST1
OLDEST
Selects open items in oldest first order by
due date. Creates a partial payment for
the next item.
#OLDESTC
CREDITS
First adds all credits to the payment
amount. Then selects open items in oldest
first order by due date. Creates a partial
payment for the next item.
#PASTDUE
PASTGR
Selects all past due open items.
PASTNET
Selects all past due open items minus
earned discounts.
#REFS
ITEMREF
Selects all open items identified by the
references regardless of customer
identification. Enables you to add a unique
debit or credit item for an underpayment
or overpayment that completes the
application.
#REF_ONE
ONECUST
Selects all open items identified by the
references limited to the customer whose
MICR ID or customer ID is supplied with
the payment. Enables you to add a unique
debit or credit item that completes the
application.
#REFS_NG
#DETAIL
DETAIL
Selects all open items identified by
matched references. Closes the item but
creates an item level adjustment that
refers back to the original item for any
difference between the item amount and
the reference amount supplied with the
item reference. Also accepts WS-08 and
WS-12 deductions references. Payments
with detail references should balance but
if not, a payment level adjustment can
also be created to balance the payment
as in #REFS.
#DTL_TLR
DTL_TLR
Selects all open items identified by
matched references. Closes items that
match the payment amount. If there is an
underpayment, it looks at the bill to
customer to see whether partial payments
are allowed. If allowed, it creates a partial
payment on the item. The actions taken
are based on the selections on the
Predictor Detail Options page.
#STATMNT
STMTALL
Selects items from the most recent
statement.
STMTDIS
Selects undisputed items from the most
recent statement.
Payment worksheets use information about customers and items to apply payments. The
system creates one worksheet for each payment, not one for each deposit.
Navigation: Accounts Receivable, Payments, Apply Payments, Create Worksheet
In Deposit ID type the Deposit ID for the batch that you want to view.
Search
This will bring up the list of all your payments in the batch including the payments that have
already been applied to the correct accounts through payment. Under Payment Status it will
either show APPLIED, WORKSHEET, IDENT or UNIDENT. All payments that show as applied are
the ones that have been posted by Payment Predictor and no further action is required on these.
Any that show as IDENT, UNIDENT or WORKSHEET needs to be posted manually by following
the below procedure:
Click on the first entry to be applied
Click on Build
This will bring up the following screen
Unidentified
A (Applied)
W (Worksheet)
C (Complete)
Over/Under Payment
Tick all of the items that are being paid by checking the box next to the invoice ID. If there is then
an under or overpayment, you will need to create either an OA (On Account) item or DED
(Deduction) item. This is done as follows:
Click on the (+) ADD button on the last row of the item list a dialogue box will
then appear where you can select how many rows you want to add (see below)
enter the amount of rows required and then click ok.
Pay amount ~ Enter the amount of the over or under payment (if an
underpayment, ensure there is a minus in front of it, -138.06.)
Type ~ Click on the magnify glass and choose the type of payment OA on
account, PR for prepayment or DED for deduction.
Reason ~ Click on the magnify glass and choose the reason why the money is to
be put on account or as an underpayment.
Save
Part Payment
Check the relevant invoice
Enter the payment amount in the Pay Amount column
Save
When you activate the SAVE button, the systems automatically produces another line showing
the remaining amount of the invoice outstanding.
As shown above the system will indicate in the balance box whether the item has been under or
over paid, in the above case it has been underpaid.
To write this off follow the procedure below:
Click on the (+) ADD button at the end of the item line
Click OK
Choose the type of write off, in this case WAU ~ Write off An Underpayment
Save
This will then give the write off an Item ID, see above
Do Not Post
Post Now
Post Later
Posts the worksheet the next time Receivable Update runs and
creates accounting entries. POST LATER refers to the
Receivable Update process that will generally run only once a
dayperhaps at the end of the work day or later in the evening
after all pending items have been entered. When you set a
pending item to Post Later during the pending item entry
process, you're separating it from those in need of immediate
processing.
Create/Review Entries
Posting Payments
AR_UPDATE
The posting process in PeopleSoft Receivables is known as Receivable Update.
Receivable Update occurs throughout the system as you post pending items.
Although Receivable Update appears to run as one process, it really consists of four
separate processes (or steps).
Step 1
Step 2
Step 3
Step 4
Unposting Payments
You cannot unpost groups unless they have been successfully processed by the Receivable
Update process. Unposting creates a new group that is the exact opposite of the original group.
Unposting a group, in this context, means reversing a completed action that posted items within
PeopleSoft Receivables. If Receivable Update hasn't run yet, groups are set to Post Now or Post
Later but aren't really posted. In that case, click the Do Not Post button on the Group Action page
so that the group will not post.
This procedure can be used to unpost payments that have been incorrectly allocated.
Navigation: Accounts Receivable, Receivable Updates, Unpost Groups
In this menu there are 3 types of unpostings, Payment Group, Maintenance Group and Transfer
Group. In this example we will be working through how to unpost a deposit batch so Payment
Group should be used, however the procedure is similar for each.
If when in the above screen this is not the payment that is to be unposted, click on return to
search and have a look again to see if there are any other payments with the same payment ID. If
this is the correct payment, click on the options tab.
The accounting date does not need to be changed unless the period the original payment was
applied in is close (ie is dated in a month prior to the current month). If this is the case tick the
Edit Accounting date box and in Accounting Date enter todays date.
Click Save
Click on the Action Tab
Because only 1 payment was unposted the system takes you straight into the worksheet, if more
than one payment was unposted a list would be shown.
Then re-apply the payment correctly
Save
And select Worksheet Action
Reports
1. Dunning letter process can generate letters for many customers or produce a single letter
for one customer. (AR_DUNNING) you specify the scope at any of the following levels:
Unit level generates a letter for each correspondence customer in the business unit.
Correspondence customer level generates a single letter containing all past due items for
all customers in the correspondence group.
Customer level generates a single letter for the specified customer's correspondence
customer. Using customer level, you can also generate letters based on specified,
sequential levels and waiting periods (or intervals) between the levels for past due items.
You do this by using the Dunning by Level method.
Every customer within Peoplesoft is allocated a Dunning ID. This Dunning ID dictates
how we will chase the customer, via letter, for overdue invoices.
Letter Code
Dunning ID
Dunning Id - 01
Letter 1
Letter 2 Letter 3 (GD)-
Dunning ID - 02
Letter 2 Letter 3 (GD)-
02 Medium Risk
03 High Risk
04 Ex Legal Account
Dunning ID - 03
Letter 1
Letter 2 Letter 4 -
There is also the functionality within PS for named users to put accounts on Dunning Hold, as
there will be some customers that should not be sent Dunning Letters.
PS 8.8 will automatically calculate, within each group, which letter should be sent, according to
the rules set out above. It will calculate on the oldest invoice, but will include all overdue invoices
within the balance outlined on the letter. Copy invoices will no longer be sent with the Dunning
Letter.
Credit Balances: Dunning Letters are not produced for accounts that have a credit balance.
Credit Items: Dunning Letters include any credit items, although pre-payments are omitted.
Disputed Items: Any items that are marked as disputed are not included in Dunning Letters.
Threshold: Dunning Letters will not be printed for accounts with a balance of 5.00 or less.
Running this process produces the Dunning Letters.
Navigation: Accounts Receivable, Customer Interaction, Dunning letters, Extract Dunning letter
info.
Access the Dunning Letters Parameters page.
Select the AR Dunning (AR_DUNNING) process to retrieve customer data and populate a
temporary table. The PeopleSoft Application Engine extract process retrieves information from
the database and stores it in the PS_AR33000_TMP table. The Application Engine also performs
the following tasks:
Extract process stores the characteristics of each letter in separate database tables so
you can later refer back to any dunning letter's contents on a page in the Collect
Receivables menu.
When the Dunning extract process begins, it assigns a process instance number to all
items it is processing.
The all-levels dunning letter includes all past due items in the age
bracket associated with the dunning level and the text associated with
the oldest or newest item in the letter (depending on the run
parameters that you specify).
AR33001
AR33002
AR33003
AR33005
The Dunning Control report shows all the dunning letters that you
printed from all dunning runs.
AR33006
The Dunning Preview report lists the dunning letters that will print.
Run this report before you print the letters.
2. Aging process (AR_AGING) Generates reports that show which customers have
outstanding receivable balances. Management and collection departments rely on aging
to identify delinquent accounts and to assess possible cash flow issues.
When the Aging process runs, it marks the customers it is processing as being In Use, by
updating the process instance on the CUST_DATA table with the process instance of the current
job.
Aging ID
Instalment
Prepayments
Current
1-30 days overdue
31-60 days overdue
61-90 days overdue
91-120 days overdue
121-180 days overdue
181-365 days overdue
365+ days overdue
Navigation
Usage
RUN_AR30003
Accounts Receivable,
Collections, Aging Reports,
Aging Detail by Unit
RUN_AR30001
Accounts Receivable,
Collections, Aging Reports,
Aging Detail by Tree
RUN_AR30004
Accounts Receivable,
Collections, Aging Reports,
Aging Summary by Unit
RUN_AR30002
Accounts Receivable,
Collections, Aging Reports,
Aging Summary by Tree
RUN_AR30005
Accounts Receivable,
Collections,
Balances/Cash Reports,
Cash Forecast
a customer..