Overview
In this guide, you will learn:
- What revenue recognition means and why it matters
- The four revenue recognition methods available in Keka PSA
- How each method works with real-world examples
Who can do this?
- Finance Admins
- PSA Admins
- Users with access to Project Financials
Pre-requisites
- A billing-enabled project set up in Keka PSA
- Revenue recognition method configured for the project
Note: You can assign different recognition methods per project depending on the operational model
Introduction
Revenue recognition is an accounting principle that helps businesses track income based on when it is earned—not when payment is received. In long-term or multi-phase projects, recognizing revenue progressively helps businesses match their earnings with the costs incurred during the same period. This ensures more accurate profit measurement and financial reporting.
Keka PSA offers four flexible revenue recognition methods that allow businesses to measure project revenue according to their specific operational model.
Note : This functionality is exclusively available on the PSA Advanced plan.
Revenue Recognition Methods
1. Income to date
This method calculates recognized revenue based on actual work delivered, multiplied by its respective selling price. It is particularly useful when you want to track earnings tied directly to billable activities—such as hours logged or units delivered—regardless of the overall project estimate.
Example: A client has been quoted for:
- 120 hours of service at ₹2,000/hour
15 devices at ₹5,000 each
By the current date, the project has:
Completed 60 hours of work
Delivered and invoiced 10 devices
Recognized revenue =
(60 × ₹2,000) + (10 × ₹5,000) = ₹1,20,000 + ₹50,000 = ₹1,70,000
This method does not depend on total project duration or cost estimates. It purely reflects revenue earned from work already delivered.
2. Invoiced amount
In this method, revenue is recognized based on the total value of invoices generated for the project. It is commonly used in milestone billing or installment-based payment models.
Example: If you have a project worth ₹10,00,000 and you’ve already invoiced the client for ₹4,00,000, the recognized revenue will be:
₹4,00,000
This method is straightforward and links directly to financial transactions. It’s ideal for businesses that prefer to align revenue with actual billing, rather than project progress.
3. Revenue based on cost (cost-to-cost method)
This method evaluates revenue based on the ratio of actual cost incurred to the total estimated project cost. It is well-suited for projects where expenses form a major part of delivery.
Example: A project has -
Total estimated cost: ₹6,00,000
Budgeted revenue: ₹8,00,000
Incurred costs so far: ₹3,00,000
Project progress = ₹3,00,000 / ₹6,00,000 = 50%
Recognized revenue = 50% × ₹8,00,000 = ₹4,00,000
This method helps you measure revenue in proportion to how much has already been spent to deliver the project.
4. Revenue based on time (time-expended method)
In this approach, progress is measured using the time already invested in the project, compared to the estimated total time required. Revenue is then recognized in proportion to that progress.
Example:
Estimated effort: 200 hours
Time spent so far: 80 hours
Budgeted income: ₹5,00,000
Project progress = 80 / 200 = 40%
Recognized revenue = 40% × ₹5,00,000 = ₹2,00,000
This method is beneficial when your projects are primarily driven by hours logged rather than external costs or milestones.
How It Connects with Other Modules
| Module | Integration Details |
|---|---|
| Timesheets | Time-based revenue recognition methods rely on hours logged in timesheets |
| Billing | Invoice-based revenue recognition pulls data from invoice creation and status |
| Costing | Cost-based recognition uses cost entries and actual expense records |
FAQs
· Q: Can I assign different recognition methods to different projects?
A: Yes, each project can follow a different method depending on its financial model.
· Q: What happens if actuals exceed budgeted values?
A: Recognition will still apply based on selected logic—Keka does not automatically cap revenue.
· Q: Can I change the recognition method mid-project?
A: This is not recommended and depends on admin permissions. Speak to your finance team.
· Q: Do these methods affect invoice generation?
A: No, invoice generation is independent; revenue recognition is used for reporting purposes only.
Troubleshooting
· Mismatch in revenue reports?
Verify the recognition method applied at project level
Check actual vs estimated cost or hours, depending on the method
Ensure timesheets or costs have been logged
Check if billing/invoice entries are posted for invoice-based method
Comments
0 comments
Please sign in to leave a comment.