You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Receivables REST API enforces contact date validation but UI allows it on backdated invoices

in Receivables & Collections

Hi everyone,

We are currently facing a critical discrepancy between the Oracle Receivables UI and the /receivablesInvoices REST API regarding date validations for Bill-to Contacts. This is currently blocking our automated invoice integrations.

Has anyone else encountered this or found a workaround?

The Business Scenario

We frequently need to create backdated invoices (e.g., TransactionDate = July 30) and associate them with a newly created Bill-to Contact (e.g., Contact created on August 3).

The Discrepancy

1. UI Behavior (Success):If we manually create this transaction in the Receivables UI, the system happily accepts the August 3rd contact on the July 30th invoice. It saves in a 'Complete' status with no errors.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!