Accounting Seed is a full accounting platform built natively on the Salesforce platform — general ledger, billing, AR, AP and financial reporting living on the same records as your clients and matters. Twopir Consulting implements it, configures it around contingency, hybrid and split-fee arrangements, and builds the custom logic a firm needs when out-of-the-box configuration runs out. One ledger, one platform, from time entry to partner P&L.
All four figures are from a single engagement with a mid-size US family law firm of 150 employees — not a blended average across clients. Read the full case study.
Twopir Consulting has delivered Salesforce and finance systems for 500+ organizations across 12+ years — including law firms running billing, trust and matter operations on one platform.
Systems We Build On
A law firm's financial problems are almost never accounting problems. They are handoff problems — between the system where the work happens and the system where the money is recorded. Every gap below is one of those handoffs, and each one costs realized revenue.
Hours are captured in the case management system and billed from somewhere else. WIP ages quietly, write-offs get discovered at month end, and nobody can say what unbilled work is actually worth today.
Client funds are tracked outside the ledger, so three-way reconciliation becomes a monthly reconstruction exercise. The firm carries real compliance exposure on a file one person maintains.
Hundreds of matters are invoiced manually, interest and late fees are tracked from memory, and the close takes days that partners spend reviewing invoices instead of practising law.
Contingency, hybrid, flat-fee, capped and split-fee arrangements get forced into an hourly template. The workaround becomes the process, and the numbers stop reflecting the actual engagement terms.
A matter closed in Salesforce is still open in accounting. Two systems hold two versions of the same client, and leadership ends up trusting neither number enough to act on it.
Revenue by matter, attorney, practice group and office requires a spreadsheet somebody rebuilds every quarter. Compensation and staffing decisions get made on a number that is already out of date.
Accounting Seed is an accounting platform built natively on the Salesforce platform. It provides general ledger, accounts receivable, accounts payable, billing and invoicing, project accounting, financial reporting and online payment processing — and because it is native rather than integrated, the firm's financial records sit on the same platform as its client, matter and intake records. It has been listed on the Salesforce AppExchange for over a decade and is used by finance teams in more than 30 countries.
For a law firm the practical consequence is specific: there is no nightly sync to reconcile, no middleware to maintain, and no second definition of "client" to keep in step. A matter and its invoices are the same record hierarchy, so realization, WIP and trust balances can be reported next to case status without an export. Accounting Seed does not publish public pricing; licensing is quoted per firm by the vendor. Accounting Seed's own legal documentation covers the product surface; this page covers what we build with it.
The platform's own capability. None of this is something Twopir built — it ships with the product.
The service. We design the financial architecture, then implement, configure and extend the product to match it.
The operating change. This is what partners actually notice in the first two quarters after go-live.
"We work with Accounting Seed" hides the only question that matters to a buyer: which of these do you actually need? Twopir Consulting offers all four, and the boundary between configuration and custom development is stated below rather than discovered halfway through a project.
| Engagement | What it covers | Where the boundary sits |
|---|---|---|
| Implement | Standing the product up: ledger structure, chart of accounts, tax and entity setup, users and permissions, opening balances, and migration of historical AR, AP and trust positions. "Accounting Seed implementation partner" | Ends when the firm can run a full billing cycle and close a period on the new ledger. Everything here is standard product setup — no custom code is involved. |
| Configure | Shaping the product to the firm's process: rate tables, billing formats, fee arrangements, trust sub-ledgers, approval routing, recurring and retainer billing, reports and dashboards. "Accounting Seed configuration for law firms" | Declarative only — Flow, formula fields, page layouts, permission sets and native settings. If it can be built without Apex, it belongs in this tier and it stays upgrade-safe. |
| Build on | Custom development where the product's configuration surface runs out: fee-split allocation logic, interest and late-fee automation, bespoke billing formats, matter-level revenue rules, external system APIs. "custom Accounting Seed development" | Starts the moment a requirement needs Apex, Lightning Web Components or an API integration. We write it as tested, bulk-safe code against the product's supported objects, never by modifying the managed package. |
| Rescue | Fixing an existing deployment: unwinding workarounds, correcting ledger and trust structure, repairing broken integrations, and rebuilding reporting the firm stopped trusting. "Accounting Seed implementation not working" | Begins with an assessment, not a rebuild. Most of what's wrong is architecture, not the product — we keep the org wherever the data and structure can be corrected in place. |
Most firms need two of the four. The purpose of discovery is to tell you which two before you commit budget to the wrong one.
A law firm's billing is not a generic AR process. These are the eight areas where legal finance differs from every other industry running Accounting Seed, and where the configuration and custom work actually goes.
Rate tables by client, matter type and timekeeper. Mass invoicing across hundreds of matters in one run, with billing formats a client's audit team will accept.
Client funds held in separated ledgers inside the accounting system, with sub-accounts tracked by matter so reconciliation is a report rather than a reconstruction.
Capture through review, approval and write-down into a billable line, so unbilled WIP is a live number on the matter rather than a month-end discovery.
Evergreen retainers with replenishment thresholds, subscription and flat-fee arrangements, and scheduled billing runs that do not need a person to remember them.
Automated calculation against each firm's own terms and grace periods. On one engagement this removed manual interest tracking from the billing team entirely.
Originating, working and referring attorney splits calculated on the revenue as it is recognised — including contingency and hybrid arrangements and cross-office referrals.
Vendor bills, expert fees and case cost advances recorded against the matter that incurred them, so advanced costs are recovered at settlement instead of absorbed.
Realization, WIP, AR aging and profitability by matter, attorney, practice group, office and entity — reported from the ledger, on the same platform as case status.
A firm's finance stack is only as good as its weakest handoff. This is the integration surface we build around Accounting Seed in legal engagements — and the one relationship on the list that needs no integration at all.
| Systems | Business purpose | What moves, and which way |
|---|---|---|
| Salesforce · Accounting Seed | Keep the client, the matter and the money on one record so finance and fee-earners argue about strategy rather than about whose number is right. | No integration Native — same platform, same database. Accounts, contacts and matters are shared objects, not synchronised copies. Nothing to reconcile and no middleware to maintain. |
| Litify · Mitratech CaseCloud | Turn the matter record and its timekeeping into billable revenue without re-entering anything, for firms running Salesforce-native case management. | Case → ledger Matters, time entries and disbursements flow into billing; invoice and balance status flows back to the matter. Consumed by billing staff and the responsible attorney. Mitratech CaseCloud was previously AdvoLogix. |
| LawPay | Take client payments compliantly — including into trust — and have them land against the right matter without a manual cash-application step. | Payments → ledger Payment events and settlement detail post to the invoice or trust sub-ledger. Consumed by finance, with the balance visible to whoever is on the client call. |
| DocuSign | Start the financial record at the moment the engagement is actually signed, rather than whenever someone gets round to opening the matter. | Signature → matter A completed engagement letter triggers matter creation and the retainer or billing schedule behind it. Consumed by intake and billing. |
| Bank feeds | Reconcile operating and trust accounts against the ledger continuously, so a discrepancy surfaces in days rather than at the next audit. | Bank → ledger Cleared transactions import for matching against cash receipts and disbursements. Consumed by the controller or bookkeeper. |
| QuickBooks · corporate ERP | Serve firms that keep a separate corporate or group ledger, or that are running Accounting Seed alongside an incumbent system during a phased move. | Bi-directional Journal summaries, vendor bills and settlement entries move both ways on an agreed cut. Consumed by group finance. Built per firm — the mapping is the work, not the connector. |
Building one of these into an existing Salesforce org? See our Salesforce Legal Accounting, or the wider Salesforce for law firms architecture this sits inside.
Most failed accounting implementations are configuration exercises that skipped the architecture. We do the financial design before anyone opens a setup screen — because a chart of accounts is very expensive to change once a year of transactions sits on top of it.
We map how the firm actually earns and collects: fee arrangements in use, trust obligations, entity and office structure, the close calendar, and which reports partners genuinely act on. Output is an architecture, not a task list. Typically 1–2 weeks.
Chart of accounts, ledger and sub-ledger structure, trust separation, revenue and fee-split rules, and the reporting dimensions the firm will need in three years — agreed with finance before a single object is configured. Typically 2–3 weeks.
Native configuration first — rate tables, billing formats, approval routing, dashboards. Custom Apex and Lightning Web Components only where the requirement genuinely exceeds the configuration surface, written against supported objects so upgrades stay clean. Typically 4–8 weeks.
Opening balances, historical AR and AP, and trust positions migrate and are reconciled line by line. The firm then runs a full billing cycle in both systems and the numbers must agree before anything is switched off. Typically 2–4 weeks.
We stay through the first billing runs and the first period close, fix what real transaction volume exposes, and hand over to a finance team that can administer the system themselves rather than one that has to call us.
Durations are typical ranges for a single-entity firm and are confirmed in discovery. Multi-entity, multi-office and multi-currency programmes run longer, and a rescue engagement starts with an assessment before any timeline is quoted.
Both are published Twopir Consulting engagements. Every figure below is scoped to the firm it was measured at — follow the link for the full story rather than reading these as an average.
Twopir's specialized Salesforce customization enabled efficient integration of third-party systems and streamlined administration and billing, leading to seamless financial operations and enhanced productivity. Automated mass billing and matter management minimized errors across our entire legal workflow.
Manual billing eliminated and matter management automated with Accounting Seed and Salesforce — 17 automation modules delivered.
Twopir provided Salesforce customisation and integration services to help us build a robust, compliant, and scalable legal operations platform — connecting case management, document processing, and financial systems into one unified workflow. The result was transformative for how we run case-to-cash operations.
Streamlining case-to-cash operations across Salesforce, AWS and QuickBooks.
Accounting Seed implementations fail in one of two directions: an accounting firm that cannot build on the Salesforce platform, or a Salesforce partner that has never closed a period. This work needs both, on the same team.
Chart of accounts, trust structure and reporting dimensions are agreed with your finance team first. It is the cheapest hour of the project and the most expensive one to skip.
We have built Salesforce infrastructure for personal injury, family law, corporate and multi-practice firms. Trust rules, contingency splits and cost advances are not concepts we look up mid-project.
When a requirement exceeds what native setup can do, the same team writes the Apex. No second vendor, no handoff, and no argument about whose scope a fee-split rule falls into.
Go-live is not the finish line for a finance system. We are there for the first billing runs and the first period close, when real volume finds what testing did not.
A large share of this work is rescue — firms already on Accounting Seed whose structure or integrations were never right. We assess before we rebuild, and we keep what can be corrected in place.
Configuration is anything achievable declaratively — rate tables, billing formats, trust sub-ledgers, approval routing, Flow automation, reports and dashboards. Custom development starts when a requirement needs Apex, a Lightning Web Component or an API integration: fee-split allocation logic, interest and late-fee automation, bespoke billing formats, or matter-level revenue rules. We always exhaust the configuration surface first, because declarative work stays upgrade-safe and your team can maintain it without us.
Twopir Consulting is a Salesforce Partner and a HubSpot Partner, and we implement, configure and build on Accounting Seed for law firms. Accounting Seed licences are bought from Accounting Seed directly — the vendor does not publish public pricing and quotes per firm. We deliver the implementation and the custom development around it; we are not reselling the product.
Sometimes you should not. QuickBooks is capable general accounting software, and a small firm with simple hourly billing may be well served by it plus a sync. The case for moving changes when matters, fee arrangements and trust obligations become the thing you need to report on: with Accounting Seed the ledger sits on the same platform as the client and matter records, so there is no sync to reconcile and no second definition of a client. Some firms keep QuickBooks or a corporate ERP as a group ledger and run Accounting Seed for legal operations — we build that arrangement too.
Yes, and the important detail is how. Accounting Seed supports multiple ledgers, which is what allows client funds to be held separately from operating funds, with sub-accounts tracked by matter. Compliance itself is not a feature you switch on — it comes from how the ledgers, sub-accounts, disbursement approvals and reconciliation reports are structured for your jurisdiction's rules. That structural design is the part we do, and it is where most trust accounting problems actually originate.
Yes. Because Accounting Seed is native to the Salesforce platform, it works alongside Salesforce-based case management such as Litify and Mitratech CaseCloud — the product previously known as AdvoLogix, which many firms still search for under the old name. Matters, time entries and disbursements feed billing, and invoice and balance status returns to the matter record. What we build is the mapping: which matter states create billable events, how time is approved, and how a closed matter settles financially.
For a single-entity firm, the phases on this page typically run around three to four months end to end, including a parallel run before anything is switched off. Multi-entity, multi-office and multi-currency programmes run longer, and the honest answer is that the timeline is set by two things we cannot see before discovery: the state of your historical data, and how many distinct fee arrangements are genuinely in use. We confirm the schedule after the architecture phase, not before it.
That is where a lot of these engagements start. A deployment can be technically live and still operationally wrong — usually because the ledger structure, trust separation or reporting dimensions were set up without a financial architecture behind them. We assess the ledger, the configuration, the integrations and the data before proposing anything, then correct in place wherever the structure can be repaired without a rebuild. Starting from a blank org is the last option, not the first.
Whether you are choosing Accounting Seed, midway through configuring it, or living with a deployment that never quite worked — the first conversation is about your chart of accounts and your fee arrangements, not about software.
Legal billing, trust accounting & matter finance on Salesforce
