Reference · FinOps Atlas · 2 September 2026

Finance questions answered with the documents that prove them

Atlas is read-oriented by design: it assembles the chain of evidence behind a number rather than restating the number. That makes it useful in an audit and safe to point an agent at. Transport and connection are on the docs home.

30Tools

21Resources

16Prompts

The financial evidence graph

Ten node types, and the edges are the point

A ledger tells you a payment happened. An evidence graph tells you which purchase order authorised it, which contract priced it, who approved it and which control it satisfied. Atlas holds these as connected nodes so “show me the support for this figure’” is a traversal rather than a week of email.

transactionsThe movement itself.
invoicesWhat was billed, by whom, against what.
purchase ordersThe commitment that preceded the bill.
paymentsSettlement, and its timing.
journal entriesHow it was booked.
contractsThe terms that make the amount correct or not.
approvalsWho authorised it, and under which threshold.
reconciliationsWhere two records were made to agree.
policiesThe rule that was supposed to apply.
controlsThe check that was supposed to catch it.

Diagram summary

The Barzel FinOps Atlas financial evidence graph: transactions, invoices, purchase orders, payments, journal entries, contracts, approvals, reconciliations, policies and controls connected as nodes

The graph as Atlas models it. A traversal from any node reaches the documents that justify it.

Coverage

Eleven workflows, five audit contexts, twelve systems

Workflows

Invoice-to-pay
Order-to-cash
Financial close
Audit request defence
Vendor onboarding
Bank reconciliation
Revenue recognition
Tax preparation
Expense reimbursement
Payroll review
Procurement approval

Audit contexts

SOX
SOC 2
ISO 27001
Internal and external audit
PBC preparation

Atlas assembles evidence for these frameworks. It does not certify you against them, and neither are we certified — see security.

Integration targets

QuickBooks · Xero · Sage
NetSuite · SAP · Oracle
Stripe
Salesforce · HubSpot
Google Drive · SharePoint · Microsoft 365

You supply read credentials per system. Nothing is pooled across tenants.

Tool surface

All 30 tool names

Note how many begin with detect_, trace_ or verify_. Atlas is built to find the gap and show the chain, not to move money.

Discovery · 5

list_capabilities
search_capabilities
describe_capability
get_supported_finance_systems
get_required_credentials

Evidence graph · 6

evidence_graph_action
trace_financial_evidence
detect_missing_evidence
map_evidence_to_control
verify_evidence_chain
generate_audit_packet

Close · 4

assess_close_readiness
generate_close_checklist
find_close_blockers
summarize_close_status

Cash · 3

analyze_cash_variance
forecast_cash_position
detect_cashflow_risk

Risk & controls · 4

score_transaction_risk
evaluate_control_risk
detect_policy_exception
recommend_control_action

Audit defence · 2

answer_auditor_request
audit_defense_action

Workflow & approvals · 4

create_finance_workflow
get_workflow_status
request_finance_approval
list_pending_finance_actions

Reporting · 2

generate_finops_report
export_finops_report

Worked example

“Show me the support for this number”

The request that turns a quiet week into a bad one. Four calls, in the order a reviewer would actually want them. Tool names are exact; argument names are illustrative.

trace_financial_evidence Start at the transaction and walk outwards: the invoice, the purchase order that authorised it, the contract that priced it, the approval that released it. This is the traversal the graph exists for.

detect_missing_evidence Then ask the more useful question: what should be attached and is not. Finding the hole yourself, a week early, is the entire value proposition.

map_evidence_to_control Tie what you found to the control it is meant to satisfy. An auditor is not asking for documents; they are asking whether a control operated.

generate_audit_packet · verify_evidence_chain Assemble the packet, then verify the chain behind it is intact before you send it. In that order — a packet you have not verified is a packet you are hoping about.

For a live audit request, answer_auditor_request wraps this sequence. Run the four calls yourself the first time anyway, so you can see what it is doing on your behalf.

Questions developers ask first

What is a financial evidence graph?

A ledger records that a payment happened. An evidence graph records which purchase order authorised it, which contract priced it, who approved it and which control it satisfied — as connected nodes across ten types. That turns “show me the support for this figure” into a traversal instead of a week of email.

Which finance systems does FinOps Atlas connect to?

Twelve targets: QuickBooks, Xero, Sage, NetSuite, SAP, Oracle, Stripe, Salesforce, HubSpot, Google Drive, SharePoint and Microsoft 365. You supply read credentials per system and nothing is pooled across tenants.

Does FinOps Atlas make us SOC 2 compliant?

No. It assembles evidence for SOX, SOC 2, ISO 27001, internal and external audit and PBC preparation. It does not certify you against any of them, and Real Biz Digital is not itself certified — our security page states exactly where we stand.

How many tools does FinOps Atlas expose?

30 tools, 21 resources and 16 prompts. Notice how many begin with detect_, trace_ or verify_ — Atlas is built to find the gap and show the chain, not to move money.

Can FinOps Atlas move money?

It is read-oriented by design: evidence assembly reads from your connected systems, and write paths are gated separately. That is what makes it safe to point an agent at during a close.