TALLYLANE / AGENTS & APPROVALS

From a goal to a reviewable outcome.

Specialist agents prepare financial work with source evidence. Deterministic services check permissions, approvals and current records before an action can run.

Partly planned

A specialist for each next step

Collections
Read outstanding balances and payment evidence, then prepare a relevant follow-up. Paid or paused invoices must not produce a sendable reminder.
Documents
Identify missing evidence and prepare a scoped request. Document text is untrusted input; it cannot grant permissions or invent tax facts.
Reconciliation
Suggest a match from invoice and payment records. Reject currency mismatches, ambiguity and amounts already allocated.
Finance coordinator
Coordinate scoped specialist work. It cannot widen permissions or bypass another tool’s approval requirement.

Goal → evidence → proposal → review → outcome

A proposal needs business context, source record versions, recipient or affected records, currency, amount and a policy reason. The execution result must come from the action service, with an audit reference.

ILLUSTRATIVE COLLECTIONS CASE

£700 remains. Ask before sending.

Invoice total £1,200 − confirmed allocation £500 = outstanding £700.

A reminder proposal needs the exact recipient and current invoice version. A new payment, revoked role, policy change or emergency pause blocks stale execution.

Inspect the synthetic scenario ↗

Approval is a server object

A conversational “yes” or an MCP client confirmation does not replace an authorised, durable approval. Bind the approval to the proposal hash, source versions, policy version, approver, business and expiry. Revalidate at execution and record one effect for a repeated request.

P0 starts with read, suggest and human-approved actions. Unattended financial execution requires a separately approved policy and risk model.

Make interrupted work understandable

Tasks need visible waiting, blocked, cancelled and failed states. A disconnected stream does not establish whether an action succeeded. Recover using persisted task and operation records; never repeat an external write because a message was lost.