Use the Lookup Codes window to define lookup codes. Lookup codes are codes that you create and associate with predefined lookup types. The lookup types determine specific transaction elements that run in Oracle Payables and Oracle Receivables.
You cannot delete lookup codes once you enter them. Instead, you can inactivate a lookup code by giving it an inactive date. You can also delete the inactive date at a later time to reactivate a lookup code.
Create and maintain as many lookup codes as you need for each lookup type. This table shows lookup types and their meanings.
| This lookup type… | Has this meaning… |
|---|---|
| Contributor Type | A customer type of tax contribution |
| Organization Class | The company type of tax contribution |
| Fiscal Classification | Item fiscal classes (used by Latin tax windows) |
| Supplier/Contributor | The supplier type for tax contribution |
| Invoice Class (Payables only) | The invoice type |
| Invoice Series (Payables only) | An invoice numbering sequence |
| Item Fiscal Type | The type of item for fiscal purposes |
| Item Origin | The kind of transaction |
| Item Transaction Nature | The transaction nature |
| Legal Messages Exception Events (Receivables only) | Legal exceptions to the basic tax rules |
| State | The name of a state in Brazil |
| Tributary Federal Situation | The tributary federal situation |
| Tributary State Situation | The tributary state situation |
To define lookup codes:
Navigate to the Lookup Codes window.
Query the lookup type in the Type field.
Enter the name of the lookup code in the Code field.
Enter the name for the lookup code that is displayed in the list of values in the Meaning field.
Enter a description for the lookup code in the Description field.
You can optionally enter an inactive date for the lookup code in the Effective Dates - To field.
Repeat steps 2 to 6 for each lookup code that you define.
Save your work.
The business day calendar defines business days and non-business days for billing purposes. For example, on non-business days, you do not pay or charge interest on invoices. Non-business days include weekends, Brazilian national holidays, and local municipal holidays.
Oracle Payables and Oracle Receivables use the business day calendar to flag exceptions to the billing period specified in incoming and outgoing invoices.
The setup procedures for creating a business day calendar are:
Define profile options
Create an exception template for national holidays
Create a standard workday calendar
Load the national holidays exception template into the standard workday calendar
Define local holidays for each city that you do business with
Use the Exception Templates window to create a template for national holidays. The exception template defines exceptions for your workday calendar. For billing purposes, you must define an exception template that includes all Brazilian national holidays.
After you create the exception template, define a standard business day calendar and apply this template to it.
To create a workday exception template:
Navigate to the Exception Templates window.
Enter a name that identifies this template, such as National Hols, in the Template field.
Enter the date for each national holiday in the Date fields. Leave the Days On check boxes set to off.
Save your work.
Use the Workday Calendar window to define a standard business day calendar. A workday calendar consists of a start date, an end date, and on and off days that follow one or more defined workday patterns.
When you define the business day calendar, you must specify the standard five-day business week of Monday through Friday, with Saturday and Sunday as the two days off. This calendar, along with the national holiday exception template, determines the annual billing pattern.
To create a business day calendar:
Navigate to the Workday Calendar window.
Enter a name that clearly identifies this calendar as the business day calendar in the Name field.
Enter a date range for this calendar in the Calendar Date Range From and To fields.
The default end date is four years from the start date. Make sure that the start date is a Monday so that the calendar follows the standard business day pattern.
Press the Workday Pattern button.
The Workday Patterns window appears.
Enter the sequence number 1 in the Seq field to apply this workday pattern to the calendar when it is built.
Enter 5 in the Days On field and 2 in the Days Off field.
This defines Monday through Friday on and Saturday and Sunday off.
Save your work.
You can view calendar dates.
Press the Dates button in the Workday Calendar window.
The Calendar Dates window appears.
Press the Exception List button.
Press the Load button and select Template to apply existing exceptions.
Enter the name of the national holidays template, and press the OK button to load the template.
Save your work.
Choose Build from the Tools menu to build the workday calendar.
Use the Local Holidays window to define local holidays for the cities that you do business with. The location where the Local Holidays window validates local holidays is defined in the Payment Location profile option. Oracle Payables and Oracle Receivables use the local holiday information, along with the business day calendar, to flag exceptions to the billing period specified in incoming and outgoing invoices for these cities.
If you select Company as the payment location in the System Profile Options window, you must enter your company's city in the Payment Location field in the Brazilian Additional Information tabbed region of the Payables Options window. This Payment Location field is used to validate the business day calendar for local holidays.
Before you can use the Local Holidays window, you must:
Define profile options
Define company information
Enter customers
Enter suppliers
To define local holidays:
Navigate to the Local Holidays window.
Enter the name of the city in the City field.
Enter the state to which the city belongs in the State field.
Enter a description in the Description field.
Leave the Inactive On field blank.
Assign a payment location.
In the Date fields, enter the date for each local holiday. Leave the Days On check boxes set to off.
Repeat steps 2 to 6 for each city that you want to enter local holidays for.
This section describes how to enter bank collection documents, correct bank information on a collection document, and associate collection documents with trade notes.
Use the Collection Documents window to enter bank collection documents into Payables and view them. After you enter a new collection document, the collection document is automatically associated with a trade note that is not associated according to the association method defined in the Payables Options window. After the association, the trade note is released to be paid.
Before you can use the Collection Documents window, you must set up procedures using these windows:
Payables Options window
Banks window
Suppliers window
To enter collection documents:
Navigate to the Collection Documents window.
Select the applicable operating unit.
Enter bank information in the Bank Name and Bank Number fields. The list of values for these fields displays bank accounts with Brazilian Real as the defined currency.
The Branch Name and Branch Number fields automatically default with values based on the bank information you entered.
Enter the payment location from the collection document in the Payment Location field.
Enter supplier information in the Supplier, Supplier Number, and Site fields.
The Inscription Number field automatically defaults with a value based on the Site information. This number is the supplier's taxpayer ID.
Enter other information for collection documents in the Due Date, Document Number, Currency Code, Amount, and Status Lookup Code fields.
The Payment Number field displays the payment number assigned to the trade note.
Use the Collection Document Association window to associate an unassociated bank collection document with an unassociated trade note (also known as a payment schedule). The trade note must be unpaid. You can also associate a trade note to a collection document as well as disassociate a collection document associated with a trade note. The manual association does not use the method you defined in the Payables Options window for automatic association. You query invoices in the Find Invoices to Match window.
Before you can use the Collection Document Association window, you must enter invoices and collection documents in the Invoice Workbench and Collection Documents windows.
To manually associate or disassociate collection documents:
Navigate to the Collection Document Association window.
The Find Invoice to Match window appears.
Note: The list of values displays invoices with a currency that matches what you defined in the JLBR Bank Transfer Currency profile option.
Enter or query invoices that you want to manually associate or disassociate with collection documents.
Press the Find button.
The Collection Document Association window appears.
Select the applicable operating unit.
Select an invoice in the Invoice region.
Select a scheduled payment, or trade note, to associate with a collection document in the Scheduled Payments region.
Press the Collection Document button.
The Collection Document window appears.
Select a collection document.
Press the Associate button to associate the selected collection document with the trade note. Press the Disassociate button to disassociate them.
Press the OK button in the popup window.
Use the Imported Collection Documents window to correct collection document information for an operating unit listed in the Brazilian Payables Import Bank Collection Documents report. This report is automatically generated after you run the Brazilian Payables Import Bank Collection Documents program and shows unvalidated collection documents. For more information about this report, see Brazilian Payables Import Bank Collection Documents Report.
When you correct an entry in this window, the entry is validated and inserted into Payables. The validated collection document is automatically associated with a trade note by the association method that you selected in the Payables Options window.
Before you can use the Imported Collection Documents window, you must set up procedures in these windows:
Currencies window
Payables Options window
Banks window
Suppliers window
You must also enter company information in the Company window and run the Brazilian Payables Import Bank Collection Documents program.
To correct entries in a collection document:
Navigate to the Imported Collection Documents window.
The File Control window automatically appears.
Select a file that contains collection documents.
Press the OK button.
Correct any entries in the collection document in the Imported Collection Documents window.
Press the Validate button to validate your corrections in Payables.
The collection document is automatically associated with its matching trade note.
Query another collection document to correct.
The Authorized Direct Debit (DDA), also known as the Electronic Collection Document, is a service that enables companies to query and perform electronic payments through the bank that owns the Checking Account.
The Electronic Payer can perform Electronic Collection Document payments by using the standard bank channels, such as EFT files, direct debit, Internet banking, phone banking, etc.
Oracle Payables supports the Brazilian DDA process and allows customers to enter and process electronic collection documents payments. Oracle Payables enables the following attributes at the Collection Document window and the Import Bank Collection Documents concurrent program:
Collection Document Barcode
Electronic Format Checkbox
To use Electronic Collection Documents, navigate the Collection Documents window, select the Electronic Format checkbox, and enter the Collection Document Barcode.
Localizations > Collection Documents > Define
The Collection Document Barcode is required at the Electronic File Transfer. This is a mandatory record and an important field to speed up the data entry of manual collection documents. This field is also required for the Standard Collection Document.
The Electronic Format checkbox determines whether a respective collection document is electronic or standard. The checkbox must be used in case the EFT format requires a different treatment for standard or electronic collection documents.
These two attributes enable customers to manually enter or load Electronic Collection Documents information in Oracle Payables to process EFT payments using the EFT bank layouts supported by the Regional Field Center.
The EFT bank layouts, or Add-On Localizations, collect new information in order to communicate payment orders. For additional information, please contact the Regional Field Center (Product ID 1671).
You must load the attributes of Collection Document Barcode and Electronic Format checkbox into the interface table though the Brazilian Payables Import Bank Collection Documents program.
Use the Maintain Interface window to correct the imported collection documents and add these attributes.
Consolidated Billing lets you enter fiscal information in a shipping invoice and then match it with a consolidated invoice for auditing purposes for a given operating unit.
The Consolidated Billing functionality lets you satisfy the Brazilian Consolidated Billing requirements. You can:
Enter shipping invoices as standard invoices
Enter consolidated invoices
Associate one or more shipping invoices with a consolidated invoice
Disassociate shipping invoices already associated with consolidated invoices
Perform the normal invoice approval process
Enter physical, tax, and financial information at the time the goods are received, based on the shipping invoices
Cancel a consolidated invoice
Note: The Consolidated Invoice functionality does not allow foreign currency invoices. Only approved invoices that you enter in ledger currency can be matched with a consolidated invoice.
You can use the shipping invoice for purchasing items and services. To associate a shipping invoice, you need to match it with a consolidated invoice. You can use the standard invoice to enter the shipping invoice information. When you associate shipping invoices with the consolidated invoice, the payment terms of the shipping invoices are updated with the payment terms of the consolidated invoice.
You can import shipping invoices from other accounting systems as standard invoices. You follow the same rules for the manually entered standard invoices.
You use a consolidated invoice to match a shipping invoice you want to pay within the same payment terms. You cannot import a consolidated invoice. You can optionally enter a pay group used in all shipping invoices and group them for payment. Calculate the payment schedule using the business day calendar.
You can enter Brazilian tax information for standard invoices (shipping invoices). You can store some taxes parameters at invoice line level. These parameters are used to calculate the tax amount for the invoice.
You can see interest information for standard invoices. You can store interest parameters at different levels (supplier, supplier site, payment schedule).
For the standard invoice, you will have default interest information from the supplier site. You can override interest information at the payment schedule level.
You can pay an invoice by associating a trade note with a collection document.
You can choose to automatically associate a collection document with a trade note. You can also associate them manually.
Payables generates these reports for Brazil:
Brazilian Payables Consolidated Invoice Register - Lists suppliers, amounts, and related shipping invoices for consolidated invoices
Brazilian Payables Cancelled Consolidated Invoices Register - Lists suppliers, amounts, related shipping invoices, and cancellation information for canceled consolidated invoices
Interest Handling lets you define interest parameters at supplier level, supplier site level, or trade note level. When you pay an overdue invoice, Payables automatically creates an interest invoice for the overdue invoice and creates a corresponding payment.
The Interest functionality lets you satisfy the Brazilian Interest requirements. You can:
Calculate interest based on the business day calendar and see the interest amount and number of days the payment is late. If the payment due date is on a weekend or holiday, you can keep, change, or delete the due date that is used for the interest calculation.
Define the period that interest must be calculated for.
Define a penalty fee for an overdue invoice.
Allow for grace days in the event of a late payment.
Allow for simple or compounded interest calculations.
Allow for interest billing in percent or value.
Allow for interest invoice generation and accounting.
You can define interest parameters at supplier level, supplier site level, or trade note level.
You can pay an overdue invoice with either a payment batch, manual payment, or a QuickCheck. Payables automatically creates an interest invoice for the overdue invoice and creates a corresponding payment when you create your payment batch, manual payment, or QuickCheck payment. If you manually pay an overdue invoice, Payables warns you that the interest is due for the invoice; you should pay the invoice in a payment batch or with a Quick payment.
You can pay or cancel the calculated interest amount when you pay the main amount. You can also change the interest invoice amount.
You can define a penalty fee and the interest when you pay an overdue invoice.
Payables calculates interest according to the business day calendar and shows the interest value and number of days a payment is late. If the due date is a weekend or a holiday, Payables lets you anticipate, postpone, or keep the due date for the interest calculation.
Related Topics
Payables Options, Oracle Payables User Guide
Entering Invoices Overview, Oracle Payables User Guide
Use the Brazilian Payables Consolidated Invoice Register report to review detailed information about consolidated invoices. This report lists consolidated invoice information such as supplier, amount and the related shipping invoices. Information such as accounting, tax, and amount are provided for each shipping invoice.
Oracle Payables sorts the information in the report by consolidated invoice currency. Within each currency section, the report sorts by the supplier name and consolidated invoice number.
Use the Standard Request Submission windows to submit the Brazilian Payables Consolidated Invoice Register report.
Enter the user's name to list consolidated invoices entered by that user. Leave this field blank to list consolidated invoices entered by all users.
Enter the beginning date of a range of dates when consolidated invoices were entered. Oracle Payables prints consolidated invoices entered on or after the First Entered Date.
Enter the last date of a range of dates when consolidated invoices were entered. Oracle Payables prints consolidated invoices entered on or before the Last Entered Date.
Enter the name of the accounting period for consolidated invoice information. Oracle Payables lists the consolidated invoices between the First Entered Date and the Last Entered Date in the accounting period you choose.
This table shows the report headings.
| In this heading… | Oracle Payables prints… |
|---|---|
| <Company Name> | The name of the company running the report |
| Date | The date and time that the company ran the report |
| <Report Title> | Consolidated Invoice Register |
| Entered By | The name of the person who entered the consolidated invoices |
| Start Date | The beginning date of the invoice entry date range |
| Period | The accounting period's name for the report |
| End Date | The ending date of the invoice entry date range |
| Currency | The currency for the consolidated invoices |
This table shows the column headings.
| In this column… | Oracle Payables prints… |
|---|---|
| Supplier Name | The supplier's name for the consolidated invoice. |
| Consolidated Invoice Num | The consolidated invoice number. |
| Consolidated Invoice Date | The consolidated invoice date. |
| Original Amount | The invoice's original amount. Payments are not subtracted from this amount. |
| Amount Remaining | The amount remaining for payment on the consolidated invoice. The amount remaining is equal to the original invoice amount unless you have paid or partially paid the shipping invoice. |
| Description | The consolidated invoice description. |
| Shipping Invoice | The shipping invoice number matched to the consolidated invoice. |
| Type | The distribution line type. |
| Line | The distribution line number. |
| Expense Accounting Flexfield | The accounting flexfield segment values for an invoice distribution line. |
| Amount | The invoice distribution line amount. |
| Description | A partial description of an invoice distribution line. |
| Accounting Date | The accounting date of an invoice distribution line. Oracle Payables uses the accounting date when creating journal entries to transfer to the General Ledger. |
| Posted | Yes if a journal entry was created for posting to the General Ledger; No if a journal entry was not created. |
| Total for <Supplier Name> | The total Original Amount and total Amount Remaining from the consolidated invoices for each supplier. |
| Total for <Currency> | The total Original Amount and total Amount Remaining from the consolidated invoices for each currency. |
Related Topics
Using Standard Request Submission, Oracle Applications User Guide
Use the Brazilian Payables Cancelled Consolidated Invoices Register report to review detailed information about the canceled consolidated invoices. This report lists consolidated invoice information such as supplier, amount and the related shipping invoices, as well as the information about its cancellation.
Oracle Payables sorts the information on the report by consolidated invoice currency. Within each currency section, the report sorts by the supplier name and consolidated invoice number.
Use the Standard Request Submission windows to submit the Brazilian Payables Cancelled Consolidated Invoices Register report.
Enter the user's name to list consolidated invoices entered by that user. Leave this field blank to list consolidated invoices entered by all users.
Enter the beginning date of a range of dates when consolidated invoices were entered. Oracle Payables prints consolidated invoices entered on or after the First Entered Date.
Enter the last date of a range of dates when consolidated invoices were entered. Oracle Payables prints consolidated invoices entered on or before the Last Entered Date.
Enter the name of the accounting period for consolidated invoice information. Oracle Payables lists the consolidated invoices between the First Entered Date and the Last Entered Date in the accounting period you choose.
This table shows the report headings.
| In this heading… | Oracle Payables prints… |
|---|---|
| <Company Name> | The name of the company running the report |
| Date | The date and time that the company ran the report |
| <Report Title> | Canceled Consolidated Invoice Register |
| Page | The page number |
| Entered By | The name of the person who entered the consolidated invoices |
| Start Date | The beginning date of the invoice entry date range |
| Period | The name of the accounting period for the report |
| End Date | The ending date of the invoice entry date range |
| Currency | The currency for the consolidated invoices |
This table shows the column headings.
| In this column… | Oracle Payables prints… |
|---|---|
| Supplier Name | The supplier's name for the consolidated invoice |
| Consolidated Invoice Number | The consolidated invoice number |
| Consolidated Invoice Date | The consolidated invoice date |
| Canceled Amount | The canceled amount of the invoice |
| Canceled By | The username of the person who canceled the consolidated invoice |
| Canceled Date | The date of the consolidated invoice cancellation |
| Description | The consolidated invoice description |
| Total for <Supplier Name> | The total Canceled Amount of the consolidated invoices for each supplier |
| Total for <Currency> | The total Canceled Amount of the consolidated invoices for each currency |
Related Topics
Using Standard Request Submission, Oracle Applications User Guide
Use the Brazilian Payables Associated Trade Notes and Bank Collection Documents report to list trade notes and associated bank collection documents. The documents can be ordered by invoice number or by supplier name and due date of the invoice.
Use the Standard Request Submission windows to submit the Brazilian Payables Associated Trade Notes and Bank Collection Documents report.
Enter the document that will be used in the sort:
Collection Document (default) - Oracle Payables sorts the report by collection document.
Invoice - Oracle Payables sorts the report by trade notes.
Enter the sorting method for this report:
Document Number (default) - Oracle Payables sorts the report either by invoice number or by collection document number, depending on whether you selected to sort either by Invoice or by Collection Document.
Supplier Name and Due Date - Oracle Payables sorts the report alphabetically by Supplier Name and for each supplier group it sorts by Due Date. It can use the Supplier Name and the Due Date of the invoice or the collection document, depending on which criteria you have selected previously.
Enter the starting collection document number for a range of bank collection document numbers that are associated with a trade note.
Enter the ending collection document number for a range of bank collection document numbers that are associated with a trade note.
Enter the beginning date for a range of bank collection documents with a due date between the Begin Date and the End Date.
Enter the ending date for a range of bank collection documents with a due date between the Begin Date and the End Date.
Enter the starting collection document amount for a range of bank collection documents associated with a trade note.
Enter the ending collection document amount for a range of bank collection documents associated with a trade note.
Enter the starting invoice number for a range of trade notes associated with a bank collection document.
Enter the ending invoice number for a range of trade notes associated with a bank collection document.
Enter the starting date for a range of trade notes associated with a bank collection document with a due date between the Begin Date and the End Date.
Enter the ending date for a range of trade notes associated with a bank collection document with a due date between the Begin Date and the End Date.
Enter the starting amount for a range of trade notes associated with a collection document that have amounts between the From: Invoice Amount and the To: Invoice Amount.
Enter the ending amount for a range of trade notes associated with a collection document that have amounts between the From: Invoice Amount and the To: Invoice Amount.
This table shows the column headings.
| In this column… | Oracle Payables prints… |
|---|---|
| Collection Doc Number | The collection document number |
| Invoice Number | The invoice number of the trade note |
| Pay Num | The payment number of the trade note |
| Due Date | The due date for collection documents and trade notes |
| Amount | The amount of collection documents and trade notes |
| Curr | The currency of the collection documents and trade notes |
| Hold? | Yes or No to indicate if the trade notes are on hold |
| Supplier Name | The supplier name of the collection documents and trade notes |
| Bank Name | The bank name for the collection documents |
| Branch Name | The branch name for the collection documents |
Related Topics
Using Standard Request Submission, Oracle Applications User Guide
Use the Brazilian Payables Non-Associated Trade Notes and Bank Collection Documents report to list trade notes that are not associated with collection documents as well as bank collection documents that are not associated with trade notes. The documents can be ordered by document number or by supplier name and due date.
Use the Standard Request Submission windows to submit the Brazilian Payables Non-Associated Trade Notes and Bank Collection Documents report.
Enter the sorting method for this report:
Document Number (default) - Oracle Payables sorts the bank collection documents and trade notes by document number.
Supplier Name and Due Date - Oracle Payables sorts the bank collection documents and trade notes alphabetically by Supplier Name and for each supplier group it sorts by Due Date.
Enter the starting collection document number for a range of bank collection document numbers that are not associated with a trade note.
Enter the ending collection document number for a range of bank collection document numbers that are not associated with a trade note.
Enter the beginning date for a range of bank collection documents with a due date between the Begin Date and the End Date.
Enter the ending date for a range of bank collection documents with a due date between the Begin Date and the End Date.
Enter the starting collection document amount for a range of bank collection documents not associated with a trade note.
Enter the ending collection document amount for a range of bank collection documents not associated with a trade note.
Enter the starting date for a range of trade notes not associated with a bank collection document with a due date between the Begin Date and the End Date.
Enter the ending date for a range of trade notes not associated with a bank collection document with a due date between the Begin Date and the End Date.
Enter the starting amount for a range of trade notes not associated with a collection document with amounts between the From: Invoice Amount and the To: Invoice Amount.
Enter the ending amount for a range of trade notes not associated with a collection document with amounts between the From: Invoice Amount and the To: Invoice Amount.
This table shows the column headings.
| In this column… | Oracle Payables prints… |
|---|---|
| Collection Doc Number | The collection document number |
| Invoice Number | The invoice number of the trade note |
| Pay Num | The payment number of the trade note |
| Due Date | The due date of the collection documents and trade notes |
| Amount | The amount of the collection documents and trade notes |
| Curr | The currency for the collection documents and trade notes |
| Hold? | Yes or No to indicate if the collection documents and the trade notes are on hold |
| Supplier Name | The supplier name for the collection documents and trade notes |
| Bank Name | The bank name for the collection documents and trade notes |
| Branch Name | The branch name for the collection documents and trade notes |
| Account Number | The account number for the trade note |
| Total for Collection Documents | The total amount and total number of collection documents |
| Total for Invoices | The total amount and total number of trade notes |
Related Topics
Using Standard Request Submission, Oracle Applications User Guide
Use the Brazilian Payables Import Bank Collection Documents report to list bank collection documents that are not validated during the import from the collection documents interface table to the system.
The Brazilian Payables Import Bank Collection Documents report is automatically submitted after you run the Brazilian Payables Import Bank Collection Documents program.
Note: The Brazilian Payables Import Bank Collection Documents program populates but cannot validate the values contained in user-defined descriptive flexfield columns.
Use the Standard Request Submission windows to submit the Brazilian Payables Import Bank Collection Documents program.
Used to access the Collection Documents Interface Extension table and the Collection Documents Interface Temporary table.
Choose the automatic association method for trade notes and collection documents.
This table shows the report headings.
| In this heading... | Oracle Payables prints... |
|---|---|
| <Company> | The company name |
| <Report Title> | Import Bank Collection Documents Report |
| Report Date | The date and time that you ran the report |
| Page | The current and total page numbers |
| File Control | The file control number of the imported collection documents file |
| Status | The status of the imported collection documents file |
| Total Collection Documents Imported | The total number of imported collection documents |
| Total Amount Imported | The total amount of imported collection documents |
| Total Collection Documents Validated | The total number of validated collection documents |
| Total Amount Validated | The total amount of validated collection documents |
This table shows the column headings.
| In this column… | Oracle Payables prints… |
|---|---|
| Seq | The sequence number |
| Collection Doc Number | The collection document number |
| Due Date | The due date of collection documents |
| Amount | The amount of collection documents |
| Transferer Name | The supplier name |
| Exception Reason | The reason why a collection document was not created or imported during the Bank Collection Document Import process |
Related Topics
Using Standard Request Submission, Oracle Applications User Guide
Businesses in Brazil must collect and remit taxes to federal, state, and city governments on most of the goods and services that they buy. Tax Handling helps you to manage tax payments for invoices.
Note: Taxes are not calculated in Oracle Sales and Marketing if you use the Latin tax method to calculate tax. The taxes are shown as zero.
The Tax Handling functionality lets you satisfy all of your tax requirements. You can:
Calculate exclusive taxes as you enter sales orders
See the exclusive tax rate or the tax amount by line on the sales order
See the total net amount of the sales order, the total tax amount of the sales order, and the gross amount of the sales order (net amount + tax amount)
Check the customer credit against the gross amount of the sales order
Transfer the tax code from the sales order line to the Receivables interface table
Calculate tax as you enter the invoice
Apply multiple tax rates to a single line
Calculate inclusive tax and exclusive tax for item amounts
Calculate regular, compounded, reduced, and increased tax bases
Assign tax codes at state ship from/state ship to, customer, item, and fiscal classification levels
Automatically create tax accounting
Enter fiscal attributes for invoices, items, and customers
Define additional tax categories for your tax codes
Receivables calculates the IPI tax and creates a corresponding tax line in the invoice. The IPI calculation supports a reduced tax base amount. The account that you defined in the Tax Codes and Rates window is used to create the tax accounting.
Receivables calculates the ICMS tax and creates a corresponding tax line in the invoice. The ICMS calculation supports the IPI included in the tax base amount and a reduced tax base amount. The account that you defined in the Tax Codes and Rates window is used to create the tax accounting.
Receivables calculates the ICMS Tributary Substitution tax and creates a corresponding tax line in the invoice. The account that you specified in the Tax Codes and Rates window is used to create the tax accounting.
Receivables calculates the ISS tax and creates a corresponding tax line in the invoice. The account that you specified in the Tax Codes and Rates window is used to create the tax accounting.
Receivables calculates the IRJ tax and creates a corresponding tax line in the invoice. The account that you specified in the Tax Codes and Rates window is used to create the tax accounting.
You can define a new tax category. Receivables calculates the tax amount with the attributes you define.
You can define a group of taxes with the Latin tax groups to apply to a transaction.
You can define the base amount rate to increase or reduce the tax base amount.
You can define where you want your tax codes to be defaulted to a transaction line from. Tax codes are defaulted from:
Item
Fiscal classification
Memo line
Customer
Ship to site from customer address
Bill to site from customer address
Organization
Customer address (state or province) and organization address (state or province)
Customer address (state or province), organization address (state or province), and item
Customer address (state or province), organization address (state or province), item, and fiscal classification
System options
Tax category
Latin tax group
You can define taxes with the Latin tax groups to apply to a transaction. You can control the effective dates and other attributes related to the tax.
You can define different Latin tax groups with the same tax category.
The payment collection process involves a series of transactions between a supplier, customer, and a bank. A supplier starts the payment collection process after the supplier creates an invoice for the customer. The supplier generates collection documents based on the invoice payment terms and sends information about these documents to a collection bank. After the collection bank collects a payment from the customer, the bank transfers the payment information to the supplier to create receipts and apply the information to the customer's balance.
The Bank Transfer functionality lets you manage payment collection. You can:
Electronically transfer collection documents to the bank
Handle bank instructions and bank occurrences, such as discounts, protests, and address updates, for each collection document
Automatically or manually create a batch of collection documents to transfer to different banks, as well as maintain and cancel these batches
Select occurrences and create a batch of occurrences to transfer to a bank
Automatically load or manually enter documents and occurrences that are transferred from the bank into Receivables
Generate receipts from the documents that are transferred from the bank and apply the receipts to corresponding invoices. Collected interest and penalty fees automatically generate adjustments, debit memos, or both in Receivables.
Create account entries for each generated occurrence and post them to General Ledger
You can create a remittance batch to send to your bank for payment collection. You can specify selection criteria to automatically or manually select the payment schedule to include in the remittance batch. A collection document is created in Receivables for each selected payment schedule. After collection documents are created, you can review the collection documents that were selected in the batch and add or delete them in the batch.
You can define limit parameters and default information for document selection, such as maximum quantity of documents per remittance batch, minimum/maximum amount for each document, and minimum/maximum total amount for the remittance batch.
You can assign different remittance formats to your banks when you define the bank accounts. If you have an error the first time you format a remittance batch, you can reformat the batch. You can also cancel a remittance batch, since the bank did not return the documents yet.
You can automatically load a bank return file into Receivables or manually enter the bank return records. In both cases, each record is validated against related collection documents, as well as supplier and customer information. After the automatic validation, you can manually correct the records that have invalid data.
The valid return records generate return occurrences, adjustments for interest and abatements, debit memos for interest not paid, and receipts. Receipts are applied to the original payment schedules selected for bank remittance.
You can define tolerance limits for applying receipts to the invoices, according to interest and abatements paid by the customer.
You can define the parameters for calculating interest for the customer. You can also define the interest account when you define the receipt method.
Receivables calculates the interest and compares it to the interest that the bank received. If the customer pays less interest than the calculated interest, Receivables creates a debit memo for the interest not received. If the customer pays the correct interest amount, Receivables creates an adjustment for the interest received.
You send instructions to the bank for a collection document. The most common instructions are:
Write-off after due date
Collect interest charges
Discharge interest charge collection
Protest after due date
You can define instruction codes for each of your banks. You can also define the instructions to send to a specific customer profile class.
Although instructions and occurrences give directions to the bank for a collection document, an occurrence is for a collection document that was already sent to the bank. You can automatically or manually add occurrences to a document.
You can define occurrence codes for different banks. Receivables automatically generates an occurrence for each related event.
You can assign different occurrence remittance formats to your banks when you define the remittance banks.
Receivables generates these reports for Brazil:
Brazilian Receivables Occurrences Remittance Batch - Lists occurrences for collection documents to send to the bank in paper or file format
Brazilian Receivables Collection Remittance Batch - Lists the collection documents to send to the bank in paper or file format
Brazilian Receivables Factoring Remittance Batch - Lists the collection documents that were traded with the bank through factoring in paper or file format
Brazilian Receivables Bank Return Import - Lists collection documents rejected by the Bank Import Program validation
Brazilian Receivables Post Bank Return - Summarizes the receipts, adjustments, interest, monetary corrections, and discounts for receipts
Brazilian Receivables Bank Collection GL Interface - Summarizes the journal entries that the Bank Transfer feature generates
Companies send a shipping invoice with a product as a customer's bill. Billing lets you enter packaging attributes, freight carrier information, customer information, an operation fiscal code, item information, and legal justification messages in an invoice.
The Billing functionality lets you satisfy the Brazilian Billing requirements. You can:
Produce a shipping invoice with information such as, Brazilian taxes, customer attributes, organization attributes, operation types, legal justification messages, item attributes, freight carrier attributes, packaging attributes, accessory expenses, and the operation fiscal code.
Reprint a shipping invoice.
Cancel a shipping invoice.
Control the document sequence number and issue date for a shipping invoice.
Define a subseries and assign a document sequence to it.
Use the issue date to calculate the due date for an invoice and account for the invoice in Receivables.
Produce a complementary invoice.
You can define and print these attributes for your customers:
Inscription number (CNPJ/CPF)
State inscription number
Municipal inscription number
You can define and print the state Tributary Substitute inscription for your organization.
You can print the date the product is shipped to the customer. This date is optional.
You can define if the invoice is used for a product entry or exit purpose. Suppliers must use the same invoice form to record sales, returned items, and imported items. Sale transactions have an exit operation type. Return-to-supplier transactions and imported item transactions have an entry operation type.
You can manually enter and print a legal justification message for the invoice when there is a tax base amount reduction, tax exemption, exportation, or tax immunity.
You can specify these inventory and non-inventory item attributes:
Federal Tributary Situation to indicate if the item is exempt, taxed, or non-taxed. The Federal Tributary Situation is added to the invoice line.
State Tributary Situation to indicate if the item is exempt, taxed, or non-taxed. The State Tributary Situation is added to the invoice line.
Item Origin to indicate if the item is imported or national. The Item Origin is added to the invoice line.
Item Fiscal Type. The Item Fiscal Type is added to the invoice line.
You can enter a freight carrier and a license plate in the invoice. You are not legally required to validate the license plate number.
You can define these freight carrier attributes for the invoice:
Address
City
State
Inscription number (CNPJ/CPF)
State inscription number
Note: You must enter these attributes in the shipping invoice if you are not responsible for the freight.
You can define and print the freight responsibility: CIF (customer responsibility) or FOB (remit responsibility).
You can enter and print these packaging attributes in the invoice:
Volume type
Volume quantity
Brand
Volume number
Total net weight
Total gross weight
You can define the default value of the brand for your organization.
You can enter and print the freight expense, insurance expense, and other accessory expense amounts in the invoice.
The accessory expenses are not accounted for and do not change the invoice total amount.
You can define the operation fiscal code (CFOP) for a transaction to identify the type of operation. You must enter this code for fiscal books.
This table provides examples of some fiscal codes:
| Enter this code… | For this purpose… |
|---|---|
| 5.10 | Sale of products by the supplier or a third party in the same state as the supplier |
| 5.11 | Sale of industrial products by the supplier or a third party in the same state as the supplier |
| 5.12 | Sale of products received by a third party in the same state as the supplier |
| 5.13 | Sale of industrial services by a third party in the same state as the supplier |
| 6.21 | Transfer of industrial products by a third party outside the state of the supplier |
You can create a credit memo to cancel an invoice. Receivables automatically changes the status of the invoice to void.
You can define an invoice subseries in Receivables. You can number invoices by subseries. Automatic and manual invoices have the same subseries.
You can create a complementary invoice to correct entries on another previously entered invoice. This new invoice shows the corrected entries without the calculations.
Receivables generates these reports for Brazil:
Brazilian Receivables Print Invoice in AutoInvoice/Brazilian Receivables Invoice Print Invoice in Batch/Brazilian Receivables Print Invoice in Batch Immediately/Brazilian Receivables Re-Print Specific Invoice - Lists completed shipping invoices and their attributes
Brazilian Receivables Invoice Print Complementary Invoice in Batch/ Brazilian Receivables Print Complementary Invoice Immediately - Lists completed complementary invoices and their attributes
Brazilian Receivables Customer Interface Error - Automatically prints after the Customer Interface program ends
Interest is calculated for invoice payments. You can choose to calculate interest based on either the total amount of the invoice or a partial payment. Interest Handling lets you pay the interest amount later, cancel the interest, or accept and receive the interest.
Receivables determines the difference between calculated and received interest. If the calculated interest is greater than the received interest, you can either write off the difference or generate a debit memo. If the difference is greater than the received interest and you write off the difference, Receivables uses the write-off tolerances and the Receivables adjustment limits. If the difference exceeds any of these tolerances, the adjustment that you created will have a Waiting for Approval status. If the calculated interest is equal to the received interest, Receivables does not use adjustment limits and write-off tolerances.
Note: For Brazilian Receivables, you must set the Allow Overapplication flag of the transaction type associated with the overdue invoice to Yes in order to calculate interest.
The Interest functionality lets you satisfy Brazilian interest requirements. You can:
Calculate interest according to when an invoice is received.
Handle the interest amount due. You can choose to pay the interest amount due and the invoice amount together, cancel the interest amount, or create an Interest Debit memo with the interest amount to pay later.
Calculate interest based on the total amount of the invoice or based on the paid amount.
Use simple or compounded interest calculation formulas to calculate the interest amount.
Use a rate or a value to calculate the interest amount for a specific period.
Define the period for interest calculation.
Create grace days for late payments.
You can define interest parameters at system option level, customer profile classes, or invoice level.
Receivables calculates interest for an overdue invoice when you enter a receipt and use the Enter Receipt, QuickCash, or Bank Transfer features.
You can choose to calculate interest either based on the total invoice amount or on a partial payment. Receivables uses a simple or compounded formula to calculate the interest based on the parameters that you set up for the invoice.
You decide to pay, cancel, or create an Interest Debit memo with the calculated interest amount when you receive the invoice.
You can define a penalty fee and interest for overdue invoices.
Receivables calculates interest according to the business day calendar and shows the interest value and number of days that a payment is late. If the due date is a weekend or a holiday, Receivables lets you anticipate, postpone, or keep the due date for the interest calculation.
This section describes the setup procedures for Brazilian Receivables. You must enter the setup information for your company before you create and import invoices and collection documents, enter receipts, or run any of the Receivables reports. Use this checklist to help you complete the appropriate steps in the correct order.
Use the globalization flexfield in the System Options window to define control options and system parameters for bank transfer, interest calculation, billing, and tax calculation. Specify your company information, tax method, customer address validation, shipping invoice printing options, and interest parameters.
Before you can use the System Options window, you must:
Define company information using the Legal Entity Configurator
Define a sales tax location flexfield structure
Define a transaction source in the Transaction Source window
Define a transaction type in the Transaction Type window
Define a receipt method in the Receipt Classes window
To enter bank transfer information:
Navigate to the Define System Options window.
Navigate to the globalization flexfield.
In the Company Name field, enter your company's name. Your company name is used in the header record in the bank remittance batch electronic file. The company name is also used to validate the header record of the bank return file.
Press the OK button.
Navigate to the Define System Options window.
Navigate to the globalization flexfield.
Enter Rate or Amount in the Interest Type field to calculate interest for past due invoices.
Enter either the rate or amount in the Interest Rate/Amount field.
In the Interest Period field, enter the number of days that interest charges are calculated over.
In the Interest Formula field, enter Simple or Compound to indicate the formula used to calculate interest.
In the Grace Days field, enter the number of receipt grace days that customers can be overdue on receipts before you charge interest.
Enter Rate or Amount in the Penalty Type field to calculate how to charge your customers a late payment penalty.
Enter either the rate or amount in the Penalty Rate/Amount field.
In the Interest Batch Source field, enter the transaction source that is used to generate an interest debit memo.
In the Interest Transaction Type field, enter the transaction type that is used to generate an interest debit memo.
In the Interest Receipt Method field, enter the receipt method that is used to generate an interest debit memo.
Press the OK button.
To enter tax information:
Navigate to the Define System Options window.
Navigate to the Tax tabbed region.
In the Tax Method field, select Latin Tax Handling.
Yes
Define a sales tax location flexfield structure in the Location Flexfield Structure field.
Check the Inclusive Tax Used check box.
Choose Line in the Calculation Level field.
Navigate to the globalization flexfield.
In the Tax Location Flexfield Classification field, enter State.
In the Use Legal Messages field, enter if you want default legal messages to appear on your invoices. Enter No if you do not.
In the Transaction Type field, enter the transaction type that you want as the default for your tax rules.
Press the OK button.
To enter billing information:
Navigate to the Define System Options window.
Navigate to the globalization flexfield.
In the Print Invoice Immediately field, enter Yes if you want to print invoices from the Transactions window or Complementary Invoice window. Enter No if you do not.
Press the OK button.
Use the globalization flexfield in the Customer Profile Classes window to define bank transfer and interest parameters for Oracle Receivables profile classes. You can define whether or not Oracle Receivables sends specific bank instructions to customers in this profile class.
The Customer Profile Classes window also displays interest parameters, if you entered them in the System Options window. You can add or modify this information in the Customer Profile Classes window. For instructions about using the System Options window, see Defining System Options.
To enter bank transfer information:
Navigate to the Customer Profile Classes window.
Enter a profile class.
Navigate to the globalization flexfield.
In the Remit Protest Instructions field, enter Yes if you want Oracle Receivables to remit protest instructions to the bank related to collection documents that belong to customers of this profile class. Enter No if you do not.
In the Remit Interest Instructions field, enter Yes if you want Oracle Receivables to remit interest instructions to the bank for collection documents that belong to customers of this profile class. Enter No if you do not.
Press the OK button.
To enter interest information:
Navigate to the Customer Profile Classes window.
Query the profile class that you want.
Navigate to the globalization flexfield. If you entered interest parameters in the System Options window, these fields are automatically populated in the globalization flexfield.
Enter Rate or Amount in the Interest Type field to calculate the interest on invoices past due.
Enter either the rate or amount in the Interest Rate/Amount field.
In the Interest Period field, enter the number of days that interest charges are calculated over.
Enter Simple or Compound in the Interest Formula field to indicate the formula used to calculate interest.
In the Grace Days field, enter the number of receipt grace days that customers can be overdue on receipts before interest is charged.
Enter Rate or Amount in the Penalty Type field to calculate how to charge customers a late payment penalty.
Enter either the rate or amount in the Penalty Rate/Amount field.
Press the OK button.
Use the globalization flexfield in the Customers window to enter additional information for your customers related to tax calculation, billing, and bank transfers. After you define standard profile classes, you can assign classes to your customers and addresses.
You can also update specific information for the customer or address, including the bank transfer parameters that you defined in the Customer Profile Class window.
Before you can use the Customers window, you must:
Define lookup codes (contributor type)
Define customer profile classes
Define receipt classes
Complete the setup at the customer level using the Party Tax Profile page in Oracle E-Business Tax.
To enter bank transfer information:
Navigate to the Customers window.
Enter a customer.
Navigate to the Document Printing region.
Navigate to the globalization flexfield.
In the Remittance Protest Instructions field, enter Yes if you want Oracle Receivables to remit protest instructions to the bank for collection documents that belong to the customer. Enter No if you do not.
In the Remittance Interest Instructions field, enter Yes if you want Oracle Receivables to remit interest instructions to the bank for collection documents that belong to the customer. Enter No if you do not.
Press the OK button.
To enter tax information:
Navigate to the Customers window.
Query or enter a customer.
Note: The application displays the customer details that you have set up in E-Business Tax.
Navigate to the Customer Addresses region.
Press the New button for a new address or the Open button for an existing address.
The Customer Addresses window appears.
Navigate to the globalization flexfield.
Enter the contributor class that defines the customer's tax contribution in the Contributor Class field.
Press the OK button.
To enter billing information:
Navigate to the Customers window.
Query or enter a customer.
Navigate to the Addresses region.
Press the New button for a new address or the Open button for an existing address.
Navigate to the globalization flexfield.
In the Inscription Type field, enter one of these codes:
CNPJ- company is a legal entity
CPF- company is a person (physical entity)
Others- other types of inscription numbers
If the Inscription Type is CNPJ, enter the company's main inscription number in the Inscription Number field.
Enter the inscription number for a company branch in the Inscription Branch field. If the Inscription Type is CPF, 0000 appears in this field.
In the Inscription Digit field, enter the control digit used to validate CNPJ and CPF types.
In the State Inscription field, enter the company registration number for the state.
In the Municipal Inscription field, enter the company registration number for the city.
Press the OK button.
Use the globalization flexfield in the Receipt Classes window to define the collection method for a receipt class.
To enter bank transfer information:
Navigate to the Receipt Classes window.
Enter the receipt class.
Navigate to the globalization flexfield.
Enter the collection method for this receipt class:
Collection Remittance Batch - if you want to use this receipt class for bank collection
Factoring Remittance Batch - if you want to use this receipt class for bank factoring
Manual Receipt - if you want to use this receipt class for manual receipt collection
Press the OK button.
Use the globalization flexfields in the Banks and Bank Accounts windows to define bank transfer information for remittance banks.
Before you can use the Banks and Bank Accounts windows, you must define Automatic Receipt Programs to define the bank transfer reports and files.
To enter bank transfer information:
Navigate to the Banks window.
Enter the bank and branch.
Navigate to the globalization flexfield.
Enter the maximum number of collection documents for a bank transfer remittance batch for this bank branch.
Press the OK button.
Navigate to the Bank Accounts window by pressing the Accounts button.
Enter the account number.
Navigate to the globalization flexfield.
Enter the report media (File or Report) and the report name used for your Collection Remittance, Factoring Remittance, and Occurrence Remittance batches for this account.
In the Company Code for Bank field, enter your company code assigned by the bank.
Press the OK button.
Use the globalization flexfield in the Remit-To Addresses window to enter your company name.
Your company name appears in the transaction records in the bank remittance batch electronic file. The company name is also used to validate the transaction records in the bank return file.
Before you can use the Remit-To Addresses window, you must:
Define company information
Define system options
To enter bank transfer information:
Navigate to the Remit-To Addresses window.
Navigate to the globalization flexfield.
Enter your company's name.
Press the OK button.
Use the globalization flexfield in the Transaction Types window to determine bank transfer, tax, and billing default information for your transaction entries.
Before you can use the Transaction Types window, you must:
Define lookup codes
Define tax codes and rates
Define operation fiscal codes
Define Latin tax groups
To enter bank transfer information:
Navigate to the Transaction Types window.
Navigate to the globalization flexfield.
Enter the document type in the Document Type field.
The document type is one of the required fields to format the bank remittance batch file. Each collection document sent to the bank requires a document type.
Press the OK button.
To enter tax information:
Navigate to the Transaction Types window.
Navigate to the globalization flexfield.
Enter the Latin tax group or tax code in the Tax Code field to define the tax categories and tax rates to apply to transactions.
Press the OK button.
To enter billing information:
Navigate to the Transaction Types window.
Navigate to the globalization flexfield.
Enter the operation type in the Operation Type field that identifies the purpose of the shipping invoice.
Enter the operation fiscal code in the Operation Fiscal Code field that identifies the operation type.
Press the OK button.
Use the globalization flexfield in the Transaction Sources window to define an import batch source for billing purposes. The import batch source lets you apply the same invoice number series to both manual and imported invoices.
Define the import batch sources for invoices with a batch source type. When you assign the import batch source, invoices that are entered manually with the invoice batch source follow the same invoice number sequence as the imported invoice batch source.
Before you can use the Transaction Sources window, you must define an Invoice Batch Source.
To enter billing information:
Use this procedure for manual invoice batch sources only.
Navigate to the Transaction Sources window.
Enter the invoice batch source information.
Enter Manual in the Type field.
Navigate to the globalization flexfield.
Enter an imported batch source in the Invoice Sub-Series field.
Enter the company's name in the Company Name field.
Press the OK button.
Use the Organization window to define the location for your organization for tax calculation and billing.
Before you can use the Organization window, you must define locations in the Location window.
To enter a location for your organization:
Navigate to the Organization window.
Enter the location in the first region.
Save your work.
Use the globalization flexfield in the Location window to enter information used to calculate tax for the ship from location. You specify the ship from address in the Location window.
Before you can use the Location window, you must:
Define the organization classes and states in the Lookup Codes window
Enter tax codes and rates in the Tax Codes and Rates window
Define Latin tax groups in the Latin Tax Groups window
To enter fiscal information:
Navigate to the Location window.
Navigate to the globalization flexfield.
In the Organization Tax Class field, enter the company fiscal definition for this organization.
Enter the Latin tax group or tax code in the Tax Code field to define the tax categories and tax rates to apply to transactions with this organization.
Save your work.
To enter billing information:
Navigate to the Location window.
Navigate to the globalization flexfield.
Enter the product brand name that will be printed in the shipping invoice.
Save your work.
Use the Standard Memo Lines window to enter billing and tax information for each standard memo line.
Before you can use the Standard Memo Lines window, you must:
Define lookup codes (transaction nature)
Define Latin fiscal classification codes
Define Latin tax groups
Define tax codes and rates
To enter tax information:
Navigate to the Standard Memo Lines window.
Query the memo line that you want.
In the Tax Product Category field, enter the fiscal classification code to be applied to transactions using this memo line.
Press the OK button.
To enter billing information:
Navigate to the Standard Memo Lines window.
Query the memo line that you want.
Enter the values that are used by the fiscal books in the corresponding fields:
A federal tributary situation, such as IPI exempt or taxable national product
A state tributary situation, such as ICMS exempt or ICMS taxation deferred
Item origin
Item fiscal type
Use the globalization flexfield in the Freight Carrier window to define information for your freight carriers. This information is printed on shipping invoices.
Before you can use the Freight Carrier window, you must define lookup codes.
To enter billing information:
Navigate to the Freight Carrier window.
Enter or query the freight carrier you want.
Navigate to the globalization flexfield.
Enter the freight carrier's address in the Address field.
Enter the freight carrier's city in the City field.
Enter the freight carrier's state in the State field.
In the Inscription Type field, enter one of these codes:
CNPJ - freight carrier is a legal entity
CPF - freight carrier is a person (physical entity)
Others - other types of inscription numbers
If the Inscription Type is CNPJ, enter the freight carrier's main inscription number in the Inscription Number field.
Enter the inscription number for a branch of the freight carrier in the Inscription Branch field. If the Inscription Type is CPF, 0000 appears in this field.
In the Inscription Digit field, enter the control digit that validate CNPJ and CPF types.
In the Inscription Number field, enter the freight carrier's federal registration number.
In the State Inscription field, enter the freight carrier's state inscription number.
Press the OK button.
Use the globalization flexfield in the Tax Codes and Rates window to add tax categories to your tax codes and associated rates, and also to define printing options for each tax code.
Before you can use the Tax Codes and Rates window, you must define Latin tax categories.
To enter tax and rate information:
Navigate to the Tax Codes and Rates window.
Query the tax code that you want.
Navigate to the globalization flexfield.
Enter the Latin tax category in the Tax Category field to associate with this tax code.
Inclusive Tax information is defaulted from the Latin tax category. You cannot change this information at this level. The Allow Inclusive Override check box is always unchecked and cannot be changed.
In the Print Tax Line field, enter Yes if you want the designated tax line with this tax code to appear on your invoices. Enter No if you do not.
In the Legal Message Exception Event field, enter the legal message exception event to use with this tax code.
Press the OK button.
Use the Global Receipt Method Accounts window to define additional accounting parameters. You define these parameters for receipt entries and receipt applications for payment methods and remittance bank accounts that are used in the bank collection process.
Before you can use the Global Receipt Method Accounts window, you must:
Define banks, branches, and accounts
Define Bank Instruction Codes
Define receipt Classes
Define payment methods with remittance banks assigned to them
Define receipt batch sources
Define Receivables activities to create default accounting information for each adjustment type
To define global receipt method accounts:
Navigate to the Global Receipt Method Accounts window.
Select the applicable operating unit.
Enter a payment method in the Payment Method field. The Receipt Class and Collection Method fields are populated according to the payment method.
Enter the name of the bank in the Bank Name field.
Enter the account number in the Account Number field.
Enter the account number for bank charges in the Bank Charges field.
Enter the endorsement account number in the Collection Endorsement field.
Enter the Bills under Collection account number in the Bills under Collection field.
If the collection method is factoring remittance batch, enter the account numbers of factoring documents in the Factoring Documents field and the factoring interest in the Factoring Interest field.
Navigate to the Additional Accounts tabbed region to update additional accounts for this payment method and account.
In the Adjustment Activity column, enter the adjustment activity for each of the additional accounts.
Oracle Receivables displays the default account number in the Account column. You can change the account number if you want.
Navigate to the Business Rules tabbed region to define rules for this payment method and account.
Enter the portfolio code assigned by the bank in the Portfolio Code field.
Enter the appropriate ranges for this payment method and account:
Enter the range of collection document amounts in the Document Amounts fields
Enter the range of totals for bank transfer remittance batches in the Remittance Amounts fields
These ranges are used as default values when bank transfer remittance batches are created.
In the Instruction Code fields, enter the default bank instruction codes that are sent to the bank with each collection document using this payment method and account.
Enter the default bank charge per collection document in the Bank Charges Amount field.
If the collection method is factoring remittance batch, enter the discounted rate of sale to the bank. Enter a percentage in the Factoring Rate field and the number of days for which this percentage is defined in the Factoring Period field.
Enter the receipt batch source in the Batch Source field.
If the collection method is collection remittance batch or manual receipt collection, enter the write-off tolerance. Enter either a percentage in the Write-off % field or an amount in the Write-off Amt field.
Oracle Receivables uses the Write-off % and Write-off Amt fields to determine the difference between calculated and received interest. If the difference exceeds the limit that you enter, the interest adjustment needs further approval.
Enter the deposit date in the GL Date for Bank Return field, if the deposit is not going to be made in your company's account on the receipt date.
The value in the Bank Floating field represents the number of days after the receipt day when the calculated amount is deposited in your company's account.
Navigate to the Others tabbed region and record applicable information.
Use the globalization flexfield in the Master Item window to enter tax and billing information.
Before you can use the Master Item window, you must:
Define lookup codes (transaction nature) in the Lookup Codes window
Define Latin fiscal classification codes
Define Latin tax groups
Define tax codes and rates
To enter tax information :
Navigate to the Master Item window.
Query the item that you want.
Click in the flexfield and select the applicable item category to apply to transactions using this item.
Press the OK button.
To enter billing information:
Navigate to the Master Item window.
Query the item that you want.
Enter values used by the fiscal books in the corresponding fields:
A federal tributary situation, such as IPI exempt or taxable national product
A state tributary situation, such as ICMS exempt or ICMS taxation deferred
Item origin
Item fiscal type
Press the OK button.
Use the Bank Occurrence Codes window to define occurrence codes for remittance banks and associate these codes with the Oracle Receivables pre-defined occurrence codes.
Before you can use the Bank Occurrence Codes window, you must define bank branches.
To define a bank occurrence code for a remittance bank:
Navigate to the Trade Notes window.
Query the bank that you want to define occurrences for in the Find Trade Notes window. Press the Occurrences button.
The Bank Occurrence Codes window appears.
Enter Remittance or Return in the Type field.
Enter the new occurrence code in the Code field.
Enter a description of the occurrence code in the Description field.
Enter the pre-defined occurrence code to associate with this occurrence code in the Standard Occurrence field.
Enter File or Report in the Media field to indicate the format for sending reports to the bank (electronic file or paper report). Use this field only if the entry in the Type field is Remittance.
In the Limit Days field, enter a number that defines the limit of the difference between the collection document due date and the occurrence remittance date.
When an occurrence remittance batch is formatted, Oracle Receivables compares the difference between the due date and the remittance date. If this difference is less than the Limit Days, a paper report is generated.
Save your work.
Use the Bank Instruction Codes window to define instruction codes for remittance banks and associate these codes with the Oracle Receivables pre-defined bank instruction codes.
Before you can use the Bank Instruction Codes window, you must define bank branches.
To define a bank instruction code for a remittance bank:
Navigate to the Bank Instruction Codes window.
Query the bank that you want to define instructions for in the Find Bank window.
Enter the new instruction code in the Code field.
Enter a description of the instruction code in the Description field.
Enter the pre-defined bank instruction code in the Type field to associate with this instruction code.
In the Number of Days to Protest/Write-Off field, enter the number of days that are allowed to protest/write-off for this instruction code. Use this field only if the entry in the Type field is Protest After Due Date or Write Off After Due Date.
Save your work.
Use the Latin Tax Categories window to create Latin tax categories that define specific characteristics of each tax calculated by the Latin Tax Group.
Before you can use the Latin Tax Categories window, you must define tax codes.
To define a Latin tax category:
Navigate to the Latin Tax Categories window.
Enter a tax category in the Category field.
Enter the effective dates for this tax category. The tax category is effective within the range that you specify.
In the Threshold Check Level field, enter one of the following:
Line – Consider the current invoice line for threshold checking.
Document – Consider the current invoice for threshold checking.
Operation – Consider the current invoice and its related debit memos, credit memos, and related invoices for threshold checking.
In the Grouping Condition Type field, enter one of the following:
Line – Use the current invoice line amount as the base amount for threshold checking.
Document – Use the sum of all amounts of relevant lines as the base amount for threshold checking. For use with the values Document or Operation in the Threshold Check Level field.
Transaction Condition – Use the sum of all amounts of relevant lines as the base amount for threshold checking. For use with the values Document or Operation in the Threshold Check Level field.
If you entered Transaction Condition in the Grouping Condition Type field, enter the transaction condition to group by in the Grouping Condition field.
Select a tax code in the Tax Code field after you define tax codes and rates from a list of values, if you want to use a default tax code for this tax category.
Note: You only perform this step after you define tax codes and rates. See: Defining Tax Codes and Rates for more information. You must also define a tax rule that looks for the tax code in the tax category. See: Defining Latin Tax Rules for more information.
In the Min Amount, Min Taxable Basis, and Minimum % fields, enter the appropriate values to use with this tax.
This table shows how Receivables uses the values in these fields:
| Field Name | Tax Does Not Apply If... |
|---|---|
| Min Amount | Tax calculated is less than this value |
| Min Taxable Basis | Taxable base is less than this value |
| Minimum % | Tax rate is less than this value |
Check the Inclusive Tax check box if you want tax included in the price at invoice line level. Leave the check box unchecked if you do not.
Note: You cannot change the Inclusive Tax setting after you associate the tax category with a tax code or a tax group.
Check the Mandatory in Class check box if you want the tax category to appear in every tax condition class.
Check the Tributary Substitution check box if you want to define this tax category for Tributary Substitution. Leave the check box unchecked if you do not. If you check the check box, you must enter a Latin tax category in the Tax Category to Compound Base field.
Enter a Latin tax category in the Tax Category to Compound Base field, if you want another tax category to compound the tax base amount.
Check the Print check box if you want the tax line printed. Leave the check box unchecked if you do not.
Save your work.
Use the Associate Latin Tax Legal Messages window or Legal Messages window to associate legal messages with Latin tax rules. You associate a legal message, which you created in the Standard Messages window, with a combination of tax rule, tax exception, and rule data.
Legal messages are fiscal messages on invoices that explain the reason why a lower tax rate is applied to an invoice line for various exceptions.
Use the Latin Tax Groups window to associate tax categories to a tax group. A Latin tax group lets you apply a group of taxes to transactions, when the taxable amounts are known.
A Latin tax group shows the taxes that are included in a specific group, the order of application of each of the taxes, particular attributes related to the specific group, and attributes that help define how many taxes of the group to apply.
You can use a Latin tax group as a tax code in these windows: System Options, Customers, Item, Organizations, and Memo Lines.
Before you can use the Latin Tax Groups window, you must:
Define lookup codes for contributor type, organization class, and transaction nature
Define Tax Codes
Define Latin Tax Categories
To define a Latin tax group:
Navigate to the Latin Tax Groups window.
Enter the code for this Latin tax group in the Tax Group field.
Enter a description of this tax group in the Description field.
Enter a tax category to associate with this tax group in the Tax Category field.
The tax category you enter populates the record with default information. You can change the information in these fields.
Enter a contributor type to associate with this tax group in the Contributor Type field.
Enter the transaction nature to apply to this tax group in the Transaction Nature field.
Enter the effective dates for this tax group. For a given combination, the default start date is the current date, and the default end date is 31 December 4712.
To prevent overlapping effective dates, when you enter a new end date, the next start date defaults to the following day. You cannot change the next start date to an earlier date than the previous end date. In addition, you cannot change the start and end dates of existing records, except for the last record for a given combination.
Use the Tax Code field to enter an optional tax code, if you want to use a tax code as the default for this tax category.
Check the Tributary Substitution check box if you want to define this tax group for Tributary Substitution. Leave the check box unchecked if you do not. If you check the check box, you must enter a value in the Tax Category to Compound Base field.
Enter the Latin tax category in the Tax Category to Compound Base field that you want to use to compound the base tax rate.
In the Minimum Amount field, enter the minimum tax amount to apply to the tax.
In the Minimum Percent field, enter the minimum tax percentage used to calculate tax.
Use the Latin Locations window to associate tax categories with specific shipment combinations and to assign tax codes to the combination. You can define the tributary substitution state inscription for specific ship from and ship to combinations.
Before you can use the Latin Locations window, you must:
Define lookup codes (state)
Define tax codes
Define Latin tax categories
Define a sales tax location flexfield structure in the System Options window
To define a Latin tax location:
Navigate to the Latin Locations window.
In the Ship From Code field, enter the state where the item or service is sold.
In the Ship To Code field, enter the destination state.
Enter the tax category to associate with this shipping combination in the Tax Category field.
Enter the effective dates for this combination. For a given combination, the default start date is the current date, and the default end date is 31 Dec 4712.
To prevent overlapping effective dates, when you enter a new end date, the next start date defaults to the following day. You cannot change the next start date to an earlier date than the previous end date. In addition, you cannot change the start and end dates of existing records, except for the last record for a given combination.
In the Tax Code field, enter the tax code that you want to use to define the tax rate for this combination.
If the tax category you chose was Tributary Substitution State Inscription, enter your Tributary Substitution State Inscription number in the appropriate field. You must have previously defined a specific tax code for this tax category.
Save your work.
Use the Latin Fiscal Classifications window to define fiscal classifications for specific items and associate them with tax categories. Each item that you enter on an invoice requires a fiscal classification.
Before you can use the Latin Fiscal Classifications window, you must:
Define tax codes
Define Latin tax categories
To define a Latin fiscal classification code:
Navigate to the Latin Fiscal Classifications window.
In the Fiscal Classifications Code field, enter the code for this fiscal classification.
In the Displayed Value field, enter the way you want this fiscal classification to be displayed in the list of values.
Enter a description of this fiscal classification in the Description field.
Enter the tax category to associate with this fiscal classification in the Tax Category field.
Enter the effective dates for this fiscal classification. For a given combination, the default start date is the current date, and the default end date is 31 Dec 4712.
To prevent overlapping effective dates, when you enter a new end date, the next start date defaults to the following day. You cannot change the next start date to an earlier date than the previous end date. In addition, you cannot change the start and end dates of existing records, except for the last record for a given combination.
In the Tax Code field, enter the tax code that you want to use to define the tax rate for this fiscal classification and tax category combination.
In the Base Rate field, enter the rate amount that is used to modify the base amount. You can enter negative amounts.
Save your work.
Use the Latin Tax Exceptions By Fiscal Classification window to define tax exceptions for shipment location combinations by fiscal classification code.
Before you can use the Latin Tax Exceptions By Fiscal Classification window, you must:
Define lookup codes (state)
Define tax codes
Define Latin tax categories
Define Latin fiscal classification codes
Define a sales tax location flexfield structure in the System Options window
To define a Latin tax exception for a fiscal classification code:
Navigate to the Latin Tax Exceptions By Fiscal Classification window.
In the Shipment Locations From field, enter the state where the item or service is sold.
In the Shipment Locations To field, enter the destination state.
Enter the fiscal classification code to apply to this exception in the Fiscal Classification Code field.
Enter the tax category to associate with this exception in the Tax Category field.
In the Base Rate field, enter the rate amount that is used to modify the base amount. You can enter a negative amount.
Enter the effective dates for this exception. For a given combination, the default start date is the current date, and the default end date is 31 Dec 4712.
To prevent overlapping effective dates, when you enter a new end date, the next start date defaults to the following day. You cannot change the next start date to an earlier date than the previous end date. In addition, you cannot change the start and end dates of existing records, except for the last record for a given combination.
In the Tax Code field, enter the tax code that you want to use to define the tax rate for this exception.
Save your work.
Use the Latin Tax Exceptions by Items window to define tax exceptions for specific items in a specific shipment location combination.
Before you can use the Latin Tax Exceptions by Items window, you must:
Define lookup codes (state)
Define tax codes
Define items
Define Latin tax categories
Define a sales tax location flexfield structure in the System Options window
To define a Latin tax exception for an item:
Navigate to the Latin Tax Exceptions by Items window.
In the Ship Location From field, enter the state where the item or service is sold.
In the Ship Location To field, enter the destination state.
In the Warehouse field, select the warehouse that you want to associate with the item for this exception.
In the Item Description field, enter the item that you want to apply an exception to.
Enter the Latin tax category to apply to this exception in the Tax Category field.
In the Base Rate field, enter the rate amount that is used to modify the base amount. You can enter a negative amount.
Enter the effective dates for this exception. For a given combination, the default start date is the current date, and the default end date is 31 D 4712.
To prevent overlapping effective dates, when you enter a new end date, the next start date defaults to the following day. You cannot change the next start date to an earlier date than the previous end date. In addition, you cannot change the start and end dates of existing records, except for the last record for a given combination.
In the Tax Code field, enter the tax code that you want to use to define the tax rate for this exception.
Save your work.
Use the Tax Rules window to define the hierarchy for applying tax codes to a transaction line. When searching to apply a tax to a transaction line, Oracle Receivables looks at the first rule in the hierarchy for the particular combination of tax category, contributor type, and transaction type. If this rule does not apply, Oracle Receivables looks at the second rule, and so on until it finds the correct rule to apply.
You can define two types of hierarchy:
For Rule Level = Base, define a hierarchy to search for tax rates to apply to the tax base amount
For Rule Level = Rate, define a hierarchy to search for tax codes to apply to the transaction taxable amount
You can define as many rules as you want for the tax.
Before you can use the Tax Rules window, you must:
Define lookup codes (Contributor type)
Define tax codes
Define Latin tax categories
Define transaction types
To define Latin tax rules:
Navigate to the Tax Rules window.
Enter a tax category in the Category field.
Enter the contributor type to use with this tax category in the Contributor Type field.
Enter the transaction type to use with this tax category in the Transaction Type field.
In the Rule Level field, enter Base or Rate to define whether this rule applies to the base or rate amount.
In the Priority field, enter the that this rule is applied. The default order is sequential.
Enter the name of the rule in the Rule field. Oracle Receivables looks at this rule to apply tax to transactions that have this combination of tax category, transaction type, and contributor type.
Save your work.
Note: You can define default hierarchies independent of tax categories if you enter DEFAULT in the Contributor Type field and enter the same transaction type that is in the System Options window in the Transaction Type field. If you do not define specific rules for finding the tax rates, Receivables uses the hierarchy for tax rules.
This section describes how to enter interest, tax, billing, and bank transfer information for invoices by using globalization flexfields in the Transaction window and Transaction Summary window. This section also explains how to correct and cancel existing invoices.
Use the globalization flexfield in the Transactions window to enter additional invoice information. You can enter interest, tax, bank transfer, and billing information for the invoices. You can also use the globalization flexfield for invoice installments to enter bank transfer information.
Before you can use the Transaction window, you must:
Define ship from states, the organization class (establishment type) for calculating tax, and billing attributes for shipping invoices in the Organization window
Define tax and billing attributes in the System Options window
Define tax categories in the Latin Tax Categories window
Define tax code Create tax groups in the Latin Tax Groups windows and rates in the Tax Codes and Rates window
Define invoice batch sources and a subseries in the Invoice Batch Sources window
Define a tax group and an operation fiscal code in the Transaction Types window
Define a freight carrier in the Freight Carriers window
Define memo lines in the Standard Memo Lines window
Define master items in the Master Items window
Define billing attributes for customers in the Customers window
Define a Tributary Substitute inscription for your company in each state in the Latin Locations window
Define Latin legal messages in the Legal Messages window
Define your master inventory organization in the Order Management Parameters window
Related Topics
Entering Transactions, Oracle Receivables User Guide
To enter interest information:
Navigate to the Transactions window.
Enter a bill to customer in the Bill To region.
Navigate to the globalization flexfield.
Note: The interest default parameters for a customer that you defined in the Customer Profile Classes window appear in the globalization flexfield.
In the Interest Type field, enter or modify an interest type (Rate or Amount) for calculating the interest amount.
In the Interest Rate/Amount field, enter or modify a rate or amount.
In the Interest Period field, enter or modify the number of days in the period for the interest charge.
In the Interest Formula field, enter or modify a Simple or Compound interest formula.
In the Grace Days field, enter or modify the number of days that customers can be overdue before interest is charged.
In the Penalty Type field, enter or modify a penalty type (Rate or Amount) if you want to charge a penalty amount to your customers.
In the Penalty Rate/Amount field, enter or modify a penalty rate or amount.
Press the OK button.
Navigate to the Transactions window.
Enter or query invoices.
Press the Line Items button.
The Lines window appears.
Enter an item, a description, or both in the Item and Description fields.
Choose the More tabbed region.
If the invoice line is an item line, enter the warehouse name in the Warehouse Name field to define an item validation organization for your ship from location.
Note: If you selected Latin Tax Handling as your tax method in the System Options window, the Warehouse Name field is mandatory only if the invoice line is an item line.
Navigate to the globalization flexfield.
When you open the globalization flexfield, the Latin Tax Engine populates the fields with the default fiscal classification code and transaction condition class. These attributes are defaulted from the master inventory organization's item definition. You define the master inventory organization in the Order Management Parameters window.
For more information about entering fiscal information for inventory items, see Defining Master Items
You can accept the default fiscal classification code and transaction condition class for the invoice line by pressing the OK button, or you can replace the defaults with other valid values.
You can also accept the default values that appear in the Operation Fiscal Code, Item Origin, Item Fiscal Type, Federal Tributary Situation, and State Tributary Situation fields. Or, after entering the global flexfield, you can replace the defaults with other valid values.
Note: Do not enter information in the remaining fields.
Press the OK button.
Press the Tax button in the Lines window.
The Tax window appears.
Navigate to the globalization flexfield.
Enter legal justification messages for taxes in the Legal Justification Messages fields.
Enter a tax base amount in the Tax Base Amount field.
Enter a tax base rate in the Tax Base Rate field.
Press the OK button.
Note: When entering credit transactions, setting up recurring invoices, or using the Copy and Void Invoices process, the Warehouse Name field on the original invoice lines is mandatory only if the invoice line is an item line and you selected Latin Tax Handling as your tax method in the System Options window.
Related Topics
Defining Order Management System Parameters, Oracle Order Management Implementation Guide
Navigate to the Transactions window.
Enter or query invoices.
Press the Freight button.
The Freight window appears.
Enter the freight name in the Carrier field.
Enter a freight responsibility (CIF/FOB) in the FOB field.
Close the window.
In the Transactions window, navigate to the globalization flexfield.
In the Freight Accessory Expenses, Insurance Accessory Expenses, and Other Accessory Expenses fields, enter amounts for freight, insurance, and other expenses.
In the License Plate field, enter a license plate number for the freight carrier.
In the Volume Quantity, Volume Type, and Volume Number fields, enter volume information for the invoice item.
In the Total Gross Weight and Total Net Weight fields, enter weight information for the invoice item.
Press the OK button.
Press the Line Items button in the Transactions window.
The Lines window appears.
Enter an item, description, or a standard memo line.
Choose the More tabbed region.
Navigate to the globalization flexfield.
Note: The parameters for a standard memo line that you have defined in the Standard Memo Lines window and the parameters for an item that you have defined in the Master Items window default to the globalization flexfield.
In the Item Origin and Item Fiscal Type fields, enter or modify the origin and fiscal type for an item.
In the Federal Tributary Situation and State Tributary Situation fields, enter or modify the tributary situations.
Enter or modify the operation fiscal code in the Operation Fiscal Code field.
Press the OK button.
Save your work.
Check the Complete check box in the header of the Transactions window after you enter an invoice. After you check the Complete check box, these actions occur:
A new number overrides your temporary invoice number that you entered in the Transactions window. This number is the next number in the subseries sequence that is assigned to the invoice's batch source.
The invoice automatically prints if the value in the Print Immediately field in the System Options window is Yes.
To enter bank transfer information:
Navigate to the Transactions Summary window.
Query or enter invoices.
Press the Installments button.
The Installments window appears. Installments are created only for completed invoices.
Navigate to the globalization flexfield.
You can optionally change the default value in the Payment Method field. The payment method defaults from the payment method for the transaction. The bearer of the trade note defaults to Manual Receipt the first time that you enter an invoice. After you have entered the invoice and saved it, you can change the bearer of the trade note to Registry or Legal Department. The value, Manual Receipt, is automatically changed to Bank when you send a collection document to the bank.
These fields are display only. You cannot change them.
Document Status
Bank Transfer Batch Number
Selection Number of Bank Transfer Batch
Press the OK button.
Use the Complementary Invoices window to correct some fields in an existing invoice for billing purposes. You enter the correct information in a new invoice.
To correct invoices:
Navigate to the Complementary Invoices window.
Enter the number, date, or due date of an existing invoice in the header region to query an invoice.
Choose the Complementary Invoice and More tabbed regions to correct any fields that are in the header region of an invoice.
Choose the Line tabbed region to correct any fields that are in the lines region of an invoice. You must enter a line number in the Line Number field.
Save your work. The invoice automatically prints if the value in the Print Immediately field in the System Options window is Yes.
Note: The transaction number for the complementary invoice is defined only when the invoice prints.
Use the Credit Memo window to cancel an existing invoice. You create credit memos in the Credit Memo window to credit invoices, debit memos, and chargebacks.
Before you can use the Credit Memo window, you must:
Define a transaction type for your credit memo in the Transaction Types window. Choose Void in the Transaction Status field in the Transaction Types window.
Set the profile option AR: Use Invoice Accounting for Credit Memos to reverse the accounting entries when a credit memo is credited for an invoice.
To cancel invoices:
Navigate to the Credit Memo window.
Enter the number for the invoice you want to cancel in the Number field in the Credited Transaction region.
Enter credit information in the Credit Memo region. You must enter the previously defined transaction type for your credit memo in the Type field.
Related Topics
Accounting for Transactions, Oracle Receivables User Guide
This section describes how to automatically and manually create and format remittance batches with trade notes and occurrences, how to enter bank occurrences, as well as how to enter, import, and correct bank return information into Receivables. You can post bank returns in Receivables and transfer journal entries to General Ledger.
Use the Bank Transfer Remittance Batches window to automatically create remittance batches with trade notes for bank collection. You can also manually create remittance batches with trade notes for bank collection or factoring. You can modify both types of batches after you save them.
Before you can use the Bank Transfer Remittance Batches window, you must:
Define bank instruction codes in the Bank Instruction Codes window
Define bank occurrence codes for remittance occurrences in the Bank Occurrence Codes window
Define transaction types in the Transaction Types window
Define additional accounts and other default information to generate the remittance batches for payment methods in the Global Receipt Method Accounts window
Enter transactions
To automatically create bank transfer remittance batches:
Navigate to the Bank Transfer Remittance Batches window.
Select the applicable operating unit.
Enter a batch name in the Name field.
A remittance batch number automatically appears in the Number field after you complete all steps and save.
Change the date in the Date field if you want to assign a different date to the remittance batch.
Choose Automatic in the Type field.
Enter a payment method from the Global Receipt Method Accounts window in the Payment Method field.
Enter the attributes for the trade notes that you want to include in the remittance batch, or leave the fields blank for all. You enter ranges in the Due Date, Transaction Date, Transaction Number, and Customer Number fields. Enter a transaction type in the Transaction Type field.
Check the Break by Due Date check box if you want trade notes with the same due date in a remittance batch.
Press the Bank Distributions button.
The Bank Account Distributions window appears.
Enter account information in the Bank Number, Bank Name, Branch Number, Branch Name, and Account Number fields. You can change the General Ledger date (accounting date) and portfolio code that automatically displays.
Note: You must enter a branch number to enter an account number.
Choose the Distribution Rules tabbed region.
Enter a percentage of the total dollar amount of the trade notes that you want in the batches for a bank account in the Percent (%) field, or enter a range of trade note amounts, remittance batch amounts, or both, in the Minimum and Maximum fields.
Choose the More tabbed region to enter a bank charge amount, bank instructions, and a remittance batch source for a bank account.
Save your work.
Select a bank account.
Press the Remittance Batches button to view all remittance batches and trade notes in each batch. They appear in the Bank Remittance Batches window after the Create Collection Remittance Batch program is done.
Choose the Trade Note, Payment Method, and More tabbed regions to view information about the trade notes.
Use the Format Remittance Batches window to format and send the remittance batches to the bank.
The Status Field table shows the meaning of statuses in the Bank Transfer Remittance Batches and Bank Remittance Batches windows.
| In this window… | This status… | Has this meaning… |
|---|---|---|
| Bank Transfer Remittance Batches | Selected | The selection is created |
| Bank Transfer Remittance Batches | Formatted | One or more remittance batches in the selection are formatted |
| Bank Transfer Remittance Batches | Canceled | All remittance batches in the selection are canceled |
| Bank Transfer Remittance Batches | Confirmed | The bank confirmed one or more trade notes in the selection |
| Bank Remittance Batches (Header) | Selected | Trade notes are selected to create this remittance batch |
| Bank Remittance Batches (Header) | Formatted | The remittance batch is formatted |
| Bank Remittance Batches (Header) | Canceled | The remittance batch is canceled |
| Bank Remittance Batches (Header) | Confirmed | The bank confirmed one or more documents in the remittance batch |
| Bank Remittance Batches (Header) | Write-off | The bank wrote-off all documents that are not refused in this remittance batch |
| Bank Remittance Batches (Header) | Refused | The bank refused all documents in the batch |
| Bank Remittance Batches (Header) | Partially Received | One or more documents in the remittance batch are partially paid |
| Bank Remittance Batches (Header) | Totally Received | All documents in the remittance batch that are not refused, not canceled, and not written-off are fully paid |
| Bank Remittance Batches (Trade Notes region) | Selected | The trade note is selected for a remittance batch |
| Bank Remittance Batches (Trade Notes region) | Formatted | The trade note is formatted |
| Bank Remittance Batches (Trade Notes region) | Canceled | The trade note is canceled |
| Bank Remittance Batches (Trade Notes region) | Confirmed | The bank confirmed the document |
| Bank Remittance Batches (Trade Notes region) | Refused | The bank refused the document |
| Bank Remittance Batches (Trade Notes region) | Written-off | The bank wrote off the document |
| Bank Remittance Batches (Trade Notes region) | Protested | The document is protested |
| Bank Remittance Batches (Trade Notes region) | Partially Received | The document is partially paid |
| Bank Remittance Batches (Trade Notes region) | Totally Received | The document is fully paid |
To manually create bank transfer remittance batches:
Navigate to the Bank Transfer Remittance Batches window.
Enter a batch name in the Name field.
A remittance batch number automatically appears in the Number field after you complete all the steps and save.
Change the date in the Date field if you want to assign a different date to the remittance batch. See the Status Field Table for possible statuses in the Status field.
Choose Manual in the Type field.
Enter either Collection or Factoring in the Remittance Batch Type field to create collection or factoring batches.
Enter the attributes for the trade notes that you want to include in the remittance batch, or leave them blank for all. You enter ranges in the Due Date, Transaction Date, Transaction Number, Customer Number, and Transaction Amount fields. Enter a transaction type in the Transaction Type fields.
Press the Bank Distributions button.
The Bank Account Distributions window appears.
Enter the account information in the Bank Number, Bank Name, Branch Number, Branch Name, and Account Number fields. You can change the General Ledger date (accounting date) that automatically displays.
Note: You must enter a branch number to enter an account number.
Select a bank account.
Press the Remittance Batches button.
Enter a trade note number in the Trade Note Number field.
The amount, due date, transaction number, and status display.
Choose the Payment Method tabbed region.
Enter a payment method in the Payment Method field.
The batch source displays. You can change the portfolio code that displays for a collection remittance batch. You can enter a portfolio code for a factoring remittance batch.
Choose the More tabbed region if you are creating a collection remittance batch. You can change any bank instructions that display.
You can optionally enter a bank charge amount in the Bank Charge Amount field.
Choose the Factoring tabbed region if you are creating a factoring remittance batch. Enter a factoring rate, period of days for the rate, and a factoring date.
Save your work.
Use the Format Remittance Batches window to format and send remittance batches to the banks.
Navigate to the Bank Transfer Remittance Batches window. You cannot make any changes in this window.
Press the Bank Distributions button.
The Bank Account Distributions window appears.
You can change only the General Ledger date (the accounting date) if the selection type is Automatic and the status in the Bank Transfer Remittance Batches window is Selected. You can change the General Ledger date and add bank accounts to create more remittance batches if the selection type is Manual and the status in the Bank Transfer Remittance Batches window is Selected.
Select a bank account.
Press the Remittance Batches button to modify remittance batches.
The Bank Remittance Batches window appears.
Uncheck the Selected check box next to a trade note to remove it from the batch.
Enter a trade note number and its attributes in the tabbed regions to add a trade note to the batch. The batch must be unformatted (status in header region is Selected).
You can change this information for any unformatted trade notes in a remittance batch:
The portfolio code, bank charge amount, and bank instructions for a trade note in a collection remittance batch
The portfolio code, factoring rate, factoring date, and period of days for a trade note in a factoring remittance batch
The payment method for a trade note in a manually created remittance batch, if the selection type in the Bank Transfer Remittance Batches window is Manual
Use the Format Remittance Batches window to format bank transfer or occurrence remittance batches to send to the bank. Trade notes that were selected for the remittance batch in the Bank Transfer Remittance Batches window are considered collection documents after they are formatted. You query the remittance batches in the Find Remittance Batches window. You can also cancel or unformat bank transfer remittance batches.
Before you can use the Format Remittance Batches window, you must:
Create bank transfer remittance batches in the Bank Transfer Remittance Batches window if you are formatting Bank Transfer remittance batches
Create occurrence remittance batches in the Occurrences Remittance Batches window if you are formatting occurrence remittance batches
To format a remittance batch:
Navigate to the Format Remittance Batches window.
The Find Remittance Batches window appears.
Select a batch name and press the OK button.
The Format Remittance Batches window appears with the remittance batches for the operating unit. The sequence number of the batch displays in the Sequence Number field. The type of documents in the batch, either collection, factoring, or occurrence, displays in the Type field. The status of the batch, either Selected or Formatted, displays in the status field. See the Status Field Table for possible statuses in the Status field.
Choose the Accounts tabbed region to see the account number, request ID, and remittance media (file or report) for each batch.
Choose the Banks tabbed region to see the bank number, bank name, branch number, or branch name.
Choose the More tabbed region to see the formatting date, total number of trade notes in each batch, and total amount of the trade notes.
Select any batch and press the Format button.
The batch is formatted in either a file or a report. The batch status is Formatted after you format a batch with Selected status. You can reformat a batch with Formatted status.
Note: The Format button is disabled if there is no trade note in a remittance batch.
Select any bank transfer remittance batch Remittance Batches window, of type collection or factoring, and press the Void button to cancel it.
The canceled batch is removed from the window. You can add the trade notes that were in the batch to a new batch or to an unformatted batch in the Bank Transfer
Note: All occurrences for a canceled bank transfer batch with Formatted status are also canceled.
Select any formatted bank transfer remittance batch and press the Reverse button to unformat it. The status changes to Selected. The occurrences for the reversed batch are canceled.
Use the Trade Notes window to select trade notes and associated collection documents that you want to create occurrences for. You enter occurrences for collection documents. You query the trade notes in the Find Trade Notes window.
Before you can use the Trade Notes window, you must format bank collection remittance batches of type Collection in the Format Remittance Batches window.
To enter bank occurrences:
Navigate to the Trade Notes window.
The Find Trade Notes window appears.
Enter search criteria in any of the fields, or leave them blank for all trade notes.
Note: You must enter a branch number to enter an account number.
Press the Find button.
The Trade Notes window appears with the operating unit, trade notes, and their attributes, such as the trade note number, transaction number, due date, and whether the trade note is in the collection process.
Select a trade note. The collection document's attributes for the selected trade note display in the bottom of the window in the tabbed regions.
Press the Occurrences button.
The Bank Occurrence Codes window appears. All occurrences for the selected collection document are displayed.
Enter a predefined occurrence code in the Code field. Remittance displays in the Type field. A description of the occurrence displays in the Description field.
Note: You can only enter an occurrence code for a formatted or protested collection document. The status for the selected collection document displays in the Collection Documents region in the Trade Notes window.
Enter the bank's charge in the Bank Charges field if the occurrence type is a write-off requisition.
Enter a General Ledger date in the GL Date field if the occurrence type is a write-off requisition. The General Ledger date is the date when the write-off requisition is accounted.
Choose the Main tabbed region to see additional information about the occurrence, such as the type, description, and date the occurrence was created.
Choose the More tabbed region to see additional information about the occurrence, such as the due date, remittance date, document amount, abatement amount, interest percent, and occurrence status.
Save your work.
Use the Occurrences Remittance Batches window to create remittance batches for occurrences.
Before you can use the Occurrences Remittance Batches window, you must enter bank occurrences for collection documents in the Bank Occurrence Codes window.
To create an occurrence remittance batch:
Navigate to the Occurrences Remittance Batches window.
Select the applicable operating unit.
Enter a batch name in the Batch Name field.
A batch number and request number display in the Batch Number and Request Number fields after you complete all the steps and save.
Enter a due date range for the collection documents with occurrences in the Due Dates fields, or leave the fields blank for all collection documents with occurrences.
You can optionally enter the number of the bank and branch you are creating the remittance batch for in the Bank Number and Branch Number field.
The name of the bank and branch automatically appears in this field.
Enter an account number in the Account Number field if you want to create a batch for a specific account. If you leave this field blank, a batch is created for each account of the bank branch that you entered.
Note: You must enter a bank and branch number to enter an account number.
Enter a GL Date for the batch occurrences, or bank or bank account occurrences. The default is the system date.
Repeat steps 4 to 6 for each bank or bank account that you want.
Save your work. The media for the occurrence remittance batch is in report format for these instances:
The occurrence codes are defined in the Bank Occurrence Codes window with the Report media type
The occurrence codeFiles are defined in the Bank Occurrence Codes window with the media type and are related to bank transfer remittance batches that are sent as reports to the bank
The occurrence codeFiles are defined in the Bank Occurrence Codes window with the media type, but the remittance date is in the limit that is defined for these occurrence codes
Use the Format Remittance Batches window to send the batch to the bank. See Formatting Remittance Batches for more information.
Use the Bank Returns window to enter bank return occurrences from a bank return report. You can also update bank return occurrences from a bank return file that has entries that were successfully validated by the import bank return validation process.
Before you can use the Bank Returns window, you must:
Define bank occurrence codes for return occurrences in the Bank Occurrence Codes window.
Format remittance batches in the Format Remittance Batches window.
Run the Import Bank Return concurrent program from the Standard Request Submission windows if you want to update imported bank return occurrences. See Importing Bank Return Occurrences for more information about this program.
To enter bank return occurrences:
Navigate to the Bank Returns window.
Select the applicable operating unit.
Enter a file control number for the bank return report in the File Control field. This number can be alphanumeric. This number must be the same for all the return occurrences you enter from a bank return report.
Enter the date that the bank generated the bank return report/file in the Generation Date field.
Enter a bank number and customer name in the Bank Number and Customer Name fields.
Enter a trade note number in the Trade Note Number field.
Enter occurrence information in the Occurrence Code and Occurrence Date fields.
Enter the date that the bank return report or file was entered or imported into Receivables in the Processing Date field.
Note: The Credit Amount field is display only if you enter a full settlement occurrence.
Save your work. The bank return information is saved in Receivables.
To update bank return occurrences:
Navigate to the Bank Returns window.
Query the bank returns.
Update the occurrence date in the Occurrence Date field.
Update the bank's trade note ID in the Our Number field.
Update the collector bank number and collector branch number in the Collector Bank Number and Collector Branch Number fields.
Update bank information in the Bank Use, Note, and Bank Charges fields.
Update the amounts in the Interest Amount Received, Abatement Amount, Discount Amount, and Credit Amount fields.
Save your work. The bank return occurrences are saved in Receivables.
Use the Correct Bank Returns window to correct imported bank return occurrences that were rejected during the validation process. You can see all rejected bank return occurrences in the Brazilian Receivables Bank Return Import report. You first select the bank returns in the Find Bank Returns window.
Before you can use the Correct Bank Returns window, you must:
Define bank occurrence codes for return occurrences in the Bank Occurrence Codes window.
Format remittance batches in the Format Remittance Batches window.
Run the Import Bank Return concurrent program from the Standard Request Submission windows. See Importing Bank Return Occurrences for more information about this program.
To correct bank return occurrence:
Navigate to the Correct Bank Returns window.
The Find Bank Returns window appears.
Enter search criteria in any of the fields, or leave them blank for all bank return occurrences. You must enter a bank number to enter a bank occurrence code.
Press the Find button.
The Correct Bank Returns window appears with the bank return occurrences for the operating unit to correct.
Choose the Company tabbed region to correct the company code in the Code field.
Choose the Banks tabbed region to correct the bank occurrence code in the Code field.
Choose the Trade Notes tabbed region to correct the trade note amount in the Amount field and to enter a document number in the Document Number field.
Choose the More tabbed region to correct the customer's name in the Customer Name field.
You can optionally select a return occurrence instead of choosing the tabbed regions, and press the Open button. The same bank return occurrence with all its fields appear in one window.
Change the remittance code in the Correct Bank Returns window to a 2 if it is not already set to 2. All bank return occurrences must have a remittance code of 2.
Check the Cancel check box if you want to cancel a bank return occurrence. After an occurrence is canceled, it does not appear in this window when you query this window again.
Save your work. Bank return occurrences are deleted from this window and appear in the Bank Returns window if they do not have validation errors.
Run the Import Bank Return request set to import and validate bank return occurrences. The bank return occurrences that are rejected by this process display in the Correct Bank Returns window and are shown in the Brazilian Receivables Bank Return Import report. For more information about this report, see Brazilian Receivables Bank Return Import Report. The bank return occurrences that are not rejected appear in the Bank Returns window. You can change occurrence information in both of these windows.
Use the Standard Request Submission windows to submit the Brazilian Receivables Import of Bank Return program.
Before you can use this window, you must:
Populate the Bank Collection Interface table
Define bank occurrence codes for return occurrences in the Bank Occurrence Codes window
Format remittance batches in the Format Remittance Batches window
Related Topics
Using Standard Request Submission, Oracle Applications User Guide
Use the Post Bank Returns window to submit the Brazilian Receivables Post Bank Return program, the Brazilian Receivables Post Bank Return report, and the Post QuickCash concurrent program for a bank return file or report:
The Brazilian Receivables Post Bank Return program creates bank return occurrences and adjustments.
The Post QuickCash program creates and applies receipts to the invoices.
The Brazilian Receivables Post Bank Return report summarizes the receipts, adjustments, interest, monetary corrections, and discounts for receipts for a bank return file or report. The Brazilian Receivables Post Bank Return report also shows the number of occurrences for each collector bank and for each bank occurrence code.
Before you can use the Post Bank Returns window, you must:
Enter or import bank returns in the Bank Returns window
Correct bank returns that were rejected by the Import Bank Return request set in the Correct Bank Returns window
To post bank returns:
Navigate to the Post Bank Returns window.
Enter a file control number in the File Control field.
The bank return file or report information displays in the Bank Number, Bank Name, Generation Date, Processing Date, and Operating Unit fields. The request ID of the master concurrent program displays in the Post Bank Return Request ID field.
Press the OK button.
Related Topics
Post QuickCash, Oracle Receivables User Guide
Use the Run General Ledger Interface window to run the GL Interface program. This program transfers the journal entries that are generated in the Bank Transfer process to General Ledger. The journal entries are for receipts as well as accountable remittance and return occurrences.
The GL Interface program transfers all Receivables transactions to your General Ledger accounts and creates journal batches.
Prerequisites
Run the Create Accounting program in the Submit Request window for the Receivables application to create account data in Subledger Accounting. When running the program, ensure that you enter the following:
Enter the applicable ledger for creation of subledger accounting.
Optionally, specify the process category to determine which receivables transactions will be selected for subledger accounting, such as Brazilian Check Collection Documents for standard bank transfer collection documents and Standard Receipts for the factoring collection documents.
To run the GL Interface program:
Navigate to the Run General Ledger Interface window.
Choose a posting detail (Detail or Summary).
Enter a General Ledger posted date in the GL Posted Date field.
Enter a range of General Ledger dates in the GL Dates fields.
Choose Yes to import your transactions into General Ledger or No to import them into the journal import interface.
Save your work. The request ID number for your concurrent process displays in the Request ID field.
Related Topics
Running General Ledger Interface, Oracle Receivables User Guide
This section explains how to manage receipts for Brazilian Oracle Receivables. In Brazil, interest is calculated on receipts for overdue invoices. If the receipt amount is a partial amount, interest is calculated on either the amount received or the total invoice amount.
Oracle Receivables automatically calculates interest based on the business day calendar. You can apply total or partial receipt amounts and generate interest debit memos on interest due.
Use the globalization flexfield in the Receipts window to calculate interest on receipts for overdue invoices. You can receive interest, create an Interest Debit Memo for interest due, or write off the due amount.
You can manually apply interest to one or more transactions, or you can automatically apply interest to several transactions.
Before you can use the Receipts window, you must:
Define system options for calculating interest
Define customer profile classes for calculating interest
Enter interest parameters in the Transactions window for your invoices
Define profile options
Define banks
Define Global Receipt Method accounts
Define Receivables adjustment limits
To manually calculate interest for a receipt:
Navigate to the Receipts window.
Query or enter the receipt to apply.
Enter the name or number of the customer who owns this receipt in the Customer Name or Number field if the receipt is unidentified.
Press the Applications button.
Enter the transaction to apply this receipt to in the Transaction Number field. The Amount Applied field displays the balance due for the transaction.
Navigate to the globalization flexfield.
The Main Amount Received field displays the amount displayed in the Amount Applied field. Change this amount to a partial amount if you want to calculate interest on a partial amount only.
Enter Total in the Base Interest Calculation field if you want to calculate interest based on the total invoice amount. Enter Partial if you want to calculate interest based on the amount entered in the Main Amount Received field, if this amount is less than the total invoice amount.
If you enter Partial, press the OK button to generate the interest calculation. The flexfield reopens automatically.
The Calculated Interest field displays the total interest due for the invoice.
The Received Interest field displays the amount of interest received for this transaction. You can change the amount of interest received for this transaction.
If the received interest amount is less than the calculated interest amount, use the Interest Difference Action field to decide whether to write off the difference or generate an Interest Debit Memo.
If you enter Write-off, enter an explanation in the Write Off Reason field. If you enter Generate_IDM, Oracle Receivables automatically generates an Interest Debit Memo for the interest due.
Press the OK button.
If you press the Adjustments button, Oracle Receivables shows the adjustment with the calculated and received interest. The adjustment reflects if the customer paid more than the interest that is due.
To automatically calculate interest for several receipts:
Navigate to the Receipts window.
Query or enter the receipt to apply.
Enter the name or number of the customer who owns this receipt in the Customer Name or Number field if the receipt is unidentified.
Press the Mass Apply button.
Enter the transactions that you want to apply this receipt to and prepare them according to the criteria that you want.
Press the Preview or Apply button. Oracle Receivables calculates the total interest that is due and the interest that has been received for each transaction.
If you press the Preview button, use the flexfield to view and modify the interest calculation for each transaction. Check the Apply check box to select the transaction for the application.
If you press the Apply button, you can either accept how Receivables has calculated interest for each transaction or use the flexfield to view and modify the interest calculation.
Navigate to the globalization flexfield for each transaction.
Enter the amount in the Received Interest field if you want to change the interest amount received.
If the received interest amount is less than the calculated interest amount, use the Interest Difference Action field to decide whether to write off the difference or generate an Interest Debit Memo.
Enter an explanation in the Write Off Reason field if you enter Write-off. If you enter Generate_IDM, Receivables generates an Interest Debit Memo for the interest due.
Press the OK button.
Repeat steps 7 to 11 for each transaction.
Use the globalization flexfield in the Receipt Batches window to view and modify the received interest amount for QuickCash transactions for overdue invoices. Receivables only applies interest to QuickCash transactions when the application type is Multiple.
For QuickCash receipts, if the received interest amount is less than the calculated interest amount, Receivables calculates whether to write off the outstanding interest or generate an Interest Debit Memo. This calculation is based on the parameters that you enter in the Global Receipt Method Accounts window.
Before you can use the Receipt Batches window, you must:
Define system options for calculating interest
Define customer profile classes for calculating interest
Enter interest parameters in the Transactions window for your invoices
Define profile options
Define banks
Define Global Receipt Method accounts
Define Receivables adjustment limits
To calculate interest on QuickCash receipts:
Navigate to the Receipt Batches window.
Query a QuickCash batch, or enter Manual-Quick in the Batch Type field and enter a batch name.
Press the Receipts button.
Query or enter the Quick receipts to apply, and choose an application type of Multiple.
Press the Multiple button.
For each transaction, navigate to the globalization flexfield. If the globalization flexfield is not in the window, choose Folder > Show Field from the Toolbar menu bar. Choose the field ( ) in the Show Field window and press the OK button.
The Main Amount Received field displays the amount displayed in the Amount Applied field. Change this amount to a partial amount if you want to calculate interest for a partial amount.
Enter Total in the Base Interest Calculation field if you want to calculate interest based on the total invoice amount. Enter Partial if you want to calculate interest based on the amount entered in the Main Amount Received field if it is less than the total invoice amount.
If you enter Partial, press the OK button to generate the interest calculation. The flexfield reopens automatically.
The Calculated Interest field displays the total interest due for the invoice. The Received Interest field displays the amount of interest received for this transaction. You can change the amount of interest received for this transaction.
If the received interest amount is less than the calculated interest amount, Receivables automatically generates an Interest Debit Memo or writes off the outstanding interest.
Press the OK button.
Repeat steps 6 to 10 for each transaction.
Save your work.
When you are ready to post the batch to Oracle Receivables, press the Post QuickCash button.
The customer merge process in Oracle Receivables merges standard as well as country-specific information. Receivables automatically associates all transaction activity from the old customer or site with the new customer or site. Receivables also removes the setup information of merged customers or customer sites.
These features support customer merge:
Bank Transfer (Brazil)
Brazilian Receivables Customer Auxiliary Ledger
Brazilian Receivables Customer Auxiliary Daily
Related Topics
Merging Customers, Oracle Receivables User Guide
This section provides overviews and detailed descriptions of these reports:
Brazilian Receivables Invoice Print
Brazilian Receivables Complementary Invoices
Brazilian Receivables Customer Account Detail report
Brazilian Receivables Collection Remittance Batch report
Brazilian Receivables Occurrences Remittance Batch report
Brazilian Receivables Factoring Remittance Batch report
Brazilian Receivables Bank Return Import report
Brazilian Receivables Post Bank Return report
Brazilian Receivables Bank Collection GL Interface report
Use the Brazilian Receivables Print Invoice in AutoInvoice, the Brazilian Receivables Invoice Print Invoice in Batch, or the Brazilian Receivables Print Invoice in Batch Immediately to print a completed payable invoice for shipment with goods. Use the Brazilian Receivables Re-Print Specific Invoice to reprint a specific invoice. This report is printed on preprinted paper.
You can continue to update the original invoice from the Transactions window for invoices entered manually until the invoice is completed. The invoice contents are frozen once the invoice is completed.
There are four ways to print invoices:
Brazilian Receivables Print Invoice in Batch Immediately - From the Transactions window, for completed invoices.
Note: The Print Invoice Immediately check box must be set to Yes in the System Options window.
Brazilian Receivables Print Invoice in AutoInvoice - From the Brazilian AutoInvoice request set of the standard submission set, after you import invoice information from another system
Brazilian Receivables Invoice Print Invoice in Batch - From the Brazilian Print Invoice in Batch request set of the standard submission set
Brazilian Receivables Re-Print Specific Invoice - From the Standard Request Submission windows
Enter Print Invoice Generated by AutoInvoice.
Enter Print Invoice Batch.
Enter the highest invoice date to print.
Enter the highest form to print.
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Exit/Entry (Operation Type) | The operation type |
| Transaction Number | The transaction number |
| Sub-Series | The sub-series of the invoice |
| Operation Nature | The operation nature of the invoice |
| Operation Fiscal Code | The operation fiscal code |
| State Inscription for Tributary Substitution | The state inscription for tributary substitution of the invoice |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Ship to Customer Name | The customer name |
| Inscription Number | The invoice inscription number |
| Issue Date | The issue date of the invoice |
| Address | The shipping address |
| District | The district of the shipping address |
| Postal Code | The postal code of the shipping address |
| Shipping Date | The shipping date |
| City | The city of the shipping address |
| State | The state of the shipping address |
| State Inscription Number | The state inscription number |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Amount Due Remaining | The amount that is due remaining in each installment |
| Trade Note Number | The trade note number in each installment |
| Due Date | The due date of each installment |
| Bill to Address | The bill to address for each installment |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Item Code | The item code for the invoice line |
| Item Description | The item description |
| Item Fiscal Classification | The invoice line number. The corresponding item fiscal classification for the invoice line is printed in the Additional Information region in this report. |
| Federal Tributary Situation | The federal tributary situation of the invoice line |
| UOM | The unit of measure for the invoice line |
| Quantity | The quantity for the invoice line |
| Unit Amount | The unit amount for the invoice line |
| Total Amount | The total amount for the invoice line |
| ICMS Tax Rate | The ICMS tax rate for the invoice line |
| IPI Tax Rate | The IPI tax rate for the invoice line |
| IPI Tax Amount | The IPI tax amount for the invoice line |
| Legal Messages | Three concatenated legal messages for the invoice line |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Description | The description for the service line |
| ISS Tax Amount | The ISS tax amount for the service line |
| Total Amount | The total amount for the service line |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| ICMS Tax Base Amount | The ICMS tax base amount |
| ICMS Tax Amount | The ICMS tax amount |
| ICMS-ST Tax Base Amount | The ICMS-ST tax base amount |
| ICMS-ST Tax Amount | The ICMS-ST tax amount |
| Item Total Amount | The item total amount |
| Freight Carrier Expense Amount | The freight carrier expense amount |
| Insurance Expense Amount | The insurance expense amount |
| Other Expense Amount | The amount of any other expenses |
| IPI Tax Total Amount | The IPI tax total amount |
| Invoice Total Amount | The total invoice amount |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Freight Carrier Name | The freight carrier name |
| Freight Responsibility | 1 - Seller or 2 - Buyer |
| License Plate | The freight carrier's license plate |
| Inscription Number | The freight inscription number |
| Address | The freight carrier's address |
| City | The city of the freight carrier's address |
| State | The state of the freight carrier's address |
| State Inscription Number | The freight state inscription number |
| Volume Quantity | The volume quantity |
| Volume Type | The volume type |
| Brand | The brand |
| Volume Number | The volume number |
| Total Gross Weight | The total gross weight |
| Total Net Weight | The total net weight |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Complementary Information | Any complementary information. If invoice is canceled, then VOID is printed. |
| Fiscal Classification Codes | Fiscal classification codes with the corresponding invoice line number |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Transaction Number | The transaction number |
Related Topics
Using Standard Request Submission
You can modify the original invoice from the Complementary Invoice window for invoices that are completed. The complementary invoice contents are frozen once the complementary invoice is printed. This report is printed on preprinted paper.
There are two ways to print complementary invoices:
Brazilian Receivables Print Complementary Invoice Immediately - From the Complementary Invoice window, after you manually enter invoice information. (Note: The Print Invoice Immediately check box must be set to Yes in the System Options window.)
Brazilian Receivables Invoice Print Complementary Invoice in Batch - From the Brazilian Print Invoice in Batch request set of the standard submission set.
Enter Print Invoice Batch.
Enter the highest invoice date to print.
Enter the highest form to print.
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Exit/Entry (Operation Type) | The operation type |
| Transaction Number | The transaction number |
| Sub-Series | The sub-series of the invoice |
| Operation Nature | The operation nature of the invoice |
| Operation Fiscal Code | The operation fiscal code |
| State Inscription for Tributary Substitution | The state inscription for tributary substitution of the invoice |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Ship to Customer Name | The customer name |
| Inscription Number | The invoice inscription number |
| Issue Date | The issue date of the invoice |
| Address | The shipping address |
| District | The district of the shipping address |
| Postal Code | The postal code of the shipping address |
| Shipping Date | The shipping date |
| City | The city of the shipping address |
| State | The state of the shipping address |
| State Inscription Number | The state inscription number |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Amount Due Remaining | The amount that is due remaining for each installment |
| Trade Note Number | The trade note number for each installment |
| Due Date | The due date of each installment |
| Bill to Address | The bill to address for each installment |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Item Code | The item code for the invoice line |
| Item Description | The item description |
| Item Fiscal Classification | The invoice line number. The corresponding item fiscal classification for the invoice line is printed in the Additional Information region in this report. |
| Federal Tributary Situation | The federal tributary situation of the invoice line |
| UOM | The unit of measure for the invoice line |
| Quantity | The quantity for the invoice line |
| Unit Amount | The unit amount for the invoice line |
| Total Amount | The total amount for the invoice line |
| ICMS Tax Rate | The ICMS tax rate for the invoice line |
| IPI Tax Rate | The IPI tax rate for the invoice line |
| IPI Tax Amount | The IPI tax amount for the invoice line |
| Legal Messages | Three concatenated legal messages for the invoice line |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Description | The description for the service line |
| ISS Tax Amount | The ISS tax amount for the service line |
| Total Amount | The total amount for the service line |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| ICMS Tax Base Amount | The ICMS tax base amount |
| ICMS Tax Amount | The ICMS tax amount |
| ICMS-ST Tax Base Amount | The ICMS-ST tax base amount |
| ICMS-ST Tax Amount | The ICMS-ST tax amount |
| Item Total Amount | The item total amount |
| Freight Carrier Expense Amount | The freight carrier expense amount |
| Insurance Expense Amount | The insurance expense amount |
| Other Expense Amount | The amount of any other expenses |
| IPI Tax Total Amount | The IPI tax total amount |
| Invoice Total Amount | The total invoice amount |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Freight Carrier Name | The freight carrier name |
| Freight Responsibility | 1 - Seller or 2 - Buyer |
| License Plate | The freight carrier's license plate |
| Inscription Number | The freight inscription number |
| Address | The freight carrier's address |
| City | The city of the freight carrier's address |
| State | The state of the freight carrier's address |
| State Inscription Number | The freight state inscription number |
| Volume Quantity | The volume quantity |
| Volume Type | The volume type |
| Brand | The brand |
| Volume Number | The volume number |
| Total Gross Weight | The total gross weight |
| Total Net Weight | The total net weight |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Complementary Information | Any complementary information. If the invoice is canceled, then Void is printed. |
| Fiscal Classification Codes | Fiscal classification codes with the corresponding invoice line number |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Transaction Number | The transaction number |
Related Topics
Using Standard Request Submission
The Customer Interface Error report contains customer information invalidated by the Customer Interface program. Use this report to update invalid customer information in the Customers window.
Use the Standard Request Submission windows to submit the Customer Interface Error report.
Related Topics
Using Standard Request Submission
Use the Brazilian Receivables Customer Account Detail report to review customer accounts for interest and bank transfer activity. For each customer listed in the report, Oracle Receivables prints all open transactions and total balance due in the ledger currency.
Use the Standard Request Submission windows to submit the Brazilian Receivables Customer Account Detail report.
Enter the first invoice number for the report.
Enter the last invoice number for the report.
Enter the first customer number for the report.
Enter the last customer number for the report.
Enter the first customer name for the report.
Enter the last customer name for the report.
This table shows the report headings.
| In this heading… | Oracle Receivables prints… |
|---|---|
| Customer Name | The customer name |
| Customer Number | The customer number |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Transaction Number | The invoice number for each transaction in the report |
| Transaction Status | The status of each transaction |
| Transaction Date | The transaction date for invoice, debit memo, credit memo |
| Transaction Due Date | The due date for each transaction |
| Transaction Days Late | Number of days past due, or the number of days until the due date |
| Original Amount | The original amount of each transaction |
| Interest Due | The calculated interest amount for each transaction |
| Balance Due | The amount due for each transaction |
| Transaction Type | The transaction type |
| Transaction Class | The transaction class of the transaction |
| Bank Transfer Batch Number | The number for the bank transfer remittance batch when the transaction was selected |
| Selection Number | The number when the bank transfer batch was selected |
| Bearer of Trade Note | The invoice bearer of trade note |
| Document Status | The document status |
| Total Balance Due | The balance due sum for the selected transactions |
| Total Interest Due | The interest calculation for each transaction |
Related Topics
Using Standard Request Submission
Use the Brazilian Receivables Collection Remittance Batch report to submit formatted collection document information to remittance banks. This report is a listing of collection documents administered by the remittance bank.
The output for the Brazilian Receivables Collection Remittance Batch report is either a paper report or an electronic file in standard CNAB format. The Brazilian Receivables Collection Remittance Batch electronic file contains three records: Header Record, Transaction Record, and Trailer Record.
For more information about file content, see Brazilian Receivables Collection Remittance Batch File Content.
Run the Brazilian Receivables Collection Remittance Batch report from the Format Remittance Batches window. For instructions about using this window, see Formatting Remittance Batches.
The Brazilian Receivables Collection Remittance Batch report is automatically submitted from the Format Remittance Batches window as a concurrent request. There are no parameters to enter.
The Output Media field indicates whether the output is a paper report (Report) or an electronic file (File).
This table shows the report headings.
| In this heading… | Oracle Receivables prints… |
|---|---|
| Bank Number | The remittance bank number |
| Bank Name | The bank name |
| Branch Number | The bank branch number |
| Branch Name | The branch name |
| Account Number | The company account number at the bank |
| Company Code | The bank's company ID |
| Company Name | The company name |
| Selection Number | The selection number assigned to the bank transfer remittance batch |
| Selection Name | The selection name assigned to this remittance batch |
| Generation Date | The generation date for the bank transfer remittance batch |
| Remittance Date | The remittance date for the bank transfer remittance batch |
| Batch Sequence Number | The sequential batch number for the bank transfer remittance batch |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Your Number | The trade note number for the collection document |
| Drawee Name | The customer name |
| Drawee Inscription Number | The inscription number of the customer site |
| Drawee Address | The customer site address |
| District | The district of the customer site address |
| City | The city of the customer site address |
| State | The state of the customer site address |
| Postal Code | The postal code for the customer site address |
| Company Inscription Number | Your company's inscription number |
| Portfolio Number | The portfolio number |
| Company Use | The collection document number |
| Collection Document Type | The collection document type |
| Due Date | The collection document due date |
| Amount | The amount of the collection document |
| Issue Date | The transaction date for the transaction associated with the collection document |
| Interest Per Day | The interest amount per day |
| Discount Date | The discount date on the collection document |
| Discount Amount | The discount amount |
| Bank Instruction 1 | The first bank instruction code and its description |
| Bank Instruction 2 | The second bank instruction code and its description |
| Bank Transfer Batch Total | The total document amount for all collection documents listed in the report |
| Number of Documents | The number of documents listed in the report |
| Bank Transfer Batch Total | The total document amount for all collection documents listed in the report |
Use the Brazilian Receivables Occurrences Remittance Batch report to submit formatted occurrence information to banks. The report is a listing of occurrences that contain updates to collection documents.
The output for the Brazilian Receivables Occurrences Remittance Batch report is either a paper report or an electronic file in standard CNAB format. The Brazilian Receivables Occurrences Remittance Batch electronic file contains three records: Header Record, Transaction Record, and Trailer Record.
For more information about file content, see Brazilian Receivables Occurrences Remittance Batch File Content.
Run the Brazilian Receivables Occurrences Remittance Batch report from the Format Remittance Batches window. For instructions about using this window, see Formatting Remittance Batches.
The Brazilian Receivables Occurrences Remittance Batch report is automatically submitted from the Format Remittance Batches window as a concurrent request. There are no parameters to enter.
The Output Media field indicates whether the output is a paper report (Report) or an electronic file (File).
This table shows the report headings.
| In this heading… | Oracle Receivables prints… |
|---|---|
| Company Code | The bank's company ID |
| Company Name | The company name |
| Bank Number | The bank number |
| Bank Name | The bank name |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Your Number | The trade note number for the collection document associated with the occurrence |
| Bank Occurrence Code | The bank occurrence code |
| Description | Bank occurrence code description |
| Company Use | The collection document number |
| Our Number | The collection document bank ID |
| Portfolio Number | The collection document portfolio number |
| Due Date | The occurrence due date |
| Issue Date | The transaction date of the transaction associated with the occurrence |
| Trade Note Amount | The face amount or nominal value of the trade note |
| Drawee Name | The customer name of the collection document associated with the occurrence |
| Interest Per Day | The interest amount per day |
| Interest Date | The beginning interest date |
| Discount Date | The discount date of the collection document associated with the occurrence |
| Discount Amount | The discount amount |
| Abatement Amount | The abatement amount of the collection document associated with the occurrence |
| Days to Protest/Write-Off | The number of days to protest or write off |
Use the Brazilian Receivables Factoring Remittance Batch report to submit formatted factoring remittance information to remittance banks. This report is a listing of collection documents traded to a remittance bank.
The output for the Brazilian Receivables Factoring Remittance Batch report is either a paper report or an electronic file in standard CNAB format. The Brazilian Receivables Factoring Remittance Batch electronic file contains three records: Header Record, Transaction Record, and Trailer Record.
Run the Brazilian Receivables Factoring Remittance Batch report from the Format Remittance Batches window. For instructions about using this window, see Formatting Remittance Batches.
The Brazilian Receivables Factoring Remittance Batch report is automatically submitted from the Format Remittance Batches window as a concurrent request. There are no parameters to enter.
The Output Media field indicates whether the output is a paper report (Report) or an electronic file (File).
This table shows the report headings.
| In this heading… | Oracle Receivables prints… |
|---|---|
| Bank Number | The remittance bank number |
| Bank Name | The bank name |
| Branch Number | The bank branch number |
| Branch Name | The branch name |
| Account Number | The bank account number |
| Company Code | The bank's company ID |
| Company Name | The company name |
| Selection Number | The selection number assigned to this remittance batch |
| Selection Name | The selection name assigned to this remittance batch |
| Generation Date | The generation date of the bank transfer remittance batch |
| Remittance Date | The remittance date of the bank transfer remittance batch |
| Batch Sequence Number | The sequential batch number of the bank transfer remittance batch |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Your Number | The trade note number |
| Drawee Name | The name of the customer |
| Drawee Inscription Number | The customer site inscription number |
| Drawee Address | The customer site address |
| District | The district of the customer site address |
| City | The city of the customer site address |
| State | The state of the customer site address |
| Postal Code | The postal code of the customer site address |
| Company Inscription Number | Your company's inscription number |
| Company Use | The collection document |
| Collection Document Type | The collection document type |
| Due Date | The collection document due date |
| Amount | The amount of the collection document |
| Issue Date | The transaction date of the transaction associated with the collection document |
| Factoring Rate | The factoring rate |
| Factoring Period | The factoring period |
| Factoring Date | The factoring date |
| Factoring Amount | The factoring amount |
| In this column… | Oracle Receivables prints… |
| Credit Amount | The credit amount. The credit amount is the document amount less the factoring amount. |
| Number of Documents | The count of documents listed in the report |
| Bank Transfer Batch Totals | The three totals of document amount, factoring amount, and credit amount of all collection documents listed in the report |
The Brazilian Receivables Bank Return Import report is an error report that lists bank return occurrences that were rejected by the validation process in the Import Bank Return program. The Import Bank Return program validates return occurrences in the electronic file received from the remittance bank.
Use the Standard Request Submission windows to submit the Brazilian Receivables Bank Return Import report.
Enter the assigned batch ID number for the batch received from the remittance bank.
This table shows the report headings.
| In this heading… | Oracle Receivables prints… |
|---|---|
| File Control | The assigned batch ID number for the batch received from the remittance bank |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Sequential Number | The invalid occurrence sequential number in the bank return's file |
| Bank Number | The bank number |
| Your Number | The document number of the collection document associated with the invalid occurrence |
| Bank Occurrence Code | The bank occurrence code of the invalid occurrence |
| Occurrence Date | The occurrence date of the invalid occurrence |
| Generation Date | The generation date of the invalid occurrence |
| Trade Note Amount | The document amount of the collection document associated with the invalid occurrence |
| Due Date | The due date of the collection document associated with the invalid occurrence |
| Processing Date | The processing date of the invalid occurrence |
| Error Description | The error description of the invalid occurrence |
Related Topics
Using Standard Request Submission
The Brazilian Receivables Post Bank Return report summarizes the receipts, adjustments, interest, monetary corrections, and discounts for receipts for return occurrences in the bank return file. The records are validated by the Import Bank Return program. The report also includes the number of occurrences for each bank and each bank occurrence code within a bank in the bank return batch.
Run the Brazilian Receivables Post Bank Return report and the Brazilian Receivables Post Bank Return program from the Post Bank Returns window. For instructions about the Post Bank Returns window, see Posting Bank Returns.
This table shows the report headings.
| In this heading… | Oracle Receivables prints… |
|---|---|
| Batch Source Name | The ID name for the batch source holding accounting information associated with the payment batch |
| Batch Name | The payment batch name |
| Batch Date | The payment batch date |
| Bank Name | The name of the bank that sent the bank remittance batch |
| Deposit Date | The deposit date for the payment batch |
| Currency Code | The currency code |
| Period | The General Ledger period |
| GL Date | The accounting date for the payment batch |
| Comments | Description of the received batch |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Number of Receipts | The receipt count of the items in the bank return batch |
| Total Receipts Amount | The total receipts amount of the bank return batch |
| Number of Abatements | The number of abatements in the bank return batch |
| Calculated Abatements Total | The calculated total amount of abatements |
| Received Abatements Total | The total amount of abatements received |
| Abatements Adjustments Total | The total amount of adjustments created for abatements |
| Number of Interest | The number of interest in the bank return batch |
| Calculated Interest Total | The calculated total amount of interest |
| Received Interest Total | The total interest amount received |
| Interests Adjustments Total | The total amount of adjustment created for interest |
| Interest Debit Memos Total | The total amount of interest debit memos created |
| Number of Discounts | The number of discounts in the bank return batch |
| Calculated Discounts Total | The calculated total amount of discounts |
| Received Discounts Total | The total amount of discounts received |
| Bank Number | The bank numbers of each bank associated with return occurrences |
| Bank Occurrence Code | The bank occurrence codes for the return occurrences |
| Description | A description of the bank occurrence codes |
| Total Occurrences | The count of occurrences for each bank and each bank occurrence code within a bank in the bank return batch |
The Brazilian Receivables Bank Collection GL Interface report summarizes the journal entries generated by the Bank Transfer function.
Run the Brazilian Receivables Bank Collection GL Interface report from the General Ledger Interface window.
This table shows the report headings.
| In this heading… | Oracle Receivables prints… |
|---|---|
| Posting Control ID | The ID for this posting |
| Start Date | The report start date |
| End Date | The report end date |
| Period Name | The accounting period name |
This table shows the column headings.
| In this column… | Oracle Receivables prints… |
|---|---|
| Currency Code | The currency code for each currency in the posting table |
| Category | The accounting entry type for each currency code |
| Entered Debits | The entered debits for a currency and accounting entry type |
| Entered Credits | The entered credits for a currency and accounting entry type |
| Accounted Debits | The accounted debits for a currency and accounting entry type |
| Accounted Credits | The accounted credits for a currency and accounting entry type |
| Currency Totals | The totals for entered debits, entered credits, accounted debits, and accounted credits for each currency |
| Report Totals | The totals for entered debits, entered credits, accounted debits and accounted credits at report level |
To comply with the Federal Senate Resolution 13/2012, and subsequent Agreement 38/2013, the following changes have been provided as part of Oracle Receivables for Brazil:
Enable new Item Origin codes
In addition to the three existing Item Origin codes (codes 0, 1 and 2), the following new codes are now seeded by Oracle:
3 - National, over 40% of imported content
4 - National, compliant with local production rules
5 - National, under 40% of imported content
6 - Foreign, acquired overboard
7 - Foreign, acquired in the domestic market
Introduce required Import Content related attributes by allowing users to:
Associate default values to Inventory Items;
Associate default values to Item Templates;
Enter and Update the Import Content at Transaction Line level (defaulted from inventory item);
The Import Content related attributes provided for Inventory Items are:
Import Content
Import Content Form Number
Foreign Portion Value
Interstate Outbound Total Value
The Import Content related attributes provided at transaction Line level are:
Import Content
Import Content Form Number
Inventory Items
You can define default values for the following Global Attributes available at Organization Items level:
Item Origin
Import Content
Import Content Form Number
Foreign Portion Value
Interstate Outbound Total Value
Item Templates
The same set of Global Attributes is enabled for Item Templates.
Item Origin
Item Origin, including the new seeded codes, can continue to be manually entered at the following transactional levels:
Order Entry line
Memo line
Transaction line
It can also be imported or automatically created via the following process flows:
Autoinvoice
Copy Invoice
Create Invoice API
The following attributes were introduced in different transactional process flows, as described below:
Import Content
Import Content Form Number
Additional Information: Please refer to the Appendix C1 Brazil Import -- Process Flows vs. Defaulting Logic of Attributes, for details on how the attributes get defaulted when entering, importing or copying transactions.
Transactions Workbench
Navigate to the Transactions Workbench form. Within the Lines region, select the Electronic Invoice Lines Attributes window from the Special Menu.
The window was modified and now has two tabs:
Industry Specific
Import Content
Access the Import Content tab to view, enter or update the Import Content related attributes.
Additional Information: The Electronic Invoice Line Attributes window can also be accessed directly from the Localizations menu, through the following navigation path:
Brazilian Localization > Electronic Invoice > Electronic Invoice Line Attributes
Accounts Receivables Open Interface
To import the Import Content related attributes at transaction line level, users must populate the newly added fields in JL_BR_INTERFACE_LINES_EXTS.
Please refer to Appendix C1 - Brazil Import - Data Model Changes and Importing Additional Attributes for details.
Copy Transactions
This process utilizes the Open Interface infrastructure which uses the JL_BR_INTERFACE_LINES_EXTS extension table; the two new attributes reside in this table. The new line level attributes and respective values are copied from the source transaction to target transaction.
Create Invoice API
This process utilizes the Open Interface infrastructure which in turn uses the JL_BR_INV_API_TRX_LINES_T temporary extension table; the two new attributes have been added to this table. Once the invoice is successfully created by the Create Invoice API, these two new attributes would reside in the JL_BR_INTERFACE_LINES_EXT table.
Please refer to Appendix C1 - Brazil Import - Data Model Changes and Importing Additional Attributes for details.
Additional Information: When importing invoice information from Legacy Systems, you must load the Industry Specific and the Import Content related attributes into the extension table JL_BR_INTERFACE_LINES_EXTS and populate the link column JL_BR_INTERFACE_LINK_ID with the ROWID from RA_INTERFACE_LINES_ALL.
Please refer to Appendix C1 - Brazil Import - Data Model Changes and Importing Additional Attributes for more information about the import process and respective data model changes introduced by this project.
The CFOP (Fiscal Code of Operations and Services) code is a 4-digit code defined by the National Tributary System in Brazil. CFOP contains information on the good's origin as well as the type of operation, such as sales, returns, stock transfers, or services.
In Brazil, all commercial transactions and movement of goods are documented using invoices, known as Nota Fiscal. Today Nota Fiscal is issued and received electronically as part of a major Government project called SPED (Public System of Digital Bookkeeping).
As part of the Fiscal SPED and NF-e (electronic invoice), any transactions related to Purchase, Sales and Transfer of Goods or Services are codified through the CFOP. This code is reported in each line of the NF-e.
SEFAZ, the State Tax Administrator, validates and approves the NF-e and Fiscal Reports.
If the CFOP code is wrong, the NF-e is not approved by SEFAZ. Issuer must correct the code and issue a new Fiscal Document. This coding system is used by the Fiscal Authority to consolidate and group the economic activity of the contributors.
CFOP code indicates:
The operation nature of the movement of goods;
Transportation services operations between Municipalities and States;
Communication services;
Different tributary situation for a region or for a specific product or service, within a State.
Additional Information: Oracle Brazilian Receivables was modified to enhance the automatic derivation and defaulting of CFOP codes from setup onto Receivables transaction lines.
For more information on Brazil CFOP, see Defaulting Order of Precedence vs. Combination of Driver Attributes Appendix C - Brazil.
The proposed solution can co-exist with the existing solution and introduces practically no impacts to Brazilian Receivables users; Receivables users can actually keep the Operation Fiscal Codes (CFOP) already defined in the Operation Fiscal Codes window as well as the association of those Operation Fiscal codes at Transaction Type level and Transaction Line level (both under the Additional Information Global Descriptive Flexfield window).
If users opt to have a more comprehensive and precise derivation and defaulting logic for CFOP codes, they can make use of the new and enhanced solution by following the setup steps below:
Main Setup Steps
Define CFOP Codes in the Operation Fiscal Codes window - (Existing or Required Step)
Assign a default CFOP Code to a Transaction Type - (Existing or Optional Step)
Define CFOP-Tributary Substitution Applicability Setup – (New or Recommended Step)
Define CFOP Derivation Setup by associating CFOP Codes to different combination of derivation drivers - (New or Recommended Step)
Existing Setup Steps
Define Operation Fiscal Codes (CFOP Codes)
CFOP codes must continue to be defined in the Operation Fiscal Codes window, irrespective of new or existing implementation.
Navigation Path: Brazilian Payables > Localizations > Setup > Operation Fiscal Codes
Assign CFOP Code to Transaction Type
This is the former defaulting association mechanism. It can still be used without any changes.
Navigation Path: Brazilian Receivables > Setup > Transactions > Transaction Types
Additional Information: The association of CFOP codes to Transaction Types is the last one in the order of precedence for defaulting purposes. When user defines new CFOP Derivation setup, the defaulting logic attempts to default a specific CFOP code from that setup first. If no entries are found, then it defaults the CFOP Code associated to the respective Transaction Type.
New Setup Steps
CFOP/Tributary Substitution Applicability Setup
For a given combination of states Ship-from and Ship-to, users can indicate the applicability of CFOP codes under the Tributary Substitution regime at Product Fiscal Classification level or even at specific Inventory Item level.
Navigation Path: Brazilian Receivables > Localizations > Brazilian Localization > Setup > CFOP-Tributary Substitution Applicability Setup
Logic Summary:
Any combination of state codes is allowed, as long as the combination is unique for a given combination of Product Fiscal Classification or Item.
Repetitive combinations can occur as long as effective dates do not overlap.
Most fields are mandatory, except Item and Effective Date To
CFOP Derivation Setup
Setup CFOP Derivation rules by associating specific CFOP codes to different combination of derivation drivers.
For a given combination of Operation Type (for example, Entry, Exit) and Operation Destination (for example, Intrastate, Interstate or Foreign), users can setup a wide variety of derivation attributes (for example, drivers) that can map to the desired transactional situation and lead to the proper defaulting of CFOP code.
Navigation Path: Brazilian Receivables > Localizations > Brazilian Localization > Setup > CFOP Derivation Setup
Logic Summary:
User can associate up to 3 CFOP Codes (CFOP standard code, CFOP Tributary Substitution code and CFOP Free Trade Zone code) to each combination of attributes.
The derivation attributes (i.e. drivers) are organized as follows:
Transaction related (Transaction Type, Transaction Business Category)
Product related (Item Origin, Product Fiscal Classification, Item)
Service related (Item Origin, Product Category, Memo Line)
Customer Location related (Customer Ship to Site)
User can associate up to 3 CFOP Codes (CFOP standard code, CFOP Tributary Substitution code and CFOP Free Trade Zone code) to each combination of attributes.
All driver fields, except Transaction Type, are optional;
Product Fiscal Classification and Product Category (i.e. Service Classification) are optional, but they are mutually exclusive;
Item and Memo Line are optional, but they are mutually exclusive;
An Item cannot be entered without entering its Product Fiscal Classification;
A Memo Line cannot be entered without entering its Product Category (ie. Product Category is the terminology used to represent Service Classification);
The CFOP code fields are optional, but at least one CFOP code must be entered per row;
The form will display a warning message in case the 1st digit of the selected CFOP Code is not consistent with the Operation Type and Operation Destination combination defined in the header level of the form. For instance:
| Operation Type | Operation Destination | 1st Digit of CFOP Code |
|---|---|---|
| ENTRY | INTRASTATE | 1 |
| ENTRY | INTRASTATE | 2 |
| ENTRY | FOREIGN | 3 |
| EXIT | INTRASTATE | 4 |
| EXIT | INTRASTATE | 5 |
| EXIT | FOREIGN | 6 |
Transactions such as Sales Invoices (NF), Complementary Invoices and Sales Return Invoices require the CFOP code at line level. Credit Memo and Adjustments are financial instruments and do not require CFOP codes.
The CFOP Derivation and Defaulting routine must be invoked for the following types of Receivables transactions or processes:
Manual Transactions
Autoinvoice
Create Invoice API
The CFOP Derivation and Defaulting routine must be invoked for the following types of Receivables transactions line types:
Item Lines
Service lines (for example, from Memo lines)
Transactions Workbench
The (CFOP) Operation Fiscal Code defaults onto transaction line level according to the setup performed by the user, from the higher number to the lesser number of attributes, being the Transaction Type the last attribute.
Important: The defaulting routine is only invoked upon saving the transaction line. Any value already populated (by the user or defaulting routine) will not be overwritten automatically. To re-default the CFOP code, you must clear the Operation Fiscal Code field, press OK and save the record.
Additional Information: If no Operation Fiscal Code (CFOP) is defaulted, you can still enter it manually by selecting the code from the list of values, which is based on the codes defined in the Operation Fiscal Codes window.
To import the Operation Fiscal Code attribute at transaction line level, users need to populate the LINE_GDF_ATTRIBUTE1 column in RA_INTERFACE_LINES table.
Additionally, SQL*Loader program can be used to upload data into the RA_INTERFACE_LINES_ALL interface table.
This process makes use of the Open Interface infrastructure. The (CFOP) Operation Fiscal Code line level attribute will be copied from the source transaction to target transaction.
Similar to the Auto Invoice process, Receivables provides the Create Invoice API scripts which can be executed by users. In this case, user needs to populate the PL/SQL header and Lines table for capturing data related to Invoice header and lines.
Like the SISCOMEX (Foreign Trade Integrated System) that deals with electronic registration in real time of foreign trade operations, the transactions between Brazilian and foreign residents/domiciled, involving services, intangibles and other operations that produce variations in entities' equity, among which the operations of acquisition and sales of services, shall be reported to the Ministry of Development, Industry and Foreign Trade - MDIC through the SISCOSERV.
The purpose of SISCOSERV and SISCOMEX is to compile more accurate and timely statistics of Brazil's foreign trade, in services and goods, respectively. SISCOSERV will allow the supervision and the registration of those operations to form a complete database with the information of the transactions carried out.
All operations of acquisition and sales of services need to be register in the SISCOSERV. These operations shall observe the classification rules established by the Brazilian Nomenclature of Services, Intangibles and Others, indicating the due NBS code.
Define NBS Codes (Lookup Codes)
Users should be able to manually define Service Nomenclature Codes (i.e. NBS Codes) under a seeded lookup type called JLBR_NBS_CODES.
Associate NBS Codes to Inventory Items
Users can associate NBS Codes to Inventory Items by navigating to the Additional Information for Brazil window and entering (for example, selecting) Service Nomenclature Code from a list of pre-defined values.
Associate NBS Codes to Item Templates
Users can associate NBS Codes to Item Templates by navigating to the Additional Information for Brazil window and entering (i.e. selecting) Service Nomenclature Code from a list of pre-defined values.
Receivables Manual Transactions Entry
When manually entering Receivables transaction lines through the Transactions workbench, users can navigate to the Electronic Invoice Line Attributes window from the Special Menu option, then click on the Service Nomenclature Code tab and select the Service Nomenclature Code (i.e. NBS Code) applicable to the transaction line from a list of pre-defined values (i.e. taken from JLBR_NBS_CODES lookup type).
Additional Information: The Electronic Invoice Line Attributes window can also be accessed directly from the Localizations menu, through the following navigation path: Brazilian Localization > Electronic Invoice > Electronic Invoice Line Attributes
Payables Manual Invoice Entry
When manually entering Payables invoice lines through the Invoice workbench, users can navigate to the Additional Information for Brazil field and select the Service Nomenclature Code (i.e. NBS Code) applicable to the invoice line from a list of pre-defined values (for example, taken from JLBR_NBS_CODES lookup type).
The import process will attempt to import the Service Nomenclature Code (NBS Code) that is populated into the Global_Attribute2 in the AP_INVOICE_LINES_INTERFACE table. If no value is populated, the system will not attempt to default the NBS Code from the corresponding Item ID being imported at Payables invoice line level.
Accounts Receivable Open Interface
To import the NBS Code (Service Nomenclature Code) attribute at transaction line level, users must populate the correspondent column (NBS_CODE) in JL_BR_INTERFACE_LINES_EXTS table.
Please refer to Brazil Appendices I and II for details.
Copy Transactions
This process makes use of the Open Interface infrastructure which in turn uses the JL_BR_CUST_TRX_LINES_EXTS extension table, where the new attribute reside. The new line level attribute and respective value will be copied from the source transaction to target transaction.
Create Invoice API
This process makes use of the Open Interface infrastructure which in turn uses the JL_BR_INV_API_TRX_LINES_T temporary extension table, where the new attribute has been added. Once the invoice is successfully created by the Create Invoice API, the new attribute would reside in the JL_BR_CUST_TRX_LINES_EXTS table.
Additional Information: When importing NBS Code from Legacy Systems, you have to also load the Industry Specific and Import Content related attributes into the extension table JL_BR_INTERFACE_LINES_EXTS and populate the link column JL_BR_INTERFACE_LINK_ID with the ROWID of the corresponding row from RA_INTERFACE_LINES_ALL.
Please refer to Brazil Appendices I and II for more information about the import process and respective data model changes introduced by this project.
Accounts Receivables Open Interface
To import the Import Content related attributes at transaction line level, users must populate the newly added fields in JL_BR_INTERFACE_LINES_EXTS.
Please refer to Brazil Appendices I and II for details.
Copy Transactions
This process utilizes the Open Interface infrastructure which uses the JL_BR_INTERFACE_LINES_EXTS extension table; the two new attributes reside in this table. The new line level attributes and respective values are copied from the source transaction to target transaction.
Create Invoice API
This process utilizes the Open Interface infrastructure which in turn uses the JL_BR_INV_API_TRX_LINES_T temporary extension table; the two new attributes have been added to this table. Once the invoice is successfully created by the Create Invoice API, these two new attributes would reside in the JL_BR_INTERFACE_LINES_EXT table.
Additional Information: When importing invoice information from Legacy Systems, you must load the Industry Specific and the Import Content related attributes into the extension table JL_BR_INTERFACE_LINES_EXTS and populate the link column JL_BR_INTERFACE_LINK_ID with the ROWID from RA_INTERFACE_LINES_ALL.
Please refer to Brazil Appendices I and II for more information about the import process and respective data model changes introduced by this project.
These are new requirements for the Electronic Fiscal Document (NF-e), version 3.10. The technical notes 2015.002 and 2015.003 complement the XML layout.
Fiscal partners are responsible for the interface and communication with the tax authority. The major requirement for Oracle is to support additional attributes required for this process and to store data regarding Electronic Invoicing.The new fields in the NF-e XML to comply with the Technical Notes 2015.002 and 2015.003 are listed below:
SEFAZ defined values for the IPI code according to the legal framework, including the IPI exemption code related to the Olympics 2016. Also it was set a new ICMS Exemption Reason related to the Olympics 2016;
New ICMS tax calculation rules;
New field: ICMS calculation basis of the recipient State;
New field: ICMS Internal rate of the recipient State;
New field: ICMS Interstate rate (The ship from and ship to locations are in different states);
New field: Provisional percentage to be applied on the value of the ICMS for sharing between the two states;
New field: Sharing ICMS value due to the recipient State;
New field: Sharing ICMS value due to the sender State;
New field: new field to inform the Identification Code of Tax Replacement (CEST).
1 - Define CEST Codes (Lookup Codes)
Use the Lookups window to manually define CEST Codes under a seeded lookup type, called JLBR_CEST_CODES.
2- Associate CEST Codes to Item Templates
Under the Global Descriptive Flexfield group, you can now associate a Tributary Substitution Identification Code (CEST Code) to an item template, thus standardizing and expediting the item creation process.
3 - Associate CEST Code to Inventory Items
You can associate a Tributary Substitution Identification Code (CEST Code) to an inventory item, belonging to a Brazilian inventory organization. That association ultimately defaults onto the Receivables Transaction Line created for that item.
1 - Enter CEST Code
When manually entering Receivables transaction lines through the Transactions workbench, users can navigate to the Electronic Invoice Line Attributes window from the Special Menu option. Select the Other Attributes tab and then enter or update the Tributary Substitution Identification Code (CEST Code) by selecting a value from a list of pre-defined values ( taken from JLBR_CEST_CODES lookup type).
It is important to highlight that the system will default the CEST Code that is associated with the inventory item. The user can change the defaulted value, if needed.
The Electronic Invoice Line Attributes window can also be accessed directly from the Localizations menu, via the following navigation path: Brazilian Localization > Electronic Invoice > Electronic Invoice Line Attributes
2 - Viewing ICMS Attributes
When manually entering Receivables transaction lines via the Transactions workbench, users can navigate to the Electronic Invoice Line Attributes window from the Special Menu option. Select the ICMS Attributes tab to visualize the attributes that are populated by the tax calculation process. They cannot be updated.
The tax calculation process is triggered when the transaction is saved or completed.
When creating transactions with Autoinvoice, you must enter a record in the JL_BR_CUST_TRX_LINES_EXTS table to trigger the tax calculation process; it will consequently populate the newly introduced ICMS Attributes.
For a manual transaction creation, navigate to the Electronic Invoice Line Attributes window to create the attributes.
1 - Accounts Receivables Open Interface
To import the CEST Code attribute at the transaction line level, populate the correspondent column (CEST_CODE) in the JL_BR_INTERFACE_LINES_EXTS table.
2 - Copy Transactions
This process uses the Open Interface infrastructure which in turn uses the JL_BR_CUST_TRX_LINES_EXTS extension table where the new attribute resides. The new line level attribute and respective value is copied from the source transaction to the target transaction.
3 - Create Invoice API
This process uses the Open Interface infrastructure which in turn uses the JL_BR_INV_API_TRX_LINES_T temporary extension table where the new attribute was added. After the invoice is successfully created by the Create Invoice API, the new attribute will reside in the JL_BR_CUST_TRX_LINES_EXTS table.
When importing the CEST Code from Legacy Systems, you also must load all other applicable attributes (examples: Industry Specific, Import Content) into the extension table JL_BR_INTERFACE_LINES_EXTS and populate the link column JL_BR_INTERFACE_LINK_ID with the ROWID of the corresponding row from RA_INTERFACE_LINES_ALL.
In Brazil, Companies are required to report electronically their accounting transactions and transactional information from sales and purchases operations to comply with the Accounting Public Digital Bookkeeping System (SPED) requirements.
The SPED text file is comprised of blocks, registers, and fields. The file is generated for a given bookkeeping type. Based on the bookkeeping type, some registers may be mandatory or optional.
Companies can provide one SPED text file per monthly accounting period, instead of multiple accounting periods per file. The accounting periods correspond to regular monthly periods and the fiscal year closing period. Depending on the reporting period (regular month or fiscal year closing), certain registers may become mandatory or optional. After the SPED text file is generated, but before submission to Federal tax authority, it has to be through the software provided by the tax authority called PVA (Validation and Signing program).
The SPED text file comprises the following blocks:
| Block | Description |
|---|---|
| O | Opening, Identification and References |
| I | Accounting Journals |
| J | Accounting Statements |
| K | Economic Conglomerates |
| 9 | Control and Flat File Closing |
Companies must report transactions using a referential chart of accounts.
Submission options are:
| Block Type | Description |
|---|---|
| G | Daily Book (complete, without auxiliary bookkeeping) |
| R | Daily Book Summarized (with auxiliary bookkeeping) |
| A | Auxiliary Daily Book with summarized bookkeeping |
| B | Daily Balance and Balance sheet |
| Z | Auxiliary Major Book |
Valid bookkeeping combinations are:
| Block Type | Description | Combination |
|---|---|---|
| G | Daily Book (complete, without auxiliary bookkeeping) | No auxiliary bookkeeping or Z |
| R | Daily Book Summarized (with auxiliary bookkeeping) | A or Z |
| A | Auxiliary Daily Book with summarized bookkeeping | N/A |
| B | Daily Balance and Balance sheet | A or Z |
| Z | Auxiliary Major Book | N/A |
SPED Solution Overview
You can generate the final text file with information available in Oracle eBusiness Suite Release 12.0.5 and above for Bookkeeping types G, R, A and B as described above.
To improve performance and allow users to generate the text file as many times as needed, the solution splits the process into two phases: The first one extracts the data (extracts and saves the data in a temporary table) and the second one generates the report output (reads from the temporary table and generates the text file) in the format required.
The solution includes the following concurrent programs, which can be invoked separately:
Brazilian Accounting SPED Data Extract Program
Brazilian Accounting SPED Text File Generation Program
Additionally, there is Brazilian Accounting SPED Financial Statements Data Extraction concurrent program for extracting FSG reports information.
Based on the parameters provided such as Legal Entity, Establishment, Period, Bookkeeping Type, etc. the data extract concurrent program accesses the required information from the various setup and accounting tables and saves the data into a temporary table where its rows and columns represent the SPED registers and fields.
General Ledger Journal Entry
Enter RTF attachments to journals.
Assign Participant Code (GDF) to journal headers or lines.
Concurrent Programs
Brazilian Accounting SPED Data Extract Program: Can be submitted for a Legal Entity or Establishment, Period and Bookkeeping Type.
Brazilian Accounting SPED Financial Statements Data Extraction: Submitted automatically when running the SPED Data Extract program for a Closing Period.
Brazilian Accounting SPED Text File Generation Program: It includes three Reporting Modes (Preliminary, Final and Reprint) and generates the text file as per SPED file structure requirements.
In Brazil, you must enter additional information for your sales orders, such as the operation fiscal code, accessory expenses, fiscal classification code, and transaction condition class. You must also enter additional volume information for your deliveries.
After you enter your order information, the Invoicing workflow activity transfers shipped item information to Oracle Receivables. When the Invoicing workflow activity is finished, you can submit AutoInvoice from Oracle Receivables to import invoice and credit data into Oracle Receivables, which processes the invoices and accounts for revenue.
Related Topics
Invoicing Activity, Oracle Order Management User Guide
Use the globalization flexfield in the Order Organizer window to enter or view additional information about your sales orders and returns.
To enter additional sales order information for a new order:
Navigate to the Order Organizer window.
The Find Orders window appears.
In the Find Orders window, press the New Order button.
The Sales Orders window appears.
In the Sales Orders window, enter your new order information.
Navigate to the Line Items alternate name region.
Navigate to the Shipping alternate name region
In the Warehouse field, enter a warehouse name.
Note: If you selected Latin Tax Handling as your tax method in the System Options window, this field is mandatory and tax is calculated based on the warehouse that you enter for the order line.
Navigate to the Others alternate name region and move your cursor to the Project Number field.
From the Special menu, choose Folders > Show Field.
From the list of values, choose ( ) and press OK.
The Additional Information for Brazil flexfield appears. You can enter or view additional information for your selected item, such as the operation fiscal code, expenses for freight and insurance, and the fiscal classification code and transaction condition class.
Press the OK button.
To enter additional sales order information for a previously entered order:
Navigate to the Order Organizer window.
The Find Orders window appears.
In the Find Orders window, enter an order or order lines to query, or leave the fields blank for all.
Press the Find button.
The Order Organizer window appears.
Select an order and press the Open Order button.
The Sales Orders window appears.
Navigate to the Line Items alternate name region.
Navigate to the Shipping alternate name region
In the Warehouse field, enter a warehouse name.
Note: If you selected Latin Tax Handling as your tax method in the System Options window, this field is mandatory and tax is calculated based on the warehouse that you enter for the order line.
Navigate to the Others alternate name region and move your cursor to the Project Number field.
From the Special menu, choose Folders > Show Field.
From the list of values, choose ( ) and press OK.
The Additional Information for Brazil flexfield appears. You can enter or view additional information for your selected item, such as the operation fiscal code, expenses for freight and insurance, and the fiscal classification code and transaction condition class.
Press the OK button.
Related Topics
Overview of Order Organizer, Oracle Order Management User Guide
Use the globalization flexfield in the Delivery window to enter information about the volume of delivered items.
You can choose to create your delivery first and then add delivery lines to your delivery or you can automatically create deliveries for delivery lines that are not yet assigned to a delivery. You can also choose to automatically create a delivery at pick release by checking the Autocreate Deliveries check box in the Shipping Parameters window.
To enter the volume of delivered items:
Navigate to the Shipping Transactions window.
In the Navigator Tree window, select Data Entry > Delivery Data Entry.
The Delivery window appears.
Enter information for a new delivery, or query an existing delivery.
Navigate to the globalization flexfield.
The Additional Information for Brazil flexfield appears.
Enter volume information for the delivery in the Volume Type, Volume Number, and Volume Quantity fields. This information is printed on the invoice after the Invoicing workflow activity transfers shipping information to Receivables.
Press the OK button.
Save your work.
Related Topics
Creating a Delivery, Oracle Shipping Execution User Guide
Use the Latin Tax Groups window to mark tax categories that you want Oracle Order Management to consider for tax calculations.
To mark tax categories for Order Management consideration:
Navigate to the Latin Tax Groups window.
In the Tax Group field, query a tax group.
Navigate to the Tax Group Details region.
Select a tax category that you want Oracle Order Management to consider for tax calculations.
Check the Calculate in OM check box.
Save your work.