You are on page 1of 30

BP.

080 FUTURE PROCESS MODEL


BR.030 BUSINESS MAPPING
MEDSTAR
ORACLE RECEIVABLE IMPLEMENTATION
Authors: Ehab Badreldin,Mohammed Moustafa
Creation Date: Jan, 2008
Last Updated: Jan, 2008
Version: 2

Approvals:

Name Signature
Document Control

Change Record

Date Author Version Change Reference

Jan 2008 Ehab Badreldin, D 1 No Previous Documents


Mohamed Moustafa

Reviewers

Name Position

Distribution

Copy Name Location


No.

Library Master MEDSTAR Project Library


1

2 Project Library CITE Project Library

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page2of30
Contents
Document Control..........................................................................................................2

Contents............................................................................................................................3

Introduction.....................................................................................................................4

AR Future Business Process Outlines..........................................................................5

Open Issues......................................................................................................................9

Event Catalog for Accounts Receivable....................................................................10

Process Description for Accounts Receivable..........................................................11

Process Step Catalogue for PRC-01 “Follow customer definition steps”............12

Process Step Catalogue for PRC-02” Run merge duplicate customers program”
..........................................................................................................................................14

Process Step Catalogue for PRC-03 “Follow bank definition steps”....................15

Process Step Catalogue for PRC-04 “Define Payment Term”...............................17

Process Step Catalogue for PRC-05 “Create customer receipt”............................18

Process Step Catalogue for PRC-06 “Perform invoice creation steps”................21

Process Step Catalogue for PRC-07 “Create credit memo”...................................23

Process Step Catalogue for PRC-08 “Reverse customer invoice”.........................25

Process Step Catalogue for PRC-09 “Create adjusting transaction”....................26

Process Step Catalogue for PRC-10 “Reverse customer receipt”..........................28

Process Step Catalogue for PRC-11 “Follow checks deposit procedures”..........30

Process Step Catalogue for PRC-12 “Review & approve transactions”..............32

Process Step Catalogue for PRC-13 “Print & Review reports & inquiries”........33

Process Step Catalogue for PRC-14 “Perform GL interface steps”.......................35

Process Step Catalogue for PRC-15 “Follow period end procedures”................37

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page3of30
Introduction

This document illustrates typical Oracle Accounts Receivable Implementation


events and business processes. It gives an overall view on how working with
Oracle Accounts Receivable will look like. This document also serves Mapping
document, which will enclose MEDSTAR complete solution.

Events, Processes and Relationship between events and processes


related with Oracle Accounts Receivable module and the business cycle
for MEDSTAR are described and explained in details. All the details of
each process and the corresponding business requirements and
procedure are explained as well.

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page4of30
AR Future Business Process Outlines

1. Accounts Receivable module is a part of order to cash cycle, in AR module you


can find invoices that are created automatically from sales orders or you can
enter invoices that has no relation with sales orders, in AR also you can handle
the collection of invoices and all types of payment received from customers.

2. Customers will be defined in the system with their sites (addresses); these sites
or addresses are used for shipping and for billing as well. The customer must
have at least one site to be used for shipping & billing activities.

3. Under the same customer, there will be an ability to generate invoice for a
particular site and receive payment from another site “No Restrictions”.

4. Customer number will be entered automatically.

5. Customer site will be numbered automatically.

6. Receivable transaction type will be as the following:

 Wholesale

 Retail.

And each Transaction type linked with various sales order type grouping
these types.

7. Accounts receivable in GL will be classified as follows:

 AR Trade local

 AR Trade Export

8. Each customer will be linked to his relevant receivable account in GL. The
receivable account will be linked at the customer address level, the link between
customers and receivable account should be done by finance department.

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page5of30
9. Several revenue accounts (Sales Revenue) are going to be defined and used for
basic sales according to AR Transaction types

10. The purpose of tracking each product sales separately, there will be a link
between the sales revenue account and the product code; this link will be
defined at item level.

11. All types of invoices will be numbered automatically by the same sequence and
starting from number the last numbered.

