Use case · accounting & bookkeeping

The monthly close where every figure ties back to the workpaper

The agent reads the files your firm already exports — trial balances, bank feeds, 1099 schedules — and writes a report where every figure points to the cell it came from. Each client's permission is checked the moment the answer is written, not just at retrieval.

The question this use case answers

How does a US bookkeeping firm close the books with reports where every figure can be audited back to its source document?

The files you already have

  • Trial balance and P&L exports (.xlsx / CSV)
  • Bank and credit-card feeds (CSV / OFX)
  • 1099 and payroll schedules
  • General-ledger detail exports
sample

What was the client's gross margin in May?

38%

pnl_may_clientA.xlsx · F2:F481 · you have access

Illustrative figure (sample) with fictional data — not a customer result or benchmark.

How the agent handles it, step by step

  1. 1

    Upload the period's files — no integration

    Drop in the exports your firm already produces per client. No connector, no IT — the agent detects the ledgers and feeds by format.

  2. 2

    The agent reconciles and cites every figure

    Every number in the trial balance and P&L carries where it came from: file, tab and range. The math is deterministic — the AI writes the prose around it, never the number.

  3. 3

    A missing document becomes a gap, not a guess

    If a bank feed hasn't landed, the agent flags the gap and asks for the file instead of estimating a balance.

  4. 4

    Schedule the recurring close

    Save the report recipe and the agent re-runs it next period with the same versioned audit trail.

Permission at synthesis time

In a multi-client firm, one team serves dozens of clients. Redijo checks the permission of each fragment at synthesis time: a bookkeeper on one client never sees — not even inside an aggregated total — a figure from another client's books. That is the moat, not a config setting.

An accounting or bookkeeping firm lives on one promise: the number is right, and you can prove it. Generic AI tools break exactly that promise — they return a fluent paragraph without saying where each figure came from.

Redijo starts with the proof. The agent reads the files your firm already produces every period — trial balances, bank feeds, 1099 schedules — and writes a report where every figure points to the cell it came from. Click a value and you see the file, the tab and the range.

Why “auditable by construction” matters for a multi-client firm

Auditable by construction means the proof is born with the answer, not generated afterward. Before writing any figure, the agent locates it in a file you uploaded and records its origin. Calculation and comparison are deterministic — the AI is never in the value path. It writes the prose around the numbers; the number itself comes from a path you can re-run and check.

Per-client permission, at synthesis time

The second win is what separates a safe firm from a leak waiting to happen. Almost every tool checks access when it fetches the document — then lets the AI blend everything into one answer. Redijo checks the permission of each fragment at the moment the answer is composed. The bookkeeper on Client A never sees a figure from Client B, not even hidden inside an aggregated total.

Who it’s for

For the CPA who signs off the close, the firm answering for many clients at once, and the controller taking the result to the board — everyone who needs every figure to have a path back to the workpaper. Your files are hosted in the cloud, with international-transfer safeguards.

Questions this page answers

Each client's files are hosted in the cloud, with international-transfer safeguards — a residency posture you can put in writing, never a marketing line.

Close the books with figures your client can audit

Get started and produce an auditable close from the files your firm already exports.

DPA for businesses · SOC 2 on the roadmap · cancel anytime

← Back to use cases by sector