.svg)
Oracle JD Edwards EnterpriseOne UAE E-Invoice processing with Azdan
Review and issue an invoice in Oracle JD Edwards EnterpriseOne, track it in Azdan UAE E-Invoice, then return to the original accounting record to finish your checks.
The connection is already set up. This guide follows EnterpriseOne 9.2 Accounts Receivable. Use the invoice already created by your sales, project or service process when one exists. Oracle’s public 9.2 examples use sample companies, older dates and foreign-currency values. Menu tasks and document types follow your assigned role and processing options.
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 the customer’s existing invoice
Open Customer Ledger Inquiry (P03B2002). Select the company and customer, then narrow the search by invoice number or date. Check whether the sale already has an invoice before adding a new one.
For a finance-led invoice that does not already exist, open Standard Invoice Entry (P03B11) from the task available to your role. Keep sales-order, contract and other source invoices in their existing workflow.
2. Confirm company, customer and document details
- Confirm the customer address-book number and company. Check the legal billing address and tax-registration information used by the connection.
- Review Invoice Date, G/L Date, Currency, payment terms and due dates. Check exchange-rate treatment where the document is not in the company’s base currency.
- Keep the final Document Number / Type / Company combination. The number alone may not uniquely identify the record. RI is a common invoice type; use your company’s approved type.
- Record the customer purchase order and the invoice reference needed to trace the underlying sale.
3. Review pay items, tax and revenue coding
Check each pay item’s gross amount, taxable amount, tax amount, tax rate/area and tax explanation code. Confirm discounts and due dates. Compare the invoice with the supporting sales lines or billing schedule.
A pay item is not necessarily a product line. For an invoice generated by Sales Order Management or another module, verify the underlying descriptions, quantities and prices that your connection uses for the e-invoice.
Review the G/L distribution and the balance of the entry before saving. If your company uses Speed Invoice Entry, the same review includes the revenue accounts and amounts shown on that form.
4. Save, approve and post the invoice batch
Save the invoice and retain its document identifiers and batch number. Review the batch total and resolve any out-of-balance or validation errors. Obtain the batch approval required by your company, then follow the normal posting process.
Check the posting result and re-query the document. If the batch failed, correct the cause and follow the authorized reposting process. Do not duplicate the invoice to work around a posting error.
Complete the configured e-invoice release. A batch posting result or customer payment-status code does not confirm receipt by Azdan. Record the final document number, type and company for the portal search.
5. Let the connection prepare the e-invoice
After the configured invoice/batch release, your existing connection prepares the electronic document from Oracle JD Edwards EnterpriseOne. 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 JD Edwards EnterpriseOne | What to match in Azdan |
|---|---|
| Document Number, Type, Company and invoice date | The final invoice number, issue date and due date. Use the issued number rather than a draft reference. |
| Company and customer address-book/billing details | The correct seller and buyer, legal names, addresses and electronic delivery identifiers. |
| Source billing lines, pay items and tax details | Descriptions, quantities, units, prices, discounts and the taxable amounts. |
| Currency, taxable amount, tax and original gross amount | The invoice currency, tax breakdown and original document total. |
| Order references and payment terms | The 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 JD Edwards EnterpriseOne invoice reference, together with its company and document type. 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 JD Edwards EnterpriseOne 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.
| Result | What to check |
|---|---|
| Validation | Passed 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.
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 JD Edwards EnterpriseOne. 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 JD Edwards EnterpriseOne 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. Enter and follow a credit memo
Review the original document in Customer Ledger Inquiry, including receipts and earlier credits. Create the approved credit through the source process for that invoice. For a direct A/R credit, Standard Invoice Entry supports a credit memo with a negative gross amount; RM is a common credit-memo type, subject to your processing options.
- Use the original customer and company and enter the original invoice reference in the field used by your company.
- Check that the amount and tax reverse only the approved portion. Review the opposite-sign revenue distribution and any relevant exchange rate.
- Save, approve and post the credit batch, then retain the credit’s own document number, type and company.
- Apply the credit to the original invoice through the approved receipt/application process if required. Credit application is separate from issuing and delivering the credit document.
Use the Standard Invoice Entry fields shown in step 2 for direct A/R credits. That screenshot is an invoice example, not a completed credit memo.
Complete the required review and release the credit through the existing Oracle JD Edwards EnterpriseOne 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 JD Edwards EnterpriseOne invoice
Return to Customer Ledger Inquiry and find the original Document Number / Type / Company. Open its detail and check the original gross amount, current open amount and batch reference.
- 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 JD Edwards EnterpriseOne 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