12. Some of payment terms are used as the following:

 Immediate

 Week.

 15 days.

 Net30

 45 Days.

13. Discount will be taken 1.5% when payment term is Net 30 and the
Payment is within one week from invoice issue date.

14. The types of taxes that are used is Sales Tax and will be defined twice one
for inclusive and another for exclusive and its source will be the
customer.

15. Withhold tax .5 % will be added on transaction lines level depending on


customer.

16. For the customers that are in the same time suppliers netting will be used
for settle balance in AR module with his payable balance.

17. In case of customer returns a credit memo transaction will be created and
applied to the original invoice to reduce the customer balance.

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page6of30
18. There might be a case that one customer may pay for another.

19. Different Payment methods are going to be defined to distinguish between Cash
receipts and checks receipts. The following payment methods will be defined:

 Cash

 Checks

 Bank Transfer

20. Customer deposit will be used and could be partially applied on invoices.

21. The receipt type “Miscellaneous “will be used for recording receipts that has no
invoices or customers.
You can’t apply miscellaneous receipts to
customers or invoices.
22. Receipts are allowed in any foreign currency which means that the receipt
currency could be different from the invoice currency, in this case the system
calculate a cross currency gain or loss.

23. Once the checks are remitted to the bank, the remittance batch should be
recorded in the system to affect the “checks under collection” account.

24. The period end close performed will be “Temporary Close” and not permanent
close for the stability of the implementation.

25. Customer site will be considered as the activity for credit control purpose.

26. Credit control will be affected by Maximum days past due which means that
each customer has maximum days (e.g. 45 days) for his last unpaid invoice and
after these days order will be hold.

27. Customer Profile class will be defined as sector and customer category will be
used for sub sector.

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page7of30
Open Issues

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page8of30
Event Catalog for Accounts Receivable
Event Name Description
Id

EV-01 New Customer New customer including customer sites required to be


defined in the system.
EV-02 Customer Customer is defined in the system with different codes or
Duplication is same Customer sites with different codes
Found
EV-03 New Banks / New banks / accounts required to be defined in the
Accounts system including all related data.
EV-04 New Payment New customer payment terms to be defined in the system
Term
EV-05 Deposit Received Advances from Customers are paid as deposit
From Customer
EV-06 Goods Shipped to Goods were issued to the customer
Customer
EV-07 Goods Returned Goods returned from customer, returns can be partial or
From Customer full
EV-08 Invoice To Be Existing invoice in the system is wrong and needed to be
Cancelled cancelled.
EV-09 Invoice To Be Customer invoice needs adjustment.
Adjusted
EV-10 Customer Receipt is Customer receipt required to be cancelled.
Cancelled.
EV-11 Checks Deposited Customer received checks are deposited in the bank for
in The Bank collection.
EV-12 Invoice Information Invoice information including lines, discounts and freight
is Complete are entered from the customer invoice and reviewed.
EV-13 Customer Balance Review customer transactions and balance
Inquiry
EV-14 GL Interface GL interface procedures to be performed to reflect the
impact of the Accounts Receivable transactions in the GL
module
EV-15 Period End Perform period end procedures for the current period
Procedures

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page9of30
Process Description for Accounts Receivable

Event Event Process Process Title Involved


Id Id Department

EV-01 New Customer PRC-01 Follow customer definition Financial


steps
EV-02 Customer PRC-02 Run merge duplicate Financial
Duplication is Found customers program.
EV-03 New Banks / PRC-03 Follow bank definition steps Financial
Accounts
EV-04 New Payment Term PRC-04 Define Payment Term Financial

EV-05 Deposit Received PRC-05 Create customer receipt Financial


From Customer
EV-06 Goods Shipped to PRC-06 Perform invoice creation steps Financial
Customer
EV-07 Goods Returned PRC-07 Create credit memo Financial
From Customer
EV-08 Invoice To Be PRC-08 Reverse customer invoice Financial
Cancelled
EV-09 Invoice To Be PRC-09 Create adjusting transaction Financial
Adjusted
EV-10 Customer Receipt is PRC-10 Reverse customer receipt Financial
Cancelled.
EV-11 Checks Deposited in PRC-11 Follow checks deposit Financial
The Bank procedures
EV-12 Invoice Information PRC-12 Review & approve Financial
is Complete transactions
EV-13 Customer Balance PRC-13 Print & Review reports & Financial
Inquiry inquiries
EV-14 GL Interface PRC-14 Perform GL interface steps Financial

