TELOMETRIS / APPROVALS
Recorded by a person. Accepted by the organization.
A record can exist without yet being authoritative. Telometris uses approval to distinguish between information entered by a user and information accepted by the organization for downstream use. The basic progression is: Recorded → Reviewed → Approved → Eligible for downstream use. Approval requirements may vary by company, project, record type, and role.
Why approval exists
Time, invoices, and other financial records affect what people are paid, what clients are charged, and how project performance is understood.
Approval provides a deliberate checkpoint before those records become part of an authoritative business process.
It is not merely a visual status. It expresses organizational acceptance.
Company and project-specific rules
A company may establish general approval policy while allowing projects to apply their own requirements or overrides.
This matters because not every project has the same level of financial risk, supervision, or client obligation.
One project may require active approval of time. Another may operate under a different policy.
Time-entry approval
A time entry describes work recorded by a user.
Where approval is required, an authorized reviewer confirms that the entry is accepted for downstream use. Approval may affect eligibility for contractor invoicing, client invoicing, reporting, profitability calculations, and administrative review.
The original time entry remains the operational record.
Contractor-invoice approval
A contractor invoice records a company obligation.
After submission, the company may review it, request revisions, approve it, and later mark it paid.
Contractor-invoice approval confirms that the company accepts the invoice as an amount owed.
Client-invoice approval
A client invoice records a company receivable.
Where configured, a draft must be approved before it can be sent or treated as an issued invoice.
This provides a checkpoint for rates, line items, expenses, fixed-fee obligations, invoice notes, and delivery information.
Roles and approval authority
Approval authority follows role and permission rules.
Company roles establish broad authority. Project assignments and project-specific permissions may refine what a user can review or approve.
Not every user can approve every record.
How approved records move downstream
Approval connects operational truth to financial use.
Examples include approved time becoming eligible for contractor invoicing or client billing, an approved contractor invoice becoming an accepted company obligation, an approved client invoice becoming eligible for delivery, and approved records contributing to reliable reporting.
The approval layer allows the same work record to support several downstream uses without collapsing those uses into one process.
Common inquiries
Does every time entry require approval?
Not necessarily. Approval requirements depend on company and project policy.
Can approval requirements differ by project?
Yes. Project-level settings or overrides may apply different approval requirements to different work.
Who may approve time?
Approval authority depends on company roles, project roles, and configured permissions.
Must a client invoice be approved before sending?
Only when the company's client-invoicing settings require approval before delivery.
Can contractor invoices be returned for revision?
Yes. A submitted contractor invoice may be returned for revision before approval.
How does approval affect invoicing and reporting?
Approval can determine whether a record is accepted for downstream financial use and whether it should be treated as authoritative in reporting.
Are expense approvals included?
Expenses do not have a standalone expense-approval workflow. They participate in billing and profitability according to their implemented status and settings.
Begin recording.
14 days free, then from $5–$8 per user per month. Every feature included.
Start Free Trial