A subscription business has two revenue numbers — the one the go-to-market team reports and the one the ledger will support at audit — and they are almost never the same. Accounting Seed puts the general ledger, billing schedules and revenue recognition on the Salesforce platform, on the same records that hold the customer and the subscription. Twopir Consulting designs the revenue architecture, configures it around your contract terms, and builds the logic when configuration runs out. One number for revenue, from contract to close.
All four figures are from a single documented Accounting Seed engagement with a 150-employee US firm — not a blended average, and not a SaaS benchmark. Read the full case study.
Twopir Consulting has delivered Salesforce and finance systems for 500+ organizations across 12+ years — including subscription businesses running billing, revenue recognition and the general ledger on one platform.
Systems We Build On
A subscription business's financial problems are rarely accounting problems. They are modelling problems — the contract lives in one system, the invoice in a second and the revenue schedule in a third, and each one holds a slightly different version of the same deal. Every gap below is one of those seams.
Deferred revenue is calculated outside the ledger and posted back as a monthly journal entry. Nobody can trace a recognised dollar back to the contract line that created it without opening a workbook.
Upgrades, downgrades, ramps, co-terming and mid-cycle cancellations each need proration the billing template was never designed for. The workaround is a credit note and a manual invoice.
Metered consumption is exported from the product, aggregated by hand and typed into a bill. Overages are found late, credits are issued to smooth it over, and margin quietly leaks.
A subscription renewed in Salesforce is not yet billed in accounting, or the reverse. Two systems hold two versions of the same customer, and leadership ends up trusting neither number enough to act on it.
Failed payments, expiring cards and overdue invoices are worked from an exported list. Involuntary churn looks like a customer problem when it is really a dunning problem.
Every new pricing model adds another reconciliation step. The close takes longer each quarter, and the finance team's growth curve tracks the customer count instead of the revenue.
Accounting Seed is an accounting platform built natively on the Salesforce platform. It provides general ledger, accounts receivable, accounts payable, billing and invoicing, recurring and scheduled billing, project accounting, financial reporting and online payment processing — and because it is native rather than integrated, the company's financial records sit on the same platform as its account, opportunity and subscription 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 subscription business the practical consequence is specific: the contract, the invoice and the revenue schedule are the same record hierarchy, so a recognised dollar can be traced back to the contract line that created it without an export. That is what makes an ARR narrative and a GL revenue figure reconcilable rather than merely close. Accounting Seed does not publish public pricing; licensing is quoted per company by the vendor. Accounting Seed's own product 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 revenue architecture, then implement, configure and extend the product to match it.
The operating change. This is what a CFO actually notices 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, entity and currency setup, users and permissions, opening balances, and migration of historical AR, AP and open deferred revenue balances."Accounting Seed implementation partner" | Ends when the company 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 your contracts: billing schedules, recurring templates, revenue recognition schedules, payment terms, dunning steps, approval routing, reports and dashboards."Accounting Seed subscription billing configuration" | 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 configuration surface runs out: usage aggregation and rating, ramp and co-term proration logic, amendment handling, bespoke invoice formats, ARR-to-GL bridge reporting, product and gateway 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 schedule structure, repairing broken billing automation, and rebuilding reporting finance 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 companies need two of the four. The purpose of discovery is to tell you which two before you commit budget to the wrong one. If your quoting already runs on CPQ, the handoff is covered in Salesforce CPQ to Accounting Seed quote-to-cash.
These are the modules we actually deliver on Accounting Seed for subscription businesses — described in revenue vocabulary rather than as a restatement of the vendor's feature list. Which of them you need is a discovery question, not a package.
Monthly, annual, multi-year and ramped terms configured as real billing schedules, with renewal and co-termination dates driven from the subscription record rather than a calendar reminder.
Revenue recognised on a schedule generated from the contract line, so the deferred balance on the balance sheet is supported by the contract that created it rather than reconstructed each month.
Mid-term upgrades, downgrades, seat changes and co-terms priced and billed by rule, with the revenue schedule adjusted at the same time instead of in a later journal entry.
Consumption aggregated from the product or a metering service, rated against the contract's tiers and committed volumes, and billed on the same cycle it was consumed.
Card and ACH collection inside Salesforce, with retry sequences, expiring-card outreach and overdue escalation running as automation rather than as somebody's weekly export.
Selling entities, functional currencies and intercompany positions modelled in the ledger, with consolidated reporting instead of a group-level workbook.
Hosting, third-party licence and partner-commission costs recorded against the same dimensions as revenue, so gross margin by product line is a report rather than an allocation exercise.
The bridge finance actually gets asked for: bookings, billings, recognised revenue and deferred balance reported side by side from one data model, with the differences explained rather than argued about.
A subscription finance stack is only as good as its weakest handoff. This is the integration surface we build around Accounting Seed for SaaS companies — 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 customer, the subscription and the money on one record so go-to-market and finance argue about strategy rather than about whose number is right. | No integration Native — same platform, same database. Accounts, contacts, opportunities and subscriptions are shared objects, not synchronised copies. Nothing to reconcile and no middleware to maintain. |
| Salesforce CPQ · Revenue Cloud | Turn a signed quote into a billing schedule and a revenue schedule without anyone re-keying the commercial terms or the ramp. | Quote → ledger Quote lines, terms, ramps and discounts create the billing and revenue schedules; billed and recognised amounts report back against the opportunity. Consumed by finance and the account team. |
| Usage & metering services | Bill what the customer actually consumed, on the cycle they consumed it, without a manual aggregation step. | Product → ledger Rated usage records post as billable lines against the subscription. Consumed by billing and by the customer on the invoice. Built per company — the rating rules are the work, not the connector. |
| Chargent · Stripe · gateways | Collect card and ACH payments inside Salesforce and have them land against the right invoice without a manual cash-application step. | Payments → ledger Authorisations, settlements and failures post to the invoice and cash receipt; retry state drives dunning. Consumed by finance and customer success. |
| Bank feeds | Reconcile operating accounts against the ledger continuously, so a discrepancy surfaces in days rather than at year end. | Bank → ledger Cleared transactions import for matching against cash receipts and disbursements. Consumed by the controller. |
| QuickBooks · corporate ERP | Serve companies that keep a separate group ledger, or that are running Accounting Seed alongside an incumbent system during a phased move. | Bi-directional Journal summaries, vendor bills and consolidation entries move both ways on an agreed cut. Consumed by group finance. Built per company — the mapping is the work, not the connector. |
Building one of these into an existing Salesforce org? See our Salesforce integration practice, or the Salesforce and Chargebee integration guide if a subscription platform already owns your billing.
Most failed accounting implementations are configuration exercises that skipped the architecture. We do the revenue modelling before anyone opens a setup screen — because a chart of accounts and a schedule structure are very expensive to change once a year of transactions sits on top of them.
We map how the company actually earns and collects: contract shapes in use, ramps and amendments, usage components, entity and currency structure, the close calendar, and which reports the board genuinely acts on. Output is an architecture, not a task list. Typically 1–2 weeks.
Chart of accounts, billing and revenue schedule structure, performance-obligation treatment, currency and entity setup, and the reporting dimensions the company will need in three years — agreed with finance before a single object is configured. Typically 2–3 weeks.
Native configuration first — billing templates, schedules, dunning steps, 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 open deferred revenue positions migrate and are reconciled line by line. The company 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 company and are confirmed in discovery. Multi-entity and multi-currency programmes run longer — see multi-entity and multi-currency consolidation — and a rescue engagement starts with an assessment before any timeline is quoted.
Both are published Twopir Consulting engagements delivered on Accounting Seed and Salesforce. Both are services businesses rather than SaaS companies — that is what the documented Accounting Seed evidence currently covers, and the mechanics shown are the recurring-billing, automation and reconciliation mechanics a subscription business needs. Every figure is scoped to the company 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 recurring invoicing 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 work-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. Subscription revenue needs both, on the same team.
Performance obligations, schedule 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.
Twopir Consulting builds revenue infrastructure across CRM, CPQ, marketing and support. We know what the ARR number is being used for, which is what makes it possible to make it reconcile.
When a requirement exceeds what native setup can do — usage rating, ramp proration, an amendment rule — the same team writes the Apex. No second vendor and no handoff.
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 transaction volume finds what testing did not.
A large share of this work is rescue — companies already on Accounting Seed whose schedule structure or integrations were never right. We assess before we rebuild.
Configuration is anything achievable declaratively — billing templates, revenue schedules, payment terms, dunning steps, approval routing, Flow automation, reports and dashboards. Custom development starts when a requirement needs Apex, a Lightning Web Component or an API integration: usage aggregation and rating, ramp and co-term proration logic, amendment handling, bespoke invoice formats, or an ARR-to-GL bridge. 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 subscription businesses. Accounting Seed licences are bought from Accounting Seed directly — the vendor does not publish public pricing and quotes per company. We deliver the implementation and the custom development around it; we are not reselling the product.
Accounting Seed schedules revenue and expense recognition against the records that generate them, which is the mechanism ASC 606 treatment is built on. Compliance itself is not a switch you turn on: whether your recognition is correct depends on how performance obligations are identified, how the transaction price is allocated across them, and how amendments are treated — decisions your finance team and auditor own. Our job is to model those decisions in the ledger so the resulting schedules are auditable and the deferred balance can be traced to the contract line behind it.
Sometimes not. If a billing platform already handles your pricing, invoicing and dunning well, the useful question is where the general ledger lives and how revenue gets from one to the other. Some companies keep the billing platform and use Accounting Seed as the Salesforce-native ledger it posts into; others consolidate billing into Accounting Seed to remove the seam entirely. Which is right depends on how exotic your pricing is and how much reconciliation the current seam costs you each month. We build both arrangements and will say plainly when the seam is not worth removing.
Yes, with design work. Accounting Seed bills from billable records, so metered usage becomes billable lines once it has been aggregated and rated against the contract's tiers, commitments and overage terms. The aggregation and rating logic is the part that is built rather than configured — it is specific to how your product meters and what your contracts promise. Hybrid models that combine a platform fee, seats and consumption on one invoice are common and are handled as separate billing components against the same subscription.
For a single-entity company, 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 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 genuinely distinct contract shapes are 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, schedule design or reporting dimensions were set up without a revenue 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 contract shapes and your revenue schedules, not about software.
Subscription billing, revenue recognition & the ledger on Salesforce
