| Bill ID | Vendor | Amount | Invoice # | Date | Mailbox | Status | Confidence |
|---|
| Bill ID | Vendor | Amount | Invoice # | Date | Mailbox | Status | Confidence |
|---|
realm_entities, bills & AMEX → tables, invoice PDFs → Storage). Batched and safe to re-run — nothing in SharePoint is modified. The dashboard keeps reading SharePoint until verify shows parity; mailbox-sync mirrors new/changed bills continuously from this deploy on.supabase-migration.sql in the Supabase SQL editor first.
Department heads (used for secondary approval on bills ≥$50K and 48hr escalation).
Automatic secondary review is disabled. Approvers below (if any) would be auto-added; this is currently empty.
Add any Credify employee who can receive bill approvals. These appear in the approver typeahead when routing bills.
When "Set as default approver for this vendor" is checked during review, the mapping is saved here.
Choose who receives email notifications for each event. Emails are sent from ap@credifyservices.com via Microsoft Graph.
Fallback GL codes (used only when no QBO data is available):
Set a default GL expense code per vendor. When AI extracts a bill and matches a vendor, this GL code is pre-filled automatically.
Each entity's GL dropdown pulls primarily from its connected QBO company's Chart of Accounts. Codes added below are merged on top — useful for forcing specific accounts to be available, or for entities without their own QBO connection. If neither QBO data nor a manual list exists for an entity, the full merged Chart of Accounts is used as fallback.
Manage who can sign into this dashboard. Users must have a Microsoft 365 account in your tenant.
Instructions for using Claude (in Chrome or claude.ai) to enter approved bills into QuickBooks Online. This content is editable — customize prompts, field mappings, and workflows for your team. Changes are saved to SharePoint.
Each company has its own 🔗 Reconnect button below — use it to refresh an expired or broken connection without touching the others. The 🩺 Check button verifies tokens are still valid by pinging QBO. Add a brand new company with the button at the bottom.
Configure each connected QuickBooks company. Toggle AMEX Active to include the realm in the AMEX upload/push flow. Set the AMEX liability GL and assign card last-4s to route transactions automatically.
Pull the latest data from QuickBooks Online. This updates GL accounts, vendor lists, and class lists used across the dashboard.
Map dashboard Class names to QBO Classes. Pull from QBO first, then select the matching QBO class for each.
Map AMEX card members to approval email addresses. Currently all routed to joe@ for testing.
Lead purchase data (dw_restricted.leads, purchased = reached_accepted). When a NuvaLoan bill from a matched lead provider (True Path, Zero Parallel, Leap Theory, …) is routed for approval, the approval email and the no-login review page show leads purchased and accept-price spend for the invoice's service period, with a $ and % variance against the billed amount.
The Treasury dash archives each day's report (pasted or, later, live Redshift) as a snapshot. Syncing pulls every snapshot's per-provider lead rows into this dataset. This also runs automatically (max every 10 min) when a NuvaLoan lead-vendor approval email is sent, so approvers always see current data.
leads_json cell. Copy that cell's value (right-click → Copy in DBeaver).sql/underwriting-cost-month.sql (treasury repo) in DBeaver at month end,
then paste the single uw_json cell below. Clarity/Ekata bills whose invoice
total lands within ±5% of system cost for the service
period arm the same 24-hour auto-approval used for NuvaLoan lead bills.
Supports .xlsx, .xls, and .csv files exported from QuickBooks Online
Match your file's columns to bill fields. Auto-detected where possible.
0 bills will be imported with status "Entered in QBO".