> For the complete documentation index, see [llms.txt](https://docs.neobanc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neobanc.com/api-reference/rent-reporting.md).

# Rent Reporting

Submit **past rent reporting** requests on behalf of your users. Neobanc reports up to 24 months of a user's past rent payments to the credit bureau, helping them build credit history from rent they've already paid.

## How it works

1. Collect the user's identity and lease details listed below (the same information Neobanc's consumer flow collects).
2. Call `POST /past-rent-reports`. The request is accepted immediately and queued for reporting — no payment step and no document upload is required from the user.
3. Neobanc processes the request and reports the rent history to the credit bureau in the next reporting cycle.

{% hint style="info" %}
Requests created through this endpoint are billed to your partner account per API call, per your partner agreement. The end user is never charged.
{% endhint %}

## Create a past rent report

Requires the `public_api:past_rent_report_create` permission.

If no Neobanc user exists with the provided email, one is created automatically — the same behavior as [creating payments](/api-reference/payments.md).

When more than one tenant is on the lease, set `numTenants` accordingly (e.g. `"3 tenants"`) and provide the full names of the other tenants in `additionalTenants`.

{% openapi src="<https://api.neobanc.com/openapi.json>" path="/past-rent-reports" method="post" %}
<https://api.neobanc.com/openapi.json>
{% endopenapi %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.neobanc.com/api-reference/rent-reporting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.