Skip to content

Main content

Shipment Document Reference Token

Associate an explicitly identified shipment document with its shipment without validating trade-document sufficiency.

Loading tool…

Description

Associate an explicitly identified shipment document with its shipment.

Cross-border business records combine named parties, contract versions, currencies, fees, shipment terms and local-time transcriptions. A supplied rate direction or fee currency determines arithmetic, while an authentic-language or trade-rule label remains a record assertion. Local calculations do not establish actual settlement or governing obligations.

Associate an explicitly identified shipment document with its shipment.

When to use this tool

Use Shipment Document Reference Token when you already have shipmentId, documentType, documentId and need to associate an explicitly identified shipment document with its shipment.

How to use the tool and how it works

  1. Enter shipmentId, documentType, documentId. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read token. Use the output convention below.

Enter shipmentId, documentType, documentId using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1

Input fieldMeaning and unitsAccepted input
shipmentIdShipment IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
documentTypeDocument TypeRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
documentIdDocument IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "shipmentId": "SHIP17",
    "documentType": "invoice",
    "documentId": "INV3"
  },
  "output": {
    "token": "[\"SHIP17\",\"invoice\",\"INV3\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without validating trade-document sufficiency. Sources and asserted relationships are not independently authenticated.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Review the original agreement, invoice, shipment and payment records with their stated editions and currency bases. Use complete contractual and valuation rules for actual obligations; supplied shares, labels and conversions are auditable components of that review.

References

  1. Calculation and input contract: international-business/shipment-document-reference-token — tool.io

Similar or alternative tools