fakturownia-recurring-definition

Create and update recurring invoice definitions with configurable billing fields.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/sixers/fakturownia-cli --skill fakturownia-recurring-definition
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fakturownia-recurring-definition
Source: https://github.com/sixers/fakturownia-cli/tree/main/skills/fakturownia/recipes/recurring-definition
Command: npx skills add https://github.com/sixers/fakturownia-cli --skill fakturownia-recurring-definition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to define and manage recurring invoice rules, eliminating manual setup and ensuring consistent billing schedules.

Core Features & Use Cases

  • Create and update recurring definitions with fields like name, invoice_id, start_date, every, end_date, issue_working_day_only, send_email, and buyer_email.
  • Integrate with related skills such as fakturownia-recurrings and fakturownia-schema to maintain consistency across the billing domain.
  • Use cases include setting up monthly or quarterly invoices, changing the recurrence, and updating buyer contact details.

Quick Start

Create or update a recurring definition by supplying a JSON payload with the required fields.

Frequently Asked Questions about fakturownia-recurring-definition

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

FAQPage Schema
How do I automate recurring billing and set up scheduled invoices?

Automate recurring billing by defining recurring invoice definitions with fields like name, invoice_id, start_date, every, and end_date to establish consistent automated billing schedules without manual setup.

Can I update an existing recurring invoice definition to change the billing cycle?

Yes, you can update recurring invoice definitions to change the recurrence interval, modify the end_date, or update buyer contact details like buyer_email while maintaining the existing billing schedule.

What fields are required to create a recurring invoice definition?

Creating a recurring invoice definition requires supplying a JSON payload with fields including name, invoice_id, start_date, every, end_date, issue_working_day_only, send_email, and buyer_email.

Does this recurring invoice definition approach work without external dependencies?

Yes, defining recurring invoices requires no external dependencies beyond the core bundle, though it integrates with related skills like fakturownia-recurrings and fakturownia-schema for billing consistency.

Why are my recurring invoice definitions not sending emails to buyers automatically?

Recurring invoice definitions require the send_email field to be configured and a valid buyer_email supplied in the JSON payload to ensure automated billing emails reach the correct recipient.

Can I restrict recurring invoices to only issue on working days?

Yes, recurring invoice definitions support the issue_working_day_only field, which restricts automated invoice generation to working days only, preventing billing on weekends or holidays.