Automation, notifications, security and troubleshooting

Run recurring purchase-invoice creation

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Allow cron to create due recurring invoice instances.

Audience: Purchasing staffPermission: Administrator or relevant Purchase capabilityModule v1.7.9

Jump to steps

Where to goCRM Cron → Purchase recurring invoices

Before you start

Use an account with Administrator or relevant Purchase capability and confirm the intended record or setting before making a change.
Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.

What this guide helps you do

Allow cron to create due recurring invoice instances. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Follow these steps

Go to CRM Cron → Purchase recurring invoices.
Select the relevant record, filter, report, model or configuration described below.
Use the displayed action or read the current values without altering unrelated data.
Compare the output with the code-backed rules and expected result in this guide.
Record or correct any mismatch before relying on the output in production.

Fields and options

Invoice headerVendor, contract, purchase order, invoice number, date/due date, currency/rate and payment status.

Invoice linesItems, quantity, rate, tax, discount and totals.

SettlementPayments, batch payments, attachments, recurrence where exposed, expiry notification and linked debit applications.

Rules and limits

Purchase-invoice status changes require the dedicated invoice status capability.
Payment labels include Unpaid, Partially paid and Paid.

Check it worked

The supported run recurring purchase-invoice creation flow completes without bypassing permission or validation checks.
The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
Unexpected validation, provider or linked-record errors are investigated before retrying.

Security, privacy and operational checks

Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
Test settings and automated jobs with controlled records before production-wide use.

Was this guide useful?Your response is stored only in this browser.