Automated Invoicing Workflow: What Each Plan Runs [2026]

Most software pricing pages tell you what you may do. This page tells you what
actually runs. Below is the invoicing workflow our platform executes, step by
step, followed by the exact run schedule, API budget, and storage each plan
includes — so you can match your invoice volume to a plan before you spend a
dollar.

Who this is for: the owner or operations lead at a service business —
an agency, clinic, contractor, studio, or consultancy — that sends recurring or
job-based invoices from data that already lives in a CRM, job tracker, or
time-tracking tool, and wants those invoices created, delivered, and reconciled
without a person doing the copying.

What it costs: plans are $32, $124, or $457 per month, and the honest way to
read that ladder is this: the tier you buy is a run schedule, not a feature
unlock. Every plan runs the same workflow logic. What changes is how many flows
you can keep active, how often they fire, and how many API calls each flow may
make per day. All plans start with a 14-day free trial and carry a 30-day
money-back guarantee, so the evaluation path is: read this page, build the flow
in the trial, and only then decide whether the schedule you need is worth the
price. That is the whole funnel — this free breakdown is step one, the trial is
step two, and a paid plan (for most invoicing volumes, Growth at $124/month) is
step three.

The 6-step invoicing workflow

This is the flow as it executes on the platform. Each step is a node you can see,
edit, and audit in the flow editor.

Step 1 — Trigger on billable events

A flow starts from a schedule (for example, nightly at 6 p.m., or the 1st of the
month for retainers) or from an inbound webhook — a job marked complete in your
field-service tool, a matter closed in your practice management system, a
project phase approved in your PM tool. The trigger defines the billing moment;
everything downstream is deterministic.

Step 2 — Pull the billable data

The flow calls your systems' APIs — job records, time entries, line items,
rates, tax settings, client billing profiles — and assembles one normalized
billing record per invoice. This is where API budget matters: each record pull,
lookup, and write in a flow counts against that flow's daily API-call allowance,
which is the main capacity number that differs between plans (50, 150, or 500
calls per flow per day — the full table is below).

Step 3 — Build the invoice in your invoicing tool

The platform does not replace your invoicing or accounting system, and it does
not process payments itself. It drives the tools you already use: it creates the
draft or final invoice in your accounting or invoicing product via that
product's API, with your numbering, your tax treatment, and your templates.
If a required field is missing — no rate on a time entry, no billing email on a
client — the record does not silently ship; it goes to the exception queue in
Step 6.

Step 4 — Deliver and log

The invoice is sent through your invoicing tool's own delivery mechanism, and
the flow writes a delivery log entry: which invoice, to whom, from which source
records, at what time. That log is what makes month-end questions ("did the
Hendersons get billed for the July visits?") a lookup instead of an
archaeology project.

Step 5 — Watch for payment and reconcile

On its next scheduled runs, the flow checks invoice status through the same
API, marks paid invoices against their source records, and flags anything past
your aging threshold. Nothing is sent to your customer by this step unless you
have configured your invoicing tool to do so — the platform's job is to keep
the states in sync and the aging list current.

Step 6 — Route exceptions to a human

Anything the flow could not do safely — missing data, an API rejection, an
amount over a review threshold you set — lands in an exception list with the
reason attached. A person clears the queue; the flow never invents data to get
an invoice out the door. In practice this queue is the difference between
"automation we trust" and "automation we audit every month."

Every run of every step above also writes a run log entry — when the flow
fired, which records it touched, which API calls it made, and what it produced.
Those logs live in your account for the life of your data storage allowance,
and they are the audit trail this article keeps referring to: when you evaluate
the platform in the trial, the run logs are the evidence you judge it on, and
when you operate it in production, they are how billing questions get answered
in minutes instead of meetings.

What each plan actually runs

These are the platform's published plan limits, verbatim from the
pricing page, as of August 1, 2026:

Support also steps with the tier: Solo includes email support with a 48-hour
response window; Growth adds one support hour per month with priority email at
24 hours; Scale includes four support hours, a 30-minute onboarding call, and a
priority execution queue. Annual billing saves roughly 17–18% on each tier.

Matching invoice volume to a plan

Because the tiers are schedules and API budgets, you can size them arithmetically
instead of guessing:

• Solo, $32/month fits a business whose invoicing is a once-a-day batch: one
  invoicing flow (plus up to two other flows), firing once daily, spending up to
  50 API calls on that run. If your nightly batch is a handful of invoices, each
  needing a few lookups and writes, this is enough — and if it is not, you will
  see exactly which limit you hit.

• Growth, $124/month is the working tier for most service businesses: five
  active flows means invoicing, payment reconciliation, and aging alerts can be
  separate flows with separate schedules, twice-daily runs keep morning and
  end-of-day billing moments covered, and 150 calls per flow per day covers a
  real batch with lookups per line item.

• Scale, $457/month is for operations where billing latency matters —
  invoices that should exist within the hour of a job closing — or agencies
  running invoicing for multiple entities: ten flows on hourly schedules with a
  500-call daily budget per flow.

• Performance (custom) exists for organizations beyond those ceilings; it
  adds local LLM support, a dedicated Slack channel, and a 99.9% SLA, and is
  scoped per organization.

If you cannot tell which side of a limit you fall on, that is precisely what the
14-day trial is for: build the flow, run it against a real billing day, and read
your own run logs. The limits above are enforced transparently, so the trial
answers the sizing question with your data, not our marketing.

What this workflow does not do

Three honest exclusions, so the contract is exact:

1. It does not process payments. Money moves through your invoicing or
   payment provider, under your merchant account and your terms. The platform
   orchestrates records via APIs; it is a run schedule you can audit before you
   pay for it, not a payment processor.

2. It does not replace your accounting system. Your books remain in your
   accounting tool; the flow writes into it through the vendor's supported API.

3. It does not send anything your tools are not already configured to send.
   Delivery happens through your invoicing product's own sending mechanism and
   settings.

How to start

1. Read the flow above against your billing process. If your billable data
   lives in systems with APIs, the workflow applies; if your billing starts from
   paper or memory, fix the data source first — no automation tier solves that.

2. Start the 14-day free trial from the pricing page on the tier
   your volume suggests — most invoicing workloads should start on Growth at
   $124/month — and build the invoicing flow from the templates library included
   with every plan.

3. Decide with your own run logs. Keep the plan if the schedule and API
   budget cleared your billing days; drop a tier, raise a tier, or cancel inside
   the 30-day money-back window if they did not.

Questions about whether your specific stack's APIs are reachable from a flow —
or whether your billing process needs a custom integration on the Performance
tier — go through our platform inquiry form, and
a person who works on the platform answers.