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

Payment (Salary Disbursement) — entity reference

A legacy, thin salary-payout record hanging off a PayrollRun, superseded by PayrollPaymentBatch and its lines. No first-party service, handler or job reads or writes it: nothing creates it, nothing settles an open item from it, and it produces no ledger entry, so rows only ever exist if a tenant or an import puts them there. The shipped disbursement path is Generate Payment on the run, which builds a PayrollPaymentBatch, and then Pay on that batch, which posts Dr Payroll Payable / Cr Bank. Treat any data here as historical and never use it to answer whether salary was actually paid.

Fields

FieldLabelTypeRequiredWhat it does
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
EmployeeIdEmployeeLookup → EmployeeThe salary payout path keys on Resource, through the payment batch lines, not on Employee.
IdIdGuidYes
ModifiedByIdModified ByLookup → UserAccountYes
NameNameTextYes
OwnerIdOwnerLookup → UserAccountYes
PaymentDatePayment DateDateThe date this legacy payout record claims money moved.
PaymentModePayment ModePickListHow the payout was supposedly made, offering Bank, Cash or Cheque. Purely descriptive data entry on a superseded entity: no payment file, journal or settlement behaviour keys off it. Values: Bank, Cash, Cheque.
PaymentStatusPayment StatusPickListA free-text state for this legacy payout record, with no picklist and no engine constants behind it. Nothing advances or validates it, so it carries whatever a user or import wrote.
PayrollRunIdPayroll RunLookup → PayrollRun_cThe payroll run this legacy payout record claims to relate to. It is the only relationship the record has, and nothing in the platform creates, reconciles or posts from it — the run's real disbursement link is its payment batch.
RecordTypeIdRecord TypeGuid, hidden
SubscriptionKeySubscription KeyGuid, hiddenYes
TotalAmountPaidTotal Amount PaCurrencyThe amount this legacy record claims was disbursed. It is not derived from payroll details, not reconciled against Payroll-Payable open items and not posted, so it should never be used as a paid-salary total — sum the payment batch or the ledger instead.
TransactionIDTransactionTextA free-text bank or transfer reference on this superseded record. Nothing writes or validates it; the shipped equivalent is the payment reference on the salary batch and the per-line bank reference on its lines.
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