Notification history

This page lists the history of notifications linked to asynchronous services called during transactions between Sage Distribution and Manufacturing Operations and your financial solutions, such as Sage Intacct or other applications. This can include sending journal entries for stocks or financial documents, tax information, or master data such as updates to business entities. The information displayed depends on the external applications with which you share data.

The term notification in this context refers to sending messages or data between application packages. It does not mean you receive a message regarding the outcome of an action or process.

This table provides information like required permissions and tips to help you get started.

Permissions Admin (full rights)
Subscriptions Sage Distribution and Manufacturing Operations and any external applications

Only functional or technical administrators can access this page to review the notification history for background tasks. Your access to this page is determined by user permissions granted by your administrator.

If there is an error or a failure, you can address errors and resend. See the section on error management for more information.

This invoice posting example explains the notification flow process:

  1. Create a new invoice and save the document. At this point no notification is created.

  2. Trigger the tax calculation. A notification for the tax engine is created and a reply to update the invoice data is processed.

  3. Post the invoice. A journal notification is created.

  4. After you create a journal entry record, the accounting engine picks up this record and creates the actual journal entry. A reply to the initial notification with the result of the operation is sent as part of the processing. The record is also sent to the external finance solution.

Results

Notifications results are organised by type across several tabs. The tabs available to you depend on linked external applications and your user permissions.

For a complete list of notification statuses, refer to the field descriptions.

To understand how data is shared between Sage Distribution and Manufacturing Operations and your external application, refer to the dedicated integration guide.

System notifications

This tab provides information on overall system integrations. This data is for information only and you cannot take further action.

You can filter by status.

Stock notifications

If you share data with Sage Intacct, the Results table displays notifications for various documents for production tracking, stock issue, material tracking, sales shipment and so on. Select the document to view the source document.

You can filter by status.

If there is an error on a line, a message displays that can provide information on why the integration failed. You can select the document number to try to resolve the issue.

Finance notifications

If you share data with a financial solution like Sage Intacct, the Results table displays notifications for various financial documents and journal entries.

You filter results by document type. The documents available in the list depend on your external application integrations. There is some overlap with documents on the Stock tab such as stock issues and receipts, sales shipments and so on. Select the document number to view the source document.

You can also filter by status for all or specific documents.

If there is a communication error on a line, you can retry the synchronisation to see if that resolves the error. The retry is performed at the top or entity level according to the Transaction integration level setting.

Error management

For certain failures to send data to your financial solution, you can try to resend the document by selecting Retry from the More actions icon on the line.

To correct attributes or dimensions, do not select the document number.

If the error could be due to incorrect or missing attributes and dimensions, you can make corrections or additions as follows:

  1. From the More actions icon on the line, select Edit dimensions.
  2. By default, the source document opens and you can modify the attributes or dimensions.
    For supplier invoices or credit notes, you can add the supplier invoice number from Sage Intacct if it is missing. Resend from that screen.
  3. When you save your corrections, they are applied to the source document.
  4. You can repost from this screen and confirm the status on the Journal entry page.

Avalara notifications

If you are subject to US tax collection for sales invoices and sales credit notes and integrate Avalara companies and financial sites, you can view notification statuses for those documents.

You can filter by multiple criteria such as status, topics, and document type and number. You can also limit notifications as of a certain date or view the latest notifications only. Select Revert criteria to reset the query to default values.

For updates to tax codes and companies, the Internal message column displays the number of records received.

Select a document number to view details.

If a sales invoice or sales credit note is not posted, you can update the document. When you save, the tax is automatically recalculated.

If there is an error with Avalara during the tax calculation, you can recalculate the tax to resolve the error. Select the document number and select Tax calculation in the window that opens.

For a sales invoice that is posted, you can create a credit note from the invoice by selecting the document number. In the window that opens, select Credit.

Integration status

The notifications on this tab refer to master data integrated with Sage Intacct. This includes business entity addresses, customers and suppliers.

If an object, such as a particular supplier is not integrated, you can select Force synchronisation on the line.

Possible issues in the notification flow

The following situations can cause errors in business flows:

  • Service issues when the notification is created.
  • An application error when the notification payload is created, for example, from incorrect data.
  • A platform issue when the notification payload is processed, for example, from a table lock.