Review Credit Bilty invoice payment synchronisation
Confirm that native invoice payment changes update the linked Credit Bilty payment state through the module hooks. The guide follows the Help Centre standard: exact route, prerequisites, ordered steps, verification and operational boundaries.
What you’ll accomplish
Confirm that native invoice payment changes update the linked Credit Bilty payment state through the module hooks. Bilty Management keeps drafts, issued records, public capability links, finance, integration events and audit evidence as connected but separately verifiable records.
How the workflow fits together
Use Credit, To Pay and Cash rules, native invoice automation and payment recording. Use the module's current status, permission checks, warnings and linked records to decide the next supported action. Where a downstream invoice, WhatsApp queue item, webhook, PDF, POD record or audit event applies, verify it separately.
Follow these steps
- Go to Bilty Management → Bilties → Open / native Invoice.
- Confirm the active tenant, intended Bilty record and your permission before entering or changing data.
- Complete the supported workflow: Confirm that native invoice payment changes update the linked Credit Bilty payment state through the module hooks.
- Review the displayed validation, dependent fields and any privacy, finance or integration warning before continuing.
- Save, submit or run the action once and wait for the module response.
- Reopen the relevant register or record and verify the final status, linked records and audit evidence.
Fields and decisions to review
Record, audit and evidence checks
Reopen the relevant Bilty record or register and confirm its identifier, current status, related parties, timestamps and connected evidence. Check the audit/compliance, payment, public-link, report, API, webhook or WhatsApp evidence that applies to this workflow rather than relying only on a success alert.
How to confirm it worked
Return to Bilty Management → Bilties → Open / native Invoice or the resulting register and verify that the stored state matches the intended action. For any downstream automation, confirm the downstream record or queue/log entry as a separate completion check.
Technical basis for this guidance
This guide was checked against controllers/Bilty_management.php; models/Bilty_management_model.php; views/admin/dashboard.php; views/admin/bilty_view.php; bilty_management.php. It documents only behaviour exposed or enforced by the supplied module; internal secrets, raw signature payloads and unsupported future workflow assumptions are intentionally excluded.
Controls, checks and common mistakes
- Do not reclassify Labour, TT or Other charges onto Credit or To Pay records.
- A native invoice and the Bilty are connected records; reconcile both when correcting genuine financial data.
- Do not use manual payment merely to hide a failed invoice/payment integration.