UAE E-INVOICE
DOCUMENTATION
Integrations

Oracle Fusion Cloud ERP UAE E-Invoice processing with Azdan

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

Oracle Fusion Cloud ERP · Receivables · For accountants · Updated 8 November 2026

The connection is already set up. This guide follows Receivables billing in the Fusion cloud application. Use the invoice already created by your sales, project or service process when one exists. The full-screen examples come from Oracle’s Receivables tutorial and a public September 2025 credit-memo walkthrough. They show different demonstration companies and themes. Use your own UAE customer, currency and tax settings.

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. Find or create the Receivables invoice

Open Receivables > Billing. From the task panel, use Manage Transactions to find an existing invoice by business unit, transaction number or customer. Confirm the business unit before opening the result.

Manage Transactions: the full search screen, with business unit, transaction number, class and bill-to customer filters. Public Fusion training example.
Manage Transactions: the full search screen, with business unit, transaction number, class and bill-to customer filters. Public Fusion training example. Source screenshot.

If the sale has not been invoiced, choose Create Transaction and select Invoice as the transaction class. Use the business unit and transaction source assigned to the sale. Leave automatic numbering to Fusion when your source supplies the number. Do not duplicate an invoice imported from Order Management, Projects or another billing process.

2. Check the buyer and invoice dates

Create Transaction: Invoice in Oracle’s official tutorial. The full screen includes the business unit, source, type, dates, currency, buyer, customer sites and payment terms.
Create Transaction: Invoice in Oracle’s official tutorial. The full screen includes the business unit, source, type, dates, currency, buyer, customer sites and payment terms. Source screenshot.
  • Confirm Bill-to Name and Bill-to Site, then review the legal billing address and buyer tax registration in the customer records used by your connection.
  • Check Ship-to Name and Ship-to Site where applicable. The billing and delivery sites can differ.
  • Review Transaction Date, Accounting Date, Currency, Payment Terms and Due Date. Confirm the accounting period and any required exchange rate.
  • Use Show More to review additional customer, payment and reference information. Match the customer purchase order and supporting documents before completion.

3. Review the lines, tax and total

On Invoice Lines, review each description or memo line, quantity, unit of measure and unit price. Check the tax classification and detailed tax calculation. Compare line amounts, discounts, freight and other charges with the approved sale.

Oracle’s invoice-entry example with a Computer Desk line. The page is scrolled to the complete line grid, with quantity, unit price and amount columns. The USD values are demonstration data.
Oracle’s invoice-entry example with a Computer Desk line. The page is scrolled to the complete line grid, with quantity, unit price and amount columns. The USD values are demonstration data. Source screenshot.

Reconcile the invoice total to the approved billing amount. Check any zero-rated or exempt lines individually and use your company’s configured UAE tax treatment. Review the final tax and total again after completion.

4. Complete the invoice and check its accounting

Save your work, resolve validation messages and complete the required approval. When authorized, use the completion action available on your transaction, such as Complete and Review.

The full Create Transaction screen with the completion menu open. Complete and Review keeps the completed record available for checking.
The full Create Transaction screen with the completion menu open. Complete and Review keeps the completed record available for checking. Source screenshot.
Review Transaction: Invoice 48765. Status is Complete and the final transaction number, tax and total are visible. Completion is a Fusion accounting-document status.
Review Transaction: Invoice 48765. Status is Complete and the final transaction number, tax and total are visible. Completion is a Fusion accounting-document status. Source screenshot.

Reopen the invoice and check Complete, the final transaction number and original total. Completion and accounting are separate checks. Follow the normal Receivables accounting process and review its result when your role requires it. If an approval workflow controls completion, leave the transaction with its approver until authorized.

Use the e-invoice release already configured for your company. Fusion’s Complete status or a printed invoice does not confirm delivery through Azdan.

Oracle: transaction completion controls

5. Let the connection prepare the e-invoice

After the configured transaction release, your existing connection prepares the electronic document from Oracle Fusion Cloud ERP. 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.

Information in Oracle Fusion Cloud ERPWhat to match in Azdan
Transaction Number, Transaction Date and Due DateThe final invoice number, issue date and due date. Use the issued number rather than a draft reference.
Business Unit, bill-to customer and sitesThe correct seller and buyer, legal names, addresses and electronic delivery identifiers.
Invoice Lines, tax details, freight and chargesDescriptions, quantities, units, prices, discounts and the taxable amounts.
Currency, line amount, tax and Transaction TotalThe invoice currency, tax breakdown and original document total.
Order references and payment termsThe customer purchase order, other required references and agreed payment information.

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 Fusion Cloud ERP transaction number. Open the matching transaction.