EV-15 Period End PRC-15 Follow period end procedures Financial


Procedures

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page10of30
Process Step Catalogue for PRC-01 “Follow customer definition steps”

Event Id Event Process Process Title Department(s)


Id

EV-01 New Customer PRC-01 Follow customer definition


steps

ID Description

PRC-01.1 Check the existence of the customer


PRC-01.2 Define new customer
PRC-01.3 Define customer site address

Policies/Procedures
Customers: Standard

 Type the customer name and select ‘Find’, if the customer exists, then the customer
data will be displayed.
 After checking the customer existence, if does not exist then select ‘New’ and enter
the customer data.
 Enter the customer site address by specifying the ‘Bill To’ & ‘Ship To’ addresses.
 The customer number will be defined manually and NOT generated by the system
 Every customer location is considered as separate account balance .
 To make certain location as a default location to be used in invoice entry, check
‘Identifying Address’ check box.
 Select profile class for the customer and you can override the data driven from the
profile class.
 Profile class includes many default data that can be grouped together and then
assigned to the customer and this profile class includes as example the following
data:

1. Terms options
2. Receipt options
3. Credit options
4. Currency limits and amounts

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page11of30
Process Step Catalogue for PRC-02” Run merge duplicate customers program”

Event Id Event Process Process Title Department(s)


Id

EV-02 Customer PRC-02 Run merge duplicate


Duplication is customers program.
Found

ID Description

PRC-02.1 Inquiry on customer


PRC-02.2 Run merge duplicate customers program.

Policies/Procedures

Customers: Standard

 Query and find duplicate customers.


 Using the navigation: Customers: Merge Run merge duplicate customers program
to merge transactions between the duplicate customers.
 Specify customer Name / Number and address to copy from.
 Specify customer Name / Number and address to copy to.
 Select to delete the original customer after ‘Merge’ by checking the check box
‘Delete after merge’
 The merge process can be performed between two sites for the same customer, and
in this case checking the check box ‘Delete after merge is NOT allowed.
 Print ‘Duplicate Customer Report’ to identify the duplicate customers.
 Review customer information by printing Customer Listing Summary and Details
Report to decide the sites that will be merged.
 Use the ‘Customer Merge Execution Report’ to review the merge process execution,
this report is generated automatically from the system while submitting the merge
process.

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page12of30
Process Step Catalogue for PRC-03 “Follow bank definition steps”

Event Id Event Process Process Title Department(s)


Id

EV-03 New Banks / PRC-03 Follow bank definition steps


Accounts

ID Description

PRC-03.1 Define bank / Account


PRC-03.2 Define new Payment method (optional)
PRC-03.3 Attach the bank account to the payment method

Policies/Procedures

Setup: Receipts: Banks

 Define the bank name and the institution type as ‘Bank’ also specifies the bank
address and bank branch.
 Bank Accounts are shared between the AR and the AP module. Same bank
accounts can be used with both modules by defining each module options.

 To define Bank Accounts perform the following:

1. Query existing bank.


2. Select bank accounts: enter bank account name, number and functional
currency.
3. Optionally enter check digits for bank account validation purposes.
4. Select internal account use.
5. Enter the GL cash accounts in the GL accounts region.
6. For Cash Management module, specify the cash clearing, bank charges, and bank
error GL accounts.
7. For Account Receivables module, specify the Receivables option and more
Receivables option.
8. Specify payable options, if multiple currency payments option is allowed, then
GL realized gain & loss accounts would be used.

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page13of30
 Define Payment Method using the navigation: Setup: Receipts: Receipt Classes
 Query and find Receipt Class.
 Define Payment Method by entering the payment method name

 The relation between ‘Receipt Class’ and payment method is One to Many, which
