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/Payment (Salary Disbursement) — entity reference
REFERENCE · Last reviewed

Payment (Salary Disbursement) — entity reference

An older salary-payout record linked to a payroll run. It is superseded by the Salary Payment Batch: Generate Payment on a posted payroll run builds the batch, and Pay on the batch posts the payment. Nothing in xMatix creates, updates or posts these records. They are on no app menu and not listed on the payroll run page, their create form has no Name box and no numbering fills one in, so saving one from the form is refused with Name is required. Rows exist only if an import or the data API wrote them. The seeded Salary Structure & Components dashboard still reads this record for its Salary Disbursed and Disbursement by Mode tiles, so those tiles stay empty unless such rows exist. To see what salary was actually paid, use the salary payment batches or the ledger.

Fields

FieldLabelTypeRequiredWhat it does
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
EmployeeIdEmployeeLookup → EmployeeNot stored. The field is declared in metadata but the record has no column for it, so a value entered here is dropped on save.
IdIdGuidYes
ModifiedByIdModified ByLookup → UserAccountYes
NameNameTextYesRequired. The create form has no Name box and no document numbering fills it in, so saving from the form is refused with Name is required; only an import or the data API that supplies a name can create a record.
OwnerIdOwnerLookup → UserAccountYes
PaymentDatePayment DateDateThe date entered as the payout date. Nothing sets it and nothing checks it against the ledger.
PaymentModePayment ModePickListHow the payout was made, entered by hand: Bank, Cash or Cheque. The Disbursement by Mode chart on the Salary Structure & Components dashboard groups by this value; nothing else reads it. Values: Bank, Cash, Cheque.
PaymentStatusPayment StatusPickListA payout status entered by hand. It has no seeded values and nothing sets or checks it.
PayrollRunIdPayroll RunLookup → PayrollRun_cThe payroll run this payout record refers to. Payroll runs never list or read these records; the run's real payout is its Salary Payment Batch.
RecordTypeIdRecord TypeGuid, hidden
SubscriptionKeySubscription KeyGuid, hiddenYes
TotalAmountPaidTotal Amount PaCurrencyThe amount entered as paid. It is not calculated from the payroll run and not posted. The Salary Disbursed tile on the Salary Structure & Components dashboard sums this field, so the tile shows only what was keyed or imported here, not what was paid through salary payment batches. Not on the create form.
TransactionIDTransactionTextA bank or transfer reference entered by hand. Nothing writes or checks it.
UpdatedDateTimeModified DateDateAndTimeYes

Actions

ActionLabelTypeWhat it does
CloneCloneServerAction (Clone)Create a copy of this record
  • PayrollRun — looks up via PayrollRunId
  • Employee — looks up via EmployeeId
  • Employee — referenced by via PaymentSalaryDisbursementId