FinTech • • 3 min read

Billing Total vs. ADBV: A Developer’s First Confusion

In the world of software engineering and project management, tracking "how much work we did" versus "how much money we asked for" is a constant challenge. Misunderstanding these two metrics can lead to skewed performance reviews or, worse, a company running out of cash despite being highly productive. Today, we break down Agreed Delivery Billable Value and Billing Total.

The Coffee Break Chat: Making Sense of the Numbers

To illustrate the difference, let’s listen in on a conversation between Sarah (a Project Manager) and Mark (a Finance Controller) as they review the end-of-month reports.

Mark: "Hey Sarah, I’m looking at the October report. The Billing Total we sent out to Client X was only $5,000, but your progress report looks much higher. What’s the deal?"

Sarah: "Ah, that’s because the Agreed Delivery Billable Value for this month is actually $12,000. My team worked overtime to finish the design phase and the initial backend setup."

Mark: "So we've technically 'earned' $12,000 worth of work? Why is the Billing Total so low then?"

Sarah: "Exactly. The $12,000 is the value of what we delivered based on our contract rates. However, our contract says we only invoice at specific milestones. Since the backend isn't 100% signed off yet, it hasn't hit the Billing Total for this month’s invoice. That remaining $7,000 will move into the Billing Total next month."

Mark: "Got it. So the Billable Value shows me how hard your team is working, while the Billing Total tells me how much cash is actually coming into the bank right now."

Sarah: "Spot on!"

Key Takeaways

  • Agreed Delivery Billable Value: This is your "Work in Progress" (WIP) value. It tracks the monetary value of tasks completed, regardless of whether a bill has been sent. It is a performance metric.
  • Billing Total: This is the "Invoice" value. It is the final amount written on the bill sent to the customer. It is a cash flow metric.

Why the Gap Matters

The gap between these two numbers tells a story about your project’s health:

  • High Billable Value / Low Billing Total: Your team is highly productive, but you are "financing" the client. This leads to high unbilled revenue and potential cash flow strain.
  • Low Billable Value / High Billing Total: You’ve likely taken a deposit or a large upfront milestone payment. You have cash in the bank, but you owe the client a significant amount of labor.

Strategic Insights: Technical Implementation

From a systems perspective, your ERP or Project Management tool needs to track these independently. Below is a simplified C# structure for calculating these variances in a .NET backend environment:


public class ProjectFinancialMetrics
{
    public decimal AgreedDeliveryBillableValue { get; set; }
    public decimal BillingTotal { get; set; }

    public decimal UnbilledRevenue => AgreedDeliveryBillableValue - BillingTotal;

    public string GetHealthStatus()
    {
        if (UnbilledRevenue > (AgreedDeliveryBillableValue * 0.5m))
        {
            return "Risk: High Unbilled Work. Check Milestone Sign-offs.";
        }
        return "Healthy: Revenue and Billing are aligned.";
    }
}

By monitoring the UnbilledRevenue (the gap), managers can identify if the team is stuck on "almost finished" tasks that aren't hitting the invoicing criteria, allowing for faster intervention and better financial stability.

← Back to Blog