The intercompany order was sent. What came back?

The same work comes back with each order: comparing references from two systems, finding the correspondence, and checking whether someone has already sent a corrected version. Resending the order can leave the recipient with another document to identify manually as part of the earlier order. Connecting the systems can help the coordinator first see what answer the other company is waiting for.

The recipient has a question about one line

Suppose company A sends an approved order to company B. Company A's system records it as sent. An employee at B has returned the document for clarification because they do not recognize the product reference on one line. Their reply is available in B's tool, but the person handling the order at A still sees only that it was sent.

The coordinator needs to open that line alongside the recipient's comment and the source order number. They can then ask the person responsible for the product which reference the other company should receive. The data owner approves the correct reference under the company's agreed process. A similar product name is not enough to replace the reference without that review.

The corrected version stays with the same order. When company B confirms acceptance, the coordinator can see which version the reply concerns and return to the earlier comment. A colleague taking over the next day can continue the conversation without asking both sides why the document was sent again.

Keep the correction with the same order

The two companies may use different document numbers. Connecting their systems means establishing how to recognize the source order and its later versions in the recipient's tool. Sending the same document again should be recognized as a repeat. An approved correction should update the existing order's history without creating another, unrelated commercial order.

If your problem concerns an outside supplier changing quantities or delivery dates, see our article on comparing an order with its first acknowledgment.

Check your ERP's intercompany workflow

Microsoft describes Business Central inboxes and outboxes for intercompany transactions. The system distinguishes created and returned transactions and supports accepting, rejecting, or canceling them. This provides a starting point for checking whether your current system shows the team the recipient's response against the right document.

If both companies already use such a workflow, configuration and an agreement on who handles returned lines may be enough. A separate connection is worth considering when the companies use different tools and staff copy information about replies and corrections between them. The scope then depends on the data both systems can provide and receive.

Ordinary rules can link order numbers, versions, and replies. AI can help summarize a longer message from the recipient if the coordinator can also read the original. It is not needed to recognize that the same document was sent again or establish whether confirmation of acceptance has arrived.

What you can commission from Syntalith

In a proposed project, Syntalith connects sent-order records with the other company's replies and builds a view of lines that need clarification. The scope can include sending an approved correction and linking the recipient's confirmation to the right version. The connection should recognize a document sent again and prevent it from creating another order for the same request.

An initial scope can cover one pair of companies and a selected order type. Your team supplies the agreed product and document reference mappings and identifies who approves corrections. Administrators from both systems help establish the available way to exchange the data.

Start a conversation about automating order handoffs with the last document someone had to send again. Describe where the recipient recorded their question and how the sender knew the corrected version had been accepted. See Syntalith pricing for pricing information.