Recorded
Someone claims an hour against a piece of work. It has an author and a timestamp, nothing more.
Recorded, billable, billed and collected are four different states of the same hour. Hold them in one field with a flag and leakage lives in the gap the schema cannot express, so work in progress becomes an argument.
Tell us what you are building
Professional services software development builds the systems a firm bills from: time capture, rate cards, work in progress, invoicing and revenue recognition. The packaged category is professional services automation, or PSA. The hard part is that recorded, billable, billed and collected are four states of the same hour, and one field with a flag cannot tell them apart.
Our work
We have no consultancy, agency, legal practice or accounting firm among our clients, and saying so beats calling a software client a practice.
The core idea
An hour recorded is not an hour billed, and an hour billed is not an hour collected. Hold one field and three become opinion.
Someone claims an hour against a piece of work. It has an author and a timestamp, nothing more.
A rule makes the claim chargeable at a value, from the engagement and the card as at the work date.
The value reaches an invoice. Until it does it is work in progress: a balance the firm carries, not a report.
Cash arrives against the invoice. High utilisation with slow collection means busy and short of money at once.
Write offs between recorded and billable, unbilled work and disbursements between billable and billed, bad debt after.
Finance counts billed hours, delivery counts recorded, both are right. Settle it in the model, not a meeting.
Scope
Six pieces of work. Most engagements are three or four, and the first decides what the rest cost.
The form is commodity. What counts as a valid entry on your engagements is not, so the rules sit behind it.
A second model, not a report on the first. If the schedule is derived from the invoice, a change to either one silently rewrites the other.
Build or buy
Three honest routes, and one case where none is us. The test: how many commercial levels your contracts need, whether your revenue schedule must be independent of billing, and whether you hold client money.
Kantata, Certinia, Scoro, BigTime, Accelo, Productive and BQE Core all bundle time, billing and resourcing. Fastest when your model fits theirs.
Worth it when the commercial model is what does not fit: caps at several levels, a schedule independent of billing, or a past date position.
Keep the ledger and the resourcing tool, build the layer between them, and settle which system owns the invoice first.
A whole platform replaced inside a quarter, legal, tax or audit advice, or a partner to hold client money. No case study in this sector yet, which argues for a small first phase.
Integration
Three families of system, and the constraint that decides the plan in each. The work is almost always integration, because these products are configurable rather than programmable.
| System family | What it is | The constraint that decides the plan |
|---|---|---|
| Practice and professional services automation | Kantata, Certinia, Deltek, Unit4, Projectworks and Scoro cover mid market and larger firms, bundling time, billing and resourcing. | How many commercial levels the product models. One that understands a project will not grow a second above it. |
| Sector specific practice management | Clio, Actionstep and LEAP under legal practices. IRIS, Karbon and CCH under accounting firms. Deltek and Newforma under engineering and design. | They carry the sector obligations natively, which is worth a lot, and are least flexible about the commercial model. |
| The ledger and everything around it | Xero, QuickBooks, NetSuite, Sage Intacct and Tally underneath, Stripe, GoCardless and Razorpay on collection, and an e-invoicing path where one is required. | Rarely the API. Nearly always which system is authoritative for the invoice and which merely reports it. |
A practice management system, a resourcing tool and a general ledger are three products; buying one does not give you the other two. Settle which owns the revenue schedule first, because retrofitting means restating closed periods. On what the engagement record tells you, see capacity and margin forecasting from engagement data.
Compliance
Not a badge wall. These change the data model, the retention policy or the delivery date. Each row names where and when we read it, and each is a requirement on your firm.
| Instrument | What it forces the software to do | When it applied, and where we read it |
|---|---|---|
| IFRS 15, Revenue from Contracts with Customers | Where a performance obligation is satisfied over time, progress must be measured and the method applied consistently: an input method such as labour hours, or an output method such as milestones. That makes the choice a system requirement. The US equivalent asks the same. | Issued by the International Accounting Standards Board in May 2014, effective for annual periods beginning on or after 1 January 2018, per ifrs.org, read 17 November 2026. |
| SRA Accounts Rules, England and Wales | A ledger specification with rule numbers. Client money stays separate from the firm's own, a client account cannot provide banking facilities, and a bill comes before costs are taken. Rules 8.2 and 8.3 require bank statements at least every five weeks plus a reconciliation signed off by the COFA or a manager. | Version marked current in effect from 25 November 2019, per sra.org.uk, read 17 November 2026. One regulator's version of a general duty: whichever licenses your firm sets your detail. |
| European e-invoicing: Directive 2014/55/EU with Peppol BIS Billing 3.0 | The Directive creates a common European standard for the semantic data model of an electronic invoice's core elements, and Article 7 requires contracting authorities to receive and process compliant invoices. Peppol BIS Billing 3.0 binds the EN16931 model to UBL syntax, so a credit note's element names still say invoice. | Dated 16 April 2014. Article 11(1) required Member States to apply the implementing provisions by 27 November 2018, per eur-lex.europa.eu. The current Peppol set is the May 2026 release, per docs.peppol.eu. Both read 13 November 2026. |
| GDPR, Regulation (EU) 2016/679 | Client files carry personal data about people who are not your client, which makes controller and processor roles a per engagement question. Retention is per data category, because record keeping duties outlast the engagement. | Dated 27 April 2016. Article 99 states that it applies from 25 May 2018, per eur-lex.europa.eu, read 17 November 2026. |
We build to these controls and hand you the evidence for your audit. A vendor assessment will also ask about ISO/IEC 27001, SOC 1 and SOC 2; Zyneto holds none. Three boundaries, stated plainly: we do not provide legal, tax or audit advice, we do not hold client money, and we are not an accredited service provider for e-invoicing or statutory filing, so confirm who yours is before a plan depends on a date. Rates, thresholds and windows differ by jurisdiction and move, so confirm yours with your regulator and accountant. On the reporting clock, see billing review and approval routing inside a workflow.
Transparency
We publish the hours and the module breakdown, and a fixed price follows discovery. Seven modules, each with its own range, and the arithmetic. The scope assumes a firm keeping its ledger and taking engagement, time, billing and recognition in house.
Phase one hours
1,180
Seven modules, each inside its range.
Typical timeline
14 to 22 weeks
As a squad. A year end compresses scope, not the calendar.
Useful hours
1,040 to 1,860
Every module at its minimum, through to its maximum.
| Driver | Hours |
|---|---|
| How many commercial levels you needOne project at one rate is a different model from caps at several levels. | High impact |
| Whether rate cards are already datedDated reference data is integration work. Rates on timesheet rows means re-rating under live history. | The largest swing |
| Whether revenue recognition is in scopeA schedule independent of billing is a second model, and the one discovered late most often. | Adds real scope |
| Which ledger you keep, and what it exposes | 80 to 200 each |
| Whether client money is heldA position for a past date is bounded. Rebuilding one from a pooled history is not. | 150 to 260 |
| How many entities, currencies and tax regimesPriced in one currency, delivered in another, reported in a third: a rate date per event. | Medium |
| How much history migratesReplay testing scales with the variety of your rate structures, not with headcount. | Rarely small |
| Module | Hours |
|---|---|
| Engagement, contract and rate card model | 160 to 280 |
| Time and expense capture with validation | 120 to 220 |
| Billing, work in progress and the invoice run | 180 to 320 |
| Revenue recognition and the schedule | 160 to 280 |
| Resourcing, capacity and forecasting | 140 to 260 |
| Integrations: ledger, payments, identity, e-invoicing | 160 to 280 |
| Client portal, reporting and audit trail | 120 to 220 |
Delivery
Five phases, each named by the artifact it produces rather than by a generic stage.
Phase 01
How contract, engagement and project relate, where terms may sit, and what a cap applies to.
Phase 02
Every rate dimension, every write off reason, and what a retroactive change does to time already billed.
Phase 03
How progress is measured per contract type, how billing and revenue schedules differ, and what happens at close.
Phase 04
A past year of time and billing replayed per engagement and compared entry by entry, not netted off.
Phase 05
Runbooks, the write off policy as implemented, and the control documentation your auditor asks for.
Two different things. Here it means software built for firms that sell expertise by the engagement: consultancies, agencies, law firms, accountants, engineers and architects. The packaged version is sold as professional services automation, or PSA. The other meaning is a software company's own consulting arm, and search results for the phrase mix the two.
Law, accountancy and audit, management and technology consulting, creative agencies, architecture and engineering, surveying, and recruitment. What they share is that the product is people's time, sold under an engagement with terms. That is why time, rate and engagement are the three objects their software is built on.
Professional services automation, or PSA, is the packaged category that bundles time capture, billing and resourcing into one product. Most firms should start there. Build custom when the commercial model is what does not fit: caps at several levels in one contract, a revenue schedule independent of billing, or a client money position for a past date.
Answer three questions first. How many commercial levels do your contracts need, must your revenue schedule be independent of billing, and do you hold money belonging to a client? A packaged product usually handles the first and rarely the second, so the common outcome is a hybrid: keep the ledger and the resourcing tool, and build the layer between.
Measure progress. Where a performance obligation is satisfied over time, IFRS 15 requires progress to be measured consistently, by an input method such as labour hours or an output method such as milestones. So the system needs a revenue schedule separate from billing, because a retainer billed evenly against work delivered unevenly recognises unevenly. The standard was issued by the International Accounting Standards Board in May 2014, per ifrs.org, read 17 November 2026.
They make a past date the question, so the system produces a per matter position for any past date rather than a reconciled bank balance. Under the SRA Accounts Rules in England and Wales, client money stays separate from the firm's own, and Rules 8.2 and 8.3 require bank statements at least every five weeks plus a reconciliation signed off by the COFA or a manager, per sra.org.uk, read 17 November 2026.
Fourteen to twenty two weeks as a squad. The worked example in the scope section is seven modules and 1,180 hours, and the same ranges sum to 1,040 hours at every minimum and 1,860 at every maximum, so a smaller or larger phase one is a question of which modules are in it.
Four steps, each with a shape, so booking a call is a known quantity.
Bring how your system decides what an hour is worth, and how last month's work in progress figure was produced.
We establish whether your rate cards are dated, and whether work in progress is computed or assembled.
Against the hour ranges published here, with anything excluded named as excluded.
Whether we build it, your team does, or your incumbent extends. The document is yours either way.
Bring one engagement and how last month's work in progress figure was produced. Thirty minutes usually tells both of us whether this is a fit.
Real feedback from the people we've proudly partnered with.
Zyneto Global Technologies provided excellent project management and technical expertise throughout the engagement. The team was responsive, collaborative, and adaptive, ensuring the project met our expectations and set a strong foundation for future growth.
We engaged Zyneto to design and develop a custom web platform for Moneteo, aimed at improving project management, data tracking, and collaboration across internal teams and external partners. Their work included full-stack web development, custom modules for workflow automation, API integration, and comprehensive testing.
Overall, their responsiveness and timely deliveries contributed positively to the project's success. The client achieved better data management and quality. The service provider delivered the project on time and ensured prompt responsiveness throughout the engagement. Their innovative approach was outstanding.
Explore further
Engagement and rate cards
Client portals
Valuation and recognition runs
Engagement letters and papers
Billing review and approvals
Capacity forecasting
Productising a practice
Client accounts
Every sector
Document, automation and reporting work that applies directly to time, billing and delivery systems.