HRMS › 급여
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.
~ 안에 HRMS → 급여 · 9 화면
작업 공간GL 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.열려 있는기록GL 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.열려 있는기록GL 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.열려 있는기록GL Interface Code CrosswalkA property, department, program, fund, grant, cost center or job as the target system codes it.열려 있는기록GL Interface Valid CodesThe receiving system's own chart and property list. With a list loaded, a code not on it stops the file.열려 있는보다GL 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.열려 있는보다GL 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.열려 있는기록Labor 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.열려 있는보다Payslip AllocationsEach payslip split by what the work was for. The employer's taxes and benefit costs follow the gross.열려 있는
열, 필드 및 작업
| 화면 | 친절한 | 그것은 무엇인가 | 컬럼 | 전지 | 행위 |
|---|---|---|---|---|---|
| GL Interface Console | 작업 공간 | 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 | 목록 | 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 | 목록 | 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 | 목록 | A property, department, program, fund, grant, cost center or job as the target system codes it. | 5 | 5 | 0 |
| GL Interface Valid Codes | 목록 | 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 | 읽기 전용 목록 | 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 | 읽기 전용 목록 | 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 | 목록 | 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 | 읽기 전용 목록 | Each payslip split by what the work was for. The employer's taxes and benefit costs follow the gross. | 15 | 0 | 1 |