Skip to content

Review payroll country demand

When a customer needs payroll in a country Humavera does not yet support, they can register that from inside their own workspace. Those requests are aggregated here, most-requested first, so coverage decisions follow real demand.

Required role: Humavera platform staff.

  1. Go to Platform → Country Demand.
  2. Read the list. It is ordered by how many workspaces have asked.
  3. Expand a row to see which workspaces asked and when.
  4. Set the country’s status using the selector on its row.
OptionDescription
NewRequested, and not yet decided on.
PlannedOn the roadmap.
SupportedPayroll is available for that country.

Set the status honestly. Planned is a commitment customers will hear as one, and a country left at Planned for a long time is worse than one left at New.

Each row carries the count of workspaces that asked, the date of the first request, and the date of the most recent. The two dates matter as much as the count: steady requests over months are a different signal from a cluster that arrived in one week and stopped.

Example: a country asked for by eleven workspaces, first eighteen months ago and most recently last week, is sustained demand. Eleven requests that all arrived on the same day are more likely one event.

Expanding a row names the workspaces behind the count, so a coverage decision can be checked against who is actually waiting on it.

Nothing here switches payroll on for a country. Setting a status records a roadmap position; the work of certifying a country’s statutory payroll happens elsewhere. A country marked Supported should be marked that way because it is supported, not to close the request.

Customers who registered a request see the position change on their side, so the status you set is the answer they get. A country that becomes supported is then configurable in the workspaces that were waiting for it, through their own payroll setup rather than anything on this screen.