Weekly Finance Ritual
Run a repeatable review of cash, receivables, transactions, customer risk, forecasts, workflows, and accountable next actions.
The weekly finance ritual turns the workspace record into an operating cadence. Use the same order every week so missing data, collection risk, and automation failures are visible before the team makes a decision.
Prerequisites
- Sign in to an Eigenn workspace with current bank, transaction, customer, and invoice data.
- Use Starter or a higher plan for the Weekly Ritual and Workflows features.
- Confirm the review period and the people responsible for cash, receivables, bookkeeping, and workflow operations.
- Ask a workspace owner to join when the review may require creating, deploying, deactivating, or deleting a workflow.
Run the Review in Order
1. Confirm source health
Open Settings → Account → Bank Connections and resolve stale or disconnected accounts. A finance review built on an incomplete sync can make cash, burn, and runway look healthier or worse than they are.
2. Read the owner brief
Open Overview, choose the correct Reporting period, and read Owner brief and Do these first before opening individual records.
Record:
- the highest-priority action,
- the weakest business-health signal,
- current cash and runway, and
- any source that is missing enough data to block a decision.
Overview is a summary. Verify each material finding in the page that owns the underlying record.
3. Work receivables
Open Invoices and Receivables. Review overdue balances, payment promises, failed payments, risky terms, and follow-up ownership.
For every exception, identify the invoice or customer, the next action, the owner, and the date the team expects the state to change.
4. Review transactions and customer risk
Open Transactions for records that need categorization or explanation. Open Customers for customer-level context when a collection issue is recurring or the same account owns several overdue invoices.
Keep the decision attached to the relevant customer, invoice, or transaction instead of moving the only copy into a detached spreadsheet.
5. Test the decision
Open Finances → Forecast before hiring, adding material spend, changing payment terms, or assuming overdue cash will arrive on time. Compare the base view with a downside scenario and write down the assumption that changed the decision.
6. Review automation health
Open Workflows in the primary sidebar.
- Compare Active and Inactive workflow counts.
- Confirm that every active workflow is still intended to run.
- Open the Executions tab.
- Filter for Failed, Waiting, and Canceled runs.
- Open each material run and review Execution Graph, Execution Replay, trigger data, context, and the recorded error.
- If Action Required appears, review the checkpoint before taking a pause action.
The Workflow section has Workflows and Executions tabs. Workflow Pauses is not a third tab; open it from Execution Details → View All Pauses when a run has a pending checkpoint.
Use Monitor and Recover Workflows for the full recovery sequence. The current web pause action needs execution-state verification after it is submitted; a changed pause badge alone does not prove that the run continued.
7. Assign decisions
Every unresolved item needs:
- one owner,
- one source record,
- one expected outcome,
- one next-review date, and
- an explicit escalation condition.
Avoid assignments such as “finance will follow up.” Name the person and the record that will prove completion.
Close the Loop
The review is complete when:
- source connections are current or have a named repair owner,
- cash and runway use the intended reporting period,
- overdue invoices and customer risks have owners,
- unusual transactions have been resolved or assigned,
- material decisions have been tested in Forecast,
- failed, waiting, and canceled workflow runs have dispositions,
- pending human checkpoints have been reviewed, and
- the shared summary links back to the authoritative workspace records.
What the Review Does Not Prove
- An empty Do these first queue does not prove that every ledger or invoice record is correct.
- A workflow marked Active is eligible to run; it does not prove that a trigger fired or that the latest run succeeded.
- A Waiting execution can represent a scheduled delay or a human checkpoint. Inspect the execution before assigning it as a failure.
- The Workflows list loads up to 100 definitions, Executions shows up to 50 runs, and the Pauses list shows up to 50 checkpoints at a time. These pages are operational views, not unlimited audit exports.
- The pause dashboard’s resumed, expired, and total cards are derived from lists capped at 100 records. Treat those cards as page summaries when a workspace has a longer history.
Troubleshooting
Cash or runway looks wrong
Confirm bank-connection health, the reporting period, and sufficient burn history before changing a decision.
Receivables work is missing from Overview
Open Invoices and Receivables directly. The owner brief only includes supported priority categories and a limited number of actions.
Workflows is locked or opens an upgrade prompt
The navigation gate requires a workspace owner on Starter or higher. Ask the owner to confirm the current workspace plan and role.
A workflow looked healthy last week but failed this week
Open the new execution rather than relying on the workflow’s Active badge. Compare its trigger data, failed step, error, and definition with the last successful run.
A resumed pause still has a Waiting execution
Refresh the execution and verify its state and timeline. The current web checkpoint action can update the pause record without proving that a continuation job was queued. Preserve the execution ID and pause resume key when escalating.