Integrations

IFS Cloud UAE E-Invoice processing with Azdan

Prepare an invoice in IFS Cloud, follow its progress in Azdan UAE E-Invoice, then return to the IFS record to complete your checks.

For accountants and accounts receivable teams · Updated 8 November 2026

Your connection, invoice release rules and return of results are already set up. This guide follows Instant Invoice, the finance-led invoice route. Use the invoice already created by your sales, project or service process if one exists. The public IFS Cloud examples use Portuguese company settings, EUR and sample taxes; follow your own company’s UAE tax treatment.

Select a screenshot to open it at full size.

1. Open Instant Invoice

Go to Financials > Customer Invoice > Instant Invoice. Confirm the active company at the upper right. Use Search to find an existing record before adding an invoice for the same sale.

IFS Cloud Instant Invoice in Preliminary status. Search is above the record list; the plus control creates a record. This public example uses Portuguese company settings. Source: IFS documentation.

For a new finance invoice, select New (+). Choose the customer, then save the general information before adding lines. If IFS displays a credit warning, follow your approval process before continuing.

IFS guidance on creating an Instant Invoice

2. Check the customer, addresses and payment details

Review Customer, Invoice Date, Delivery Date, Invoice Address, Delivery Address, Currency and Currency Rate. Expand Payment and Tax Information to check payment terms, the due date, supply country and tax liability.

Confirm that the invoice address is the customer’s legal billing address. Check the buyer’s tax registration and electronic delivery identifier in the records used by your connection.
Use More Information to review the customer reference and other references needed for this sale. Check the purchase order and agreed payment terms against the supporting documents.
Review the values defaulted from the customer. A familiar customer name does not establish that the correct address, currency or tax treatment was selected.
Keep the preliminary reference for internal follow-up. After issue, use the final series and invoice number when searching Azdan.

IFS guidance on invoice header information

3. Review invoice lines and tax

Expand Lines. Add or open each line and review its description, quantity, unit of measure and price. Check the sales object and income information where your company uses them.

IFS Cloud line and total fields on a posted example: Quantity, Price, Price Type, Tax Code, Tax Percent, Gross Amount and Net Amount. This example’s 10% tax is not a UAE tax instruction. Source: IFS documentation.

Check Price Type and the line’s tax code. Use Tax Lines for the detailed tax breakdown, including multiple taxes where applicable. Tax lines are editable while the invoice is Preliminary; review them before issue.

Reconcile the quantities and prices to the approved sale, including any agreed adjustments.
Check net, tax and gross amounts at both line and invoice level. Make sure the figures use the intended currency.
Where the invoice includes different tax treatments, review each affected line. Do not copy the tax rate or country settings from these public examples.

IFS guidance on invoice-line tax

4. Check a work copy, then issue the invoice

Save the invoice and complete the required review. Use Print Work Copy to inspect the draft. A work copy leaves the invoice editable and does not complete issue.

When authorized, select Print Invoice and use your company’s normal output options. In this IFS workflow, final printing creates the accounting voucher and normally changes the invoice to Posted Auth. The voucher then follows your normal general-ledger update process.

If the invoice remains Printed because posting failed, have the accounting owner resolve the posting error. Confirm the final invoice series, number and date; company settings can change the date when final printing occurs.

IFS Cloud issued invoice with its final Series ID, Invoice No and Posted Auth status. Externally Certified is part of the source’s Portuguese example and is not an Azdan acceptance result. Source: IFS documentation.

Complete the e-invoicing release already configured for your company. Neither a printed PDF nor Posted Auth confirms that Azdan received the document.

IFS guidance on printing and accounting effects

5. Let the connection prepare the e-invoice

After the configured invoice release, your existing connection prepares the electronic document from IFS Cloud. 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 IFS Cloud	What to match in Azdan
Series ID, Invoice No and invoice dates	The final invoice number, issue date and due date. Use the issued number rather than a draft reference.
Company, Customer and selected addresses	The correct seller and buyer, legal names, addresses and electronic delivery identifiers.
Invoice lines and tax lines	Descriptions, quantities, units, prices, discounts and the taxable amounts.
Currency, Net Amount, Tax Amount and 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 IFS Cloud final invoice number, including its series where used. Open the matching transaction.

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 IFS Cloud 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.

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.

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.

Incorrect customer or invoice information: Compare the named field with IFS Cloud. 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 IFS Cloud 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 follow a credit invoice

Open the original debit Instant Invoice in Posted Auth status and select Create Credit Invoice. IFS creates a preliminary credit for the original amount. The action is unavailable for a credit invoice or when a credit already exists; ask the accounting owner to select the appropriate correction route in those cases.

IFS Cloud preliminary credit invoice. The example shows negative quantities and amounts, Print Invoice, and View Connected Invoices. Its Portuguese credit tax code is illustrative. Source: IFS documentation.

Before issue, check the customer, date, currency and lines. For a partial credit, adjust the preliminary credit to the approved reduction and recheck its tax and total. Keep the original invoice reference and the correction reason in the fields used by your connection.

Use View Connected Invoices to check the related debit invoice. Review a work copy, then issue the credit through the approved IFS process. Record the credit’s final number and follow its own Azdan transaction through validation, delivery, receiver response and FTA reporting.

Have the receivables owner check how the credit settles the original balance. A connected invoice reference is not proof that a refund or offset has been completed. Handle returned goods and any refund through their normal processes.

IFS guidance on credit Instant Invoices

10. Return to the original IFS Cloud invoice

Return to Instant Invoice and search for the final series and invoice number. Open the original record, then compare it with the Azdan transaction you reviewed. Use View Connected Invoices when checking a related credit.

Posted Auth is an IFS accounting status. It does not stand in for the validation, delivery, receiver and reporting results in Azdan.

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 IFS Cloud 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