Camlin Workflow
Camlin Workflow
A business system for services businesses. People record their time, billing works from the approved hours and draws on purchase orders, and statements are built from the invoices. Each customer has an install of its own, with modules switched on for the work it does, and an assistant that acts through the same permissions as the person using it.
TimesheetsBilling against purchase ordersStatementsPeople and permission roles
“What does Camlin Workflow do for a services business?”
THE MODULES
What Camlin Workflow does
Each install switches on the modules it needs. A module that needs another is on only while that one is on: billing needs timesheets, and statements need billing.
Core: the company and its people
The company profile holds the legal details, the tax rate and how invoice numbers are formed. People are invited onto a roster with a permission role, which is kept apart from their job title. Core is always on.
Timesheets
Team members enter and see their own timesheets. Administrators and finance see everyone’s. Billing works from the approved hours.
Billing
Billing covers how work is billed, numbered and taxed, and how it is drawn from a purchase order. A customer’s billing rule, such as which purchase order a person’s days go to first, is kept as a record with who confirmed it and when. What was issued is never changed.
Statements
Statements are built from the invoices that billing issues.
Work that runs on a schedule
Scheduled jobs raise recurring invoice drafts and poll a mailbox. Each job names the company it acts for, and a module that is off runs no jobs.
Permission roles
The built-in roles are Administrator, Finance and Team member. An administrator runs the install. Finance works with billing, accounting and the figures behind them. A team member sees and records their own work.
THE ASSISTANT
An assistant that asks first
The assistant works through the same permissions as the person using it.
- It acts in every module as the signed-in person, with that person’s permissions.
- It can read, and it can leave drafts for a person to approve.
- Changing a record needs that person’s confirmation for that exact change.
- Issuing an invoice, sending an email or pushing to accounting needs confirmation too, and never runs unattended.
MOVING OVER
Moving from the current system
A customer moves from their current system to Camlin Workflow with the old one still running.
An import from the current system
A customer’s records come over from their current system by an import, run before cutover and again on each refreshed copy. Each imported record keeps the id it had in the old system.
Nothing sent out until the switch is on
Until cutover the new install runs beside the old one. No email to a customer, no push to accounting and no webhook leaves it until the install’s outbound switch is on.
Issued months rebuilt and compared
Billing rebuilds every month already issued from the imported records, and it must match to the cent.