Professional Documents
Culture Documents
Table of Contents
Payment Methods
Various payment methods are configured with Umoja each of which applies to different payee
destinations.
These payment methods are entered in payment documents by the processors which can then
be amended by Cashiers.
Common Payment Methods are:
A – Bank Transfer (ACH-CCD): For payee bank in the US, currency USD
H – Vendor will pick up cheque at Cashier window
Q – Cheque will be mailed. In this case the correct mailing address must exist in the
vendor record
S – SEPA: (Single Euro Payments Area) For payee bank in Eurozone and currency
of payment is Euro
W – Wire (SWIFT MT103): Used in all other regions
Y – For travel advances through Cash Journal (cash payments)
Key Concepts
The key points covered in this User Guide are listed below:
After the Umoja implementation, the concept of House Banks will be introduced
House bank accounts will enable missions to make international payments
The Umoja subsystems used to process outgoing payments: Financial Payment Program,
Treasury Payment Program and SAP Bank Communications Manager
The Umoja Cash Journal is used to post 3 types of outgoing payments: petty cash
disbursements, imprest disbursements, cashier’s imprest disbursements
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Module Introduction
The Outgoing Payments process identifies the steps to create a payment proposal, conducts
required cash sufficiency checks, holds a payment (if necessary) and release the payment.
The first step for processing an outgoing payment is to create a payment proposal. In this step,
Umoja scans all documents that are due for payment by a particular date, creates list that can
be paid, identifies documents that cannot be paid listing reason and creates exception list for
review/fix by users/Cashiers.
7. Enter the document number in the Values field. Use a comma when specifying more
than one document number
Note: The options in step 9 are required to get the log reports which help identify error in case
document falls in Exceptions.
The Information pop-up window displays “Payment Release List is activated; see long text”.
17. Click the Status button until the message “No parameters entered as yet” displays in
the Status tab
The transaction F110 has successfully identified the payable documents for a particular vendor.
Now we have to pay the documents which is done through steps in T-code FPRL_LIST.
Note: UNHQ treasury will run the F110 three times daily, 7 AM, 3 PM and 9 PM. Offices will do
the approval and payment from their house banks.
Note: All payment proposals must be assigned to a Payment Release List in order to be
processed and released in Umoja. The FPRL_LIST screen displays the last Payment Release
List created by the user. If no Payment Release Lists have been created, the screen displays
blank.
Note: Selecting a processor enables the system to pull all payment proposals created by that
user into the list being created.
Note: In previous slides we say what Cashier have to do when there is an emergency payment
which cannot wait for the scheduled payment run by UNHQ Treasury which is executed daily at
7 AM, 3 PM and 9 PM. The 7 AM and 3 PM runs cover cheque and cash payments while 9 PM
run covers other payment methods (W, X, S, etc).
Following the scheduled run, UNHQ, Treasury will assign all items in the FPRL_LIST.
Having approved the payments and after checking the cash sufficiency at the nominal account
level, the user merges payments. Merging will ensure that vendor (with multiple document) gets
only one payment.
3. The Creation of Cross-Payment Run Payment Media screen is displayed. Populate the
following fields:
Run Date: The processing date (not the value date)
House Bank
Payment Method
Currency
4. Click the Execute icon
5. The pop-up window displays the number of payments selected, the medium run created
and the program has started as a separate job
Note: After scheduling a payment run, the payment batch is automatically sent to the SAP Bank
Communication Management (BCM) program to be released. The batch will not be released
from BCM until it has been approved by the bank signatories associated with the House Bank
account the money is being withdrawn from.
Let’s take a closer look at the BCM and review the process followed by the bank signatory to
approve (and ultimately release) the payment batch.
3. The Payment Batches screen appears displaying all payment batches created in the
system. A batch can be easily located by referencing its run date or its three letter
identification. As stated in each line item, a batch requires approval by two separate
bank signatories
The Payment Batches screen groups batches into separate tabs based on status:
The batch is now ready for approval by the second bank signatory.
The second Bank Signatory approval triggers the automatic release of the batch. For
batches containing electronic payments, a SWIFT202 message is automatically generated and
sent to notify the bank that the specified amount must be drawn and deposited in the vendor’s
bank account. For cheques, the second Bank Signatory approval triggers cheque printing. It
is thus important that the second approver coordinates with the Cashier’s Office where the
cheque printer is installed.
The Batch and Process Monitor screen is a component of the Bank Communications
Management program and is used to conduct the following activities:
Review SWIFT messages sent to banks following batch approval
Manage cheque log and print cheques
3. The Batch and Payment Monitor screen is displayed. Populate the following fields:
Company Code
House Bank
Run Date
The Batches screen displays all the batches that fit the criteria.
A consolidated list of all batches is displayed in the “All” tab. Batches are also listed in separate
tabs according to status:
4. Click the Select button on the left side of the desired batch
5. Click the Files icon
The pop-up window displays the SWIFT MT202 message sent to the bank.
To view and modify cheques, run the T-code FCHN. The Check Register screen will be
displayed.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Module Introduction
The Cash Journal is a functionality in Umoja that is used to record the following types of cash
transactions:
Outgoing Payments
- Main Cashier's Imprest Disbursements
- Imprest Disbursements
- Petty Cash Transactions
Incoming Payments
- Cash Receipts
- Cheque Receipts
The incoming cash and cheques should be recorded in the Incoming Cash Journal.
The first step in the Cash Journal is recording the opening balance from the cutover activity.
Same process is used to record the replenishment in the cash journal.
Cashier Imprest Journal, Imprest Journal and Petty Cash Journal follow same process.
3. The Cash Journal pop-up window is displayed. Enter 1000 in the Company Code field
Key Terminology
None.
6. The Main Cashier's Outgoing Journal is displayed. Click the Today button to ensure
that the available balance of the journal is up to date
8. Click the Matchcode icon in the Business Transaction field. A pop-up window is
displayed. Select RECEIPT BANK ACCOUT from the list
Key Terminology
None.
16. Click the Select button on the left side of the document to view the FI documents
17. Click the Follow-on doc button
18. Double-click Accounting Document in the pop up window
19. The FI document displays Cash in Hand is debited and Clearing Account is credited.
Cash Journal is ready to post disbursements
1. Click the Cash receipts tab and populate the following fields:
Business Transaction: Enter REVENUE
Amount
G/L account: Contact Accounts Unit for appropriate GL account. If Accounts team
is not available, select 39201020 (Unapplied Cash)
Text: Enter appropriate text identifying reason for receipt
Reference: Enter appropriate reference
Assignment Number if any
Business Area
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Module Introduction
Cash disbursements are entered in the Cash Payments tab of the Cash Journal.
Three types of Cash Payments are configured and should be selected from match code:
• PAYMENT TO BANK ACCOUNT: When we send cash to the UN bank account, we
use Payment to Bank Account to record
Dr Bank Cheque-In Clring Acct (Fund 64VQA, Bus Area S101)
Cr Cash Journal (line generated by system)
Note: All Bank Clearing accounts belong to Fund 64VQA and Business Area S101.
• PAYMT ON CLEARING ACCT: All payables with payment method Y will debit
(clear) the AP Payable account (Vendor) and credit GL 35109920 when the cashier
posts the payment with F110 and FPRL_LIST. We use Paymt on Clearing Acct to
record
Dr 35109920 – Cash Payment Clearing
Cr Cash Journal (line generated by system)
• PAYMT ON EXPENSE ACCT: When the item to be paid is not already set up as an
account payable through MIR7 or FV60, we use the business transaction Paymt on
Expense Acct to record
Dr Expense with Cost Center/Order/WBSE (GL 7xxxxxxxx)
Cr Cash Journal (line generated by system)
The table below shows the common fields to be filled for Cash Payments transactions.
Notes:
Receipt Recipient: In the Receipt Recipient field, enter the name of the person (e.g.
courier) who delivered the receipt or received the payment. For Payment to Bank
Account, enter the name of the person who is bringing the deposit to the bank
Posting Date: Transactions should be recorded on the same day as they happen.
Thus posting date will usually be today. However, it is possible to back date the
posting date up to the go-live date if needed. For example, after go-live, it usually
takes a few days before we open the cash journal so we will want to back date the
first transactions for the month
Assignment: The Assignment field is filled in when we have a clearing a pre-existing
item. We have to find the Assignment field of the pre-existing item and enter it in the
Assignment field on the Cash Journal
Key Transactions
Transactions T-Code
Creating Payment Proposal F110
Making Payment FPRL_LIST
Scheduling Payment Run FBPM1
Releasing Payment Files BNK_APP
Processing Incoming Receipts/Cash Payments
FBCJ
Key Terminology
None.
4. Click the Select button on the left side of the item
5. Click the Post button. Document is post
9. Click the Select button on the left side of the document to view the FI documents
10. Click the Follow-on doc button
11. Double-click Accounting Document in the pop up window
12. The FI document displays that Cash is credited, Expense is debited and VAT
recoverable is established
Transactions T-Code
1. Enter the total amount paid including
Creating PaymentVAT inProposal
the Amount field F110
2. Making
Click the empty Tax Code box Payment FPRL_LIST
3. Click the drop-downScheduling
list to make the Payment
Limitations Run FBPM1
box appear
4.
Releasing Payment Files BNK_APP
Enter the Tax Country and click the Green check button
Processing Incoming Receipts/Cash Payments
5. Select the tax code
FBCJ
6. Proceed to enter the rest of the information as usual
Key Terminology
None.
In the example, the amount of LBP 350 included the tax of 10%. The finance document
reflects:
A reduction of the petty cash of LBP 350
An expense of LBP 318.18
VAT recoverable for LBP 31.82
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Key Transactions
Transactions T-Code
Key Terminology
None.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *