Sigma for dashboards
Dashboards that get to the answer
Reconciliation
Reconcile every number in one place
Finance matches the ledger and the subledger live on the warehouse, explains every exception, and signs off with a full trail.
Schedule demoWhat today's close costs, and what changes
What the current cycle costs
Every figure comes from a customer describing how they reconcile today, without Sigma.
A close pulls numbers from 12 reportsone model, spends a day a quarterno time at all on copy and paste, and leaves 1% of marginnothing behind on the table.
How it works
Reconcile in 3 steps
- 1Match both systems
Sigma joins both sources live on the warehouse. Every break surfaces the moment your feeds land.
- 2Explain the exception
Analysts type the reason into an Input Table, so the explanation stays with the row it explains.
- 3Sign off and close
Actions route each exception to an approver. Audit history records who changed what, and when.
Match both systems. Explain the exception. Sign off and close
Live tie-out
Balances land, breaks surface themselves
gl_balancesLive query
1100 · Cash operating4,182,905.14Matched
1210 · Accounts receivable9,847,230.08Exception
1215 · AR allowance412,660.00Matched
1300 · Finished goods inventory6,204,118.72Matched
1310 · Inventory in transit878,450.00Exception
The ledger and the subledger are read in place, so a break shows up the moment the difference clears tolerance.
Reconciliation you can audit
01Explore
Match live on the warehouse
Sigma queries both systems where the data already lives, so the match runs on the rows your feeds just landed. Controller and auditor read the same governed number.
- Join both systems live, with no extract to refresh
- Inherit warehouse roles and row-level security on every query
- Drill from a variance straight to the source rows
02Act
Fix the break in place
An analyst types the explanation, the adjustment, and the owner directly into the row. The number a controller signs is the number the board reads.
- Enter the adjustment, route it for review, and trace who changed it
- Keep the explanation with the row it explains
- Sign off once, under warehouse roles and row-level security
03Govern
Catch anomalies before the close
Sigma Agents watch the reconciliation as data lands, flag balances outside tolerance, and summarize what changed. Every call runs through the LLM provider you configure or a warehouse-native model.
- Flag balances that move outside your tolerance thresholds
- Summarize what changed, with guided next steps for review
- Point AI at your own provider or a warehouse-native model
Connections
Always on the newest trusted data
Sigma queries your warehouse live, so a workbook reads what landed a moment ago.
What your auditor gets
Every edit carries a user identity and a timestamp, and existing warehouse controls still decide who can make it.
Change historyAppend only
DWAccountant edited Explanation on 1100 · Cash operating14:22
MEReviewer approved Status on 1210 · Accounts receivable14:09
ROController reassigned Owner on 1215 · AR allowance13:51
JTController locked Period on 1100 · Cash operating11:04
Non-destructive edits
Sigma appends each correction as a row-level insert, so production tables stay as your pipeline left them.
One set of rules
Warehouse roles and row-level security govern the workbook. There is no second permission layer to maintain.
Full change history
Audit history on an Input Table records the complete trail, so a disputed figure has one traceable owner.
Reconciliation apps to start from
Every app here runs on live warehouse data, writes back, and keeps the trail an auditor asks for.
Budget variance
Move from variance analysis to an approved reforecast in one workflow, with commentary and overrides that write straight back to your numbers.
Budget and Variance Approvals
Analyze budget vs. actuals on live data. Track variances, update forecasts, and route approvals in a governed AI app.
Month End Reporting
Centralize financial data and automate reconciliations. Real-time insights for complex month-end close processes.
Commission Reconciliation
Cut commission disputes by 75 percent. An AI app gives reps the structure behind their payouts, lets them submit tickets, and lets ops resolve cases in one place.
Provider anomaly detection
Surface the providers with the most outlier behavior, then work every case with notes, files, and escalation in one place, backed by a full audit trail.
Claims Anomaly Detection Agent
Four differentiators in one app. A claims analyst pulls live data, drills with a spreadsheet UI, writes back changes, and chats with an agent that summarizes the case.
Every kind of app
Sigma for every kind of app
All 7 build on the same live, governed platform.
Questions finance teams ask
Retire the midnight call
See a live reconciliation on your own warehouse data, and swap period-end scrambling for a close that runs continuously.
Schedule demoActivate your data warehouse
Stop buying a new tool for every workflow. Build it once on governed data, then scale it across the business.