Welcome!

Microservices Expo Authors: Liz McMillan, Elizabeth White, Pat Romanski, AppDynamics Blog, TJ Randall

Related Topics: @CloudExpo, Microservices Expo, Containers Expo Blog, Agile Computing, @DXWorldExpo, SDN Journal

@CloudExpo: Article

Everything-as-a-Service Demands New Approach to Accounts Receivables

Today’s increasing service complexity is best handled by an integrated complete solution for monetization

When we first built our MetraNet billing platform our customers (large enterprises and service providers) generally offered services that were clearly defined in terms of character and scope, with fairly stable setup charges, usage charges, and periodic recurring charges. Back then, with some exceptions, it was normal to issue regular periodic invoices that consolidated all of those charges. The invoice would then trigger an entry in the service provider's Accounts Receivable (AR) ledger. That in turn, again with a few exceptions, would constitute the point at which Revenue Recognition would take place. The few exceptions (for example, an invoice for a payment in advance for a service set-up charge) would be handled by adding a matching journal entry in Deferred (or unearned) Revenue until such time as the services had been delivered. The adjustment could be handled automatically (triggered by a flag from order management or billing) or manually.

Things have moved on from there and the metadata driven character of MetraNet has enabled MetraNet to support new requirements fluidly and easily. A few years ago, we developed a capability to handle the increasingly more complex requirements of services-related AR. In discussions with customers on AR, it is becoming clear that the additional power and flexibility delivered by our approach to AR will no longer be an exceptional need - it will be an everyday requirement for most service providers.

I have written a lot recently about "Everything as a Service" (XaaS) and the closely linked concept of the "Internet of Things." These labels are helpful in crystallizing in our minds what has been going on for some time. We are observing changes on multiple fronts. Products and devices increasingly become tools for the delivery of services. Services can be delivered by Agents that interact with other Agents to deliver more complex service bundles, or strip out service components to recombine them with other components to create new services. It's conceivable that Cloud Service Brokers will evolve into brokerage networks, collecting and representing services for adaptation and resell in a way that compensates multiple contributors along the value chain. At the same time services providers have to do all this while continuing to operate, and be seen to operate, within the regulatory rules.

Periodic invoices just seem so slow for this kind of environment!

As invoicing becomes more flexible and more complex, the way we handle Accounts Receivables needs to keep up. MetraTech's AR solution (MetraARTM) abstracts accounting securely from the dynamic business modeling of the billing system and enables solid and auditable integration with our customers' accounting systems.

What is special about MetraTech's metadata-driven approach? For one thing, it provides a flexible and pragmatic way around the all-or-nothing choice usually available with traditional systems. The traditional approach forces a choice between Invoice Accounting and Line Item Accounting. Invoice Accounting doesn't provide sufficient granularity when reselling supplier services, selling or re-selling regulated services, or in any case where different parts of the invoice have varying contractual or legal demands for prioritization. On the other hand, Line Item Accounting becomes completely unwieldy and difficult to scale when used on enterprise accounts or for any high-volume, event-based service.

Within MetraAR we have built on our innovative patent-pending "Demand for Payment" (DfP) technology. This enables a service provider to select the most appropriate level of granularity for managing receivables. Rather than being forced into an all-or-nothing choice, a service provider can segment different components of the invoice into separate DfPs without having to go down to the line item detail. For example, perhaps you are reselling cloud services from different vendors. One vendor has a net 30-day contract with you and the other a net 45. You would want to distribute payment against the receivables associated with the Net 30 supplier, but you don't want to track the hundreds or thousands of line items that wound up on your channel partner's wholesale invoice. Instead you can group all the charges into a single Demand for Payment and manage that group as one entity.

It doesn't stop there. Each Demand for Payment can be further split as needed to handle partial payments, payments on account, disputes, and any other events that affect receivables. A single customer payment can be apportioned across multiple DfPs in whatever way is required.