means that more than one payment method can be attached with the same Receipt
Class.

 From the Receipt Class window select the ‘Bank Accounts’ button and attach the
payment method to Bank Accounts.

 The relation between ‘Payment Method’ and ‘Bank Accounts’ is One to Many,
which means that more than One bank account can be attached with the same
payment method.

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page14of30
Process Step Catalogue for PRC-04 “Define Payment Term”

Event Id Event Process Process Title Department(s)


Id

EV-04 New Payment PRC-04 Define Payment Term


Term

ID Description

PRC-04.1 Define Payment Term

Policies/Procedures

Setup: Transactions: Payment terms

 Enter payment term name and description.

 Select Discount Basis rule to specify the base used for discount calculation.

 Enter the effective date and make sure to NOT to specify the current date, as
invoices entered with previous date will not be able to use this payment term.

 Enter the sequence number, the relative amount and the due days and as
example to define payment term that specifies that 3% to be paid within 10
days and 2% within 30 days:

1. Specify 3 in the percentage column with 10 in the column days


2. Specify 2 in the percentage column with 30 in the column days

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page15of30
Process Step Catalogue for PRC-05 “Create customer receipt”

Event Id Event Process Process Title Department(s)


Id

EV-05 Deposit / PRC-05 Create customer receipt


Receipt Received
From Customer

ID Description

PRC-05.1 Create customer receipt


PRC-05.2 Print system reports

Policies/Procedures

The Receipts window is used to enter new or query existing receipts. For each receipt, you
can see whether the receipt is identified and what portion of the receipt has been applied,
placed on– account, and left unapplied.
There are two types of receipts in Receivables:

Cash receipts: Received payment (such as cash or a check) from customers for goods or
services.

Miscellaneous transactions: Revenue earned from Non-sales invoices.

Receipts: Receipts

NOTES:

 If the customer is not specified in the receipt window, then the receipt will be
unidentified and will update the unidentified receipts GL account
 Unidentified receipts cannot be applied to invoices.
 View the accounting lines for the receipt from the ‘Tool’ menu.
 Print and review ‘Receipt Register’ report

 The receipt status has one of the following statuses:

