Oracle E-Business Suite UAE E-Invoice processing with Azdan

Review and issue an invoice in Oracle E-Business Suite, track it in Azdan UAE E-Invoice, then return to the original accounting record to finish your checks.

R12.2 Receivables · Classic Forms · For accountants · Updated 8 November 2026

The connection is already set up. This guide follows R12.2 Receivables, through the Transactions workbench. Use the invoice already created by your sales, project or service process when one exists. The screenshots are public R12 classic Forms examples. They use older sample dates and non-UAE currencies; local responsibilities, menu labels and tax settings can differ.

Select a screenshot to open it at full resolution.

Follow your company’s existing approval, e-invoice release and result-recording process. The screenshots show the accounting screens; the Azdan release action and returned-result fields depend on your company’s configuration.

1. Open Transactions in the correct responsibility

Select the Receivables responsibility for the selling company. Open Transactions > Transactions and use Find to search for the existing invoice. Check the operating unit and customer as well as the number. Use a new transaction only if the sale has not already been invoiced.

2. Review the transaction header and customer

• Check Source, Class, Type, transaction Date, GL Date, Currency and the responsible legal entity. Keep the numbering assigned by the approved source.
• Confirm the Bill To customer, account number, location and legal address. Review Ship To, Sold To and Paying Customer where they are used.
• Match payment terms, due date and customer references to the approved sale. Check tax registration and delivery identifiers in the records used by the connection.
• For an imported invoice, correct the originating process where appropriate. Do not bypass an import issue by entering the same sale manually.

3. Check line items, tax and distributions

Choose Line Items. Review each item or description, unit of measure, quantity, unit price and amount. Open the tax details and confirm the treatment and calculated tax. Review freight and additional charges where applicable.

Choose Distributions when you need to review revenue and receivable allocations. Reconcile the original line amount, tax, freight and charges to the invoice total. Do not use the remaining balance after receipts as the amount to send.

4. Complete the transaction and review accounting

Save the invoice, resolve incomplete data and obtain the required approval. Choose Complete when authorized. Re-query the invoice to confirm the completed state and final transaction number.

Follow your normal Create Accounting process. Use Tools > View Accounting where available to review the accounting entries. Completion, final accounting and general-ledger posting are distinct stages; check the stage required by your company’s release rule.

Release the invoice through the existing Azdan process. A completed checkbox, accounting entry or PDF does not by itself confirm electronic delivery.

Oracle R12.2 Receivables: transactions, completion, accounting and credit memos

5. Let the connection prepare the e-invoice

After the configured Receivables release, your existing connection prepares the electronic document from Oracle E-Business Suite. You continue to work with the original invoice. Do not enter the same sale again in Azdan.

The connection translates the accounting record into the format used for electronic exchange. It carries the invoice details into the appropriate fields; it should not change the agreed sale, tax treatment or document total.

Azdan validates the document before delivery. If a required value is missing or the figures do not reconcile, use the validation message to identify what needs correcting. A PDF is a readable copy; the connection also sends structured invoice data.

6. Find the invoice in Azdan

Open Invoicing > Transactions > Outbound in the Azdan portal. Search using the Oracle E-Business Suite final transaction number. Open the matching transaction.

• Confirm the selling company and buyer before comparing amounts. The same number may appear in more than one company or document series.
• Match the invoice date, currency, VAT and document total. Compare the original invoice amount, rather than the remaining customer balance after payments or credits.
• Keep the Azdan transaction reference with the invoice so colleagues can find the same record.

If you cannot find it, clear restrictive filters and check that the Oracle E-Business Suite invoice completed its required approval and release. If it remains missing after your normal processing interval, give the administrator the company, invoice number and release time. Keep the original invoice; creating a second one can duplicate the sale.

7. Review delivery, the receiver response and FTA reporting

Open the transaction details and read each outcome separately. A successful result in one stage does not close an issue in another stage.

The results may arrive at different times. Retain the available invoice, response and reporting records under your company’s filing process. Record any outstanding result and who will follow it up.

Read the Azdan transaction-status guide

8. Resolve an exception without duplicating the invoice

In Azdan Transactions, open Filters, choose Failed or rejected, set the date range and apply the filter. Review In progress separately. Open an affected transaction and read its message before taking action.

• Incorrect customer or invoice information: Compare the named field with Oracle E-Business Suite. Updating a customer master does not necessarily change an invoice already issued or prepared for sending.
• Failure before delivery: Have the accounting owner approve the correction, check whether any attempt already reached the receiving provider, then use your configured correction and retry process.
• Still in progress: Allow scheduled processing and automatic retries to complete. Avoid repeated submissions. Escalate a stalled transaction with its invoice number, Azdan reference, exact message and time.
• Receiver or FTA rejection: Assign the message to the responsible colleague and follow the required correction route. A delivered invoice can still have an unresolved receiver or reporting result.

Do not delete, cancel or recreate a posted Oracle E-Business Suite invoice simply to refresh an e-invoicing result. If the original accounting document must change, the finance owner should decide whether a credit note or another approved correction is required.

9. Create a credit memo against the invoice

Open Credit Transactions from the Receivables Transactions menu, or use the credit action from the original transaction where your responsibility provides it. Find the completed invoice and verify the operating unit, number and customer.

• Choose the approved credit source and type; enter the credit date, GL date, reason and reference.
• Use Credit Lines for a line-specific correction. Review the amount or percentage credited and the resulting tax; consider credits already issued.
• For a full remaining-balance credit, use the appropriate credit-balance action only after checking the outstanding amount and receipt applications.
• Save, complete and account for the credit under your normal controls. Keep the credit number and the link to the original invoice.

Complete the required review and release the credit through the existing Oracle E-Business Suite connection. Search for its own number in Azdan, confirm the original invoice reference and credited amounts, then repeat the status checks in steps 6–8. Keep both documents and their results together. Applying a credit to the customer balance or issuing a refund is a separate accounting task.

10. Return to the original Oracle E-Business Suite invoice

Return to Transactions > Transactions, query the original invoice and check its transaction details and credit activity. Use Account Details when you need to reconcile the customer’s invoices, credits and receipts.

• Match the company, buyer, invoice number, currency, VAT and original total to the Azdan transaction.
• Open the integration result fields, linked record, note or attachment used by your company. Check the Azdan reference, latest outcomes and last update time.
• If the returned information is missing or older than Azdan, ask the administrator to investigate the return update. Keep the transaction reference and latest portal result available.
• Check any related credit note under its own number. Review payment, allocation and refund records separately from electronic delivery.

Finish the review when the accounting record and Azdan transaction match, the amounts agree, the returned results have been checked and every unresolved issue has an owner.

The public Oracle E-Business Suite screens in this guide show standard accounting functions. Your company’s existing configuration determines the release action and where Azdan results appear.

Related guides

Azdan UAE E-Invoice documentation