PIP 3C6 — Notify of Remittance Advice

RosettaNet choreography in cluster 3 (Order Management — Remittance), covering the XML exchange between Payer ↔ Payee. Operational unit for order management — remittance on RNIF V02.00.

PIP purpose

PIP 3C6 is the equivalent of EDIFACT REMADV or X12 820: the buyer notifies the seller that a payment has been or will be executed, with the detail of settled invoices (invoice number, amount, applied discount, withheld amount).

Message structure

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

Action: Notify of Remittance Advice 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:

text rnif-envelope-3C6.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>3C6</GlobalProcessIndicatorCode>
</ServiceHeader>

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

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

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-3C6.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip3C6NotifyOfRemittanceAdvice xmlns="http://www.rosettanet.org/PIP3C6">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Payer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Payee</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260515T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
      <RemittanceAdvice>
        <RemittanceAdviceIdentifier>
          <ProprietaryDocumentIdentifier>REM-2026-887214</ProprietaryDocumentIdentifier>
        </RemittanceAdviceIdentifier>
        <paymentDate>
          <DateStamp>20260812</DateStamp>
        </paymentDate>
        <SettledInvoice>
          <InvoiceIdentifier>
            <ProprietaryDocumentIdentifier>INV-2026-552190</ProprietaryDocumentIdentifier>
          </InvoiceIdentifier>
          <SettledAmount>
            <FinancialAmount>
              <GlobalCurrencyCode>USD</GlobalCurrencyCode>
              <MonetaryAmount>2750000.00</MonetaryAmount>
            </FinancialAmount>
          </SettledAmount>
        </SettledInvoice>
      </RemittanceAdvice>
</Pip3C6NotifyOfRemittanceAdvice>

Transport and acknowledgment

Asynchronous emission, RNIF V02.00 over HTTPS POST or AS2. Coupled with a SEPA / SWIFT instruction at the payer bank, to which this PIP is strictly informational (not a payment request).

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 OEM pays a $2.75M foundry invoice at Net 30. Before issuing the bank transfer, it pushes a PIP 3C6 to the foundry: detail of attached invoices, effective net amount, planned payment date. The foundry treasury syncs its forecast.

Foundations

Standards

Flagship messages

Tools