Integrations and source ownership

• HR system. Keep the resource list, managers, classification and state of work in step with the HR master.
• Billing or invoicing. Receive approved billable hours with resolved rates, once per sheet.
• Payroll. Receive the per-person bundle of locked hours at each pay period end.
• Project management. Keep project codes and forecasts aligned with active projects.
• Email. Send Monday reminders and approval notices.
• Identity provider. Map staff sign-in to resources; removing a leaver’s access must also remove their app access.

Each connection needs an agreed source of truth, a field mapping, a stable identifier and a retry policy. A sheet already exported must not be sent to billing again, and a period bundle must not be sent to payroll twice. Keep credentials in the approved secret store and grant the smallest scope the connection needs. Queue rejected records with their source identifier and a visible reason.

Test a timeout, a duplicate send and a revoked credential before turning on schedules. Availability depends on each provider’s API, commercial access and configuration.

Use the implementation plan to agree acceptance criteria for each connection.