Create Manual Standard Receipts
Become familiar with the current Integrator’s limitations. These will be resolved over time as Oracle improves the underlying web services enabling us to add functionality to this product.
The Receivables Receipts Integrator enables you to create a Standard type of Manual receipt with or without Customer information. Receipts with no Customer information are created as Unidentified receipts: receipts created with Customer information are created as Unapplied receipts.
To create such receipts enter data only into the ‘Receipts’ section.
Relevant Notes:
To create Manual Standard receipts set the Header Upload Action to Create or Create records.
A single row of data is entered for each receipt, either directly into the Integrator sheet or via the Data Form.
Data must be entered into the fields which uniquely identify the receipt, e.g. Business Unit, Receipt Method, Receipt Date, Remittance Bank Account Number, etc. The entry of Customer data is optional.
The Integrator has several read-only columns designed to assist the user when processing data. Values will be defaulted into some of these columns during the Validation process, e.g. Remittance Bank details and Taxpayer Identification Number, while others will be populated by the upload and download processes. The read-only columns are coloured grey.
Once all required receipt information is entered, the upload process can be initiated. The Integrator will process the receipts in batches of 50. For details on uploading refer to the Upload section.
Successful uploads will return an ‘Accepted’ status at the Header level and return Receivables Standard Receipt information from the web service.
Rejected uploads will return messaging.
More information on how to reprocess these records can be found here.
Points to Note:
1. Receipt Method and Remittance Bank Account Number
The form LOV for this field works slightly differently from the LOV in the Oracle UI.
The Integrator LOV shows distinct values for the Receipt Method field. If you have defined multiple Remittance Banks under one Receipt Method for a specific Business Unit the LOV for the Remittance Bank field will enable you to select the correct value.
For example, in the following screenshot there are 5 different Receipt Methods available for the Business Unit selected. The ‘>’ symbol alongside the ‘Check (Directly/No Remit)’ value indicates that there are multiple Remittance Bank Accounts associated with this Receipt Method for the Business Unit.
If you select a Receipt Method with multiple Banks, you can then use the Remittance Bank Account Number’s LOV to select the appropriate value:
Selecting this value, will default the rest of the data from the Remittance Bank LOV into the Data Form’s fields:
2. Receipt ID
It is possible to create ‘duplicate’ receipts in Oracle where several of the elements of the receipt are the same, e.g.:
If you wish to update a receipt the suggested steps are for you to download it and then process it as required. Having the Receipt ID available enables the user and the Integrator to distinguish between the duplicate receipts when making the updates.
3. Customer Bank Account Number
We are currently unable to provide an LOV for the Customer Bank Account Number due to the fact that these numbers can be automatically masked by Oracle and the webservice does not recognise masked numbers. Therefore, the original Customer Bank Account Number (i.e. the unmasked number) has to be manually entered into this field: there is no validation on the data entry. However, the API will reject the record if the entered Customer Bank Account Number is invalid.
When a record with a Customer Bank Account Number is uploaded, the associated Customer Bank and Customer Bank Branch details will default into the read-only columns in the Integrator.
When the receipt is downloaded, if the installation has masking applied, the masked value will be downloaded into the Masked Customer Bank Account Number field: if no masking applies, the original Customer Bank Account Number will be downloaded into the Masked Customer Bank Account Number field. No value will be downloaded into the Customer Bank Account Number field.
Attachments
Attachment functionality is not included in this version of the Receivables Receipts Integrator.
Refer to section:
