> For the complete documentation index, see [llms.txt](https://docs.oscollective.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oscollective.org/for-hosted-member-projects/spending-money-and-getting-paid/expenses-marked-as-incomplete-or-otherwise-have-not-been-paid.md).

# Expenses marked as "Incomplete" or otherwise have not been paid

## Why Was My Expense Marked as "Incomplete"?

If your expense was marked as "incomplete", it means that we need more information before processing your payment.&#x20;

* This does not mean your payment was canceled; it was just paused until an issue or question is resolved.
* If there is action that the payee or project admin must take, OSC will leave a comment in the expense.&#x20;
* Sometimes, if no comment is left, it means our team is reviewing the payment for another reason, and no action may be required from you.

***

## My Payment Didn't Go Through.

It's the payee's responsibility to ensure their payment method is set up correctly and that all necessary sections are completed on Open Collective, but if something doesn't go through, we're here to help.

If the issue is tied to a specific expense, the quickest way to get support is by commenting directly on that expense. You can also email us at <hello@oscollective.org>. Please include the expense link.

Keep in mind: sometimes payment processors (like banks or PayPal) may take longer than expected to complete a transaction.

***

## What Happens if OSC Identifies a Payment Issue?

1. **Notification**
   1. OSC will notify the hosted project and/or payee by commenting on the expense and marking the expense as 'incomplete'.
2. **Required Action Within 30 Days.**
   1. The payee or project admin must edit and correct the issue.&#x20;
   2. The project admin must re-approve the expense after the changes are made.
      1. If no corrections are made within 30 days, OSC will close the expense request.
      2. If payment is still required, the payee should resubmit the expense.
3. **End-of-Year Check**
   1. At the end of the calendar year, OSC will make one final attempt to confirm whether the payment is still needed. If no response is received within 30 days, the expense will be closed.

### Why does OSC Close Unresolved Expenses?

By declining unresolved expense requests after 30 days, OSC prevents:

* Confusion in expense tracking for the project and OSC
* Inaccurate financial reporting and budget complications

OSC can[ pay out funds](https://docs.opencollective.com/help/expenses-and-getting-paid/expenses#by-what-method-can-i-get-paid) via PayPal and electronic bank transfer via Wise. Make sure to review the[ Expenses and Getting Paid](https://docs.opencollective.com/help/expenses-and-getting-paid/expenses) section of Open Collective’s documentation for a complete overview of the process.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.oscollective.org/for-hosted-member-projects/spending-money-and-getting-paid/expenses-marked-as-incomplete-or-otherwise-have-not-been-paid.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
