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/Posting Definition — entity reference
REFERENCE · Last reviewed

Posting Definition — entity reference

The account-determination rule that decides which GL account a document's journal lines hit, and the successor to the legacy accounting rules. Each rule names the document entity and the posting role within it, points at a GL account, and can be narrowed by company, branch, item or party; when several rules match, the most specific wins and Priority only breaks ties among equally specific rules. It is consulted first during document posting, ahead of the tax-subtype resolution and the plain chart-of-accounts lookup by account type.

Fields

FieldLabelTypeRequiredWhat it does
AccountGroupIdAccount GroupLookup → AccountGroupIntended to scope a rule to a group of parties. The current account-determination logic does not read it, so a rule scoped solely by account group behaves as an unscoped rule and can win over rules the author expected to be more specific.
AccountIdAccountLookup → AccountScopes the rule to one customer party and is the weakest specificity signal. It is matched against the document's party, so a rule naming a different party is excluded from consideration for that document.
BranchIdBranchLookup → BranchScopes the rule to one branch and is the second-strongest specificity signal. Blank means the rule applies to any branch; a non-matching branch disqualifies the rule completely.
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
EntityNameEntity NameTextYesThe document entity the rule applies to, held as plain text — Invoice, Bill, Payment, CreditNote and so on — and matched case-insensitively against the posting document. A rule whose entity name is blank is never considered.
GLAccountIdGL AccountLookup → GLAccountYesThe account the rule resolves to.
GranularityGranularityTextIntended to choose between one summarised journal line per resolved account and a journal line per document line. The current document-posting engine does not read this field — it always summarises, grouping line and tax amounts by resolved account, dimensions and party — so setting it has no effect on how a document posts.
IdIdGuidYes
IsActiveIs ActiveBooleanRules are loaded for matching only when this is explicitly true — a rule left unset is treated as inactive and never participates in account determination. This makes it an opt-in switch rather than a soft delete.
ItemGroupIdItem GroupLookup → ItemGroupIntended to scope a rule to a group of items rather than a single item. The current account-determination logic does not read it — matching considers company, branch, item and party only — so a rule scoped solely by item group behaves as an unscoped rule.
ItemIdItemLookup → ItemScopes the rule to one item, ranking below company and branch but above party in specificity. A rule naming a different item than the line being posted is excluded, not just demoted.
LabelLabelText
ModifiedByIdModified ByLookup → UserAccountYes
NameNameText
OwnerIdOwnerLookup → UserAccountYes
PartnerAccountIdPartner AccountLookup → AccountYesScopes the rule to one company and is the strongest specificity signal in matching. Leaving it blank makes the rule apply to every company; setting it to a different company than the document's excludes the rule outright rather than merely ranking it lower.
PostingRolePosting RoleTextWhich leg of the document the rule resolves — the header or control side, the line side, the tax side, cost of goods sold, inventory, rounding or discount. A rule with no role set is treated as a header rule, and a rule only competes against others for the same role.
PriorityPriorityNumberOnly breaks ties between rules of equal specificity, with the lower number winning; rules with no priority sort last. Specificity always dominates, so a priority value cannot make a general rule beat a narrower one.
RecordTypeIdRecord TypeGuid, hidden
SupplierAccountIdSupplier AccountLookup → AccountThe supplier-side counterpart of the customer party scope, matched against the same party value on the posting document and carrying the same specificity weight. Setting either party field to a non-matching account disqualifies the rule.
TaxTypeTax TypeTextNarrows a tax-role rule to one tax component and is matched strictly: a rule with a tax type only ever matches a leg carrying that same tax type, and a rule with a blank tax type only ever matches a leg with no tax type at all.
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
EditInLineEditEditInlineEdit
EditListRowEditEditEditListRow
NewNewNewNew

Lookup filters

FilterLookup fieldNotes
Branch For Partner AccountBranchIdBranch For Partner Account
Customer AccountAccountId
PartnerAccountPartnerAccountId
SupplierAccountSupplierAccountId