PIP 5C3 — Distribute Account Status

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

PIP purpose

PIP 5C3 distributes the current status of a partner account from manufacturer to distributor: open credit, discount level, available MDF. Used as a response to PIP 5C2 or as a periodic push notification.

Message structure

The 5C3 choreography follows the RosettaNet action model:

Primary action: Account 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-5C3.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>5C3</GlobalProcessIndicatorCode>
</ServiceHeader>

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

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

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-5C3.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip5C3AccountStatusNotification xmlns="http://www.rosettanet.org/PIP5C3">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Manufacturer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Distributor</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260516T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
    <AccountStatusReport>
      <reportIdentifier>
        <ProprietaryDocumentIdentifier>ACCT-STATUS-2026-051601</ProprietaryDocumentIdentifier>
      </reportIdentifier>
      <partnerAccountIdentifier>
        <ProprietaryAccountIdentifier>CHANNEL-HPX-IM-014</ProprietaryAccountIdentifier>
      </partnerAccountIdentifier>
      <creditLimit currencyID="USD">500000</creditLimit>
      <openExposure currencyID="USD">214500</openExposure>
      <discountTier>Gold</discountTier>
    </AccountStatusReport>
</Pip5C3AccountStatusNotification>

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

HP sends Ingram Micro every Friday a PIP 5C3 recap of the 320 active channel accounts: credit limits, exposure, quarterly bonuses.

Foundations

Standards

Flagship messages

Tools