Payables by system entry date (firstCreatedAt)

# Payables filtered by system entry date (firstCreatedAt)

## Key distinction: payableDate vs firstCreatedAt

| Field | Meaning | When to use it |
|-------|---------------|------------------|
| `payableDate` (= `creationDate` in the response) | Document date (date written on the invoice) | Accounting period, month-end close |
| `firstCreatedAt` | Date the payable was entered into Spendesk | What was processed this week, processing SLA |

An April 2026 invoice can be **entered into Spendesk in July 2026** — `payableDate` = April, `firstCreatedAt` = July. These two filters return completely different sets.

## Query — Entries from the last week

```json
{
  "companyId": "<companyId>",
  "filters": {
    "field": "firstCreatedAt",
    "operator": "inLast",
    "value": { "timeUnit": "days", "amount": 7 }
  },
  "pageSize": 20
}
```

## Operators for date filters

**⚠️ Date operators are different from amount operators:**

| Goal | Date operator | ❌ Do not use |
|----------|---------------|-------------------|
| After a date | `after` | `>=` (invalid for dates) |
| Before a date | `before` | `<=` (invalid for dates) |
| Between two dates | `between` | — |
| Rolling window | `inLast` | — |
| Exact date | `=` | — |

## Available magic values (no hardcoded date)

Instead of an ISO date, these dynamic values are accepted:

| Value | Meaning |
|--------|--------------|
| `"today"` | Today |
| `"yesterday"` | Yesterday |
| `"thisMonth"` | Since the 1st of the current month |
| `"lastMonth"` | The previous month (from the 1st to the last day) |

Examples:
```json
// This month
{ "field": "firstCreatedAt", "operator": "after", "value": "thisMonth" }

// Last month
{ "field": "firstCreatedAt", "operator": "between", "value": { "from": "lastMonth", "to": "today" } }

// The last 30 days
{ "field": "firstCreatedAt", "operator": "inLast", "value": { "timeUnit": "days", "amount": 30 } }
```

## These operators apply to all date fields

The same operators (`before`/`after`/`between`/`inLast`) work for all date fields of `get_payables`:
- `payableDate` — document date
- `firstCreatedAt` — date of entry into Spendesk
- `firstExportedAt` — date of first ERP export
- `lastUpdatedAt` — date of last modification
- `dueDate` — due date
- `accountingDate` — accounting date (optional feature — see skill S18)

## Use case: monitoring the entry backlog

To measure the delay between the document date and entry into Spendesk:
1. Filter by `firstCreatedAt` (entries from the week)
2. Compare with `payableDate` (`creationDate` in the response)

Example observed on real data:
- "Contrat 1527322 - 2026-05" → payableDate=**2026-04-16**, firstCreatedAt=**2026-07-01** (2.5 months of delay)
- "Clare Holmes freelancer" → payableDate=**2026-04-30**, firstCreatedAt=**2026-07-01** (2 months of delay)

→ Large delays reveal a processing backlog or late entries.

## Example prompts

- "Which invoices were entered into Spendesk this week?"
- "How many invoices were processed last month by our accounting team?"
- "Show me the expenses entered into Spendesk since June 1st"
- "Are there any April invoices still being entered?"