EPM Payload Encryption and Compression

Plain-language summary

In EPM workflows, encryption and compression are optionally applied to the payload layer, not by encrypting the PDF container itself.

That separation matters because the PDF remains readable for people, while structured data can still be protected and optimized for system-to-system exchange.

Why this separation matters

  • The PDF remains readable and usable as a document
  • Encrypting a PDF/A-3 or PDF/A-4f file invalidates the file's compliance
  • Structured payload data can still be protected and optimized
  • Producer and consumer systems can follow declared processing rules

This is the core design choice: preserve document usability while adding machine-readable transport controls at the payload layer.

Why one size does not fit all

When federal workflows required electronic appraisal submissions, they were designed for immediate portal validation in a tightly controlled pipeline. That model is appropriate for that use case.

But appraisal data also moves in many non-federal contexts, where confidentiality, transport efficiency, and policy constraints vary. A single fixed rule for every workflow is not practical.

EPM was designed for that broader reality.

The federal model: transparency by design

The Uniform Appraisal Dataset (UAD) governs appraisal data delivery to Fannie Mae and Freddie Mac through the Uniform Collateral Data Portal (UCDP). UAD uses XML, based on standards maintained by MISMO, in a controlled submission pipeline.

In that model, the portal needs immediately readable content to check the submission.

As a result:

These choices are deliberate for that environment and are not inherently a limitation of structured data itself.

Where that model stops

Outside UCDP delivery, appraisal data may move through different channels and trust boundaries, such as:

  • Private or portfolio lending workflows
  • Third-party review workflows
  • Institution-to-institution transfer in secondary markets
  • AMC delivery paths with data integrity or confidentiality requirements
  • Protected archive and retention scenarios

In these contexts, structured data still needs to travel, but policy and operational needs may differ from federal submission rules.

The EPM approach: implementer choice with declared behavior

EPM provides a structured wrapper for payload transport and allows implementers to choose transforms appropriate to the use case, while declaring them so consumers can process them consistently.

Compression in EPM

EPM supports payload compression. Producers can compress payload content and declare the method so consumers can reverse it predictably.

Why this matters:

  • Structured payloads, especially XML, can be verbose
  • Compression can reduce file size and improve transfer and storage efficiency

If compression is not needed, producers simply omit it.

Relevant terms: payload compression, compression algorithm

Encryption in EPM

EPM supports payload encryption at the application layer. Producers can encrypt payload content and declare the method so authorized consumers can process it.

Why this matters:

  • Sensitive data can be protected in transit and at rest
  • The PDF host remains readable and printable for human use
  • Machine-readable payload access can be limited to intended systems

Under PDF/A workflows, container-level PDF encryption is not used; payload-layer encryption remains available for protected exchange behavior.

If encryption is not needed, producers simply omit it.

Relevant terms: encryption, application-layer encryption

Using both together

EPM supports both compression and encryption together, with explicit order of operations: compress first, then encrypt. Consumers reverse the sequence: decrypt first, then decompress.

That ordering removes ambiguity and helps ensure consistent behavior across conforming systems.

Producer and consumer expectations

  • Producers declare how payload content is encoded, compressed, and protected
  • Consumers validate metadata and apply compatible decode/decrypt handling

This supports predictable interoperability while preserving one-file delivery behavior.

Same standard, different contexts

EPM does not force all workflows into one model.

  • If a workflow requires open payloads, producers can embed plain, uncompressed, unencrypted payload content
  • If a workflow requires confidentiality and efficiency, producers can declare and apply encryption and compression
  • In both cases, behavior is explicit, declared, and processable by consumers

The result is transport flexibility without sacrificing predictable interoperability.

Sources

Glossary terms referenced on this page: UAD, UCDP, XML, MISMO, Base64, payload compression, encryption