Pull contractor invoices for AP

👥

Who this is for — AP teams processing contractor payments who want Remote's contractor invoices flowing into their own accounting / AP system instead of being read in the Remote UI.

What you'll do: pull contractor invoices for the period, code each one to the right contractor and account, and hand it to your AP workflow.

How contractor billing is different from EOR & payroll

Contractors are paid via invoices, not payroll — a genuinely different money flow, and that's the whole reason this is its own guide.

Think of a Remote contractor exactly like any vendor who bills you: the contractor submits an invoice, you (the customer) approve it, Remote facilitates the payment. Unlike your EOR/PEO costs — which arrive as Remote's own invoices on a billing cycle — a contractor invoice is the source of truth for what's owed. There's no estimate-vs-actual reconciliation; there's a bill, an approval, and a payment.

Two things to know:

• An invoice moves through a lifecycle — status values like issued → approved → paid_out tell your AP system whether it's payable yet (see the API Reference for the full set).
• Invoices can be one-off, scheduled, or recurring — pick up the scheduled/recurring ones if you want forward visibility into what's coming.

Before you begin

• A Remote API token (customer short-token, or partner OAuth with the company in scope).
• Your AP system's model for vendor + account coding — you'll map each contractor to a vendor.
• A read-only, scheduled pull; no writes.

The approach

1. List contractor invoices for the period (and scheduled/recurring ones for forward visibility).
2. Filter to the statuses you treat as payable.
3. Join each invoice to its contractor via the invoice's employment_id for vendor/cost coding.
4. Hand to AP — map to your account, route for approval, reconcile against the payment.

Key capabilities

Each invoice carries status, date/due_date, currency, an employment_id, an items[] breakdown (description + amount; deductions are negative), and source_amount/target_amount with fx_rate. Amounts are integer minor units — e.g. amount: 1337000 = 13,370.00. The API Reference has the full field, status, and filter list — let your AI assistant generate the calls and pagination.

Gotchas & limits

• Don't reach for payroll endpoints here. Contractor money doesn't flow through payroll runs or gross-to-net — the invoice is the source of truth.
• Mind the lifecycle. Decide which statuses you ingest and which count as "payable" so you never book an unapproved invoice.
• Currency: cross-border contractors invoice in different currencies — the invoice exposes source_amount/source_currency (what the contractor billed) and target_amount/target_currency (the payout) with fx_rate. Carry the original currency through rather than pre-converting.
• Read-only and periodic, like the EOR/PEO breakdown pull.

🤖 For AI agents

Point your assistant (or the Remote MCP server) at the API Reference with this plan:

List contractor invoices for the period → filter to the statuses the customer treats as payable (e.g. approved, paid_out) → join each to its contractor via employment_id → convert amounts from minor units → map to the AP system's vendor/account model. Carry original currency through (source_*); pick up contractor-invoice-schedules if forward visibility is needed.

Next steps

• Pull your EOR & PEO cost breakdown — the EOR/PEO side of the same finance pipeline.
• Pull GL & payroll reports (coming soon) — for Global Payroll customers booking journals.