Skip to main content

Entering Bank Statements Manually

In addition to loading bank statement information automatically with the Bank Statement Open Interface, you can enter bank statement information manually. You can enable users to update information on a statement that was previously entered manually or loaded automatically, even if the statement is already reconciled.
When you enter a bank statement manually, you enter the bank statement header and the transaction lines. You can reconcile transaction lines as you enter them, or you can reconcile the bank statement (manually or automatically) after you enter all the transaction lines and save your work.
Note: Cash Management assumes that you enter statements in chronological order, and uses this order to calculate cumulative bank account balances.
Prerequisites
Define your banks.
If you plan to use the Bank Statement Import program, you need to define bank transaction codes for the bank account.
Set up Receivables activities and payment methods for miscellaneous transactions.
If you want to use document sequences, you or your System Administrator must set up sequential document numbering for Cash Management.
Note: For document sequencing, the effective date is the statement date.
If you have enabled the Add Lines to Automatic Statements feature in the System Parameters window, you can add lines to automatically-loaded statements.
To enter a bank statement manually:
1. Navigate to the Find Bank Statements window. Choose New.
2. Choose the New button to display the Bank Statement window.
3. Enter the following bank header information: Account Number, Account Name, Bank Name, Bank Branch, and Currency.
4. Enter the new statement Date.
5. If you use manual document sequence numbers, enter the bank statement Document Number.
Additional Information: If you use automatic document sequence numbers, Cash Management creates the Document Number for the statement automatically. You cannot edit an automatically assigned Document Number.
6. Enter the Statement number. The default Statement Number is the statement date.
7. Enter the GL Date--the default is the Statement Date. The GL Date must be in an open or a future-enterable period in Receivables or Payables.
8. Optionally, enter bank statement Control Totals:
Enter the opening and closing balances as needed. Enter control totals for Receipts and Payments, as well as the number of statement lines for each.
Additional Information: You can compare the Control Total amounts to those displayed by Cash Management in the Line Totals tabbed region of the Statements window, to ensure the completeness and correctness of your entered bank statement.
9. Choose Lines to begin entering your statement lines. Optionally, you can save the header information now and enter the statement lines later.
10. Save your work.

Comments

Popular posts from this blog

Applying Prepayments to Invoices

You can apply the available amount of Item type distributions from a Temporary type prepayment to one or more invoices to offset the amount you pay on the invoice(s). If you entered the prepayment as a Permanent type and want to apply it, you can query the prepayment in the Invoices window and change the Prepayment Type to Temporary. If you use Automatic Offsets then your setting for the Prevent Prepayment Application Across Balancing Segments Payables option controls whether you can apply a prepayment to an invoice or expense report with a different balancing segment. Prerequisites The invoice type is Standard, Mixed, or Expense Report. Today's date is on or after the Settlement Date of the prepayment. The invoice date is on or after the date of the prepayment. The prepayment is type Temporary, fully paid, validated, not cancelled, has no active holds, and has not already been fully applied. The prepayment has the same supplier, invoice currency and payment currenc

Application Utilities Lookups and Application Object Library Lookups

Maintain existing and define additional Lookups for your shared Lookup types. You can define up to 250 Lookups for each Lookup type. Each Lookup has a code and a meaning. For example, Lookup type YES_NO has a code Y with meaning Yes, and a code N with a meaning No. Note: In Releases 11.0 and earlier, there were two Lookup features, Special Lookups and Common Lookups. These two features have been merged into one. The new consolidated Lookups feature has Lookups maintained in this form. If you make changes to a Lookup, users must log out then log back on before your changes take effect. Lookups Block Type Query the type of your Lookup. You can define a maximum of 250 Lookups for a single type. User Name The user name is used by loader programs. Application Query the application associated with your Lookup type. Description If you use windows specialized for a particular Lookup type, the window uses this description in the window title. Access Level The access level restricts changes that

Matching Prepayments to Purchase Orders

You can match a prepayment to a purchase order or receipt. The accounting entries for Item distributions on a matched prepayment typically debit a prepayment account that Payables provides. However, during prepayment entry you can override any account that Payables defaults or builds. Payables does not create an encumbrance entry for the prepaid amount when a prepayment is matched to a purchase order. The match is treated like a reservation of the quantity billed. Payables does not calculate the invoice price variance or exchange rate variance at this point. Furthermore, you cannot change the unit price during the prepayment match to purchase order. A final match to the purchase order is not allowed either. When the matched prepayment is applied to an invoice, Payables reverses the matched quantity on the prepayment to reflect the balance of the total quantity matched. The following example illustrates a prepayment application to a purchase order: You contract to attend a $5,000 trade