Aria Transaction Tables
Overview
All financial transactions in the Aria System appear in two tables:
-
ARIACORE.ACCT_TRANSACTION: Every transaction has a unique EVENT_NO across all clients, accounts, and transactions. For example, only one record can have EVENT_NO 12345.
-
Second Table: Depends on the transaction type:
-
Electronic Payments (transaction_type 3): Recorded in ARIACORE.PAYMENTS. The SOURCE_NO in ACCT_TRANSACTION matches the PAYMENT_ID in PAYMENTS.
-
Write-offs (transaction_type 6): Recorded in ARIACORE.WRITE_OFFS. The SOURCE_NO in ACCT_TRANSACTION matches the WRITE_OFF_NO in WRITE_OFFS.
-
SOURCE_NO and Transaction Types
Different transaction types can share the same SOURCE_NO. For example:
-
Account 123 (Client X): transaction_type 2, SOURCE_NO 45678.
-
Account 456 (Client Y): transaction_type 3, SOURCE_NO 45678.
This is valid in the data model.
Voided Transactions
Voided transactions share the same SOURCE_NO as the original but have a different EVENT_NO. For example:
-
Original: Account 789, transaction_type 10, EVENT_NO 54321, SOURCE_NO 98765.
-
Void: Account 789, transaction_type -10, EVENT_NO 54322, SOURCE_NO 98765.
Transaction Types and Balances
Transactions are recorded against an account in Aria:
-
Charge: Yes (is_charge_type = 1): Increases the account or plan instance balance.
-
Charge: No (is_charge_type = 0): Decreases the account or plan instance balance.