PIP 3C3 — Notify of Invoice

RosettaNet choreography in cluster 3 (Order Management — Invoice), covering the XML exchange between Seller ↔ Buyer. Operational unit for order management — invoice on RNIF V02.00.

PIP purpose

PIP 3C3 is the equivalent of EDIFACT INVOIC or X12 810: the seller issues an invoice to the buyer. Header (seller, buyer, date, currency, total), lines (product, delivered quantity, unit price, taxes), payment conditions, references to the originating PIP 3A4 and 3B2.

Message structure

The 3C3 choreography follows the one-action (notification) RosettaNet model:

• Action: Notify of Invoice Action
• Signal: Receipt Acknowledgment

Each 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>3C3</GlobalProcessIndicatorCode>
</ServiceHeader>

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

<!-- payload PIP 3C3 ci-dessus -->

--RN-BOUNDARY-2026--

Simplified XML example

Minimal PIP 3C3 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"?>
<Pip3C3NotifyOfInvoice xmlns="http://www.rosettanet.org/PIP3C3">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260515T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
      <Invoice>
        <InvoiceIdentifier>
          <ProprietaryDocumentIdentifier>INV-2026-552190</ProprietaryDocumentIdentifier>
        </InvoiceIdentifier>
        <invoiceDate>
          <DateStamp>20260712</DateStamp>
        </invoiceDate>
        <TotalAmount>
          <FinancialAmount>
            <GlobalCurrencyCode>USD</GlobalCurrencyCode>
            <MonetaryAmount>2750000.00</MonetaryAmount>
          </FinancialAmount>
        </TotalAmount>
      </Invoice>
</Pip3C3NotifyOfInvoice>

Transport and acknowledgment

Asynchronous emission, RNIF V02.00 over HTTPS POST or AS2. Depending on the jurisdiction (EU post-2026 in particular), a parallel PEPPOL or Factur-X path is required for tax compliance.

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

A foundry invoices 50,000 wafers shipped two days earlier to an OEM via PIP 3C3: total amount, taxes, references to PO and ASN, Net 30 terms. The OEM integrates the invoice into its automatic Procure-to-Pay cycle.

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.