Help Center

Document Correlation 

In Syncrofy, a document's partner identifier is the information which identifies its trading partner and is referred to as the Business Partner ID. This is an identifier assigned to all documents which have a business data identifier that is associated with an in-application business partner, with respect to the document’s company and environment.

We support the following format for these business data identifiers:

  • EDI - Qualifier (ISA*05/07) | Value (ISA*06/08) | Sub-Value (GS*02/03)

By default, all documents that match any of a partner’s business data identifiers will have the same partner identifier and can therefore be correlated together.

Note: When Strict ID Checking is turned OFF, Syncrofy will consider all IDs for that partner/organization equally. When Strict ID Check is ON, Syncrofy will only consider the exact specific Business Partner ID. For more on Strict ID checking, click here

Functional Acknowledgement Correlation & Acceptance Status

When Syncrofy processes a Functional Acknowledgement (997), it ingests the Group Control Number (AK1*02) and finds documents that have the identical number in their GS*06. The same is done for the following to ensure they match up:

  • Functional ID Code (AK1*01)==(GS*01)
  • Transaction Control Number (AK2*02)==(ST*02)†

A document is “Accepted” when it is correlated to:

  • A Functional Acknowledgement document with AK5*01 or AK9*01 == A or E
  • An Application Advice (824) document with 0TI*01 == GA, TA, TE, or TC

A document is “Rejected” when it is correlated to:

  • A Functional Acknowledgement document with AK5*01 or AK9*01 == R, M, W, or X
  • An Application Advice document with 0TI*01 == RD, RF, RJ, RN, RO, or RV


Application Advice Correlation

 Syncrofy correlates Application Advice (824) documents to other documents by the following data:

  • Business Partner ID
  • A hash of the following control numbers (if they are all present)
    • Reference id (OTI*03 == the document's identifier, e.g. Purchase Order Number, Invoice Number, Shipment Number, etc)
    • Transaction ID Code (OTI*10 == ST*01)
    • Transaction Control Number (OTI*09 == ST*02) 
    • Group Control Number (OTI*08 == GS*06) 

Note: If either the Transaction Control Number or Group Control Number are missing from the application advice document, Syncrofy will attempt to correlate without them.


Timeline & Lifecycle Correlations

Document timelines are linked together in Syncrofy by:

  • Business Partner ID
  • Purchase Order number(s) 

Note: Typically for invoices, POs, ASNs, POC, POA, Motor Carrier BOL; and sometimes not (application advice uses something that closely resembles its correlation criteria). In the case of multiple purchase order numbers, multiple composite keys are created, linking to multiple timelines.

Once a document is correlated to a timeline, it will add relevant data to other documents in its timeline based on its type (e.g. invoice will add invoice numbers and invoice dates to a purchase order in its timeline).

Incoming documents are correlated to lifecycles based on:

  • Business Partner ID
  • Opposite flow directions (e.g. an inbound acknowledgement can only correlate to an outbound document)

as well as their type and the following document-specific data:

  • Invoice - Purchase Order number, Invoice number
  • Purchase Order - Purchase Order Number
  • Advance Ship Notice - Purchase Order Number
  • Purchase Order Change - Purchase Order Number
  • Purchase Order Acknowledgement - Purchase Order Number
  • Remittance Advice - Invoice Number
  • Transportation Carrier Shipment Status Message - Invoice Number
  • Functional Acknowledgement - Reference to acknowledged document