The new support for multiple billing entities in the Accounting API enhances security and access control for organisations managing invoices across different internal entities.
What does this feature include?
Invoice Endpoints Update: The external API Invoicing endpoints now include a new
billing_entitysection, providing more information about the specific entity linked to an invoice.
Multiple Integrations: You can now create multiple Accounting API integrations, each explicitly linked to a specific billing entity.
Filtering: You can filter invoices and tasks based on their connected billing entity.
Dedicated API Clients: You can create Accounting API clients within the Accounting API Integration settings page. These clients are essential for full functionality.
How does this impact my external integration's ability to manage invoices?
The primary impact is on access control for posting (completing/posting) invoices:
Restricted Posting: Your external integrator will now only be able to complete/post invoices that are connected to the specific billing entity associated with the credentials they are using.
Viewing Invoices: Users will still be able to see invoices not related to their billing entity (subject to existing viewing permissions) but will be prevented from posting them.
Credential Configuration is Key:
To be able to post invoices (set status to completed), integrators must configure their API credentials in the Accounting API Integration settings page and link them to the correct billing entity.
Credentials created in the general Organisation Settings page will not be allowed to set the status of an invoice to completed or list invoices still waiting to be synchronised.