1C integration and custom solutions

Employee Web Portals

An employee portal moves frequent actions out of the 1C thick client: requests, approvals, schedules, or time records.

Discuss this directionContact form

Tell me the goal, stack constraints, and timeline — I reply on Telegram.

An employee portal moves frequent actions out of the 1C thick client: requests, approvals, schedules, or time records. I build a mobile web interface while keeping accounting data and agreed rules in their proper system.

Scope begins with one process and role matrix, then may include forms, statuses, notifications, 1C APIs, decision logs, and delegates. It does not imply a full HRM, payroll, or new HR methodology. Acceptance covers request creation, manager scope, duplicate commands, revoked access, complete decision history, and predefined behaviour during 1C outages.

Acceptance criteria

Done when

  • Agreed entities sync with externalId and no duplicates on retry
  • Exchange journal shows object, result, and attempt
  • Failure paths are visible to operators

Deliverables

  • API/contract notes + mapping table
  • Staging exchange runbook

Out of scope

  • 1C accounting-policy changes
  • Production 1C upgrades without change windows

Assumptions

  • Test infobase and a 1C contact for metadata

The final acceptance checklist is confirmed in the brief or contract; the list above is a scope alignment guide.

Ballpark estimate

Scope size
Extras

FAQ

Tap a question to expand the answer.

Is a separate login required?

Not always. Corporate OAuth/LDAP can be connected, or an existing identity can map to a 1C employee.

Can we begin with approvals?

Yes, when the route, delegates, deadlines, and post-submission change rules are known.

Discuss this directionContact form

Tell me the goal, stack constraints, and timeline — I reply on Telegram.

View full service page