The MetraNet billing platform already provides a complete and flexible system for handling subscriptions to the most complex accounts. With the added MetraAR functionality, we provide even more scope for handling those "exceptional" needs that are rapidly becoming normal everyday business. It is now even easier to set up custom payment plans, reassign and consolidate debt, and manage external debt. The use of DfPs enables Aging to be managed more accurately, with a range of aging algorithms that ensure that priority is given to the right accounts for collection and follow-up.

Our customers realize that today's increasing service complexity is best handled by an integrated complete solution for monetization, rather than a fragmented approach using separate point products. At the same time, the solution needs to work smoothly with financial accounting systems. The latest evolution of MetraNet with MetraAR does all this, and does so in a way that enables the service provider to introduce more complexity only where complexity is really needed, and to keep things simple where simple is the smarter way.

More Stories By Esmeralda Swartz

Esmeralda Swartz is VP, Marketing Enterprise and Cloud, BUSS. She has spent 15 years as a marketing, product management, and business development technology executive bringing disruptive technologies and companies to market. Esmeralda was CMO of MetraTech, now part of Ericsson. At MetraTech, Esmeralda was responsible for go-to-market strategy and execution for enterprise and SaaS products, product management, business development and partner programs. Prior to MetraTech, Esmeralda was co-founder, Vice President of Marketing and Business Development at Lightwolf Technologies, a big data management startup. She was previously co-founder and Senior Vice President of Marketing and Business Development of Soapstone Networks, a developer of resource and service control software, now part of Extreme Networks.

Comments (1)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Microservices Articles
"There is a huge interest in Kubernetes. People are now starting to use Kubernetes and implement it," stated Sebastian Scheele, co-founder of Loodse, in this SYS-CON.tv interview at DevOps at 19th Cloud Expo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
Today most companies are adopting or evaluating container technology - Docker in particular - to speed up application deployment, drive down cost, ease management and make application delivery more flexible overall. As with most new architectures, this dream takes significant work to become a reality. Even when you do get your application componentized enough and packaged properly, there are still challenges for DevOps teams to making the shift to continuous delivery and achieving that reducti...
Skeuomorphism usually means retaining existing design cues in something new that doesn’t actually need them. However, the concept of skeuomorphism can be thought of as relating more broadly to applying existing patterns to new technologies that, in fact, cry out for new approaches. In his session at DevOps Summit, Gordon Haff, Senior Cloud Strategy Marketing and Evangelism Manager at Red Hat, discussed why containers should be paired with new architectural practices such as microservices rathe...
With the rise of Docker, Kubernetes, and other container technologies, the growth of microservices has skyrocketed among dev teams looking to innovate on a faster release cycle. This has enabled teams to finally realize their DevOps goals to ship and iterate quickly in a continuous delivery model. Why containers are growing in popularity is no surprise — they’re extremely easy to spin up or down, but come with an unforeseen issue. However, without the right foresight, DevOps and IT teams may lo...
Kubernetes is a new and revolutionary open-sourced system for managing containers across multiple hosts in a cluster. Ansible is a simple IT automation tool for just about any requirement for reproducible environments. In his session at @DevOpsSummit at 18th Cloud Expo, Patrick Galbraith, a principal engineer at HPE, will discuss how to build a fully functional Kubernetes cluster on a number of virtual machines or bare-metal hosts. Also included will be a brief demonstration of running a Galer...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
In his session at 20th Cloud Expo, Mike Johnston, an infrastructure engineer at Supergiant.io, will discuss how to use Kubernetes to setup a SaaS infrastructure for your business. Mike Johnston is an infrastructure engineer at Supergiant.io with over 12 years of experience designing, deploying, and maintaining server and workstation infrastructure at all scales. He has experience with brick and mortar data centers as well as cloud providers like Digital Ocean, Amazon Web Services, and Rackspace....
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and co...
At its core DevOps is all about collaboration. The lines of communication must be opened and it takes some effort to ensure that they stay that way. It’s easy to pay lip service to trends and talk about implementing new methodologies, but without action, real benefits cannot be realized. Success requires planning, advocates empowered to effect change, and, of course, the right tooling. To bring about a cultural shift it’s important to share challenges. In simple terms, ensuring that everyone k...