Azdan Transactions: use Outbound, Search and Filters to find a sent invoice. This reference account has no outbound transactions.
Azdan Transactions: use Outbound, Search and Filters to find a sent invoice. This reference account has no outbound transactions.
  • 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 Fusion Cloud ERP 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.

Azdan reference illustration: validation, delivery, the receiver response and FTA reporting are separate results.
Azdan reference illustration: validation, delivery, the receiver response and FTA reporting are separate results.
ResultWhat to check
ValidationPassed means Azdan’s document checks passed. For a failure, read the field, rule or amount identified in the message.
Delivery (AS4)Delivered confirms delivery to the receiving provider. It does not confirm buyer approval or payment.
Receiver response (MLS)Read the response and any reason supplied. Technical acceptance is separate from commercial approval of the invoice.
FTA Reporting (TDD)Review the reporting result and available response details. Reported means tax data was sent; that label alone does not establish FTA acceptance.

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.

Azdan reference illustration of the exception filter, with Failed or rejected selected.
Azdan reference illustration of the exception filter, with Failed or rejected selected.
  • Incorrect customer or invoice information: Compare the named field with Oracle Fusion Cloud ERP. 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 Fusion Cloud ERP 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 and apply a credit memo

Open the original invoice and review its customer, currency, tax, current balance and earlier credits. Use your company’s approved correction route. When that route uses Credit Transaction, select the original invoice and retain its link while entering the approved credit amount and reason.

The full-screen example below follows the alternative on-account credit memo route: create the credit, complete it, then apply it to the original invoice. Use this route only when it is part of your company’s correction process. Keep the original invoice reference required by your e-invoice connection; applying a customer balance is a separate accounting action.

Create Transaction: Credit Memo. The full screen shows the business unit, source, type, dates, currency, credit reason and customer fields. Public September 2025 training example.
Create Transaction: Credit Memo. The full screen shows the business unit, source, type, dates, currency, credit reason and customer fields. Public September 2025 training example. Source screenshot.
  • Choose Create Transaction in Billing and set Transaction Class to Credit memo. Check the business unit, approved source and type, credit date, accounting date and reason.
  • Select the correct bill-to customer and site. Confirm the currency matches the invoice that will receive the credit.
  • Enter only the approved quantities or amounts being credited. Review the tax reversal, description and original-invoice reference. Follow the sign convention of your configured credit type.
Credit Memo Lines: the training example uses quantity −1 and unit price 35 for a line credit of −35. Review the tax and total before completing the document.
Credit Memo Lines: the training example uses quantity −1 and unit price 35 for a line credit of −35. Review the tax and total before completing the document. Source screenshot.

Complete the required review and use the completion action. Note the final credit memo number and confirm the customer, currency, line amount and tax on the completed record.

Completed credit memo 137766: line credit −35.00, tax −3.24 and total −38.24 USD. This is a separate demonstration record from Oracle’s invoice-entry tutorial above.
Completed credit memo 137766: line credit −35.00, tax −3.24 and total −38.24 USD. This is a separate demonstration record from Oracle’s invoice-entry tutorial above. Source screenshot.

For an on-account credit, open Receivables > Accounts Receivable and choose Manage Credit Memo Applications from Tasks. Find the completed credit memo and open it. Use Add Open Receivables, or the application row provided by your page, to select the intended original invoice.

Apply Credit Memo 137766 to invoice 137765. The full screen shows the customer, currency, applied amount, unapplied amount and application dates.
Apply Credit Memo 137766 to invoice 137765. The full screen shows the customer, currency, applied amount, unapplied amount and application dates. Source screenshot.

Check the application reference, Applied Amount, Application Date and Accounting Date, then save. Confirm the intended amount has been applied and follow your normal accounting process. If only part of the credit is used, reconcile the remaining unapplied amount. A refund is a separate transaction.

Oracle: applying receipts and on-account credit memos

Complete the required review and release the credit through the existing Oracle Fusion Cloud ERP 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 Fusion Cloud ERP invoice

Return to Receivables > Billing > Manage Transactions and open the original invoice in the correct business unit. Review its original total and related credit activity. Open Balance Details from the transaction actions to reconcile the remaining balance.

Balance Details for invoice 137765: original total 114.71 USD, credit 38.24 USD and remaining balance 76.47 USD. The complete Fusion screen remains visible around the dialog. Compare the original invoice amount with Azdan separately from the remaining balance.
Balance Details for invoice 137765: original total 114.71 USD, credit 38.24 USD and remaining balance 76.47 USD. The complete Fusion screen remains visible around the dialog. Compare the original invoice amount with Azdan separately from the remaining balance. Source screenshot.
  • 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 Fusion Cloud ERP 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