1. Confirmed: For manual receipts this status indicates that the receipt belongs to a
receipt class that requires remittance.
2. Remitted: The receipt has been remitted (which means that the check has been sent

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page16of30
to the bank.
3. Cleared: The receipt has been reconciled in the bank
4. Reversed: The receipt has been reversed; this status is valid for cash receipts and
miscellaneous receipts.

To enter receipt:

1. Enter receipt data including receipt number, date, GL date, currency, and amount
and payment method.
2. Payment method specifies the account to be updated, bank accounts and the receipt
status.
3. Enter customer name or number otherwise the receipt will be unidentified.
4. Select ‘Mass Apply’ to automatically apply the receipt on invoices, and the
remaining of the receipt will be on account.
5. To re-apply the receipt to another invoice, uncheck the check box of ‘Apply’ and
open a new line to select the correct transaction

Accounting Transactions
 When the receipt is entered:

DR/ Cash
CR/ Receivable

 When the receipt is entered and applied

DR/ Cash
DR/ Unapplied Cash
CR/ Unapplied Cash
CR/ Receivables

 IF the receipt is unidentified

DR/Cash
CR/Unidentified

 IF the receipt uses payment method requires remittance:

DR/ Confirmation
CR/ Receivables

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page17of30
Process Step Catalogue for PRC-06 “Perform invoice creation steps”

Event Id Event Process Process Title Department(s)


Id

EV-06 Goods Shipped PRC-06 Perform invoice creation steps


to Customer

ID Description

PRC-06.1 Review issuing voucher


PRC-06.2 Manual review customer prices
PRC-06.3 Create invoice
PRC-06.4 Approve invoice

Policies/Procedures

 Check the issued voucher from the stores department and review the following :
Customer – Items – Quantity
 Review the customer prices and check the price list to enter the customer item price.
 Enter customer invoice using the navigation : Transactions: Transactions

1. Enter transaction date and transaction currency, the default currency is ‘SAR’ (the
functional currency)

2. Select transaction source ’Manual’, and the transaction type ‘Invoice’

3. Specify the GL date and the default GL date is the end of period for the last opened
period (Current)

4. Select the ‘Bill To’ and the ‘Bill To Location’, the default ‘ Bill To Location’ will be
automatically displayed (the location having ‘Primary Address’ check box is set to ‘Yes’.

5. Payment terms will be automatically displayed from the customer profile class and can be
overridden.

6. Transaction number will be automatically driven from the transaction source when saving the
transaction and cannot be changed.

7. Select the item and specify the quantity and unit price, the system will display item
total value.

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page18of30
8. From ‘Distribution’ review the General Ledger distribution accounts

9. Select ‘Complete’ when finishing all invoice data.

Accounting Transactions
DR/ Receivables (specified in the customer site)
CR/ Revenue (specified in the item data)
CR/Freight (if Freight is applied)

NOTE:

 After transaction completing select ‘Tools’ to review invoice lines, adjustment,


balances.

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page19of30
Process Step Catalogue for PRC-07 “Create credit memo”

Event Id Event Process Process Title Department(s)


Id

EV-07 Goods Returned PRC-07 Create credit memo


From Customer

ID Description

PRC-07.1 Review return voucher


PRC-07.2 Create Credit Memo

Policies/Procedures

 Check the returned voucher from the stores department and review the following :
Customer – Items – Quantity
 A transaction must be complete before you can create a credit memo against it.
 Use the transaction window to enter Credit Memo: Transactions: Transactions

1. Query the invoice to be credited


2. From the tool bar select ‘Credit’ and the credit transaction window is displayed
3. Select the type ‘Credit Memo’
4. Enter the GL date
5. Specify percentage in the percentage field with positive sign or enter amount in the
amount field with negative sign
6. Select complete to complete the transaction.

To enter a Credit Memo using the Credit Transaction

1. Use the Navigation Transactions > Credit Transactions


2. Enter the transaction number then select Find
3. Follow the previous steps starting from sequence (3)

Accounting Transactions

DR/ Revenue

CR/ Receivable

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page20of30
Process Step Catalogue for PRC-08 “Reverse customer invoice”

Event Id Event Process Process Title Department(s)


Id

EV-08 Invoice To Be PRC-08 Reverse customer invoice


Cancelled

ID Description

PRC-08.1 Review invoice data


PRC-08.2 Reverse invoice

Policies/Procedures

This option is used to cancel any customer invoice; there are 2 cases when canceling the
invoice:

 The invoice is NOT completed


 The invoice is completed

Use the Navigation: Transactions: Transactions

To Cancel Customer Invoice:

 If the invoice is not completed then select ‘Edit>Delete>Record’ and confirm the delete
option.

 If the invoice is completed then follow the steps of entering a Credit Memo

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page21of30
Process Step Catalogue for PRC-09 “Create adjusting transaction”

Event Id Event Process Process Title Department(s)


Id

EV-09 Invoice To Be PRC-09 Create adjusting transaction


Adjusted

ID Description

PRC-09.1 Review Invoice Data


PRC-09.2 Create adjusting transaction
PRC-09.3 Print system reports

Policies/Procedures

 Setup Approval Limits before using Adjustments.


 You can enter an amount greater than the balance due only if the transaction type’s
Allow over application option is set to Yes (for the transaction you are adjusting)
 Use the following navigation: Transactions: Transactions Summary

1. Navigate to the Transactions Summary window.


2. Query the transaction to be adjusted.
3. Select the transaction, and then choose Adjust.
4. Enter an Activity Name and choose the Type of adjustment you are creating.
Valid adjustment types include Invoice, Line, Charges, Freight, and Tax.
5. Enter the Amount of this adjustment. If you specify ’Invoice’ as your
adjustment type, Receivables requires that the amount of your adjustment be
at least enough to close the item you are adjusting, and displays this value in
the Amount field.
6. Enter adjustment date and GL date, the default is the current date but can be
changed.
7. Open the Account IDs tabbed region, and then modify the GL Account (if
required) for this adjustment. The activity name provides the default GL
account.
8. Open the Comments tabbed region, then enter a Reason for creating this
adjustment (optional). Receivables print your reasons on the Adjustment
Register.
9. Optionally Update the Status of this adjustment. If this adjustment is within
your user approval limits, you can choose any status. If you are reviewing a
previously approved adjustment, Receivables skips this field.

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page22of30
10. Save the work and Receivables generates unique number for this transaction.

Accounting Entries:

 In case of positive adjustments:

DR/ Receivables

CR/ Adjustment Account (specified with the adjustment type defined in


Receivable Activities)

 In case of negative adjustments:

DR/ Adjustment Account (specified with the adjustment type defined in Receivable
Activities)

CR/ Receivables

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page23of30
Process Step Catalogue for PRC-10 “Reverse customer receipt”

Event Id Event Process Process Title Department(s)


Id

EV-10 Customer Receipt PRC-10 Reverse customer receipt


is Cancelled.

ID Description

PRC-10.1 Query and select receipt


PRC-10.2 Reverse customer receipt

Policies/Procedures

 There are Two types of reversals:


 Standard
This type is used if the receipt was applied to Charge Back or Adjustment that was NOT posted
to GL,
 Debit Memo Reversal
This type is used If the receipt was applied to Charge Back or Adjustment that was posted to
GL, OR if the receipt was applied to a Charge Back that has an activity on it (another receipt or
adjustment)
The created credit memo can inherits the same original receipt number if selected in the receipt
class definition,

To reverse customer receipt:


1. Query and find the receipt to be reversed.
2. Review the receipt details and applications.
3. Select ‘Reverse’
4. Enter the reverse date, GL reversal date, category and reason.
5. To create Standard Reversal select ‘Reverse’
6. To create a Debit Memo reversal, check the debit memo reversal check box and enter the transaction type and
account, then select reverse.

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page24of30
Process Step Catalogue for PRC-11 “Follow checks deposit procedures”

Event Id Event Process Process Title Department(s)


Id

EV-11 Checks Deposited PRC-11 Follow checks deposit


in The Bank procedures

ID Description

PRC-11.1 Create remittance batch


PRC-11.2 Approve the remittance batch
PRC-11.3 Print system reports

Policies/Procedures

 The Remittance process is used to deposit checks in the bank for collection. When
the check is collected, the receipt status is ‘Cleared’ and the bank account increases
with the collected check.

 Use the navigation: Receipts: Remittances


 To Deposit Check (Remit a receipt)

1. Navigate to the window Receipts> Remittances.


2. Select ‘New’ to define new remittance batch.
3. Select the Bank, Branch, Account, and the currency will be driven from the bank
account.
4. Enter the bank deposit number (Optional)
5. Select ‘Manual Create’ to enter selections.
6. Enter the selection criteria then CTL+F11
7. Check the ‘Select’ check box to select the receipts to be remitted to the bank.
8. Approve the selections
9. Print the ‘Remittance Batch Management Report’ and review the remitted check
report.
Accounting Transactions:

 When the check is remitted on the bank:


DR/ Remittance
CR/ Confirmation

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page25of30
Process Step Catalogue for PRC-12 “Review & approve transactions”

Event Id Event Process Process Title Department(s)


Id

EV-12 Invoice PRC-12 Review & approve


Information is transactions
Complete

ID Description

PRC-12.1 Review invoice information


PRC-12.2 Approve invoice

Policies/Procedures

 Use the navigation: Transactions: Transactions


 Review transaction distributions, tax, and line items.
 Select ‘Complete’ to approve transaction details.
 From ‘Tools’ select view accounting, overview and line items.

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page26of30
Process Step Catalogue for PRC-13 “Print & Review reports & inquiries”

Event Id Event Process Process Title Department(s)


Id

EV-13 Customer PRC-13 Print & Review reports &


Balance Inquiry inquiries

ID Description

PRC-13.1 Print system reports


PRC-13.2 Review reports
PRC-13.3 Review Inquiries

Policies/Procedures

 Receivable lets you view customer account information in a variety of ways. You
can view the total amount overdue for a customer or customers in the Account
Summary window.
 You can view all transactions that are past due for a specific customer in the
Account Details window.
 The Customer Accounts window displays a customer’s credit limit and available
credit if you set Display Currency to yes in the Find Customer Accounts window.
 Receivable displays a customer’s current account balances in the functional currency
using the most recent exchange rate.
 Use the navigation Reports: Accounting
 Print and review transactions register reports and aging reports.
 Use the navigation Collections: Customer Accounts

1. Navigate to the Customer Accounts window using the above navigation.


2. Enter selection criteria in the Find Customer Accounts window.
3. Select Find.
4. To view transaction totals by their entered amounts, choose an Amount Type of
Original Amount. To view transaction totals by the amount due, choose an Amount
Type of Amount Due Remaining. The default is the transaction amount due.
5. To view the total number and amount of on time, late, non–sufficient funds (NSF),
finance charges, and discount for this customer, open the Key Indicators tabbed
region.
6. To view transactions for a different period, select a different period. To view
transaction totals for more than one period, select a period, press and hold the Shift

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page27of30
key, then select another period.
7. You can view transaction summary or details by selecting ‘Transaction Overview’

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page28of30
Process Step Catalogue for PRC-14 “Perform GL interface steps”

Event Id Event Process Process Title Department(s)


Id

EV-14 GL Interface PRC-14 Perform GL interface steps

ID Description

PRC-14.1 Review transactions reports


PRC-14.2 Run GL posting program

Policies/Procedures

 Run the General Ledger Interface program to transfer Receivables transaction


accounting distributions to the general ledger interface table and create either
detailed or summarized journal batches.
 Receivable lets you create un-posted journal entries in your general ledger when
you run General Ledger Interface.
 Post journal batches in Oracle General Ledger to update your account balances.

Use the Navigation: Interface: General Ledger

1. Navigate to the Run General Ledger Interface window.

2. Choose a Posting Detail of Summary or Detail, detail means that a journal will be
created for every transaction, but summary means that one journal entry will be
created for each account.

3. Enter the GL Posted Date for the created journal in the GL, (the journal posting date
in GL)

4. Enter the range of GL Dates for your submission.

5. Choose whether to Run Journal Import.

6. Save your work.

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page29of30
Process Step Catalogue for PRC-15 “Follow period end procedures”

Event Id Event Process Process Title Department(s)


Id

EV-15 Period End PRC-15 Follow period end


Procedures procedures

ID Description

PRC-15.1 Run the auditing reports


PRC-15.2 Create adjusting transactions (if any)
PRC-15.3 Post transactions to GL
PRC-15.4 Close the current period
PRC-15.5 Open the new period

Policies/Procedures

 Open and close accounting periods in your calendar to control the recording of
accounting information for these periods.
 Receivables let you open future accounting periods while your current period is still
open.
 Receivables also lets you reopen previously closed accounting periods and enter
receivables activities without transferring transactions to the general ledger when
you set your accounting periods to ’Future.’
 Use the navigation Control: Accounting: Open/Close Periods

The period Status is one of the following:


Closed: Journal entry, posting, and transaction entry are not allowed unless the
accounting period is reopened. Receivables verify that there are no unposted items in
this period. Receivable does not let you close a period that contains unposted items.
Close Pending: Similar to Closed, but does not validate for unposted items. Journal
entry, posting, and transaction entry are not allowed unless the accounting period is
reopened.
Future: This period is not yet open, but you can enter transactions in this period.
However, you cannot post in this period until you open it.
Not Opened: This period has never been opened and journal entry and posting are not
allowed.
Open: Journal entry and posting are allowed.

“MedStar” Oracle Receivable Implementation


Future Process Model, and Business Requirements Mapping
Company Confidential – For Internal Use Only
Page30of30

You might also like