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

Salary Structure — entity reference

A named salary template — an ordered set of SalaryComponent lines that together define how an employee's pay is composed. It is assigned to a person through ResourceCompensation (which also carries the CTC that percentage-of-CTC components are computed against), and the payroll calculation resolves the structure from the employee's most recent active ResourceCompensation, NOT from Resource.SalaryStructureId. An employee with no active ResourceCompensation pointing at a structure, or whose structure has no active lines, is counted as skipped by the run rather than failing it. Unlike the statutory rule masters this entity has no PartnerAccountId column, so a structure is tenant-wide rather than scoped to a legal entity. EffectiveFrom and IsActive describe the template's own validity, and neither is applied as a filter when the run loads the structure's lines.

Fields

FieldLabelTypeRequiredWhat it does
BusinessUnitIdBusiness UnitLookup → BusinessUnitStructures are not scoped to a business unit — or to a legal entity at all. Do not filter or join on this field.
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
EffectiveFromEffective FromDateYesIntended start of the template's validity. The run resolves the structure through the employee's most recent active ResourceCompensation and does not compare this date to the payroll period, so it does not by itself prevent an unstarted structure from being used.
EmployeeIdEmployeeLookup → Employee
IdIdGuidYes
IsActiveIs ActiveBooleanMarks the template as usable. Note the payroll run filters on the ResourceCompensation being active, not on this flag, so deactivating a structure does not on its own stop employees whose compensation still points at it from being calculated.
ModifiedByIdModified ByLookup → UserAccountYes
NameNameTextYes
OwnerIdOwnerLookup → UserAccountYes
PayFrequencyPay FrequencyPickListYesIntended pay cadence of the template. Nothing in the payroll calculation reads it: the period and its day count come from PayrollPeriod's start and end dates, so setting this does not change how amounts are computed or prorated. The seeded picklist offers Monthly only. Values: Monthly, Weekly, Biweekly, Daily.
RecordTypeIdRecord TypeGuid, hidden
StructureNameStructure NameText, uniqueYesThe human-facing name of the template, separate from the record's system Name. Nothing in the calculation keys off it — component lines reference their structure by id — so it is descriptive only.
SubscriptionKeySubscription KeyGuid, hiddenYes
UpdatedDateTimeModified DateDateAndTimeYes

Actions

ActionLabelTypeWhat it does
CloneCloneServerAction (Clone)Create a copy of this record
DeleteentityDeleteDeleteDelete
DeleteHeaderDeleteDeleteDelete
EditEditEditEdit
EditRowEditEditEditRow
NewNewNewNew