export_transaction

All data associated with a single transaction. Can be joined to other financial detail tables with transaction_id.

Primary Key: transaction_id

Identifiers

transaction_id
STRINGRequired

Unique transaction ID

voids_transaction_id
STRING

The original charge transaction that this void is reversing. This will only be completed if it is a voiding charge transaction (so it is reversing a charge).

voided_by_transaction_id
STRING

The ID here references the charge transaction which reverses this charge. This is added to a charge transaction if it is later voided.

target_id
STRING

Organization ID, claim ID, or service line ID to tell you which specific place it’s allocated

counter_party_id
STRING

External patient ID, counterparty ID for payer = payer UUID

batch_id
STRING

ID of the custom batch period created

encounter_id
STRING

Unique ID associated with the encounter in the Candid system

service_line_id
STRING

Unique service line ID

charge_id
STRING

Parent charge for the transaction, so it allows you to tie payments and adjustments to the original charge (billed A/R)

charge_transaction_id
STRING

Identifier of every unique charge to easily map payments and adjustments to charge transactions

Timestamps

transaction_timestamp
TIMESTAMP

Timestamp of when the Transaction / payment record was created or entered into the Candid system. Though it is often identical to batch date, transaction date reflects when the record was created in Candid, meaning that if historical data is uploaded, transaction date reflects when the data was uploaded to Candid rather than when the payment took place.

batch_date
TIMESTAMP

Financial period for which the transaction should count - mutable field based on when you would want to account for a transaction. While this typically aligns with the date a payment or charge is posted, it can be manually adjusted (backdated) to reflect when a transaction truly occurred. This is primarily used to group early-month transactions into a previous month’s close or to accurately record historical accounts receivable data.

Organization

organization_id
STRING

User’s unique organization ID in the Candid system

organization_name
STRING

User’s Organization / Company Name

external_organization_id
STRING

Organization’s External ID - the ID that the organization uses to map to their own upstream system

Financial

amount_cents
INTEGER

Amount in cents. Note on the signage: Charge transaction types will always be a positive amount. Payments will usually be negative. However, in cases of reversals (for insurance counter party) or refunds (for patient counter party), the amount cents will be positive.

Transaction Details

transaction_type
STRING

Type of Transfer: Charge, Payment, Balance Transfer, or Adjustment. Note on Balance Transfers: Balance Transfers are a specific transaction type used to move financial liability between different counterparties (such as moving a balance from an Insurance Payer to a Patient). Unlike a payment or a charge, which might stand alone, balance transfers always come in pairs - ie a charge is deducted from Payer (Counterparty A) and added to Patient (Counterparty B). This ensures the ledger remains balanced.

Other

target_type
STRING

Organization, claim, or service line - it tells you to what extent a payment is allocated

counter_party_type
STRING

Patient, payer, non-insurance, organization

payer_plan_group_id
STRING

Unique ID associated with the specific Payer Plan