> ## Documentation Index
> Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Clearinghouse Transactions

> Append-only audit trail of all individual clearinghouse transactions, capped at 500 most recent entries per query.

This page is the Transaction Log — a read-only audit trail of all clearinghouse transactions — accessible at `/pm/clearinghouse/transactions`.

## Overview

The Clearinghouse Transactions page presents an append-only <Tooltip tip="An immutable log where records are inserted server-side; UPDATE and DELETE are denied by RLS policy">transaction log</Tooltip> (`pm_transaction_log`) of individual clearinghouse transactions. Records are created server-side by edge functions or a service client; no mutation actions are available from the UI. Each entry shows the transaction type, status, optional trace number, the associated batch file name (from `pm_transaction_batches`), claim number (from `pm_claims`), and the creation timestamp. Error codes, when present, are displayed inline. The list is capped at the 500 most recent records per query. This page is a sub-route within the Clearinghouse area (`/pm/clearinghouse/...`).

## Who it's for

Requires permission `pm.claims.view` (route guard: `PM_PERMISSIONS.CLAIMS_VIEW`). This page is read-only for all users.

## Before you start

* Transaction log entries are created automatically when clearinghouse batches are processed; no manual creation is available.
* You must hold `pm.claims.view` to access this page.

## Steps

<Steps>
  <Step title="Open the Transaction Log">
    Navigate to `/pm/clearinghouse/transactions`. The page loads the 500 most recent transaction log entries for your organization, newest first.
  </Step>

  <Step title="Filter by status">
    Use the status dropdown to filter entries to: Pending, Accepted, Rejected, Error, or Warning.
  </Step>

  <Step title="Filter by transaction type">
    Use the transaction type dropdown to filter to a specific X12 type (e.g., `837P — Professional Claim`, `835 — ERA/EOB`, `270 — Eligibility Inquiry`).
  </Step>

  <Step title="Investigate errors">
    Entries with a status of Rejected or Error display the raw `error_codes` value below the metadata row. Use the trace number and batch file name to correlate with the batch record at `/pm/clearinghouse/batches`.
  </Step>
</Steps>

## Key concepts

<AccordionGroup>
  <Accordion title="Append-only log">
    The `pm_transaction_log` table is immutable. RLS enforces `USING(false)` deny policies for UPDATE and DELETE. All entries are written server-side; the UI provides read access only.
  </Accordion>

  <Accordion title="Transaction types">
    Log entries carry the same X12 transaction type identifiers as batches:
    <Tooltip tip="Professional claim">837P</Tooltip>,
    <Tooltip tip="Institutional claim">837I</Tooltip>,
    <Tooltip tip="Electronic Remittance Advice">835</Tooltip>,
    <Tooltip tip="Eligibility inquiry">270</Tooltip>,
    <Tooltip tip="Eligibility response">271</Tooltip>,
    <Tooltip tip="Claim status inquiry">276</Tooltip>,
    <Tooltip tip="Claim status response">277</Tooltip>,
    <Tooltip tip="Prior auth request">278</Tooltip>,
    <Tooltip tip="Functional acknowledgment">999</Tooltip>,
    <Tooltip tip="Claim acknowledgment">277CA</Tooltip>.
  </Accordion>

  <Accordion title="Log status values">
    Status values are `pending`, `accepted`, `rejected`, `error`, and `warning`. These reflect the clearinghouse's response to the individual transaction, which may differ from the parent batch status.
  </Accordion>

  <Accordion title="Empty state">
    When no entries exist, the page shows "Transaction log entries are created automatically when batches are processed."
  </Accordion>
</AccordionGroup>

## Related

<Columns cols={2}>
  <Card title="Practice Management" icon="briefcase" href="/pm/overview">
    Overview of the Practice Management core.
  </Card>

  <Card title="Governance & parity" icon="scale-balanced" href="/governance/index">
    Documentation coverage and governance.
  </Card>
</Columns>

<Note>
  This page documents shipped product behavior. It is not medical, legal, or
  billing advice. Verify against your organization's policies and applicable
  regulations before using it for clinical, compliance, or billing decisions.
  Protected health information (PHI) shown in the product is governed by your
  tenant's access controls and is never exposed in this documentation.
</Note>

<Accordion title="Documentation sources">
  * src/routes/pm.tsx
  * src/cores/pm/pages/TransactionLogListPage.tsx
  * src/cores/pm/hooks/useTransactionLog.ts
  * src/cores/pm/types/clearinghouse.ts
  * src/platform/permissions/constants.ts
</Accordion>