AR Transaction Upload creates new Oracle Receivables transactions – invoices, credit memos and debit memos, with their lines, tax, freight, distributions and sales credits – from Excel, using the standard Receivables invoice API. It creates new transactions only; it does not update or delete existing ones.
When to use it
- Mass-create customer invoices from an external billing system or spreadsheet.
- Load on-account credit memos or debit memos in bulk.
- Migrate historical transactions with no tax recalculation (use the Historical template).
- Create multi-line invoices with manual tax lines or freight lines.
- Load invoices with several GL distributions or split sales credits per line.
Before you start
- Blitz Report is installed and you are signed in to a Receivables responsibility with access to the operating unit.
- The AR period for your GL date is open.
- A valid transaction batch source and transaction type exist for the operating unit.
- The customer account and site (bill-to, and ship-to if used) are active.
Choose a template
| Template | Use it for |
|---|---|
| Default (default) | Standard transaction entry, with tax calculated by E-Business Tax. |
| Historical Transactions Upload | Loading historical transactions with no tax calculation – the amounts are stored as entered. |
Step 1 – Choose a template, set the parameters and download
In Blitz Report, open AR Transaction Upload, choose your template, and set the parameters:
| Parameter | Purpose |
|---|---|
| Operating Unit | The operating unit the transactions are created in. |
| Source | The transaction batch source. |
| Default Transaction Type | Default type for new rows (invoice, credit memo or debit memo). |
| Default Transaction Currency | Default currency for new rows. |
| Default Transaction Date / Default GL Date | Default dates for new rows. |
| Use SalesPersons | Whether to default a salesperson when system options do not require one. |
Run the upload to download and open the Excel file.
Step 2 – Enter the transaction header
A transaction can span several rows. Group the rows into one transaction with the same Upload Trx Identifier; the header is taken from the first row. Enter the Bill To Customer and site, the Transaction Type, Transaction Date and Transaction Currency, and – for manual numbering – the Transaction Number.
Step 3 – Enter the lines
- On each row set the Line Number, Line Type (Line, Freight or Tax) and the line details – item or memo, description, quantity, unit price or amount.
- Tax lines and line-level Freight lines link to a standard line via Link to Line Number.
- Add sales credits and GL distributions per line where needed.
Step 4 – Validate and Save
Click Validate and Save. This checks for missing required values and runs the upload’s row validation (for example, the line-type rules for Line, Freight and Tax lines), then saves the file. Correct anything it flags before continuing.
Step 5 – Upload and view the result
Back in Blitz Report, click Upload and select your saved file. This submits the Blitz Upload request, which creates each transaction through the Receivables invoice API. When it finishes, a result report opens showing each row as success or error.
What’s produced
- New Receivables transactions (invoices, credit memos or debit memos) with their lines, tax, distributions and sales credits.
- A result report listing every row with a status and a message; a rejected transaction is rolled back as a whole.
Common questions
Can I update or delete an existing transaction with this upload?
No. It only creates new transactions. Use standard Receivables functions to adjust or void existing ones.
How do I put several lines on one invoice?
Give every row of that invoice the same Upload Trx Identifier; the header is taken from the first such row and each row adds a line.
Where does the Transaction Number come from?
With automatic numbering the system assigns it. With manual numbering it comes from the Transaction Number column, or from the Upload Trx Identifier if that column is blank.
What does the Historical template do?
It loads transactions with no tax calculation – the amounts you upload are stored as entered. Use it for historical or migration loads.
Do I have to enter a salesperson?
Only when Receivables system options require one. Otherwise the Use SalesPersons parameter controls whether a salesperson is defaulted.
Troubleshooting
| Message | Cause | What to do |
|---|---|---|
| Quantity and Unit Price are required on an invoice line | A Line-type row is missing the quantity or unit price. | Enter both; the upload computes the line amount. |
| Link to Line Number / tax attributes are required for tax lines | A Tax row lacks its link to a standard line, or is missing required tax columns. | Set Link to Line Number to a standard line earlier in the sheet, and fill the required tax columns. |
| Amount, or Quantity and Unit Price, are required for freight lines | A Freight row has neither an amount nor quantity and unit price. | Supply an amount, or a quantity and unit price. |
| Salesperson is required for this operating unit | System options require a salesperson and none was entered. | Enter a valid salesperson. |
| Transaction rejected (API error) | The Receivables API rejected the transaction; the whole transaction is rolled back. | Read the message on the row, correct the data, and re-upload the whole transaction. |