Verwendung
- Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
- Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
- Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/payabli/integration-skills --skill payabli-billsVor dem Start
- Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
- Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.
Payabli bills (AP automation)
Capture vendor bills and pay them.
Load fundamentals first
If payabli-fundamentals is not already loaded, load it now, then continue.
On load
If payabli-integration.md exists at the repo root, read it; honor its ## SDK value.
Capture a bill
Create a bill with POST /Bill/single/{entry} — identify the vendor with a nested vendor object (vendor: { vendorNumber }) — a top-level vendorNumber is rejected. Plus amount, due date, and an optional bill image. A bill needs only a top-level netAmount; unlike invoices, line items aren't required — but if you do send billItems, their itemTotalAmount must sum to netAmount exactly (the API adds nothing on top), or the create fails with 400 ("Sum of BillItems does not match Bill TotalAmount"). Bulk-import with POST /Import/billsForm/{entry}. https://docs.payabli.com/guides/pay-out-developer-bills-manage.md
Set status: 1 (Active) on create so the bill is immediately payout-eligible. -99 is Cancelled — don't use it.
Bill OCR is a standalone capture path — Payabli's OCR engine extracts bill data (line items, amounts, vendor details) from a PDF or image. It is its own feature, not part of vendor enrichment. Extract via POST /Import/ocrDocumentForm/{typeResult} (multipart) or /Import/ocrDocumentJson/{typeResult} (base64), with typeResult set to bill. https://docs.payabli.com/guides/pay-ops-developer-ocr-use.md
When you create a bill from an OCR result, build the `POST /Bill/single` payload explicitly from the fields you actually need — billNumber, netAmount, dueDate (plus any other dates), the nested vendor: { vendorNumber }, and status: 1. Don't spread the raw OCR envelope (responseData.resultData, or the full response with attachments / totalAmount / discount / billItems) into the create call: the shapes don't line up, and you'll get 400 "field BillNumber empty" or 400 "The sum of netAmount and discount is more than the total from the original bill". Map the extracted values onto a clean bill instead, keeping the netAmount == sum(billItems) rule above.
List bills
List bills with GET /Query/bills/{entry}. Filter by vendorNumber(eq) or vendorId(eq) — `idVendor(eq)` is silently ignored and returns every bill, so never use it to scope to a vendor. Query basics (filter syntax, pagination) → payabli-reporting.
Pay the bill
Bills are paid through Pay Out — see payabli-send-payments. One payout can pay multiple bills for the same vendor. (A raw payout can skip bill creation with doNotCreateBills: true.)
Bills vs. invoices
A bill is money out (a vendor's invoice that you pay); an invoice is money in (you billing a customer — payabli-invoices). https://docs.payabli.com/guides/platform-bills-vs-invoices.md
Boundaries
- Payout mechanics, vendors, and vendor enrichment →
payabli-send-payments - Customer-facing invoices →
payabli-invoices