Full invoice detail (get_payable_by_id)

# Full detail of an invoice (get_payable_by_id)

## Flow: get_payables → ID → get_payable_by_id

Do not search by invoice number directly — first resolve the ID via `get_payables`:

### Step 1 — Find the invoice ID

```json
{
  "companyId": "<companyId>",
  "filters": {
    "field": "documentaryEvidenceNumber",
    "operator": "=",
    "value": "INV-2026-001"
  },
  "pageSize": 5
}
```

Or via description:
```json
{ "field": "description", "operator": "contains", "value": "CBS Consultant" }
```

→ Extract the `id` from the returned payable (e.g. `5c902f76-c87e-59a6-8bb8-4e70fbd1dd39`)

### Step 2 — Enriched detail

```json
{
  "id": "5c902f76-c87e-59a6-8bb8-4e70fbd1dd39"
}
```

## What get_payable_by_id adds vs get_payables

| Information | get_payables | get_payable_by_id |
|-------------|--------------|-------------------|
| Supplier name | ❌ (only supplierId) | ✅ `counterparty.name` |
| Accounting account code | ❌ (only expenseAccountId) | ✅ `lineItems[].expenseAccount.code + description` |
| VAT account code | ❌ (only taxAccountId) | ✅ `lineItems[].vatAccount.code + description` |
| Analytics name | ❌ (only fieldEntityValueId) | ✅ `analyticalProperties[].valueName` |
| Cost center name | ❌ (in analyticalFieldAssociations) | ✅ `costCenterName` (at root) |
| Team name | ❌ | ✅ `teamName` |
| Amortization | ❌ | ✅ `amortisation` (null if absent) |
| Supplier AP code | ❌ | ✅ `counterparty.accountPayable.generalAccountCode` |

Example of an enriched response:
```json
{
  "counterparty": {
    "id": "76r950em3qde5o",
    "type": "supplier",
    "name": "Think Software",                          // ← resolved name
    "accountPayable": {
      "generalAccountCode": "Think Software",          // ← AP code
      "auxiliaryAccountCode": ""
    }
  },
  "lineItems": [{
    "expenseAccount": {
      "code": "622800",
      "description": "622800 - Other fees and intermediaries"  // ← resolved account
    },
    "vatAccount": { "code": "445660", "rate": 20 },   // ← resolved VAT
    "analyticalProperties": [{
      "fieldName": "Analytic codes",
      "valueName": "Banking investments"               // ← resolved analytics
    }],
    "costCenterName": "X-old Banking"                  // ← resolved cost center
  }],
  "teamName": "Banking"
}
```

## ⚠️ Different naming between get_payables and get_payable_by_id

Both endpoints use different field names for the same data:

| Concept | get_payables | get_payable_by_id |
|---------|--------------|-------------------|
| Accounting status | `state` | `bookkeepingStatus` |
| Detail lines | `itemLines[]` | `lineItems[]` |
| Spendesk entry date | `firstCreatedAt` | `createdAt` |
| ERP export date | `firstExportedAt` | `exportedAt` |
| User ID | `memberId` | `userId` |
| Due date | `dueDate` | `invoiceDueDate` |
| Document date | `creationDate` (datetime) | `payableDate` (date) |

→ If your code handles both types of response, adapt field names according to the endpoint called.

## What is ABSENT from get_payable_by_id

`get_payable_by_id` does not return:
- `spendingAmount` / `spendingCurrency` / `spendingExchangeRate` — for the original spending currency, use `get_payables`
- Full `documentaryEvidence` (validity, compliances) — `invoiceNumber` is at the root but the validation structure is not there
- `kind` field (`expense` vs `reversal`)

## When to use which?

| Need | Recommended tool |
|--------|-----------------|
| List + filter invoices | `get_payables` |
| Resolved names (supplier, accounts, analytics) | `get_payable_by_id` |
| Original spending currency (spendingAmount) | `get_payables` |
| Amortization / full GL codes | `get_payable_by_id` |

## Example prompts

- "Show me the full detail of the CBS Consultant invoice with the accounting codes"
- "What is the expense account code of the Docusign invoice?"
- "Show the analytics and cost center of invoice INV-2026-001"