Everything in AdComPro hangs on a single chain. Once you know that chain, you can find every screen:
| Term | What it is |
|---|---|
| Organisation | The environment you work in. Everything you see — customers, projects, hours, reports — belongs to your organisation and is invisible to other organisations on the same platform. |
| Company | The B.V. that does the invoicing. An organisation can have several companies; for each project you choose which company sends the invoice. The default hourly rate is also stored here. |
| Customer | The party you work for. A customer belongs to a company and has zero or more projects. Customers of the type Internal are not a real client but your own organisation, for internal hours. |
| Project | The unit that hours are logged on and that you report on. Every project has a type (retainer, fixed price, time and materials…) that determines which fields and calculations apply. |
| Milestone | A block of work within a project, for example “Content & social”. Milestones determine the structure of your report. |
| Task | The work within a milestone that time is actually logged on. A task can have its own hourly rate or fixed price. |
| Time entry | One booking: who, which day, how much time, on what, and with which description. The rate is fixed at the moment of booking. |
| Report | A draft overview of all not-yet-invoiced hours and costs of a project. You edit it, check it and finalise it; after that it is the basis for the invoice. |
The rate ladder
The hourly rate of a booking is determined in this order, and the first one that is filled in wins:
- Task — the rate on the task itself
- Milestone — the rate of the milestone that task belongs to
- Project — the default rate of the project
- Company — the default rate of the company that invoices the project
Note: the rate is fixed on the time entry at the moment of booking. If you change a price later, the hours already booked do not change — only new bookings follow the new price. Price changes are, however, tracked in the project’s activity block.
From hour to invoice
- Someone logs hours on a project (chapter 4).
- Those hours are in draft or pending and get approved (chapter 7). Only approved hours end up on a report.
- You generate a report for a period (chapter 13). All approved, not-yet-invoiced hours of that project are included.
- You edit the report: merge lines, hide them, roll them over, round them (chapter 14).
- You check the end result and finalise (chapter 15). The PDF goes to the customer, and the hours are thereby processed.
The five roles
| Role | What it is meant for |
|---|---|
| Reader | Watching along. No changes. |
| User | The regular employee: log and view your own hours, view your own projects. |
| Project manager | Everything a User can do, plus manage all projects of their own organisation, approve other people’s hours and create reports. |
| Admin | Manages the organisation: users, companies, customers, settings and all financial screens. |
| Super admin | Manages the platform itself. Also sees the technical screens from chapter 27. |
Chapter 28 contains a matrix showing, per screen, who has access. If you do not see a button from this book, it is almost always your role — or the module is switched off for your organisation (chapter 27).