It is common in Japan for customers to pay suppliers by transferring funds from the customer's bank to the supplier's bank. The customer's bank charges a fee to complete the transfer, and the customer and supplier negotiate who will bear the fee.
If the customer bears the bank charge, the full invoice amount is requested for transfer. For example, for a 100 dollar invoice and a 5 dollar bank transfer fee, the customer transfers 100 dollars to the supplier's bank, and pays 5 dollars to the customer's bank for the bank transfer fee. The total cost to the customer is 105 dollars.
If the supplier bears the bank charge, the invoice amount less the bank charge is requested for transfer. For example, for a 100 dollar invoice and a 5 dollar bank transfer fee, the customer transfers 95 dollars to the supplier's bank and pays 5 dollars to the customer's bank for the bank transfer fee. The total cost to the customer is 100 dollars.
The bank charge is based on several factors, such as:
Originating bank/branch, supplier bank/branch
Transfer priority
Bank charge type (standard or negotiated)
Currency used
Amount of payment
This form of electronic fund transfer is accomplished with a Zengin file, an electronic or paper file submitted by the customer that instructs the customer's bank to transfer funds to the supplier's bank.
The Bank Transfer feature lets you record if the customer or supplier bears the bank charge along with the bank charge rate type. There are three bank charge values:
Internal - Customer bears the bank charges
Supplier/Standard - Supplier bears the bank charges at standard rate
Supplier/Negotiated - Supplier bears the bank charges at a negotiated rate
The Oracle Payables Bank Transfer feature lets you handle bank charges borne by the supplier when the customer requests to transfer the full invoice amount less the bank charge.
Bank charges for transfer to suppliers flagged as supplier/standard or supplier/negotiated are automatically calculated during the build payments program with bank charges stored in the Bank Charges window. Bank charges, standard or negotiated, are deducted from the check amount.
Charges are automatically calculated during the Build Payment based on:
Bank Charge Bearer
Transfer Priority
Payment amount
Currency
Remit-to Account (supplier's bank/branch)
Remit-from Account (customer's bank/branch)
The Bank Transfer feature lets you make additional accounting entries that you need for bank charges. Two reports were created to support these accounting entries.
If the customer agrees to bear the bank charge, the customer requests to transfer the full invoice amount plus the negotiated bank charge. This is an Internal rate type.
For example, for a 100 dollar invoice, 5 dollar standard bank charge, and 3 dollar negotiated bank charge, the customer transfers 100 dollars, the full invoice amount. The supplier receives 100 dollars as payment and the customer pays a 3 dollar negotiated bank charge.
If the customer requests to transfer the invoice amount less the standard bank charge, but bears the negotiated bank charge instead, the customer receives the discount merit. This is a Supplier/Standard rate type.
For example, for a 100 dollar invoice, 5 dollar standard bank charge, and 3 dollar negotiated bank charge, the supplier expects to receive 95 dollars. The bank, however, gives the customer a negotiated rate instead; the customer pays 95 dollars for the invoice, 3 dollars for the bank transfer fee, and receives a 2 dollar discount merit.
Because the supplier does not know the bank's negotiated transfer rate, the business custom in Japan is to transfer the invoice less the standard bank charge and account the difference between the standard and negotiated bank charge as miscellaneous income.
If the supplier agrees to bear the bank charge and the customer requests to transfer the full invoice amount less a negotiated bank charge, the result is that the supplier receives a discount merit, the difference between the negotiated bank charge and the standard bank charge. This is a Supplier/Negotiated rate type.
For example, for a 100 dollar invoice, 5 dollar standard bank charge, and 3 dollar negotiated bank charge, the customer transfers the invoice amount less the negotiated bank charge, which is 97 dollars. The supplier bears the negotiated bank charge of 3 dollars, but had expected to bear the standard charge of 5 dollars; the supplier received 97 dollars instead of 95 dollars. The supplier receives a 2 dollar discount merit.
The Bank Transfer feature provides two reports that support additional accounting entries needed for bank charges, including miscellaneous income accounting and consumption tax on the bank charge.
The Bank Charge Accounting Upon Payment report shows the additional accounting required when payments are accounted. Users can create manual journal entries based on the Bank Charge Accounting Upon Payment report. See Bank Charge Accounting Upon Payment Report for more information.
The Bank Charge Accounting Upon Notification report shows the additional accounting required when bank charge notification receipts are accounted at period end. SeeBank Charge Accounting Upon Notification Report for more information.
This section overviews the steps required to set up the Bank Transfer feature, including:
To set up Disbursement System Options:
Navigate to the Disbursement System Options page.
Choose the Payment Processing Options region.
Define your payment processing options.
Check the Allow Payee Bank Account Override on Proposed Payments check box to override the remit-to bank account.
Select the bank charge bearer. The value you select defaults to the Bank Charge Bearer field in the Suppliers and Supplier Sites pages:
Internal - Customer bears bank charges. Customer pays the supplier invoice amount as well as negotiated bank charges.
Supplier/Standard - Supplier bears bank charges. Customer pays the invoice amount less standard bank charges as well as the negotiated bank charge.
Supplier/Negotiated - Supplier bears bank charges. Customer pays the invoice amount less negotiated bank charges as well as the negotiated bank charge.
Navigate to the Reports tabbed region and check the Sort By Alternate Field check box if you want to sort supplier or supplier site names using alternate names in the Invoice Transaction Check report.
To set up the discount method - system:
Navigate to the Financials Options window.
Choose the Accounting tabbed region.
Enter the Discount Taken GL Account for:
Bank Charge Accrual account (accrual basis)
or
Bank Charge Holding account (cash basis)
Set up a payment format using the Japanese Zengin Format XML Publisher template.
See: Step 4. Setting Up Formats, Oracle Payments Implementation Guide for more information.
To set up your bank account (Remit-from Account)
Navigate to the Banks window.
Define your Bank/Bank Branch that will be used to transfer funds to the supplier's bank account:
Define Bank/Bank Branch Alternate Name with the Zengin Standard Bank/Branch Kana Name.
Define Bank/Bank Branch Number with the Zengin Standard Bank/Branch Number. You must set up four numbers for banks and three numbers for branches.
Navigate to the Bank Accounts window.
Define the Bank Account that you will use to transfer funds to the supplier's bank account:
Enter the account number. You must use seven numbers with right alignment and 0 filling.
Enter the account type. You can enter either 1 (ordinary) or 2 (check). The exact value you set up in the Account Type field is printed in the Zengin file output as paper media. If the Zengin file output is electronic media, the format program picks up the first digit of the setup value.
In the Account Use field, enter Internal from the pull-down list.
Choose the Account Holder tabbed region.
Define your Account Holder information for your bank account:
Enter the Alternate Account Holder.
Enter the EFT Requester ID. You must enter 10 numbers with right alignment and 0 filling.
To set up the supplier's bank account (Remit-to Account):
Navigate to the Banks window.
Define the supplier's Bank/Bank Branch that you will transfer funds to:
Define Bank/Bank Branch Alternate Name with the Zengin Standard Bank/Branch Kana Name.
Define Bank/Bank Branch Number with the Zengin Standard Bank/Branch Number. You must set up four numbers for banks and three numbers for branches.
Navigate to the Bank Accounts window
Define the bank account that you will transfer funds to the supplier's bank account:
Enter the account number. You must use seven numbers with right alignment and 0 filling.
Enter the account type. You can enter either 1 (ordinary) or 2 (check). The exact value that you set up in the Account Type field is printed in the Zengin file output as paper media. If the Zengin file output is electronic media, the format program picks up the first digit of the setup value.
In the Account Use field, enter Supplier from the pull-down list.
Choose the Account Holder tabbed region.
Define the Account Holder information for supplier's bank account by entering the Alternate Account Holder.
Choose the Supplier Assignment tabbed region.
Choose the Supplier and/or Supplier Sites that you would like to associate with the bank account. Designate one primary supplier bank account per currency and per supplier site.
Note: If you haven't yet defined your supplier/supplier sites that you want to associate with this bank account, skip steps 7 and 8 and go to the next section to define your supplier/supplier sites first. You can then assign bank accounts for supplier/supplier sites in the Suppliers window.
Navigate to the Suppliers window.
Navigate to the Payment tabbed region.
Enter the bank charge bearer from the pull-down list. The bank charge bearer defaults from the Disbursement System Options. There are three choices:
Internal
Supplier/Standard
Supplier/Negotiated
Navigate to the Bank Accounts tabbed region.
Enter the supplier's Bank/Branch that you will transfer funds to:
Select the supplier bank account that you will transfer funds to.
Enter Bank/Branch Number. Use Zengin Standard Bank Branch code.
Note: If you have defined your supplier's bank branch and/or bank account before you define your supplier/supplier sites, you can assign bank accounts for suppliers and supplier sites in the Supplier window without navigating to the Bank/Account window. In the Bank Accounts tabbed region in the Supplier/Site window, select the bank accounts that you would like to associate from the list of values.
If you have not defined your supplier's bank branch and/or bank account, click on the box to the left of the Name field in the Suppliers window. The Banks window appears. Define your supplier's bank account and return to the Suppliers window.
Use the Create Settlement Batches concurrent program to settle batches and submit them to the appropriate payment systems.
See: Creating Settlement Batches, Oracle Payments User Guide for more information.
Related Topics
Understanding Credit Card Transactions, Oracle Payments Implementation Guide
Use the Bank Charge Accounting Upon Payment report to see bank charges as well as additional accounting entries that should be manually entered in General Ledger to account for bank charges. The report calculates bank charges for:
Manual payments with an Internal or Supplier bank charge type
Batch payments with an Internal bank charge type under accrual basis accounting
The report displays the bank charge and tax amount differently for internal and supplier bank charges. If the bank charge type is Internal, the report shows the bank charge and the tax amount in separate columns.
The Bank Charge Accounting Upon Payment report shows the deducted bank charge and paid bank charge in separate columns. The difference between both columns is displayed as miscellaneous income.
Enter the start date for the payments you want to report on. The report includes all payments with a start date on or after the payment start date.
Enter the end date for the payments you want to report on. The report includes all payments with an end date that is on or before the payment end date.
Enter one of these bank charge types to report on:
Internal - if your company bears the bank charge
Supplier - if the supplier bears the bank charge
Enter one of these accounting methods to report on:
Accrual - for the accrual basis method
Cash - for the cash basis method
Enter one of these payment types to report on:
Manual/Quick - for single payments
Batch - for batch payments
All - for all types of payments
Note: If you entered a bank charge type of Supplier, you can only enter a payment method of Manual/Quick. If you entered a bank charge type of Internal, you can enter a Batch payment method only if you selected accrual basis accounting for the Accounting Method parameter.
Enter the currency code for the payments you want to report on. The default is the currency code of your Payables ledger; however, you can enter any valid currency code defined in your system.
Enter the tax used to calculate the tax amount on a bank charge. Your system default tax name is the default. Enter None if you do not want the report to display the tax amounts separately from the bank charge amounts.
| In this heading... | Oracle Payables prints... |
|---|---|
| <Payment Date Range> | The payment date range |
| Bank Charge Bearer | The bank charge type |
| Accounting Method | The accounting method |
| Payment Type | The payment type |
| Currency Code | The currency of the payment |
| Tax | The tax you entered for calculating the tax on bank charges |
| In this column... | Oracle Payables prints... |
|---|---|
| Bank Name | The bank name that payments are made from. |
| Bank Branch | The bank branch name. |
| Account Number | The bank account number. |
| Payment Method | The payment method used with the bank account. |
| Payment Document | The payment document type. |
| Batch Name | The settlement batch name. |
| Payment Date | The payment date. |
| Supplier Name | The supplier name. |
| Supplier Site | The supplier site where the payment is sent. |
| Standard/Negotiated | S for supplier/standard and N for supplier/negotiated. |
| Payment Amount | The amount paid to the supplier. |
| Transfer Priority | Express or Normal depending on the priority of the payment made to the supplier. |
| Bank Charge | The bank charge amount for only internal bank charge types. |
| Tax | The tax amount for the bank charge for only internal bank charge types. |
| Bank Charge Deducted | The deducted bank charge amount including tax. |
| Bank Charge Paid | The computed value of the paid bank charge based on a negotiated rate. |
| Miscellaneous | The difference between the deducted bank charge and the paid bank charge. This amount represents a realized miscellaneous income on the payment bank charges. |
| Total | The subtotal of the payment amount and bank charge amounts for each settlement batch. |
| Grand Total | The grand total for each amount column in the report. |
Use the Bank Charge Accounting Upon Notification report to see the additional accounting required when bank charge notification receipts are accounted at period end. Use the information in the Bank Charge Accounting Upon Notification report to enter the appropriate account entries in General Ledger after you have entered a notified bank charge in the Receivables Miscellaneous Receipt window.
The report calculates:
Bank charges for bank charge types of Internal
Payment deduction amounts for Supplier/Standard and Supplier/Negotiated bank charges by summing the discounts taken on the payment invoices
Miscellaneous income and offset amounts based on the bank charge amounts on the notification receipts
Enter the start date for the payments you want to report on. The report includes all payments with a start date that is on or after the payment start date.
Enter the end date for the payments you want to report on. The report includes all payments with an end date that is on or before the payment end date.
Enter the name of the bank account to report on. The report shows all payments from this bank account.
Enter the currency code of the payments to report on. The default is the currency code for your Payables ledger; however, you can enter any valid currency code defined in your system.
Enter the bank charge amount on the notification receipt from your bank. This amount is used to compute the miscellaneous income and offset amounts.
Enter the tax used to calculate the tax amount on the bank charges. Your system default tax name is the default. Enter None if you do not want the report to display the total tax amount separately from the bank charge amounts.
| In this heading... | Oracle Payables prints... |
|---|---|
| <Payment Date Range> | The payment date range |
| Currency Code | The currency of all amounts in the report |
| Bank Charge Amount upon Notification | The bank charge amount on the bank notification receipt |
| Tax | The tax you entered for calculating the tax on bank charges |
| In this column... | Oracle Payables prints... |
|---|---|
| Bank Name | The name of the bank that payments are made from. |
| Bank Branch | The bank branch name. |
| Account Number | The bank account number. |
| Account Name | The bank account name. |
| Transfer Date | The date when the payments were transferred to the supplier. |
| Payment Amount | The total amount of payments transferred on the transfer date. |
| Deduction | The total amount of bank charges for the Supplier/Standard or Supplier/Negotiated bank charge type for all payments made on the transfer date. |
| Internal Bank Charges | The total amount of internal bank charges for all payments made on the transfer date. |
| Total Bank Charges | The sum of the deduction and internal bank charges of all payments made on the transfer date. |
| Total | A total for each Payment Amount, Deduction, Internal Bank Charges, and Total Bank Charges column. The total is for all transfer dates. |
| Total Internal Bank Charges (Excluding tax) | The total amount of internal bank charges excluding tax. This total is only displayed if you specify a tax other than None for the report parameters. |
| Total Tax | The total tax amount on the internal bank charges. This total is only displayed if you specify a tax other than None for the report parameters. |
| Miscellaneous Income | The difference between the notification amount and the total bank charges. |
| Holding Offset | The difference between the miscellaneous income and the internal bank charges. The field is called Holding Offset if the ledger has a cash basis account. |
Use the Bank Charges window to specify the fee charged by the customer's bank to transfer money to the supplier's bank. Use the Bank Charges region to specify the transferring from and receiving to banks and branches. Use the Bank Charges Lines region to specify the charge amounts. You can define charges from:
A single bank to a single bank.
A single bank to all banks. For example, all banks including the transferring bank.
A single bank to all other banks. For example, all banks except the transferring bank.
All banks to a single bank.
All banks to all banks.
Note: When you specify a single bank, you can select a particular branch of that bank or all branches. For an overview of the Bank Transfer feature, see Bank Transfer.
Refer to these sections in your Payables manual for prerequisite information:
Define remittance banks. See Defining Banks, Oracle Payables User Guide.
Define customer banks. See Defining Banks, Oracle Payables User Guide and Automatic Receipts and Remittances, Oracle Receivables User Guide .
Define bank accounts. See Defining Bank Accounts, Oracle Payables User Guide.
Bank Charges uses an established hierarchy to search for a match in the bank charges table. This hierarchy is illustrated in the Bank Charges Search Hierarchy table. When you create a bank transfer, Payables first searches for an exact match on bank and branch for both the transferring and the receiving bank. If no match is found, the system moves down to the next row in the table, and so on until a match is found.
Payables also takes transfer priority (express, normal, any) into account when it searches. At each level in the hierarchy, the system searches in this order:
Express bank charges
Normal
Any
If no match is found, the system goes on to the next level and repeats the process.
Understanding the search process will help you set up bank charges in the most efficient way possible. For example, although all combinations in this table are valid, Japanese users only set up bank charges with lines 1, 7, 9, and 12.
If you take advantage of the search hierarchy, you can avoid creating a bank charge record for every bank and branch combination. This table shows the bank charges search hierarchy.
| Search Order | Transferring | Transferring | Receiving | Receiving |
|---|---|---|---|---|
| 1 | Bank | Branch | Bank | Branch |
| 2 | Bank | Branch | Bank | Other Branches |
| 3 | Bank | Branch | Bank | All Branches |
| 4 | Bank | Branch | Other Banks | All Branches |
| 5 | Bank | Branch | All Banks | All Branches |
| 6 | Bank | All Branches | Bank | Branch |
| 7 | Bank | All Branches | Bank | All Branches |
| 8 | Bank | All Branches | Other Banks | All Branches |
| 9 | Bank | All Branches | All Banks | All Branches |
| 10 | All Banks | All Branches | Bank | Branch |
| 11 | All Banks | All Branches | Bank | All Branches |
| 12 | All Banks | All Branches | All Banks | All Branches |
For example, you need to set up bank charges for the following situations:
A transfer within the same bank and branch: from Tokyo Bank, Ginza branch to Tokyo Bank, Ginza branch.
A transfer within the same bank, but between different branches: from Tokyo Bank, Ginza branch to Tokyo Bank, Shinjuku branch.
A transfer between different banks: from Tokyo Bank, Ginza branch to Kyoto Bank, Roppongi branch.
Another transfer between different banks: from Osaka Bank, Yokohama branch to Tokyo Bank, Ginza branch.
The most efficient way to set up these charges is to create records in the Bank Charges window as illustrated in this table. Note that the last row in this table creates a default setting that is used any time the system cannot find a match (it corresponds to line 12, or the last row, in the Bank Charges Search Hierarchy table).
| Search Order | Transferring | Transferring | Receiving | Receiving | For Situation |
|---|---|---|---|---|---|
| 1 | Bank | Branch | Bank | Branch | 1. Tokyo/Ginza to Tokyo/Ginza |
| 2 | Bank | All Branches | Bank | All Branches | 2. Tokyo/Ginza to Tokyo/Shinjuku |
| 3 | Bank | All Branches | All banks | All Branches | 3. Tokyo/Ginza to Kyoto/Roppongi |
| 4 | All Banks | All Branches | All banks | All Branches | 4. Osaka/Yokohama to Tokyo/Ginza |
The four rows in this table correspond to rows 1, 7, 9, and 12 in the Bank Charges Search Hierarchy table.
When trying to match each of these situations, the system first looks for an exact match on transferring and receiving bank and branch. In the case of situation 1, it finds such a match and quits searching. In the case of situations 2, 3, and 4, the system cannot find an exact match on transferring and receiving bank and branch, so it continues searching in the order illustrated in the Bank Charges Search Hierarchy table until it finds a match.
Navigate to the Bank Charges window.
Select the transferring bank, as described in this table:
| To specify... | Do this.... |
|---|---|
| A single bank | Select Bank from the pull-down list. Enter the bank number or name. |
| A particular bank branch | Select Branch from the pull-down list. Enter the branch number or name. |
| Charges that apply to all branches of the bank | Select All Branches. |
| Charges that apply to all banks | Select All Banks. |
Select the receiving bank, as described in this table:
| To specify... | Do this.... |
|---|---|
| Charges to a single bank | Select Bank from the pull-down list. Enter the bank number or name. |
| Charges specific to a particular bank branch | Select Branch from the pull-down list. Enter the branch number or name. |
| Charges that apply to all branches except the transferring branch | Select Other Branches. |
| Charges that apply to all branches of the banks | Select All Branches. |
| Charges that apply to all banks | Select All Banks. |
| Charges that apply to all banks except the transferring bank | Select Other Banks. This option is not available when the transferring bank is All Banks. |
Select a transfer priority. There are three choices:
Express
Normal
Any
Note: To define default bank charges used when charges are not defined, select All Banks for both the transferring and receiving bank. See Setting up Bank Charges for additional information about how Bank Charges searches for matches in the bank charges table.
Enter the currency in the Currency field.
Enter transfer amount ranges and charges that apply to each range.
Note: The way that the Bank Charge Bearer is defined determines whether your company or the supplier pays the charges and if the standard or negotiated rate is used. See Setting up Bank Transfer for more information.
Enter from and to amounts to indicate the transaction amount range. Note that:
The first range must start from zero; enter 0 in the first transaction amount from field.
The last range must be open ended; do not enter information in the last transaction amount to field.
The to amount from one range is the from amount for the next range. The system defaults this value for you automatically. Each range goes up to, but does not include, the to amount. For example, if the first range is 0 to 500, and the second range is 500 to 1,000, the charge for the first range is applied to amounts up to 499.99. The charge for the second range will be applied to amounts from 500 to 999.99.
Enter the standard bank charge for the range.
Enter the negotiated bank charge for the range (optional).
Enter a from date in the Effective Dates - From field to indicate the first day this charge is applied. Leave the Effective Dates - To field blank to indicate that the charge is in effect indefinitely. Enter a to date when a charge is in effect for a specific period of time or when you want to inactivate a charge.
Use the Bank Charges report to list all bank charges entered in the Bank Charges window.
Enter the currency that you want to report on.
Select a name from the List of Values.
In Payables, enter one of these values:
Express
Normal
Any
Note: The Transfer Priority parameter does not exist in Receivables.
Enter one of the following values:
Bank Name - Orders the report by the bank's name. In Japan, the bank is ordered by the bank's phonetic name.
Bank Number - Orders the report by the bank's number.
| In this heading... | Oracle Payables prints... |
|---|---|
| Report Date | The date and time the report is run |
| Page | The report's page number |
| Currency | The currency that you selected in the Currency parameter |
| Transferring Bank Name | The transferring bank's name |
| Order by | The bank charges ordered by the value in the Order By parameter |
| Transfer Priority | The transfer priority parameter value |
| In this column... | Oracle Payable prints... |
|---|---|
| Transferring Bank - Num | The transferring bank number |
| Transferring Bank - Bank Name | The transferring bank name |
| Transferring Bank - Num | The transferring bank branch number |
| Transferring Bank - Branch | The transferring bank branch name |
| Receiving Bank - Num | The receiving bank number |
| Receiving Bank - Bank Name | The receiving bank name |
| Receiving Bank - Num | The receiving bank branch number |
| Receiving Bank - Branch | The receiving bank branch name |
| Transaction Amount - From | The beginning range of the transaction amount |
| Transaction Amount - To | The ending range of the transaction amount |
| Bank Charge - Standard | The standard bank charge |
| Bank Charge - Negotiated | The negotiated bank charge |
| Transfer Priority | The transfer priority for the Payables report |
| Effective Date - From | The beginning range of the effective date |
| Effective Date - To | The ending range of the effective date |
If you are importing bank data in Zengin format, receipts must be manually confirmed before you can post them by submitting Post QuickCash. Therefore, when you import Zengin receipts, AutoLockbox can be either a three or four step process:
Import data into the AutoLockbox Tables.
Match customers with receipts or confirm automatic matching.
Submit the validation program.
Submit Post QuickCash to update your customer's balances (you can submit the validation and Post QuickCash steps simultaneously).
See Importing Zengin Format Data Using AutoLockbox for more information.
Related Topics
Using AutoLockbox, Oracle Receivables User Guide
How AutoLockbox Identifies Customers for a Receipt, Oracle Receivables User Guide
AutoLockbox accommodates bank transfers that use the Zengin file format, the standard format for bank transfers in Japan. Usually, Receivables uses the customer number or invoice number to identify the customer who remitted the payment. However, the Zengin bank file format does not include this information. Therefore, AutoLockbox identifies customers by their alternate names, which is usually the customer's phonetic name spelled with Kana characters (or a shortened form of the full Kana name). You can enter an alternate customer name in the Alternate Name field of the Customers window.
Receivables stores the relationship between a customer and their alternate name in the Alternate Names table (AR_CUSTOMER_ALT_NAMES) so Zengin receipt data can be matched with the correct customer data. Specifically, the Alternate Names table contains the alternate name, the customer ID, the customer's site use ID (bill to location), and payment terms. Before receipts can be validated and posted as identified receipts, they must be matched with a customer from the Alternate Names table or from the Customers table (RA_CUSTOMERS).
Note: To use the Alternate Names table, the profile option AR: Alternate Name Search must be set to Yes. If it is set to No, Receivables does not display the Alternate Name Search field in the Lockbox Processing window.
During the import process, you can choose to use the Alternate Names table to automatically match receipts with customers or you can import the data and then match the receipts manually in the Maintain Transmission Data window. When submitting the import step of AutoLockbox, enter one of the following options in the Alternate Name Search field:
Manual Matching - When the import process is complete, AutoLockbox assigns each receipt a status of Manual and you must use the Lockbox Transmission Data window to match them with customers. When you match a receipt with a customer, Receivables changes the receipt status to Confirmed.
Automatic Matching - If you choose the Automatic Matching option and a single, exact match is found in the Alternate Names table, AutoLockbox assigns this receipt a status of Verify. If no match is found, the receipt status is None. If multiple matches are found, AutoLockbox assigns a receipt status of Multiple (see Note below). Use the Lockbox Transmission Data window to manually match records with a status of None and Multiple and to confirm records with a status of Verify.
None - Choosing the None option is the same as setting the profile option AR: Alternate Name Search to No (in this case, Receivables does not search the Alternate Names table for customers or receipts).
Note: An alternate name occurs more than once in the Alternate Name table if, for example, the same alternate name is used by more than one customer.
See Importing Zengin Format Data Using AutoLockbox for more information.
Related Topics
Overview of Receivables User Profile Options, Oracle Receivables Implementation Guide
How AutoLockbox Identifies Customers for a Receipt, Oracle Receivables User Guide
Receivables validates the data you receive from the bank to ensure that the entire file was received, that there are no duplicate receipts within a batch, and that customers and invoices are valid.
Transmission Level Validation - validates your lockbox transmission to ensure that transmission information corresponds to your transmission format. Validation of the origination number does not apply to Zengin file format.
Lockbox Level Validation - AutoLockbox validates your lockbox records to ensure that lockbox information corresponds to your transmission format. Validation of the origination number does not apply to Zengin file format.
Related Topics
AutoLockbox Validation, Oracle Receivables User Guide
When you submit the Import, Validation, and Post Batch steps of AutoLockbox, Receivables stores receipt information in temporary application tables until it is approved for the next step. For example, the Validation step checks data in the AutoLockbox tables for compatibility with Receivables before passing the information into the Receipt and QuickCash tables.
When you run the Import step of AutoLockbox, Receivables stores receipt data from your bank file in the Lockbox Interface table AR_PAYMENTS_INTERFACE. Each column in AR_PAYMENTS_INTERFACE has important, detailed information which you need to successfully run Lockbox.
This table shows the values stored in the STATUS and DEPOSIT_DATE columns of the AR_PAYMENTS_INTERFACE table.
| Column Name | Value |
|---|---|
| STATUS | There are five possible status values for data converted from the Zengin file format:
|
| DEPOSIT_DATE | Enter the date on which this transmission was actually deposited into your bank account. The Japanese file conversion program automatically converts Heisei imperial era dates to Oracle date format. |
If your record type is either a Lockbox Header or a Lockbox Trailer, enter this column with the value described in this table.
| Column Name | Value |
|---|---|
| ORIGINATION | Enter the sending bank's transit routing number. The restriction that the origination value must be the same as that included in a Transmission Header or Trailer does not apply to Zengin file format. |
If your record type is a Payment, you can enter these columns with the values described in this table.
| Column Name | Value |
|---|---|
| LOCKBOX_NUMBER | For the Zengin file format, the lockbox number is system-generated. |
| ITEM_NUMBER | For the Zengin file format, the item number is system-generated. |
| CHECK_NUMBER | For the Zengin file format, the check number is system-generated. |
| CUSTOMER_NUMBER | For Zengin file formats, the system looks up the customer number in the Alternate Names table. |
| CUSTOMER_NAME_ALT | The customer's alternate name from the Zengin bank file. |
| STATUS | Oracle Receivables assigns one of the following values:
|
You can import, validate, and run AutoLockbox all in one step, or perform the steps separately using the same window, except when importing Zengin data. If you are using AutoLockbox to import bank files in the Zengin format, you must perform the steps separately.
Related Topics
Running AutoLockbox, Oracle Receivables User Guide
Use the Submit Lockbox Processing window to import bank files that are in Zengin format. Unlike some file formats, you cannot select, import, validate, and post bank files in Zengin format in a single step. You must import the data, match and confirm receipts with customers, then return to the Submit Lockbox Processing window to validate and post the records.
Although you must submit the import step separately from the validate and post steps when transferring Zengin format files, you can submit the validate and post steps either separately or at the same time.
For more information about matching receipts with customers when importing Zengin format bank files, see Alternate Name (Zengin Receipts).
The Lockbox Processing window only displays the Alternate Name Search field and lets you import Zengin bank files if the profile option AR: Alternate Name Search is set to Yes and the profile option AR: Zengin Character Set is defined.
Before importing Zengin format data using AutoLockbox, you must:
Define AutoCash rule sets
Define lockboxes
Define transmission formats
Define receipt classes
Define receipt sources
Define system options
Define banks
Define profile options
Define payment methods
Define sequential numbering (optional)
To import Zengin format data using AutoLockbox:
Navigate to the Submit Lockbox Processing window.
If you are importing a new bank file, check the New Transmission check box, then enter a Transmission Name. If you are resubmitting an existing lockbox transmission, you can select the name from the list of values.
To import a new bank file into Receivables, check the Submit Import check box, then enter your bank file's Data File, Control File, and Transmission Format information. If you are re-importing data, the default is the transmission format you specified in the initial import step; you can either accept the default value or override it. When you run the import step, Receivables generates the import section of the Lockbox Execution report.
Choose the matching method to use in the Alternate Name Search field. Choose one of these options:
Automatic - AutoLockbox imports the data and attempts to match customers with receipts. If AutoLockbox cannot match some receipts, you must match them manually. If you choose the Automatic method, your lockbox must have the Require Billing Location option set to No.
Manual - AutoLockbox only imports the data; you must manually match receipts with customers.
None - Choosing the None option is the same as setting the profile option AR: Alternate Name Search to No (Receivables does not search the Alternate Names table to match customers with receipts).
To match receipts in this transmission with customers and change each receipt's status to Confirmed, see Maintaining Zengin Lockbox Transmission Data.
To see which customers and receipts were successfully imported, see Alternate Customer Name Receipt Matching Report.
Related Topics
Overview of Receivables User Profile Options, Oracle Receivables User Guide
Defining Banks, Oracle Payables Implementation Guide
Lockboxes, Oracle Receivables Implementation Guide
Use the Lockbox Transmission Data window to match your Zengin receipts with their respective customers and update the status of these receipts to Confirmed. Receipts must have a status of Confirmed to be included in a Post QuickCash submission.
The Lockbox Transmission Data window only displays the fields you need to identify customers for your Zengin receipts if the profile option AR: Alternate Name Search is set to Yes.
When you import Zengin data into Receivables, AutoLockbox assigns a status to each receipt. This status indicates whether AutoLockbox was able to match the receipt with a customer. These are valid receipt statuses:
Verify - AutoLockbox found a single, exact match in the Alternate names table. Verify that the customer name is correct, then update the status to Confirmed.
Manual - You selected a matching method of Manual when submitting the import step of AutoLockbox. Identify the customer for each receipt, then update the status to confirmed.
Multiple - AutoLockbox found more than one match for this receipt in the Alternate Names table. More than one match could be found, for example, if there are multiple customers that use the same alternate name. Identify the correct customer for this receipt, then update the status to Confirmed.
None - AutoLockbox could not find a match for this receipt in the Alternate Names table. Identify the customer for this receipt, then update the status to Confirmed.
Confirmed - This receipt was either manually matched with a customer and then confirmed in the Lockbox Transmission Data window or it was matched during AutoLockbox and then confirmed in the Lockbox Transmission Data window. Receipts with a status of Confirmed can be included in a Post QuickCash submission.
Import Zengin format data into Receivables tables using AutoLockbox. See Importing Zengin Format Data Using AutoLockbox for more information.
To maintain lockbox transmission data in Zengin format:
Navigate to the Lockbox Transmission Data window.
If you entered a matching method of Automatic, confirm the matching for receipts whose status is Verify. Select the receipts to be confirmed, then choose Confirm Match(es) from the Tools menu. AutoLockbox changes the status of the selected receipts to Confirmed.
If you entered a matching method of Manual (or if you need to match receipts that AutoLockbox was unable to match automatically), identify the customer for each receipt. Unmatched receipts have no customer name or bill to location and a status of Manual, None, or Multiple.
To match the receipt from the Alternate Names table, select a customer using the list of values. Receivables enters the customer's bill to location (if one is defined).
If the customer is not in the Alternate Names table, select All Customers from the Tools menu to display information from the Customers table (RA_CUSTOMERS). Locate the customer name and select it from the list.
To define a bill to location for this customer, choose Receipt, then define the bill to location in the Lockbox Receipt window.
When you select the customer from either the Alternate Names or the Customers table, Receivables changes the status of the receipt to Confirmed. Receivables updates the Alternate Names table with any new data you selected from the Customers table so it can match receipts for those customers the next time you run AutoLockbox.
To validate and post receipts in this transmission, navigate to the Submit Lockbox Processing window, then perform steps 4-6 in Running AutoLockbox in Oracle Receivables User Guide.
See Alternate Customer Name Receipt Matching Report and Deleting Records from the Alternate Names Table for more information.
Related Topics
Overview of Receivables User Profile Options, Oracle Receivables Implementation Guide
Using AutoLockbox, Oracle Receivables User Guide
Lockbox Execution Report, Oracle Receivables User Guide
Maintaining Lockbox Transmission Data, Oracle Receivables User Guide
AutoLockbox Field Reference, Oracle Receivables User Guide
Monitoring Requests, Oracle Applications User Guide
When you match Zengin receipts with customer information in the Lockbox Transmission Data window, Receivables updates the Alternate Names table so it can automatically match receipts for these customers the next time you run AutoLockbox. The Alternate Name Receipt Matches window lets you remove this information from the Alternate Names table if, for example, this information is no longer valid.
Deleting information in the Alternate Name Matches window only removes the record from the Alternate Names table; it does not delete the customer's name, number, or any other information from Receivables.
Note: The records in the Alternate Names table are not the same as the Alternate Name you can assign to a customer using the Customers window. The records in the Alternate Names table originate from the bank file you imported using AutoLockbox, and are simply alternative customer names often used by Japanese businesses.
Import Zengin format data into Receivables tables using AutoLockbox. See Importing Zengin Format Data Using AutoLockbox for more information.
Maintain Zengin lockbox transmission data. See Maintaining Zengin Lockbox Transmission Data for more information.
To delete records from the Alternate Names table:
Navigate to the Alternate Name Receipt Matches window.
Enter selection criteria. For example, enter the Alternate Name, Customer Name, Customer Number, Bill To Location, or Payment Term associated with the Alternate Name to view. Leave a field blank if you do not want to limit your query to information matching that criteria.
Choose Find.
Select the record to delete, then choose Delete.
Choose OK to delete the record from the Alternate Names table.
Note: If the profile option AR: Alternate Name Search is set to Yes, Receivables deletes this record from the Alternate Names table if you perform any of the following operations:
Modify or delete a customer address that includes a bill to business purpose
Inactivate a customer or their billing location
Merge two different customers (Receivables deletes the From customer from the Alternate Names table if a bill to location was defined; otherwise, the record is not affected.)
Records in the Alternate Names table that do not have a bill to location are not affected by these operations.
Note: If you assign a new payment term to a customer or modify the customer's name or alternate name, Receivables automatically updates this information in the Alternate Names table (it does not delete the record).
See Alternate Customer Name Receipt Matching Report for more information.
Related Topics
Using AutoLockbox, Oracle Receivables User Guide
Lockbox Execution Report, Oracle Receivables User Guide
AutoLockbox Field Reference, Oracle Receivables User Guide
Use the Lockbox Transmission Data window to delete and edit lockbox transmission data imported into Receivables from your bank.
If you are maintaining data from a Zengin format bank file, see Importing Zengin Format Data Using AutoLockbox for more information.
Related Topics
Maintaining Lockbox Transmission Data, Oracle Receivables User Guide
Run the Alternate Customer Name Receipt Matching report to see which alternate customer names and receipts were successfully imported into the AR Payment Interface table when running AutoLockbox to import Zengin bank files.
Use the Standard Request Submission windows to submit the Alternate Customer Name Receipt Matching report.
Import Zengin format data into Receivables tables using AutoLockbox. See Importing Zengin Format Data Using AutoLockbox for more information.
Enter the name of the lockbox transmission to include in the report. Leave the Transmission Name field blank to include all lockbox transmissions.
To include only receipts with a certain status, enter a Status. Choose Confirmed, Manual, Multiple, None, or Verify. Leave the Status field blank to include all receipts.
Specify how you want Receivables to display the data in the report. Choose Alternate Name, Customer Name, or Date Created.
Related Topics
Running Reports and Programs, Oracle Applications User Guide
Use the Invoice Transaction Check report to check data entry for invoice transactions. Invoices are sorted by the last update date.
Note: If you check the Sort By Alternate Field check box in the Reports tabbed region of the Disbursement System Options page, then this report uses alternate names when sorting by supplier or supplier site.
Enter the beginning updated date for the report.
Enter the ending updated date for the report.
Enter an invoice type.
Enter a supplier name.
Enter the name of the user who last updated invoices.
| In this heading... | Oracle Payables prints... |
|---|---|
| From <Start Date> To <End Date> | The date range for the report |
| Updated Date | The latest updated date for the invoice |
| Supplier | The supplier code and name |
| Site | The name of the supplier site |
| Invoice Number | The invoice number |
| Invoice Date | The invoice date |
| Tax Calculation | The tax calculation method |
| Currency | The invoice currency |
| Invoice Amount | The invoice amount |
| Exchange Rate | The invoice exchange rate |
| Liability | The liability accounting code and description |
| Updated By | The user's name who last updated the invoice |
| Sequence Name | The document sequence name for each transaction associated with the document sequence |
| Invoice Type | The invoice type |
| Voucher Number | The voucher number for each transaction associated with the document sequence |
| In this column... | Oracle Payables prints... |
|---|---|
| Line | The distribution line number for the invoice distribution |
| Line Type | The line type |
| Amount | The invoice distribution amount |
| Line Description | The invoice distribution description |
| Due Date | The payment due date for the payment schedule |
| Payment Method | The payment method for the payment schedule |
| Scheduled Amount | The scheduled amount for the payment schedule |
Use the Actual Payment report to review payment activity by bank account and payment date. The Actual Payment report also prints all invoices in a payment batch so that you can review which invoices and suppliers were paid.
The Actual Payment report is an RXi report. The default attribute set displays bank information and payment details. You can copy this attribute set and customize the layout to suit your reporting needs.
Use the Standard Request Submission windows to submit the Actual Payment report.
Enter the beginning payment date that you want to report from.
Enter the ending payment date that you want to report to.
Enter the payment currency for the report.
Enter the bank account for the report.
Enter the payment method for the report.
| In this heading... | Oracle Payables prints... |
|---|---|
| Payment Currency | The payment currency |
| Bank | The bank name |
| Bank Branch | The bank branch name |
| Bank Account | The bank account name |
| Account Currency | The bank account currency |
| In this column… | Oracle Payables prints… |
|---|---|
| Payment Date | The payment date |
| Supplier Name | The supplier name |
| Supplier Site | The name of the supplier site |
| Document Number | The payment document number |
| Payment Method | The payment method |
| Future Date | The date of the future dated payment and manual future dated payment |
| Seq Name | The document sequence name for each payment associated with the document sequence |
| Voucher Number | The voucher number for each payment associated with the document sequence |
| Invoice Number | The invoice number paid by this payment |
| Invoice Date | The invoice date |
| Invoice Amount | The invoice amount |
| Bank Charge | The bank charge amount paid on this invoice |
| Payment Amount | The total payment amount |
| Exc Rate | The payment exchange rate |
| Functional Amount | The payment amount in the ledger currency |
| Description | The invoice description |
Related Topics
Working with Attribute Sets, Oracle Financials RXi Reports Administration Tool User Guide
Using the RXi Reports Concurrent Program, Oracle Financials RXi Reports Administration Tool User Guide
Running Reports and Programs, Oracle Applications User Guide
Use the Payment Schedule report to print payment schedules by payment method, due date, and supplier. The Payment Schedule report helps to forecast cash needs for invoice payments.
Enter the payment currency for the report.
Enter the end due date for the report.
Enter the payment method to use for the report.
Enter the pay group to use for the report.
Enter the lowest invoice payment priority to use for the report.
Enter the highest invoice payment priority to use for the report.
Enter the supplier name to use for the report.
| In this heading… | Oracle Payables prints… |
|---|---|
| Payment Currency | The payment currency |
| End Due Date | The payments with a due date before or equal to the requested due date |
| Payment Method | The payment method |
| Pay Group | The pay group |
| Payment Priority From | The lowest invoice payment priority in the report |
| To | The highest invoice payment priority in the report |
| In this column… | Oracle Payables prints… |
|---|---|
| Due Date | The payment schedule due date |
| Supplier | The supplier name |
| Site | The name of the supplier site |
| Invoice Number | The invoice number |
| Invoice Date | The invoice date |
| Invoice Amount | The invoice amount |
| Scheduled Amount | The scheduled amount for the payment schedule |
Use the Invoice Register by Detail report to view detailed information about invoices. Previously, Japanese commercial codes required that this report either be printed, filed and kept for five years. You may now keep this report on disk, as specified in the Electronic Account Book law.
The Invoice Register by Detail report is an RXi report. The default attribute displays invoices grouped by the supplier name. You can copy this attribute set and customize the layout to suit your reporting needs.
Enter the output format that you want for the report:
CSV
HTML
Tab Delimited
Text
Choose Line or Invoice for the report. Choosing Line retrieves only the distribution lines which match the Distribution Account Range and Distribution Amount Range. Choosing invoice retrieves the entire invoice.
Enter the range of dates for the report.
Enter the name of the batch for the report.
Enter the invoice type for the report.
Enter the user who created the invoice for the report.
Enter the document sequencing value range for the report.
Enter the supplier range for the report.
Enter the range of natural account segments for the liability account flexfield for the report.
Enter the range of natural account segments of the distribution account flexfield for the report.
Enter the currency code for the report.
Enter the distribution amount range for the report.
| In this column… | Oracle Payables prints… |
|---|---|
| Supplier Name | The supplier name |
| Site | The supplier site name |
| Invoice Number | The invoice number |
| Sequence Name | The document sequence name |
| Sequence Value | The document sequence value |
| Invoice Date | Transaction date of the invoice |
| Invoice Amount | Total amount of the invoice |
| Description | Description of the invoice |
| Invoice Type | Type of invoice |
| Payment Method | Payment method for the invoice |
| Line Type | Invoice distribution line type |
| Line | Line number of the distribution |
| Amount | Line amount of the distribution |
| Description | Line description of the distribution |
| Accounting date | Accounting date of the distribution |
| Income Tax Type | Income tax type of the distribution |
| Tax | Tax code of the distribution |
| Post | Posting status of GL |
| Account | Distribution account flexfield |
| Distribution | Distribution account flexfield description |
Related Topics
Working with Attribute Sets, Oracle Financials RXi Reports Administration Tool User Guide
Using the RXi Reports Concurrent Program, Oracle Financials RXi Reports Administration Tool User Guide
Use the Japanese Depreciable Assets Tax reports to print summary and detail asset information in the required format once a year to your tax authorities. Japanese Depreciable Assets Tax Reports is a program that controls these reports:
Japanese Depreciable Assets Tax Summary Report
Japanese Detail by Asset Type (Addition/All Assets) Report 132 Characters
Japanese Detail by Asset Type (Addition/All Assets) Report 180 Characters
Japanese Detail by Asset Type (Decrease Assets) Report
The Japanese Depreciable Assets Tax Summary report summarizes asset information by location as of January 1 for the selected calendar year. The report also calculates the evaluated and theoretical net book value for each asset type, as well as the decision cost, which is the larger of the two net book values.
The Japanese Detail by Asset Type (All Assets) report prints detail information for all assets by location as of January 1 of the selected calendar year. This report prints the residual rate, which the tax authorities require, based on the asset's useful life. The Japanese Detail by Asset Type (Addition Assets) report includes asset increases between January 2 of the prior year and January 1 of the selected calendar year. You can print these two reports in the 132 or 180 characters wide format.
The Japanese Detail by Asset Type (Decrease Assets) report displays asset decreases between January 2 of the prior year and January 1 of the selected calendar year.
All four reports print asset information based on the transaction or effective date, no matter what the book's open period is. After January 1 of a given year, if you enter a transaction with a transaction date prior to January 1, you need to reprint the reports for this year because the results may differ from what was printed before you entered the new transaction.
The Japanese Depreciable Assets Tax Reports displays Japanese era names and years. The Japanese era names are:
1 - Meiji (1868 - 1911)
2 - Taisho (1912 -1925)
3 - Showa (1926 - 1988)
4 - Heisei (1989 - )
When you submit the Japanese Depreciable Assets Tax Reports program, the reports that you select automatically run. Use the Standard Request Submission windows to submit the Japanese Depreciable Assets Tax program and reports.
The report is printed using XML Publisher with the information that you enter in the Company Information and Tax Authority windows along with the financial data in the format mandated by your tax authorities.
Before you submit the Japanese Depreciable Assets Tax reports, you must:
Set up your category flexfield with segment values in this table. Set up this segment to use independent value sets.
| Value | Description |
|---|---|
| 1 | Building |
| 2 | Machine and Equipment |
| 3 | Ship |
| 4 | Airplane |
| 5 | Car and Truck |
| 6 | Tool, Apparatus, and Fixture |
Set the FA: Tax Asset Type Category Segment profile option to the category segment number used for Tax Asset Type definition.
Note: The category segment number is the order in which the segments appear in the Flexfield window.
Define a lookup code for the Retirement lookup type to describe retirements due to sales. Use this lookup code for all retirements due to sales and select this lookup code from the Sale Code parameter's list of values for retirements due to sales.
Set up the State segment of the location flexfield with the independent validation type. The State segment should include the locations of each tax authority that you need to report.
Create a separate tax book for assets that use the seeded JP-DB <year>YR depreciation method if you use other depreciation methods in the corporate book. The value <year> can be from 2 to 100 and represents the useful life of the method. For example, JP-DB 2YR has a useful life of 2 years.
Copy all the assets from the corporate book to this tax book. The Japanese Depreciable Assets Tax reports prints only the seeded JP-DB <year>YR depreciation method.
Enter the necessary information in the Company Information window by selecting Japan Tax Reports Information in Setup: Asset System.
Enter the necessary information in the Tax Authority Information window by selecting Tax Authorities in the Company Information window.
Enter the corporate or tax book that you want to report on.
Enter the calendar year that you want to report on.
Enter the first location that you want to report on.
Enter the last location that you want to report on.
Enter the first category flexfield segment value that you want to report from. This must be the value of the segment selected in the FA: Tax Asset Type Category Segment profile option.
Enter the last category flexfield segment value that you want to report to.
Enter the sale code that you want to report on. In the Japanese Detail by Asset Type (Decrease Assets) report, sold retired assets are separated from other retired assets. If an asset's retirement type in the Retirements window matches the sale code that you enter in this parameter, the asset is reported as a sold retirement.
Enter Yes if you want to print the Japanese Depreciable Assets Tax Summary report or No if you do not. The default is Yes.
Enter the format of the Japanese Detail by Asset Type (All Assets) report that you want, 132 or 180 characters. Enter No if you do not want to print this report. The default is the 132 characters format report.
Enter Yes if you want to print the Japanese Detail by Asset Type (Addition Assets) report or No if you do not. The default is No.
Enter Yes if you want to print the Japanese Detail by Asset Type (Decrease Assets) report or No if you do not. The default is No.
| In this heading... | Oracle Assets prints... |
|---|---|
| Book | The corporate or tax book that you entered in the Book parameter |
| State | The location that you entered in the State parameter |
| <Japanese Era Name and Year> | The calendar year that you entered in the Year parameter converted into Japanese era name and year |
| <Report Title> | The name of the report:
|
| Report Date | The date and time that you submit the report |
| Page | The current and total pages of the report |
| In this column... | Oracle Assets prints... |
|---|---|
| Asset Type | The category flexfield value |
| Cost - Addition Before Prior Year (X) | The addition amount before the year prior to the fiscal year that you entered |
| Cost - Decrease in Prior Year (Y) | The decrease amount in the year prior to the fiscal year that you entered |
| Cost - Addition in Prior Year (Z) | The addition amount in the year prior to the fiscal year that you entered |
| Cost - Total ((X) - (Y) + (Z)) | The total amount of the three previous columns, calculated (X) - (Y) + (Z) |
| <Japanese Era Name and Year>: January 1 Theoretical NBV | The theoretical net book value as of January 1 of the calendar year that you entered |
| Evaluated NBV | The evaluated net book value |
| Decision Cost | Either the theoretical or evaluated net book value, whichever is larger |
| Taxable Standard Cost | The decision cost rounded down by the thousandth, by default |
| Num of Assets | The number of assets in each minor category |
| In this column... | Oracle Assets prints... |
|---|---|
| Num | The line number for the page; each page has 20 lines |
| Asset Number | The asset number |
| Asset Type | The category flexfield value |
| Asset Name | The asset name or description |
| Units | The units of each asset |
| Addition - Era Name | The Japanese era name of the date in service |
| Addition - Year | The Japanese era year of the date in service |
| Addition - Month | The month of the date in service |
| Cost | The acquisition cost of the asset |
| Life | The useful life of the asset |
| Residual Rate | The residual rate, based on the addition date and useful life |
| NBV (132 characters) Net Book Value (180 characters) |
The evaluated net book value, calculated as the cost multiplied by the residual rate |
| Exception of Taxable Standard - Code | The exception code if a tax exception applies to the asset |
| Exception of Taxable Standard - Rate | The exception rate if a tax exception applies to the asset |
| Taxable Standard Cost | The taxable standard cost, by default equal to the evaluated net book value |
| Addition Reason | The reason for the asset addition:
|
| Description | The transfer period if the asset was transferred from another location |
| In this column... | Oracle Assets prints... |
|---|---|
| Num | The line number for the page; each page has 20 lines |
| Asset Number | The asset number |
| Asset Type | The category flexfield value |
| Asset Name | The asset name or description |
| Units | The units of each asset |
| Era Name | The Japanese era name of the date in service |
| Year | The Japanese era year of the date in service |
| Month | The month of the date in service |
| Cost | The acquisition cost of the asset |
| Life | The useful life of the asset |
| Decrease - Reason | The reason for the asset decrease:
|
| Decrease - Type | The type of asset decrease, whether the asset is retired or transferred in whole or part: |
| Description | Additional information about the asset depending on the decrease reason:
|
| In this row... | Oracle Assets prints... |
|---|---|
| Total | The page totals |
Related Topics
Running Reports and Programs, Oracle Applications User Guide
Category Flexfield, Oracle Assets User Guide
Entering QuickCodes, Oracle Assets User Guide
Location Flexfield, Oracle Assets User Guide