Up to 50 managed devices
Proposed platform scope · unlimited techniciansAccount and customer billing
Keep platform costs and client invoices on separate records.
Understand your MSP’s Dayrook subscription, then explore billing work for your own customers. Each ledger needs its own invoice identity, permissions and reconciliation.
A record people can use
Keep the source, owner and next decision together.
Illustrative workflow · explore the steps · no action is executed
01
Choose the billing scope
Start in either Dayrook account billing or a specific MSP customer billing record before viewing or changing commercial state.
Confirm this step for your release, permissions and environment.02
Reconcile the owning records
Compare product usage and signed provider events for the Dayrook account, or service and usage evidence for the selected customer.
Confirm this step for your release, permissions and environment.03
Recover or hand off
Use the approved platform payment-recovery path, or send customer billing data through the configured accounting and payment workflow with evidence attached.
Confirm this step for your release, permissions and environment.Reporting and commercial operations
Two billing jobs with separate scope and ownershipSimple pricing previewTarget platform scope
Progressive volume pricing
Rates fall as the fleet grows25 GB pooled storage included
Lower rate from user 501PlatformManaged devicesSaaS usersBackup storage
Keep the Dayrook account bill separate from MSP customer billing.
Let account owners understand the Dayrook subscription without exposing unrelated customer billing.
Prepare customer-scoped billing from owned service and usage evidence, then hand it to the configured accounting and payment path.
Inside the workflow
The work this connects.
- Dayrook account billing
- Review the platform subscription, included allowances, usage, invoice, payment method, contract exception, and entitlement state.
- MSP customer billing
- Prepare customer-scoped agreements, service items, approved usage, invoice handoff, adjustments, and payment-status workflows.
- Owned usage evidence
- Keep every billable quantity linked to its module-owned source instead of copying an unexplained total into either ledger.
- Invoices and provider handoff
- Use the approved payment portal for the Dayrook account and configured accounting or payment connections for MSP customer billing where enabled.
- Platform payment recovery
- Apply staged notices, reversible read-only states, reconciliation, and entitlement restoration to the Dayrook account without changing customer invoices.
Try one useful scenario
Two ledgers with an explicit handoff
Fictional example: a client invoice for 100 units is unpaid while the MSP’s platform subscription is paid. A reviewer reconciles the provider transaction ID before deciding any permitted restriction. Ledger A (MSP subscription): invoice S-10, USD 469, provider receipt P-10, paid. Ledger B (client receivable): invoice C-20, USD 100, USD 0 settled, disputed. Review each separately: a client debt does not prove the MSP subscription is unpaid. Preserve invoice, settlement, dispute, reviewer and adjustment IDs; do not restrict access on an unmatched event.
Illustrative evaluation scenario, not a recorded product result.What a useful result must show
Keep contract, invoice, provider event and reconciliation owner linked. Duplicate or disputed events require a human exception; do not infer one ledger’s state from the other.
Get the evaluation worksheet →Check the support boundaries
- Dayrook subscription ledger
- MSP-to-client invoice ledger
- Accounting/payment-provider handoff
- Taxes, refunds, disputes and export rights
This is a planning example, not a sandbox/live payment claim. Confirm invoice direction and accepted terms. No universal grace period, tax advice or authority to restrict protected exports is implied.
Check public evidence and availability →Scope, availability and evaluation details
Dayrook does not store cardholder data from provider-hosted payment flows.
Live prices, meters, tax, customer invoice behavior, accounting connectors, and payment behavior require the approved production catalog and provider configuration.
The proposed $99 monthly model includes the target product scope for evaluation, unlimited technicians, unlimited customers, and the first 50 managed devices. Final terms require confirmation. See transparent pricing →
Review full environment and integration scope
Stripe-backed Dayrook account state
Platform subscriptions, invoices, hosted payment recovery, usage, tax inputs, and payment events reconcile through Stripe into the Dayrook account ledger.
Separate customer-provider paths
MSP customer billing uses the configured accounting and payment connections available for the release; those records remain customer-scoped and separate from the Dayrook subscription.
Stripe events reconcile against the Dayrook account ledger; MSP customer accounting and payment connections remain separate and provider-specific.
Questions, answered
Before you choose your next step.
Does this cover my Dayrook bill or the invoices I send customers?
Both jobs are represented, but they remain separate. Dayrook account billing covers your platform subscription; MSP customer billing covers customer-scoped service and usage billing workflows.
Can Dayrook create customer invoices?
The target workflow can prepare and hand off customer-scoped billing records. Confirm the current invoice, accounting connector, tax, and payment-provider scope during evaluation.
Can an account owner update the Dayrook payment method?
The Stripe Customer Portal is the target self-service path for supported Dayrook payment, invoice, tax, and recovery actions.
Does a failed Dayrook payment immediately stop service?
No. The proposed policy uses staged notices and a grace path before reversible read-only suspension.