Skip to content

Document Navigation

One click leads between a Business Central document and the matching Jarltech record, in both directions. Anyone checking a posted invoice reaches the original PDF and Jarltech's payment status without a portal login; anyone looking at a Jarltech order jumps to the documents it produced.

From Business Central to Jarltech

Starting point Actions
Posted purchase invoice (card and list) Open Jarltech invoice · Open Jarltech order · Download original invoice as PDF
Posted purchase receipt (card and list) Open Jarltech shipment · Open tracking · Download delivery note and proof of delivery
Purchase order Show Jarltech order · Refresh status · Check availability
Sales order (drop shipment) Open Jarltech order · Tracking FactBox
Vendor ledger entry Open Jarltech invoice · Download original invoice as PDF

The posted purchase invoice also carries a FactBox with Jarltech's payment status, including due date and payment date. While checking an invoice you can therefore see at a glance how Jarltech records the transaction — independently of what has been posted in Business Central.

From Jarltech to Business Central

Starting point Actions
Jarltech order (card and list) Purchase order · Sales order · Posted purchase invoices · Posted purchase receipts
Jarltech invoice (card and list) Open posted purchase invoice
Jarltech shipment Open posted purchase receipt · Open Jarltech order

What the match depends on

The connection runs through three standard fields of the purchase document. They are the key — without them no navigation finds its target.

Field in Business Central Content Filled
Vendor Order No. Jarltech order ID manually, when the document is entered
Vendor Invoice No. Jarltech invoice ID automatically while the order is processed
Vendor Shipment No. Jarltech shipment ID automatically while the order is processed

Fill in Vendor Order No. when entering the document

The order ID is the strongest key: it is unique, and it lets the connector find the order without any search. Maintaining it on a purchase order keeps navigation and the historical import working even when Jarltech never stored a reference for your order number.

A suffix on the number does no harm

Business Central requires vendor invoice numbers to be unique. When a document has to be posted a second time — a correction, a single line rebooked — the number gets a hand-written suffix:

53804456 - 2

What counts for the match is the leading number. The document still belongs to Jarltech invoice 53804456, no matter whether the suffix was appended with a space, a dash, a slash or as a word. A longer number is not confused with it: 538044567 is a different invoice and is treated as one.


When an action is dimmed

The actions check whether the target document actually exists — not merely whether a number sits in a field. A dimmed action therefore always means: this order currently has no such document.

Dimmed action Reason
Purchase order The order has been posted in full and no longer exists. The posted documents are reachable through the other two actions.
Sales order Not a drop shipment, or the sales order has already been posted.
Posted purchase invoices The delivery has not been invoiced yet.
Posted purchase receipts The goods receipt has not been posted yet.

Sales order on drop shipments

In Business Central the link to the sales order sits on the purchase line, not on the header. The connector therefore resolves it through the lines of the purchase order — and once that is posted, through the lines of the posted receipts. For very old transactions whose purchase order and lines were removed long ago, the link no longer exists in Business Central and the action stays dimmed.