# Workflows • Scellus

Every workflow stack Scellus runs end to end, in one view: matter readiness, client intake, billing recovery, claims, invoice processing, recurring charges, document control, and data cleanup. Each built from the same blocks, operated against a named outcome.

Source: https://scellus.com/workflows/

---

Workflows ▪ Overview

# Every workflow we run, as one stack.

Eight back-office processes Scellus operates end to end, built from the same blocks, run against a named outcome. Browse the stacks and pick the one your team keeps rebuilding by hand.

STACKS

08

MODE

RUN END-TO-END

OUTPUT

NAMED OUTCOME

How stacks work

## The same blocks fit together around different outcomes.

Six blocks, each doing one job. Every stack below is built from them, sequenced for its own process and run against one named outcome.

* [01folderCollectInto one queue](/blocks/#block-collect)
* [02scanReadFields from documents](/blocks/#block-read)
* [03shieldVerifyAgainst your rules](/blocks/#block-verify)
* [04mark\_chat\_unreadChaseFollow-ups, tracked](/blocks/#block-chase)
* [05account\_circleReviewA person decides](/blocks/#block-review)
* [06verifiedDeliverTo the next system](/blocks/#block-deliver)

01

### Blocks

Each has a defined input, a defined output, and one job it is responsible for.

02

### Workflow stack

Sequenced around your real process, so intake, billing, claims, or migration work moves without being rebuilt by hand.

03

### Operated outcome

Scellus builds, runs, monitors, and improves the workflow. Judgement stays with the people responsible for it.

The stacks

## Eight stacks, each one built to run end to end.

Matter readiness, client intake, billing recovery, claims, invoicing, recurring charges, document control, data cleanup — each assembled from the same six blocks and operated against a named outcome. Open one for its full sequence.

[01gavelMatter readiness.We collect matter records, check the file against the agreed checklist, verify key data, and follow up on missing items.You receiveA review-ready matter file, missing-item queue, readiness report, and audit trail.Your team keepsMatter-specific judgement, risk acceptance, and final approval.Typical cadenceDaily intake with deadline-based review.Best fitFirms opening or preparing repeated matters against a set checklist.How we engageWe build the workflow, then operate it as a managed service.REVIEW-READY↗Block sequence01folderCollect02scanRead03shieldVerify04mark\_chat\_unreadChase05account\_circleReview06verifiedDeliver](/workflows/matter-readiness/)
1. [02person\_addClient intake.We collect inquiries, capture key details, check required documents, follow up on gaps, and prepare the intake record.folderscanshieldmark\_chat\_unreadaccount\_circleverified6/6OMNICHANNEL↗You receiveA complete intake record, missing-document queue, reviewer pack, and audit trail.Your team keepsConflict decisions, client acceptance, risk calls, and final approval.Typical cadenceDaily, as new inquiries arrive.Best fitTeams handling repeated intake across email, forms, and messaging channels.How we engageWe build the workflow, then operate it as a managed service.](/workflows/client-intake/)
2. [03paymentsBilling recovery.We collect billing evidence, match time and costs, follow up on gaps, prepare the invoice record, and monitor the run.folderscanshieldmark\_chat\_unreadaccount\_circleverified6/6LHDN E-INVOICE↗You receiveA billing-ready record, exception queue, ageing view, e-Invoice file, and monthly report.Your team keepsPricing, write-offs, disputed items, and final invoice approval.Typical cadenceDaily capture with weekly and month-end runs.Best fitFirms that lose billable work between delivery and invoice approval.How we engageWe build the workflow, then operate it as a managed service.](/workflows/billing-recovery/)
3. [04receipt\_longClaims processing.We collect claims, match receipts, check agreed policy rules, follow up on missing documents, and prepare the payroll export.folderscanshieldmark\_chat\_unreadaccount\_circleverified6/6PAYROLL-READY↗You receivePayroll-ready records, an exception queue, policy flags, and an audit trail.Your team keepsPolicy decisions, disputed claims, and payment approval.Typical cadenceMonthly or twice monthly.Best fitTeams processing repeated staff, supplier, customer, or panel claims.How we engageWe build the workflow, then operate it as a managed service.](/workflows/claims-processing/)
4. [05request\_quoteInvoice processing.We collect supplier invoices, capture their fields, match them to orders and receipts, follow up on gaps, and prepare posting.folderscanshieldaccount\_circleverified5/63-WAY MATCH↗You receiveA posting-ready batch, mismatch queue, approval pack, and audit trail.Your team keepsDisputes, exceptions, payment release, and accounting policy.Typical cadenceDaily intake with scheduled payment runs.Best fitFinance teams processing repeated supplier invoices against purchase records.How we engageWe build the workflow, then operate it as a managed service.](/workflows/invoice-processing/)
5. [06event\_repeatRecurring charges.We prepare recurring charges, monitor failed payments, follow up within scope, reconcile receipts, and report exceptions.scanshieldmark\_chat\_unreadverified4/6DUNNING · GL↗You receiveA charge file, failed-payment queue, reconciliation summary, and operating report.Your team keepsCredits, disputes, exceptions, and customer-sensitive communication.Typical cadenceDaily monitoring with scheduled billing cycles.Best fitTeams running recurring billing across more than one payment or accounting system.How we engageWe build the workflow, then operate it as a managed service.](/workflows/recurring-charges/)
6. [07folder\_managedDocument control.We inventory files, apply agreed controls, monitor backups, run restore checks, and report gaps.foldershieldaccount\_circleverified4/6RESTORE-TESTED↗You receiveA controlled file register, access report, restore record, exception queue, and audit log.Your team keepsAccess policy, retention rules, legal holds, and approval of exceptions.Typical cadenceContinuous monitoring with scheduled reviews and restore tests.Best fitTeams whose work depends on shared records, controlled access, and tested recovery.How we engageWe build the workflow, then operate it as a managed service.](/workflows/document-control/)
7. [08databaseData cleanup & migration.We profile source data, clean and map records, prepare exceptions, run test loads, and validate the migration.folderscanshieldmark\_chat\_unreadaccount\_circleverified6/6TRACEABLE CUTOVER↗You receiveA validated target dataset, exception log, reconciliation summary, and migration audit trail.Your team keepsMapping policy, disputed matches, record disposal, and final cutover approval.Typical cadencePhased batches through test, parallel run, and cutover.Best fitTeams moving repeated, high-value records between business systems.How we engageWe build the workflow, then operate it as a managed service.](/workflows/data-cleanup-migration/)

Pricing

## How managed workflow pricing works.

Most managed workflows include a one-time setup fee and a monthly operating fee. Pricing depends on volume, workflow complexity, integrations, review requirements, and service levels. The fit check confirms whether the process is suitable before any paid work begins.

Workflow Review

We assess the workflow, confirm fit, and define the operating scope.

Setup and transition

A one-time fee covers workflow mapping, rules, integrations, testing, parallel runs, and rollout.

Managed operation

A monthly fee covers ongoing processing, monitoring, exception handling, maintenance, and reporting.

Additional scope

New integrations, major workflow changes, exceptional data cleanup, or work outside the agreed service level is scoped separately.

After the Workflow Review, your proposal will set out the fee bands and a firm timeline. The Review confirms the volume, systems, review model, service level, and scope exclusions needed to price and schedule the work accurately.

## Don’t see your process here?

Tell us about one transaction that keeps stalling. We’ll tell you whether Scellus can run the operation behind it.

[See if we’re a fit→](/review/?context=workflows)[See how we work](/how-it-works/)
