Every entity billed from one CRM. Each paid into its own books.

Billing for a business with more than one legal entity or location, where each one needs its own invoices, its own bank account and its own books. Paycove runs it from the deals in one CRM.

A payment provider that collects for more than one legal entity or location and pays each into its own bank account, with its own books. Paycove does it from the deals in your CRM: each entity or location pays out to its own Stripe account and posts to its own QuickBooks or Xero file.

Look for three things: each entity invoices under its own name, each is paid into its own bank account, and each posts to its own books. Accounting suites keep separate books per entity, and an app can create an invoice in them from a CRM deal, but they don't build the payment plan from the deal or choose from the deal which entity's Stripe account is paid. Paycove bills from the deal in HubSpot or Pipedrive and pays each entity into its own Stripe account and QuickBooks Online or Xero file. What multi-entity accounting software covers, and what it doesn't

Create invoices and payment plans for the right entity from the deal, collect on schedule by card or bank transfer, pay each entity into its own account, and record each payment in that entity's books. In Paycove, rules on each template send a deal to the right entity by pipeline, location or another field, so a rep doesn't have to pick.

Yes. Run every location as a template in one Paycove account, or give each entity its own account under a parent.

Yes. Each location or entity pays out to its own Stripe account, so the money lands in its own bank.

Yes. Each template or entity account connects its own QuickBooks Online or Xero file.

Yes, with a separate Paycove account per entity under a parent. Each has its own users, roles and permissions.

Yes. Document templates belong to the account, so a parent with an account per entity gives each entity its own agreement templates, its own logo on the signing page, and is countersigned by its own team. In one account, keep a template per location and pick it when the document is created. Either way the agreement is built from the deal with the payment schedule filled in, each signer confirms their email before signing, and the signed PDF with its signature certificate stays on the record.

One account running every location as a template is priced the same however many locations it has. A separate Paycove account per entity is $50 a month for each one after the first. See pricing.

Not for separate entities. A HubSpot account connects one Stripe account, and every brand shares it, so all the money lands in one bank account. The usual workaround is a HubSpot portal for each entity, joined with multi-account management, which needs an Enterprise main account and a Professional or Enterprise subscription for every other portal. Paycove works from one portal and routes each deal to the right entity's Stripe account and books. If you already run a portal per entity, each one can connect its own Paycove account under a parent. Can you connect multiple Stripe accounts to HubSpot?

No. Paycove collects what customers owe each entity and pays it into that entity's own Stripe account and books. Paying vendors and approving bills across entities is the job of an accounts payable tool.

Yes. Rules on each template match deals to it by pipeline, location, contact or company fields, or any custom field, so a deal lands on the right entity's template, Stripe account and books without the rep choosing.