AR_RECEIVABLE_APPLICATIONS_ALL

The Create Automatic Receipts process

Verified directly against a practitioner's real walkthrough of the two pages involved (not just general documentation). Page 1 — Create Automatic Receipt (Receivables > Task list > Create Automatic Receipt): enter the selection criteria — Business Unit, Receipt Method, and Receipt Date — and Receivables filters and displays every eligible open invoice matching that combination for review. Two buttons: 'Format' previews the batch (shows exactly which invoices would be included, commits nothing), while 'Format and Submit' commits it — that single click automatically kicks off the underlying Create Automatic Receipt Batch ESS process in the background, creating receipt records in AR_CASH_RECEIPTS_ALL. Page 2 — Manage Receipt Remittance Batches (Receivables > Task list > Manage Receipt Remittance Batches, a separate page reached afterward): search for the batch by its receipt batch ID, verify all the invoices/receipts pulled into the remittance batch, then click Approve — that single click is what starts the actual process of remitting the receipts to the payment service provider (bank or card processor). There is no separate manually-triggered 'Confirm' or 'Remit' button beyond this Approve action. This is the direct debit/EFT/card collection alternative to a customer-initiated manual cash receipt, driven by Receipt Methods, not payment methods.

Where the open receivables balance lives

AR_PAYMENT_SCHEDULES_ALL carries one row per invoice, credit memo and receipt with AMOUNT_DUE_ORIGINAL / AMOUNT_DUE_REMAINING — the basis for aging and DSO. Adjustments (AR_ADJUSTMENTS_ALL) and receipt applications change the remaining amount; receipt state changes are in AR_CASH_RECEIPT_HISTORY_ALL.

CreditMemoService — create and apply an AR credit memo via SOAP

CreditMemoService is the Oracle Fusion Receivables SOAP web service for creating standard credit memos. WSDL: https://<your-fusion-host>:443/fscmService/CreditMemoService?WSDL (POST the SOAP envelope to the same URL without ?WSDL, WS-Security UsernameToken). Primary operation: createCreditMemo, which takes a credit-memo header (business unit, transaction source, transaction type, date, bill-to customer/site, currency) plus a repeating line block (line number, description, amount, tax classification). Application to an existing invoice is expressed on the request by referencing the transaction being credited (the 'apply to' / applied-to-document element on the header or line) — confirm the exact element names against the WSDL for your release. It returns the created credit memo's customer transaction id and number.