01.05.2017 Views

534857304

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 9 ■ Defining the House Bank<br />

Follow this menu path to customize your manual bank statement: IMG: Financial Accounting (New) ➤<br />

Bank Accounting ➤ Business Transaction ➤ Payment Transactions ➤ Manual Bank Statement ➤ Create and<br />

Assign Business Transaction. Or use transaction code OT52.<br />

The initial screen where you will specify the manual bank statement, called Change View: Manual Bank<br />

Statement Transactions”: Overview, appears. Click the<br />

button on the top-left side of the screen. The<br />

New Entries: Overview of Added Entries screen is displayed (Figure 9-15). This is where you create new business<br />

transactions for your manual bank statement and assign them to the posting rules you defined previously.<br />

Figure 9-15. Creating and assigning business transactions<br />

Update the following items:<br />

Transaction: Enter the transaction codes that you want to use for your manual<br />

bank statement. You can enter a maximum of four digits for each transaction<br />

type for the system-posting rule. For example, in this activity we used MCHG<br />

for Manual Bank Charges, MTRN (Manual Transfer for Bank Transfer), MICK<br />

(Manual Incoming Checks for Incoming Checks), MOCK (Manual Out Going<br />

Checks) for outgoing checks, and MRIT (Manual Reconciliation Items) for<br />

reconciliation Items.<br />

■■Note<br />

You can use any transaction code as long as it makes sense to you.<br />

+/- Sign: This field allows you to further differentiate your business transactions.<br />

The plus (+) sign in front of a business transaction code indicates receipt and the<br />

minus sign (-)indicates payment.<br />

Int algthm: Enter 011 in the outgoing check field only.<br />

Text: Enter short texts that describes each item transaction here.<br />

137

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!