absuite-payments

Manage payment records and configurations via the Alliance Business Suite Payments Service REST API.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/FenixAlliance/ABS.Agents --skill absuite-payments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: absuite-payments
Source: https://github.com/FenixAlliance/ABS.Agents/tree/main/paperclip/skills/absuite-payments
Command: npx skills add https://github.com/FenixAlliance/ABS.Agents --skill absuite-payments

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually managing payment records, configurations, and lifecycle transitions in the Alliance Business Suite is time-consuming and error-prone when relying on ad-hoc requests or manual UI operations.

Core Features & Use Cases

  • Full Payment CRUD Operations: Create, read, update, patch, and delete payment records, plus manage supporting lookup configurations including payment methods, payment modes, and payment terms.
  • Atomic Lifecycle Transitions: Use JSON Patch RFC 6902 to safely update payment status (e.g., Initialized → Accepted) without resending full payment records.
  • End-to-End Workflow Support: Follow guided steps to set up payment configurations, create payments linked to invoices, and verify payment status changes.
  • Use Case: A finance team can use this skill to configure Net 30 payment terms, create received payments for cleared invoices, and update payment statuses as transactions process.

Quick Start

Use the absuite-payments skill to set up required payment configurations, create a new received payment linked to an existing invoice, and transition its status to Accepted once the payment is processed.

Frequently Asked Questions about absuite-payments

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage payment records and configurations via REST API?

Payment records and configurations are managed via tenant-scoped REST API CRUD operations for payments, payment methods, payment modes, and payment terms, requiring valid bearer token authentication and tenant ID scoping for all requests.

How do I update a payment status without resending the full payment record?

Payment status updates use JSON Patch RFC 6902 to apply atomic lifecycle transitions, such as moving a payment from Initialized to Accepted, without the need to resend the full payment record.

What do I need to authenticate API requests for payment lifecycle management?

Payment lifecycle management requires a valid bearer token and a tenant ID for scoping all API requests, ensuring operations are securely isolated to the correct tenant context.

Can I configure payment terms like Net 30 and link payments to existing invoices?

Configuring payment terms like Net 30 and creating received payments linked to existing invoices are supported through end-to-end workflow operations that allow finance teams to set up configurations and track payment processing.

What is the best way to transition a payment workflow status atomically?

The best way to transition a payment workflow status atomically is using JSON Patch RFC 6902 partial updates, which safely modify the payment lifecycle state without risking data overwrites from full record submissions.

Does the Alliance Business Suite Payments Service support tenant-scoped CRUD operations?

The Alliance Business Suite Payments Service supports tenant-scoped CRUD operations for full payment lifecycle management, covering records, methods, modes, and terms with secure authentication.