An Onit eBilling implementation configures the platform that receives, validates, and approves outside counsel invoices for a corporate legal department, then connects every law firm on the panel to it. The work runs on two sides at once. Inside the platform, billing guidelines become rules the system applies to every invoice. Outside it, each firm needs adding, briefing, and testing before the first live billing cycle. Programmes that treat both sides as one workstream produce clean invoices quickly, and programs that treat vendor onboarding as an afterthought spend their first quarter on rework.
What does an Onit eBilling implementation cover?
Five workstreams make up the delivery, and they run largely in parallel.
- Billing guideline configuration. Translating the written guidelines into conditions the platform evaluates on every submitted invoice.
- Approval and routing setup. Deciding who reviews what, at which thresholds, and what escalates.
- Data migration. Moving historical invoice, matter, vendor, and timekeeper records, cleansed before they land.
- Vendor onboarding. Adding each firm, identifying administrators, inviting users, and briefing billing staff.
- Testing. Proving every configured rule fires correctly, including deliberate submission of non-compliant invoices.
Firm count is the variable that most reliably predicts effort. A panel of twenty firms and a panel of two hundred are different exercises, because each firm needs credentials, rate loading, training, and testing regardless of how much it bills.
How do billing guidelines become platform rules?
Each written guideline is classified by whether the platform can evaluate it against invoice data, then configured as a condition, then tested. Rules built on data the system already holds convert cleanly, including rate compliance, timekeeper approval status, billing period windows, format validation, and budget thresholds.
This is where the return on the program is generated. Guidelines that stay in a shared folder get applied inconsistently, because every reviewer interprets them slightly differently and volume eventually outpaces attention. The same guidelines expressed as platform logic produce identical outcomes on every invoice. The translation work is covered in detail in turning outside counsel billing guidelines into enforceable rules.
Configuration volume grows quickly at enterprise scale. On one legal technology program, Basla configured more than fifty custom business rules, including compound conditional actions where several conditions resolve together before the platform acts. That rule configuration runs on the platform workflow engine described in what Onit Apptitude is.
Where do law firms actually submit invoices?
Through a vendor portal, and which one depends on the Onit product in use. CounselGO is the portal for SimpleLegal deployments. BillingPoint is the equivalent used with OnitX. The legal department works inside the eBilling application while firms work in the portal.
That two-layer structure is the defining characteristic of an eBilling deployment. Internal configuration determines what the platform will accept. Firm onboarding determines whether anyone submits correctly. The portal side is covered in what CounselGO is and how firms use it, and the platform context in what SimpleLegal is.
Firms with prior portal experience adapt faster. A firm already submitting through CounselGO, BillingPoint, or another eBilling portal for a different client needs far less support than a firm invoicing by email for the first time, and sequencing onboarding accordingly protects the schedule.
What results do legal departments report?
Published practitioner guidance gives two useful reference points. Swiftwater reports that well-implemented Onit eBilling programs typically deliver a 5 to 12 percent reduction in outside counsel spend through guideline enforcement, with billing guideline compliance rates moving from 60 to 70 percent on entry to 85 to 95 percent within the first year of governed enforcement. Swiftwater notes these ranges are illustrative and vary with the department’s starting point, the rigor of the guidelines, the size of the outside counsel portfolio, and the strength of implementation and governance.
The mechanism matters more than the number. Savings come from visibility, meaning rate inconsistencies, guideline breaches, and staffing patterns that were previously invisible become measurable and therefore negotiable. Departments with previously underenforced guidelines see larger movement, since there is more to correct.
Invoice validation accuracy is improving alongside this. Onit reports that Spend Agent achieves 92% invoice-level accuracy and 81% line-item accuracy, compared with 72% and 43% for experienced lawyers, based on research from the Onit AI Center of Excellence. Spend Agent is part of the AI-native capability in Onit Unity, the architecture Onit is consolidating its products onto. Automated validation of that quality depends on the guidelines being configured properly first, which returns the value of the program to the configuration work.
What does the data migration involve?
Historical invoice, matter, vendor, and timekeeper records move with the implementation, and their condition determines how much analytics value is available at go-live. Clean spend history produces immediately useful reporting.
This is consistently the most underestimated workstream. Invoice history carries years of accumulated inconsistency in vendor naming, matter references, timekeeper records, and currency treatment. Resolving it before migration costs far less than correcting reports afterwards, a pattern set out in why messy legacy data can ruin a perfect platform build.
Multi-currency environments add a further dimension, since accrual accuracy and reporting depend on consistent treatment across jurisdictions. Basla has supported matter management and eBilling programs spanning more than ten global jurisdictions, and jurisdiction count predicts eBilling effort more reliably than headcount does.
How is an eBilling configuration tested?
Through negative testing, meaning deliberate submission of invoices that breach each configured rule to confirm the platform responds correctly. Confirming that a compliant invoice passes proves very little, since the purpose of the configuration is catching what should be caught.
A complete test set covers every rule twice, once compliant and once breaching, across every firm type and jurisdiction in scope. On a contract lifecycle management rollout, Basla created and executed over a thousand test records to cover the configured paths, and eBilling rule sets generate comparable volumes once jurisdictions multiply.
Role permissions belong in the same cycle, since invoice data is commercially sensitive and reviewer access varies by matter and region. The reasoning is set out in why skipping role-based security testing breaks go-lives.
What happens in the first billing cycle?
Questions arrive from both directions, from firms querying a rejection and from reviewers querying a flag. The volume is predictable enough to staff for, and planning it keeps the configuration team free to resolve genuine defects.
On one Onit rollout, Basla’s delivery team handled roughly two hundred tickets in the first week after go-live. Around sixty percent were users asking how to complete a task, and the balance were genuine defects requiring a developer. The hypercare window ran for eight weeks with every report triaged before anything reached the configuration team. That model is described in why launches fail without a dedicated hypercare triage desk.
A practical measure that costs little: give each firm a named contact for the first cycle. Questions arrive regardless of preparation, and a clear route for them protects the legal operations team from becoming the helpdesk.
Conclusion
An Onit eBilling implementation is among the more measurable legal technology investments a department can make, because the output is spend data and the return shows up in the invoice review process within months. The platform side is well understood. What separates programs that deliver from programs that stall is the discipline applied to four specific things.
Guidelines translated into rules the system enforces, since a guideline the platform does not check is a guideline that gets applied inconsistently. Historical data cleansed before it migrates, because analytics built on inconsistent invoice history produce reports nobody trusts. Vendor onboarding run as a scheduled workstream with an owner, since the platform can only enforce rules against invoices firms actually submit. And the first billing cycle staffed deliberately, because that is when both sides of the relationship decide whether the new process works.
How Basla can help
Basla provides the delivery capability behind legal eBilling implementations, covering business analysis, billing guideline configuration, data migration support, rule testing, vendor onboarding support, documentation, and post-go-live support. Basla has supported matter management and eBilling programs spanning more than ten global jurisdictions, with hands-on experience across Onit matter management, eBilling, legal service request, and contract workflows.
Frequently asked questions
What does an Onit eBilling implementation involve?
Five workstreams: configuring billing guidelines as platform rules, setting up approval routing and thresholds, migrating historical invoice and vendor data, onboarding every law firm onto the vendor portal, and testing every configured rule including deliberate non-compliant submissions.
How long does an Onit eBilling implementation take?
It depends on scope more than on the platform. The variables that move the timeline are the number of firms to onboard, how many jurisdictions and currencies are in scope, the volume and condition of historical invoice data, and how complex the billing guidelines are.
Where do law firms submit invoices in an Onit eBilling deployment?
Through a vendor portal. CounselGO is the portal for SimpleLegal deployments and BillingPoint is the equivalent used with OnitX. The legal department reviews and approves inside the eBilling application while firms work in the portal.
What savings does Onit eBilling deliver?
Practitioner guidance from Swiftwater indicates well-implemented programs typically deliver a 5 to 12 percent reduction in outside counsel spend through guideline enforcement, with those ranges described as illustrative ranges that depend on the department’s starting point, guideline rigor, portfolio size, and implementation quality.
How much does billing guideline compliance improve?
Swiftwater reports compliance rates commonly moving from 60 to 70 percent on entry to 85 to 95 percent within the first year of governed enforcement, again presented as an illustrative range, not a guaranteed outcome.
What is the most underestimated part of an eBilling rollout?
Historical data migration and vendor onboarding. Invoice history carries years of inconsistency in vendor naming, matter references, and currency treatment, and every firm on the panel needs credentials, rate loading, briefing, and testing regardless of how much it bills.
*This article is provided for general information only and does not constitute legal advice. Basla Solutions provides legal technology implementation and support services and does not practice law.*