PIP 5D1 — Request Financial Status

RosettaNet choreography in cluster 5, transported on RNIF V02.00 and signed with S/MIME. Operational unit between Buyer and Seller across the high-tech supply chain.

PIP purpose

PIP 5D1 queries a partner about its current financial health (open exposure, payment delay, score). Generally used to validate the start of a new partnership or to monitor a strategic account. The partner answers with PIP 5D2.

Message structure

The 5D1 choreography follows the RosettaNet action model:

• Primary action: Financial Status Inquiry Action
• Signal: Receipt Acknowledgment (RNIF)
• Response action: Financial Status Response Action

The action is wrapped in a multipart MIME RNIF V02.00 envelope signed with S/MIME. Here is a condensed view of the envelope:

MIME-Version: 1.0
Content-Type: multipart/related; type="application/xml";
  boundary="RN-BOUNDARY-2026"

--RN-BOUNDARY-2026
Content-Type: application/xml
Content-Location: RN-Preamble.xml

<Preamble xmlns="http://www.rosettanet.org/RNIF/V02.00">
  <standardName>RosettaNet</standardName>
  <standardVersion>V02.00</standardVersion>
</Preamble>

--RN-BOUNDARY-2026
Content-Type: application/xml
Content-Location: RN-ServiceHeader.xml

<ServiceHeader xmlns="http://www.rosettanet.org/RNIF/V02.00">
  <GlobalProcessIndicatorCode>5D1</GlobalProcessIndicatorCode>
</ServiceHeader>

--RN-BOUNDARY-2026
Content-Type: application/xml
Content-Location: Pip5D1FinancialStatusInquiry.xml

<!-- PIP 5D1 payload above -->

--RN-BOUNDARY-2026--

Simplified XML example

Minimal PIP 5D1 payload for didactic purposes. The structural elements (fromRole, toRole, thisDocumentGenerationDateTime, and the PIP-specific business block) are required in any conformant implementation.

<?xml version="1.0" encoding="UTF-8"?>
<Pip5D1FinancialStatusInquiry xmlns="http://www.rosettanet.org/PIP5D1">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260516T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
    <FinancialInquiry>
      <inquiryIdentifier>
        <ProprietaryDocumentIdentifier>FIN-INQ-2026-051601</ProprietaryDocumentIdentifier>
      </inquiryIdentifier>
      <inquiryScope>Consolidated</inquiryScope>
      <reportingPeriod><DateStamp>20260331</DateStamp></reportingPeriod>
    </FinancialInquiry>
</Pip5D1FinancialStatusInquiry>

Transport and acknowledgment

Core of the standard: HTTPS POST to the partner endpoint or via AS2. S/MIME signature and Receipt Acknowledgment are systematic. PIP 5D1 is typically transported asynchronously.

The transport channel is typically AS2 or direct HTTPS (RNIF over HTTP). For a reference of the security layers in use, see the AS2 on ediverse page.

Use case

Intel queries a new ASEAN distributor via PIP 5D1 about its consolidated financial status before opening a channel account with USD 2M credit line.

Further reading

• RosettaNet Standards Programme — GS1 US — official PIP catalogue.
• RosettaNet PIP Catalog (web.archive.org) — historical version of the rosettanet.org catalogue before its 2013 retirement.
• RosettaNet — hub on ediverse — overview, PIP / RNIF architecture, and clusters.
• AS2 on ediverse — alternative transport compatible with RNIF.