🚨 This documentation is out of date.
View our New Documentation!
Open Collective Docs
Go back to Open Collective
  • Welcome
  • About
    • Introduction
    • Documentation
    • Terminology
    • Company
    • Pricing
    • Team
    • The Open Collective Way
      • Mission and Values
      • Community Guidelines
    • Hiring
    • Investors
    • Contributing
    • Refund Policy
    • Contact Us
  • Product
    • Features
    • Roadmap
    • Comparison
    • User Profile
    • Dashboard
      • Preview Features
    • Currencies
    • Log-in System
    • Privacy Policy
    • Moderation
    • Security
    • Ledger
      • Individual Transactions
      • Transaction Pairs, Groups & Perspectives
      • Viewing Transactions
      • Exporting Transactions
      • Fiscal Host Ledger Perspective
      • Contributions in the Ledger
      • Added Funds in the Ledger
      • Expenses in the Ledger
      • Ledger Changelog
    • Notifications
    • Two-factor Authentication
    • Activity Log
  • Collectives
    • Collectives FAQ
    • Creating a Collective
    • Quick Start Guide
    • Collective Settings
      • Customize Collective
      • Team
      • Collective Goals & Tiers
      • Expense Policy
      • Data Export
      • Security
      • Integrations
      • Zero Collective Balance
      • Closing a Collective
    • Add Fiscal Host
    • Change Fiscal Host
    • Open Source Collectives
      • Setting up GitHub Sponsors
    • Transparent Budget
    • Expenses
    • Updates & Comms
    • Custom Email
    • Moderation
    • Conversations
    • Events
    • Projects
    • Funding Options
    • Buttons & Banners
    • Connected Collectives
    • Contribution flow
  • Financial Contributors
    • Financial Contributors FAQ
    • Guest contributions
    • Payments
    • Platform Tips
    • Website Badge
    • Receipts
    • Collective to Collective
    • Organizations
      • Organization FAQ
      • Funds
      • Bulk Transfers
      • Gift Cards
      • Sustainer Resources
  • Expenses & Getting Paid
    • Expenses FAQ
    • Submitting Expenses
      • Inviting a third-party to submit an Expense
    • Expense Comments
    • Edit or Download an Expense
    • Receiving payment through Payoneer or Wise
    • Tax Information
  • Fiscal Hosts
    • Fiscal Hosts FAQ
    • Becoming a Fiscal Host
    • Creating a Fiscal Host
    • Organisation Settings
      • Info
      • Customize Profile Page
      • Connect external accounts
      • Accounting Categories
      • Security
      • Manage updates
      • Policies
    • Fiscal Host Dashboard
      • Expenses
      • Financial contributions
      • Pending applications
      • Hosted Collectives
      • Vendors
      • Transaction Report
        • Reports
    • Receiving Money
      • Bank Transfers
      • Credit Card
      • Add Funds Manually
      • Expected Funds
    • Payouts
      • Virtual Card Settings
      • Payouts with PayPal
      • Payouts with Wise
      • Two-factor authentication for payouts
      • Refunds
    • Host Fees
    • Local Tax Support
    • Agreement Templates
  • Independent Collectives
    • About Independent Collectives
    • Create an Independent Collective
      • Migrate from Self-Hosted to Independent Collective
      • Migrate from a Fiscal Host to Independent Collective
    • Independent Collective Setup
    • Independent Collective Management
      • Money coming in: Contributions
      • Money going out: Expenses
    • Close an Independent Collective
  • Contributing
    • Design
      • Design Workflow
      • Design Contribution Guidelines
    • Development
      • Contribution Guide
      • Best Practice Guidelines
      • Bounties
      • Architecture
      • API
        • Members
        • Collectives
        • Events
      • README Integration
      • PayPal
      • TransferWise
      • Post-Donation Redirect
      • Manual Reporting
      • GitHub Permissions
      • Internationalization (i18n) system
      • Testing with Cypress
      • Testing features
        • Conversations
      • Collective's locations
      • Virtual Cards
    • Documentation
      • Resources for documentarians
      • Style guide
      • Suggesting changes
    • Translation
  • Developers
    • OAuth
    • Personal Tokens
Powered by GitBook

Helpful Links

  • Website
  • Blog
  • Contact
  • Slack

Ⓒ Open Collective 2024

On this page
  • Expense Types
  • Expense Transactions
  • Unpaid Expenses
  • Perspectives of Unpaid Expenses

Was this helpful?

Edit on GitHub
Export as PDF
  1. Product
  2. Ledger

Expenses in the Ledger

PreviousAdded Funds in the LedgerNextLedger Changelog

Last updated 1 year ago

Was this helpful?

Expense Types

Expenses in the ledger are used to represent various kinds of financial activities. Therefore, in order to properly understand expense transactions you need to first look at the “Expense Type” field:

  1. Invoices are expenses submitted by an expense submitter paid against submitted invoices.

  2. Reimbursements are expenses submitted by an expense submitter that have already been paid by the expense submitter who is asking to be reimbursed against a receipt or another proof-of-payment.

  3. Virtual Card Charges are expenses created on the platform when expenses have been paid using virtual credit cards.

  4. Settlements are expenses generated by the platform based on and to account for debt transactions (PLATFORM_TIP_DEBT & HOST_FEE_SHARE_DEBT) that accumulate on the platform. These are typically paid from fiscal hosts to the platform.

  5. Grants are also represented as expenses by which funds are typically transferred within a fiscal host from a fund account to recipients collectives.

Expense Transactions

An expense transaction group will typically include:

  1. A pair of EXPENSE transactions.

  2. A pair of PAYMENT PROCESSOR FEE transactions.

Unpaid Expenses

Fiscal hosts are able to mark expenses as unpaid when they encounter a payment error (it is the responsibility of the fiscal host admin to verify that the funds paid are accounted for). When an expense is marked as unpaid a new transaction group is created in which:

  1. The expense is credited back to the paying collective and debited from the payee.

  2. Payment processor fees transactions are NOT reversed since they are typically not refunded by the payment processors. In such cases fiscal hosts cover the not-refunded payment processor fees and this is represented in the ledger with a pair of PAYMENT_PROCESSOR_COVER transactions.

A complete transaction set for an expense marked as unpaid can therefor look like:

As a result, the ledger footprint of an expense marked as unpaid includes:

  1. The expense payment transactions are one transaction group.

  2. The expense "unpaid" transactions are a second transaction group.

  3. Relationships between the transactions in the two transaction groups. Each transaction in the expense transaction group (except the payment processor fees) will have a Refund Transaction ID that points to the opposite transaction in the "unpaid" transaction group.

  4. The expense transactions will be marked as REFUNDED.

  5. The related "unpaid" transactions will be marked as REFUND.

It is possible to imagine these two transaction sets side by side:

Perspectives of Unpaid Expenses

From the perspective of the payee (the person or organization being paid) the expense was first credited and then debited from their account:

From the perspective of the paying collective an expense and payment processor fee were first debited from the collective and then, when the expense was marked as unpaid, the funds are credited back to the collective together with credit from the fiscal host to cover the payment processor fees:

From a fiscal host “Operational Funds” perspective an “Unpaid” expense leaves only a PAYMENT PROCESSOR COVER transaction debited from the fiscal host to the collective to cover the un-refunded payment processor fees:

From a fiscal host “Managed Funds” perspective, an “Unpaid” expense looks the same as it does from a collective perspective: