Oracle Fusion Receivables: Import AutoInvoice rejects lines
Oracle Fusion Receivables AutoInvoice lines rejected how to find and fix errors
Also searched as
- Import AutoInvoice errors Fusion
- RA_INTERFACE_ERRORS_ALL Fusion Cloud
- Fusion AutoInvoice invalid transaction type batch source
- Manage AutoInvoice Exceptions Fusion
Short answer
Import AutoInvoice validates each interface line against transaction sources, types, customers, terms, accounting rules and tax, then writes failures to an error table instead of creating the transaction. Open the AutoInvoice exceptions for the batch, fix the data on the interface lines or the setup behind it, and resubmit the import.
Applies to: Oracle Fusion Cloud Receivables, including billing integrations from SCM and external systems
Find and clear rejected lines
- 1Run Receivables > Billing > Import AutoInvoice (or review the scheduled run) and open the output of the Import AutoInvoice process.
- 2Open the Import AutoInvoice Execution Report and note the batch source, the number of lines rejected and the error messages.
- 3Use the Manage AutoInvoice Exceptions task to see each rejected line with its message and the interface line attributes.
- 4Correct the value in place when the task allows editing, or correct the source data and reload through FBDI or the feeding integration.
- 5Check the batch source in Manage Transaction Sources: invoice numbering, allowed transaction types and whether validation of reference fields is on.
- 6Confirm the transaction type, payment terms, bill-to customer account and site, and revenue accounting rule exist and are active for the business unit.
- 7Resubmit Import AutoInvoice for the same batch source and batch name, then verify the created transactions in Manage Transactions.
What AutoInvoice does with each line
AutoInvoice reads rows from the interface tables, chiefly RA_INTERFACE_LINES_ALL, with distributions and sales credits in their companion tables. It groups lines into transactions using the grouping rule on the batch source, validates each reference, derives defaults and creates the invoice, credit memo or debit memo. A line that fails any validation is not created; the error is written to RA_INTERFACE_ERRORS_ALL with a message and the offending column.
Because the whole transaction is grouped, one bad line can reject the other lines that share its grouping attributes. That is why a single missing account on line three can make a ten-line invoice disappear. The execution report counts rejected lines, but the business impact is whole invoices not billed.
The usual causes
Transaction source and type. The batch source named on the interface line must exist in the business unit, and the transaction type must be valid for that source. A typo in the source name or a type that is inactive produces an invalid reference message.
Customer and site. The bill-to account or site number must exist and be active, and the bill-to site must be usable for the business unit. Integrations that pass the customer by number when the target expects an internal identifier are a recurrent trap.
Accounting. When revenue accounts are not supplied, AutoInvoice derives them from AutoAccounting rules. If a rule cannot derive a segment, or the resulting combination fails cross-validation, the line is rejected. Missing or end-dated accounting rules for deferred revenue have the same effect.
Terms, currency and rates. Payment terms must be active, and a foreign currency invoice needs a conversion rate for the transaction date and rate type. Missing daily rates are often only noticed at month end.
Tax. If tax determinants are missing, tax line creation fails even though the invoice lines are fine.
Reading the interface tables directly
When the exceptions screen is not enough, query the interface tables through a BI Publisher data model or the supported reporting path your environment allows. Join errors to lines on the interface line ID and group by message text to see which error dominates. Direct database access is generally not available in Fusion, so use reports and the exceptions task rather than expecting SQL*Plus.
Most volume problems are systemic: one upstream system sending a retired transaction type, or one new business unit with no transaction source defined. Grouping rejects by message and batch source usually points to the setup gap in a few minutes.
-- BI Publisher data model sketch (names indicative, verify in your pod) SELECT l.interface_line_attribute1, e.message_text, COUNT(*) FROM ra_interface_lines_all l JOIN ra_interface_errors_all e ON e.interface_line_id = l.interface_line_id WHERE l.batch_source_name = :batch_source GROUP BY l.interface_line_attribute1, e.message_text
Resubmitting safely
Rejected rows stay in the interface until corrected or purged, and a resubmit picks up the unprocessed rows. Check the Purge Interface Tables option on the batch source: if purging is on, rejected rows can be removed and you must reload them from source. Confirm what your source setting does before resubmitting a large run.
Do not resubmit blindly after a partial success. Reconcile the number of transactions created against the source system document count first, to avoid duplicate invoices when a feeding job also retries on its own.
Common pitfalls
- !Fixing the rejected line but not the batch source or AutoAccounting rule, so the next run rejects again.
- !Resubmitting a batch after partial success without reconciling, which can duplicate invoices when the upstream also retries.
- !Ignoring grouping: correcting one line while its siblings in the same group remain rejected.
- !Missing daily conversion rates for the transaction date and rate type on foreign currency billing.
- !Assuming rejected rows are retained when the batch source is set to purge the interface.
How an ERP-grounded AI assistant handles this
A grounded assistant such as ERPray can group the rejected interface lines by message and batch source, then tell you that most rejections point to one inactive transaction type or one customer site, citing the rows. Because it is read-only by default and shows its query, finance can verify the finding. Corrections to interface data or setup still go through your normal change control.
Frequently asked questions
Where do I see why an AutoInvoice line was rejected?
Open the Import AutoInvoice Execution Report from the scheduled process output, then use the Manage AutoInvoice Exceptions task. Each rejected line carries a message and the attribute that failed. The underlying messages live in the interface errors table.
Why did a whole invoice disappear when only one line was bad?
Lines are grouped into a transaction using the grouping rule on the batch source. If one line in the group fails validation, the transaction cannot be created cleanly, so related lines are rejected with it. Fix the failing line and resubmit the batch.
Can I just edit the interface data and rerun?
Yes for many fields through the exceptions task, but check the source's purge setting and your upstream retry logic first. If the feeding system will also reload the data, edit at the source to avoid a mismatch or duplicates.
Why does AutoInvoice fail on revenue accounts?
When accounts are not supplied, AutoAccounting derives them. If a rule is missing, a segment cannot be derived, or the combination fails cross-validation or is end-dated, the line is rejected. Review AutoAccounting setup for the business unit.
Related
Fix FBDI Import Failures From Interface Table Validation Errors
When a Fusion FBDI import job errors out, the cause is almost always bad data in the interface tables (an invalid value set, a wrong date format, or a missing required column), not the ESS job itself. Open the process's Interface Errors Report or the Correct Import Errors spreadsheet to see the exact rejected rows and reason codes, fix the source data, and resubmit from the interface tables instead of re-running the whole FBDI load.
How-toOracle Fusion Period Close: A Practical Checklist
Closing a Fusion GL period cleanly means closing every feeder subledger first (Payables, Receivables, Costing, Fixed Assets), running Create Accounting to post everything to GL, reconciling subledger-to-GL balances, and only then setting the GL period status to Closed - not Close Pending, which still allows adjustments. Close Monitor gives a single dashboard of every subledger's close status instead of checking each module separately.
Error fixClear An Oracle Fusion ESS Job Stuck In Blocked Status
A Blocked status on an Oracle Fusion Enterprise Scheduler (ESS) job almost always means an earlier instance of the exact same job is still running or stuck, and the job definition does not allow simultaneous requests. Find and finish, or cancel, the earlier request first; only then does the Blocked request move to Running.
How-toConnect Oracle Integration Cloud (OIC) To Fusion ERP
OIC connects to Fusion ERP primarily through the prebuilt ERP Cloud Adapter, which wraps Fusion's REST and SOAP web services with OAuth-based authentication and pick-list discovery of available business objects and operations, instead of you hand-building every REST call. Use the adapter for standard integrations; drop to a generic REST or SOAP adapter only when the ERP Cloud Adapter does not yet expose the specific service you need.
How-toOTBI vs BI Publisher: Which One Should You Use
Use OTBI when a business user needs ad hoc, self-service, real-time analysis with no fixed layout. Use BI Publisher when you need a pixel-perfect, scheduled, high-volume, or externally distributed document such as an invoice, check, or statutory report. Most Fusion implementations end up using both, not one instead of the other.
How-toPaginate And Authenticate Oracle Fusion REST API Calls Correctly
Oracle Fusion Cloud REST APIs authenticate with HTTP Basic Authentication, an integration user's credentials, over HTTPS by default, and paginate with limit and offset query parameters rather than a page number. Loop on the hasMore flag in the response until it returns false to retrieve a full result set.
AI for ERPFusion Cloud ERP AI: OCI Generative AI Service vs. a Private LLM
Oracle's OCI Generative AI Service is a real option for Fusion Cloud ERP, but not the only one. Compare it honestly against a private LLM for sensitive data.
Stuck on Oracle Fusion Cloud ERP?
Talk to engineers who work inside Oracle Fusion Cloud ERP every week, and who build private AI that answers these questions from your own ERP data.