xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField SalesCRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →
PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopers
SENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse cases
SOLUTIONS
FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →
RESOURCES
Knowledge CenterDeveloper & CLIBlogGuidesWhat is xMatix?Company facts
COMPANY
AboutCareersPartnersEventsContactAuthorsLegal
Sign in Request demo
Home/Docs/Entity Reference/Open Transaction — entity reference
REFERENCE · Last reviewed

Open Transaction — entity reference

One open AR/AP item per posted document — invoice, bill, credit or debit note, advance receipt or payment — created at posting time by DocumentJournalPostingService and reduced by SettlementAllocation rows. Direction (Receivable or Payable) and ControlGLAccountId place it in the right subledger; the source document is referenced polymorphically through SourceEntityName + SourceRecordId so a new document type needs no schema change. This is the table ageing, statements, balance confirmations, reminders, Rule 37 ITC reversal and the subledger-to-GL verification job all ride on: to answer "what does this party still owe", query OpenTransaction rather than summing document OpenAmount columns.

Fields

FieldLabelTypeRequiredWhat it does
BranchIdBranchLookup → Branch
BusinessUnitIdBusiness UnitLookup → BusinessUnit
ControlGLAccountIdControl GL AccountLookup → GLAccountThe control (reconciliation) GL account this open item rolls up to — receivables, payables or a tax account. Ageing reports scope themselves by joining this account and filtering on its account type, which is how an AP ageing separates supplier payables from tax payables.
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
DirectionDirectionTextReceivable or Payable — which subledger the open item belongs to. It is set from the posting purpose, and credit documents flip the sign rather than the direction: a customer credit note is a Receivable item with a negative sign, a purchase return a Payable one.
DocumentDateDocument DateDate
DocumentNumberDocument NumberText
DueDateDue DateDateWhen the item falls due; the axis ageing buckets are built on. DocumentDate is when it was raised, and the two differ by the party's payment terms.
GSTRegistrationIdGST RegistrationLookup → GSTRegistration
IdIdGuidYes
JournalIdJournalLookup → JournalThe journal whose posting created this open item, the link that lets the subledger be reconciled to the general ledger.
LabelLabelText
ModifiedByIdModified ByLookup → UserAccountYes
NameNameText, uniqueYes
OpenAmountOpen AmountCurrencyWhat is still outstanding on this item. Maintained by SettlementAllocation rows — each allocation reduces it, and reversing an allocation adds the amount back and returns the status to Open. This is the authoritative outstanding figure for ageing and statements, in preference to the OpenAmount columns on the documents themselves.
OriginalAmountOriginal AmountCurrencyThe item's value when it was created at posting time. It never changes, so OriginalAmount minus OpenAmount is how much has been settled.
OwnerIdOwnerLookup → UserAccountYes
PartnerAccountIdPartner AccountLookup → Account
PartyAccountIdParty AccountLookup → AccountThe customer or supplier the item is owed to or by — the key for party ageing and statements. Distinct from PartnerAccountId, which carries the trading partner for partner-scoped reporting.
RecordTypeIdRecord TypeGuid, hidden
SourceEntityNameSource Entity NameTextName of the entity that produced this open item ("Invoice", "Bill", "CreditNote", "DebitNote", "Payment", …). Paired with SourceRecordId it is a polymorphic reference, deliberately used instead of typed FKs so a new document type needs no schema change — which also means it must be filtered as a string, not joined.
SourceRecordIdSource RecordLookup → @sourceEntityNameId of the source document row, to be read together with SourceEntityName. Reversal of a posted document finds its open items by this pair and sets their status to Reversed.
StatusStatusTextOpen, PartiallySettled, Settled or Reversed. Reversed is set when the source document's posting is reversed, and reversing an allocation moves a Settled item back to Open — so exclude Reversed items rather than assuming Settled is terminal.
UIPropsUI PropsText
UpdatedDateTimeModified DateDateAndTimeYes

Actions

ActionLabelTypeWhat it does
BulkDeleteDeleteDeleteDelete the selected records.
CloneCloneServerAction (Clone)Create a copy of this record
DeleteDeleteDeleteDelete
DeleteInListDeleteDeleteDelete in a list page
EditEditEditEdit
EditInLineEditEditInlineEditInLine
EditListRowEditEditEditListRow
NewNewNewNew