Skip to main content
Finance in Corgtex centers on a single native operating record for project work, time, expenses, invoices, and cash payment status.

​
Contribution Entries

Finance contribution entries capture actual work and costs:
  • Time entries record the project, contributor, date, description, hours, and internal value.
  • Expense entries record the project, contributor, date, description, USD amount, and receipt metadata when available.
  • Every entry chooses one payment path: cash reimbursement or internal Slicing Pie contribution treatment.

​
Cash Payables

Cash entries stay in Finance as requested payables until an authorized reviewer confirms they were paid. By default, confirmation is restricted to a finance steward or workspace admin. A workspace can also enable all-member Finance writes, which lets active contributors confirm payables without becoming admins. In every configuration, the person who submitted the payable cannot confirm their own cash payment, and entries without submitter ownership must be repaired before confirmation. This keeps reimbursement workflow separate from ownership analysis while preserving a complete audit trail.

​
Optional Slicing Pie

When enabled for a workspace, Slicing Pie is an internal calculation view derived from recorded Finance entries. It does not replace the finance record and does not act as a legal cap table.
  • Unpaid work contributes slices at a fixed 2x multiplier.
  • Unreimbursed cash expenses contribute slices at a fixed 4x multiplier.
  • Cash-paid entries are excluded from slice totals.
  • Ownership percentages are derived at read time from each contributor’s slices divided by total slices.
The Slicing Pie page shows contributor totals and source-entry evidence so the calculation can be backed up from the underlying ledger.

​
AI Cost Budgets

Beyond standard fiat currency, workspaces can configure Model Usage Budgets. Because AI agents consume tokens during execution, Corgtex allows you to manage this exposure securely. You can provision a specific monthly budget (e.g., $250 API exposure) to a Circle’s agent pool. When the agent nears the 80% threshold, Corgtex alerts the relevant roles, preventing runaway infrastructural costs caused by unmonitored LLM loops.