The reason for review.
Follow the exception to its source records, dates, and context. Keep uncertainty visible alongside the amount.
Bring payments, commitments, and financial decisions into context. Know which exceptions need a closer look and keep the next action within your controls.
A repeated payment, an overdue balance, a discount window. Bring the amount and its supporting records into view before deciding what to do.
Review the evidence before deciding on the next step.
Do these payments settle separate obligations?
Check the invoice references and any reversal before deciding whether a correction is needed.
Connect accounting and payment records to the customer conversations, supplier terms, and commitments that help explain them.
Your accounting system remains the system of record. Choose which supported records to include, with access governed by your connections and permissions.
Explore financial connectionsRecorded balance · September 13
Payment is waiting on delivery sign-off.
Acceptance review remains open.
Can the account and delivery teams confirm acceptance?
An outstanding balance is a starting point. Bring in the customer conversation, disputed terms, and work still open before deciding how to follow up.
Ask about the account context. Follow the concern through your Watchlist as new evidence arrives, keeping missing or delayed settlement records in view.
Explore Ask OrcintaSet the boundary for financial actions routed through the governed path. Hold requests that need review and give the authorized person the rule and evidence behind them.
The same governance path applies to people and connected agents. Approval still has to respect other permissions, policies, and operating limits.
Explore policies and approvalsWhen a decision needs explaining, start with its history. Keep the supporting evidence, applicable policy, and recorded outcome within reach.
Follow the exception to its source records, dates, and context. Keep uncertainty visible alongside the amount.
Trace governed decisions to the policy that applied, even after the rule changes.
Review the action history and prepare scoped evidence for internal review or a conformance packet.
Connect QuickBooks Online, Xero, and Stripe. Configure the connection and select the supported record types you want to include. Accounting records can be considered alongside evidence from supported CRM, document, project, and communication systems. Available context depends on the connections and permissions you configure.
No. Your accounting system remains the system of record. The QuickBooks, Xero, and Stripe connectors ingest evidence; connecting them does not authorize journal entries, account reconciliation, or fund transfers. Financial intelligence and governed actions are separate capabilities.
Supported checks include possible duplicate payments, stalled receivables, early-payment discount windows, and signs of unused recurring spend. Their availability depends on the checks enabled for your workspace and the evidence available. Figures, subjects, dates, and terms need enough support to produce a useful finding. A possible exception still needs review.
Not by itself. Similar payments can have legitimate explanations. Review the recorded amounts, recipient, dates, and supporting context with an authorized person. The amount associated with a finding is an amount to investigate, not a claim of confirmed loss or recovered savings.
An overdue receivable can surface when the connected record does not show a later settlement. You can inspect the invoice evidence, ask about the account context, and follow the issue through your Watchlist. Missing or delayed payment evidence needs to be checked before treating the balance as unpaid.
Supported actions routed through the governed path are checked against permissions and applicable policies. A refund above a configured threshold can be held for an authorized reviewer, with the request and context attached. Approval does not bypass other required checks or agent limits. Activity that ran outside the governed path and was imported afterward is recorded as observed evidence; a hold cannot be applied to it after the fact.
Receipts connect governed events to their policy reference, actor, and supporting record. Assemble scoped receipts, reconstruction, coverage, and control mappings into a conformance packet with a verification link. Verification establishes record integrity and related proof properties, not accounting accuracy, decision correctness, or regulatory certification.
Connect the numbers, the business context,
and the controls around them.