Almanac / Integrations
Accounting → Client economics

The books tell one story.
Your client work tells the rest.

Connect the economics of each account to the work it takes to keep it. A proposed QuickBooks Online view for revenue, unpaid invoices, and delivery cost.

Planned integration · Sample data. No live accounts connected.

AlmanacIllustrative workflow
You ask

Which accounts need a closer look at delivery cost?

Compare the same month, the same revenue basis, and the effort allocated to each client. Then investigate the exceptions.

$15,500Illustrative service revenue
Harbor Dental$6,000$2,400 delivery cost
Juniper Animal$4,500$3,100 delivery cost
Kestrel Roofing$5,000$2,000 delivery cost
Review requiredJuniperConfirm scope and hours
Explore the sample agency
A little less busywork. A lot more possibility.
01

A consistent revenue basis.

Keep invoiced, recognized, and collected amounts distinct so your answer matches the decision.

02

Delivery cost in view.

Account for the hours, contractors, and direct costs behind the retainer.

03

Exceptions worth a conversation.

Surface missing mappings and unusual changes before a confident-looking total becomes a bad decision.

The workflow

Useful from the first question
to the next decision.

  1. Map the source

    Choose the company, period, currency, and client identifiers with the finance owner.

  2. Reconcile the result

    Compare the proposed imported totals with the accounting platform. Keep unresolved records visible.

  3. Act with context

    Review scope, effort, and renewals with the account lead. Leave the ledger as the source of truth.

Planned integration · This prototype uses sample data. No QuickBooks Online account is connected.

Customer and invoice mapping

Match each agency client to the correct customer record before comparing invoices, outstanding balances, and delivery cost. An invoice sent is not the same as cash collected. Keep those views separate.

A useful first workflow

  1. Choose a reporting period and a named owner for the connection.
  2. Review the proposed client or team mappings before importing data.
  3. Keep source totals, imported totals, and unresolved records visible.
  4. Compare the result with the source system before using it in a client decision.

What the connection should not do

Do not assume accounting access includes payroll access. The planned first version is a read-only accounting view; compensation requires a separate authorized source.

The accounting or payroll platform remains the source of truth. A missing field, expired permission, or incomplete period should be shown as missing—not silently converted to zero. Any future write action would need a separately reviewed permission and an explicit approval step.

From data to a better decision

Use this information to ask whether the team can serve another client sustainably, which services consume too much effort, and whether automation frees time for strategy. Do not call recovered staff hours cash savings unless a real expense falls.

Read the agency margin guide → · Try the savings model →

Implementation reference

QuickBooks Online platform documentation ↗. Product scope, provider approval, geography, and permissions must be verified during implementation.

Before you connect

A few clear answers.

Can I connect a live account today?

Not in this prototype. The demo uses fictional clients and numbers. Live access requires a production integration, provider permissions, and an authorized account owner.

Does Almanac replace my accounting platform?

No. Your accounting platform remains the source of truth. The proposed agency view adds delivery context without posting to the ledger.

How should I evaluate it?

Start with a single workflow, a small client set, and a documented baseline. Compare effort, accuracy, and review burden. Use observed results rather than the sample numbers shown here.

See the work in context.

Explore a sample agency in Almanac. No account, payment, or real client data required.

Open the demo ↗Model your capacity