Microsoft Dynamics 365 Finance UAE E-Invoice processing with Azdan
Review and issue an invoice in Microsoft Dynamics 365 Finance, 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 Accounts receivable free-text invoices in the Finance cloud application. Use the invoice already created by your sales, project or service process when one exists. The screenshots show Microsoft and public training examples in demo legal entities, using EUR or USD. Sales-order invoices stay in their existing order-invoicing process.
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 All free text invoices
Confirm the active legal entity in the top bar. Go to Accounts receivable > Invoices > All free text invoices. Search for the existing invoice; choose New only when a finance-led invoice is needed for a sale that is not already invoiced.

2. Check the customer and invoice header
- Review Customer account and Invoice account. The invoice account can be different from the ordering customer, so confirm the legal buyer and billing address.
- Check the invoice date, due date, currency, payment terms and payment method. Confirm any required exchange-rate date.
- Review the customer tax-registration information and delivery identifiers already used by your connection. Keep the purchase-order and service-period references with the invoice.
- Confirm the correct legal entity and financial dimensions before posting. Follow your approval process for credit warnings or changes to the billing customer.
3. Review invoice lines and sales tax
Under Invoice lines, check the description, main account, quantity, unit price and line amount. Review Sales tax group and Item sales tax group for every line; their combination affects the tax calculation.

Open Sales tax to review the calculated tax and Totals to reconcile the document. Check any charges and accounting distributions. Compare the amounts with the approved sale; do not copy the foreign tax groups shown in the examples.
4. Post and retain the final invoice number
Save, complete the required review and select Post when authorized. Review the posting dialog and confirm the appropriate options. After processing, read the completion message and check the invoice’s accounting status.

Record the final invoice number and original amount. If posting fails, resolve the reported cause before releasing the record. Complete your configured Azdan release; the Finance posting message does not establish e-invoice delivery.
5. Let the connection prepare the e-invoice
After the configured invoice posting/release event, your existing connection prepares the electronic document from Microsoft Dynamics 365 Finance. 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 Microsoft Dynamics 365 Finance | What to match in Azdan |
|---|---|
| Final Invoice number, date and due date | The final invoice number, issue date and due date. Use the issued number rather than a draft reference. |
| Legal entity, customer account and invoice account | The correct seller and buyer, legal names, addresses and electronic delivery identifiers. |
| Invoice lines, tax groups, calculated tax and charges | Descriptions, quantities, units, prices, discounts and the taxable amounts. |
| Currency and original posted invoice totals | 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 Microsoft Dynamics 365 Finance final invoice number and legal entity. 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 Microsoft Dynamics 365 Finance 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 Microsoft Dynamics 365 Finance. 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 Microsoft Dynamics 365 Finance 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. Prepare a credit and link the original invoice
Review the posted original and any settlements or earlier credits. For a free-text credit, use the approved free-text credit process with negative line amounts. Keep the same invoice account and use the appropriate tax groups so the intended amount and tax are reversed.

Where the configured Credit invoicing action is available, select the original invoice and enter the reason code/comment. Otherwise, use the original-invoice link already provided by your company’s correction process. Verify the reference before posting.
Review the total, approve and post the credit. A sales-order correction may require a return order or another sales process; do not substitute a free-text credit if it would leave inventory or order balances incorrect. Settlement and any cash refund are separate from issuing the credit.
Complete the required review and release the credit through the existing Microsoft Dynamics 365 Finance 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 Microsoft Dynamics 365 Finance invoice
Return to All free text invoices, select the original posted invoice and check its final number, invoice account, currency and original total. Use the invoice journal or customer transactions when you need to review the voucher, settlement or linked credit.
- 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 Microsoft Dynamics 365 Finance 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