Payroll ERP Export Pipelines

Enterprise organizations do not calculate payroll manually. The TitanGrid ecosystem is designed to act as the single source of truth for billable hours, which must be seamlessly pushed into External Resource Planning (ERP) systems.

Export File Compilation

Different ERP systems require completely different column headers, delimiters, and data formats. Rather than writing hardcoded CSV generators, TitanGrid utilizes a Dynamic Mapping Engine.

How it Works:

1. Cycle Aggregation: The system sums all valid worked_minutes from the AttendanceRecord table between the requested cycle_start and cycle_end dates.
2. Overtime Segmentation: Based on local labor laws, hours exceeding the weekly threshold (e.g., > 40 hours) are automatically segregated into a secondary overtime_hrs variable.
3. Template Mapping: The engine passes the variables through the requested target_erp template (e.g., sage_vip, xero, or quickbooks). This template renames the JSON keys to match the exact CSV header columns expected by the financial software.

Automated Cycle Exports

By hitting the Export Cycle endpoint, integrators can generate flat, delimited text files ready for immediate drag-and-drop into standard payroll software.

Operation Details

• Endpoint: POST /api/payroll/export-cycle/
• Action: Compiles the requested 30-day payroll cycle. It calculates exact decimal hours (e.g., 160.5 hours instead of 160h 30m), separates standard time from overtime, and outputs a flat CSV string that financial controllers can save natively as a .csv file.

POST /api/payroll/export-cycle/

{
  "target_erp": "sage_vip",
  "cycle_start": "2026-05-01",
  "cycle_end": "2026-05-31",
  "apply_overtime_rules": true,
  "deduct_late_minutes": true
}

EMP_CODE,DEPT,REGULAR_HRS,OVERTIME_HRS,LATE_DEDUCTION_MIN
EMP-9042,HR,160.0,12.5,14
EMP-1043,ENG,158.0,0.0,0
EMP-4099,ENG,160.0,5.0,45
EMP-2001,MGT,160.0,0.0,0