TRANXACT.AI Help
HRMS › Payroll

Labor Distribution & GL Interface

What each payslip was for -- grant, property, program, fund, cost center, department, job -- and the payroll journal as a file for the general ledger that receives it, balanced, reconciled and sent.

In HRMS → Payroll · 9 screens

WorkspaceGL Interface ConsoleChoose an interface and a payroll run: the control totals, anything that would stop the file, make it, send it, and take the specification and mapping workbook away.OpenRecordsGL InterfacesWhere payroll goes in the general ledger that receives it: the target system profile (Yardi Voyager journal ETL, or a generic CSV / JSON journal), its codes, the schedule and the transport. A new interface sends TEST files until Go live.OpenRecordsGL Interface MappingsWhich target account (and property, segments) each payroll amount goes to. The most specific rule wins: a code before *, then each dimension it names, then priority.OpenRecordsGL Interface Code CrosswalkA property, department, program, fund, grant, cost center or job as the target system codes it.OpenRecordsGL Interface Valid CodesThe receiving system's own chart and property list. With a list loaded, a code not on it stops the file.OpenViewGL Interface FilesEvery file made, version by version, with its checksum and control totals -- never changed, never deleted. Resend sends the same file again; Reprocess makes the next version after a correction.OpenViewGL Interface ExceptionsWhat stopped a file: a missing mapping, an invalid code, an imbalance, a control total that did not agree, a failed transmission. Correct the cause and Reprocess.OpenRecordsLabor SplitsThe standing distribution of an employee's (or a position's) pay, used where no time says otherwise: salaried people, holidays, retro and off-cycle pay.OpenViewPayslip AllocationsEach payslip split by what the work was for. The employer's taxes and benefit costs follow the gross.Open

Columns, fields and actions

ScreenKindWhat it is ColumnsFieldsActions
GL Interface Console Workspace Choose an interface and a payroll run: the control totals, anything that would stop the file, make it, send it, and take the specification and mapping workbook away. 0 0 0
GL Interfaces List Where payroll goes in the general ledger that receives it: the target system profile (Yardi Voyager journal ETL, or a generic CSV / JSON journal), its codes, the schedule and the transport. A new interface sends TEST files until Go live. 9 29 5
GL Interface Mappings List Which target account (and property, segments) each payroll amount goes to. The most specific rule wins: a code before *, then each dimension it names, then priority. 10 17 0
GL Interface Code Crosswalk List A property, department, program, fund, grant, cost center or job as the target system codes it. 5 5 0
GL Interface Valid Codes List The receiving system's own chart and property list. With a list loaded, a code not on it stops the file. 5 5 0
GL Interface Files Read-only list Every file made, version by version, with its checksum and control totals -- never changed, never deleted. Resend sends the same file again; Reprocess makes the next version after a correction. 11 0 6
GL Interface Exceptions Read-only list What stopped a file: a missing mapping, an invalid code, an imbalance, a control total that did not agree, a failed transmission. Correct the cause and Reprocess. 7 0 2
Labor Splits List The standing distribution of an employee's (or a position's) pay, used where no time says otherwise: salaried people, holidays, retro and off-cycle pay. 11 13 0
Payslip Allocations Read-only list Each payslip split by what the work was for. The employer's taxes and benefit costs follow the gross. 15 0 1

Take the lesson on this section