PIP 5D2 — Distribute Financial Status

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

PIP purpose

PIP 5D2 distributes a consolidated financial status in response to PIP 5D1 or as a quarterly push: total exposure, credit score, liquidity ratio. Channel financial governance building block.

Message structure

The 5D2 choreography follows the RosettaNet action model:

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

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

text rnif-envelope-5D2.eml

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>5D2</GlobalProcessIndicatorCode>
</ServiceHeader>

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

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

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-5D2.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip5D2FinancialStatusNotification xmlns="http://www.rosettanet.org/PIP5D2">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260516T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
    <FinancialStatusReport>
      <reportIdentifier>
        <ProprietaryDocumentIdentifier>FIN-STATUS-2026-Q1</ProprietaryDocumentIdentifier>
      </reportIdentifier>
      <reportingPeriod><DateStamp>20260331</DateStamp></reportingPeriod>
      <totalOpenExposure currencyID="USD">1850000</totalOpenExposure>
      <creditScore source="DnB">78</creditScore>
      <currentRatio>1.82</currentRatio>
    </FinancialStatusReport>
</Pip5D2FinancialStatusNotification>

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 5D2 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

An ASEAN distributor returns to Intel via PIP 5D2 its consolidated Q1 2026 balance sheet, complete with a Dun & Bradstreet score 78/100 and a current ratio 1.82.

Foundations

Standards

Flagship messages

Tools