payabli/integration-skills

payabli-bills

Use when building accounts-payable automation on Payabli — capturing vendor bills (manual entry or OCR) and paying them through Pay Out.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/payabli/integration-skills --skill payabli-bills

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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
同じリポジトリから

関連する Skills

すべての Skills
payabli
コミュニティ

payabli-accept-payments

Use when writing code that accepts payments through Payabli: charging cards or ACH, integrating embedded payment components or a hosted payment page, handling Apple Pay or Google Pay, or processing voids and refunds. Boundaries — subscriptions: payabli-subscriptions; invoices and payment links: payabli-invoices; disputes and refund-failure recovery: payabli-disputes. Reads payabli-integration.md on load if present.

1時間の導入数
1
GitHub Stars
0
更新日
10月23日
payabli
コミュニティ

payabli-boarding

Use when onboarding merchants to Payabli through the API — creating the business, its people, paypoints, and bank accounts, opening a boarding application, validating and submitting it, answering underwriting requests, or tracking an application's status and enablement. Moving an existing integration off the legacy /Boarding/ endpoints lives in payabli-boarding-migration. Reads payabli-integration.md on load if present.

1時間の導入数
1
GitHub Stars
0
更新日
10月23日
payabli
コミュニティ

payabli-boarding-migration

Use when moving an existing integration off Payabli's legacy boarding endpoints (/Boarding/app, /Boarding/read, boarding links) to intelligent boarding — converting legacy application payloads to the new records, mapping fields, values, and statuses, or planning the cutover before the legacy sunset. Building boarding from scratch lives in payabli-boarding. Reads payabli-integration.md on load if present.

1時間の導入数
1
GitHub Stars
0
更新日
10月23日
payabli
コミュニティ

payabli-certification-prep

Use when a partner wants to rehearse the Payabli certification test scenarios in sandbox before their certification call — running the checks they can self-serve and confirming expected results. This is prep for the call, not self-certification (certification happens with a Payabli SE). Reads payabli-integration.md on load if present.

1時間の導入数
1
GitHub Stars
0
更新日
10月23日