Skip to main content
One row per financial movement recorded in Elation Billing - the payments and adjustments applied to charges and claims. This is the most granular billing record: each row carries its type, amount, and running balance, and links to the charge, claim, payment, patient, and patient_insurance it relates to, where known. This table’s columns and relationships are shown in the Hosted Database schema.
The relational columns are all nullable - a transaction only carries the ones that apply to it, so charge_id, claim_id, payment_id, patient_id, and patient_insurance_id are frequently empty. patient_id and patient_insurance_id are also empty when the Elation Billing record does not map to an EHR entity.
For reporting on but not limited to:
  • Payments vs. adjustments by practice or date (type)
  • The full financial history behind a single claim or charge
  • Adjustment reason codes (code) and their amounts
  • Reconciling a payment against the transactions it produced

Payments and adjustments by practice and month

Rolls up transaction counts and amounts by practice, month, and transaction type.

All financial movements for a claim

Returns every payment and adjustment recorded against a single claim, in the order they occurred, with the running balance after each.

Transactions tied to a payment

Joins financial transactions to the payment they belong to, so you can see how a single payment was split across charges and claims.
If you have any questions about this topic please reach out to Elation Support Portal with the subject line HDB - <your_question>