Organisation and automatic codes

Employee codes, contract numbers and payslip numbers look small but everything else hangs on them. Rifena lets the company define the numbering rules once and issues consistent numbers from then on.

Organisation

Packages: number of companies

One Rifena account can run several companies, each with its own data, structure and payroll. Standard includes one company, Professional two, Enterprise has no limit. Beyond that you can still create a company; the system shows a warning so the Rifena team can talk to you about the package, and Rifena blocks further creation only where the company’s package is set to block past the limit.

Screen: System → Open organisation settings

This screen manages the logo, organisation name, phone, address, timezone, minimum-wage region and read-only system information.

Safe update

1. Verify the selected organisation.
2. Change only fields backed by confirmed information.
3. Use a supported PNG, JPG or WebP for the logo.
4. Treat timezone as a cross-product setting that affects dates and times.
5. Choose Save and wait for success.
6. Reload and confirm the value remains correct.

Country cannot change after organisation creation. Do not choose an approximately correct wage region to complete the form; leave it unselected when the information is not confirmed and the workflow permits.

Automatic codes

Review the next-code preview before saving. Organisation identifiers and account details are replaced with demonstration data.

Screen: System → Settings → Automatic codes

Open automatic codes cover entities with a real issuance flow, such as employees, groups, positions, payslips, payroll runs, contracts, leave, overtime, payments, advances, expenses and training. The visible list can change when a new issuing flow is introduced.

Edit a pattern

1. Select the exact code type.
2. Use the pattern canvas or raw mode when offered.
3. Configure prefix, suffix, separator, number padding and date/time tokens.
4. Inspect current and next-code Preview.
5. Save and reopen the same type.

Rifena can infer reset frequency from year/month/day tokens. Do not add a time token merely for appearance if it changes the intended counter reset.

Activate

Allows the configuration to issue new codes.

Deactivate

Preserves configuration/history but stops new use.

Reset counter

Requires a reason and checks collision with issued codes.

Preview

A prediction from current configuration, not an issued code.

Never reuse an issued code

A reset must not erase history or recreate a used code. If Rifena reports a collision, verify and change the pattern/start value; do not delete old records to release a code.

A missing type normally means it is not currently exposed or has no live consumer. Do not substitute a similar type.

When editing is unavailable

• Organisation is read-only: the account lacks update permission.
• A code type is absent: it is not exposed for current issuance.
• Reset is blocked: missing reason, locked configuration or collision risk.

See Advanced setup when needed and Settings screen map.