xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField Sales & SFACRMRewardsClaimsInventoryProcurementWarehouse 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
Auto DMSConsumer Goods DMSSales Force Automation (SFA) 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 pay template: an ordered set of salary component lines that turns a person's CTC into earnings, deductions, employer contributions and reimbursements. A person is paid from a structure through a Resource Compensation record, which names the structure and the monthly CTC. The payroll run uses the person's compensation record with the latest Effective From, not the Salary Structure field on the resource. An employee with no compensation record naming a structure, or whose structure has no active lines, is counted as skipped. A structure has no company field, so it is shared across the tenant. Its Effective From, Pay Frequency and Is Active are descriptive: the run reads none of them, and deactivating or deleting a structure does not stop anyone being paid from it. Found in the Payroll app under Settings, Pay Structure.

Fields

FieldLabelTypeRequiredWhat it does
BusinessUnitIdBusiness UnitLookup → BusinessUnitNot stored. Structures are not scoped to a business unit or a company.
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
EffectiveFromEffective FromDateYesWhen the structure is meant to start. Descriptive only: the run does not compare it with the payroll period. The start of a person's pay is decided by the Effective From on their Resource Compensation record.
EmployeeIdEmployeeLookup → EmployeeNot stored. A structure is assigned to a person through a Resource Compensation record.
IdIdGuidYes
IsActiveIs ActiveBooleanMarks the structure as in use. Not checked by the run, and the Salary Structure picker on compensation records still offers inactive structures. To retire a structure, give its people compensation records that name another structure.
ModifiedByIdModified ByLookup → UserAccountYes
NameNameTextYesThe structure's number, filled from the SS document series when the structure is saved.
OwnerIdOwnerLookup → UserAccountYes
PayFrequencyPay FrequencyPickListYesHow often the group is paid: Monthly (the default), Weekly, Biweekly or Daily. Descriptive only. Runs are calculated per payroll period, and the period's dates decide the days used for proration. Values: Monthly, Weekly, Biweekly, Daily.
RecordTypeIdRecord TypeGuid, hidden
StructureNameStructure NameText, uniqueYesThe name people pick when they assign the structure, for example Field Staff. Required and unique across the whole tenant. The run does not use it; lines belong to their structure by link.
SubscriptionKeySubscription KeyGuid, hiddenYes
UpdatedDateTimeModified DateDateAndTimeYes

Actions

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